Customer Landing Page/Subdomain? How Can I Do This Best?

Shopify Discussion
1

Hi,

We’re in the process of thinking about how to handle repeat customers who always purchase the same items over and over and get tiered discounting as they build volume. We want them to be able to self-manage so we were thinking to set up a landing page for each customer with their products on it (tagged so they would only see what they want in their collection), displaying their current pricing and anything else peculiar to them. They would check out through out through our normal Shopify cart and the orders would flow automatically to our production partners for fulfillment.

Question though: what is the best way to do this? We will have multiple of these so is it a new page per account at www.abcstore.com/customer (locking it with password to restrict availability) or is it a subdomain per account customer.abcstore.com or ?? Is there an app that you would recommend to keep track of volume purchased by customer so that tiered pricing would be automatically available to them?

We’re open to suggestions, trying to avoid a ton a pay-for apps and keeping it simple as neither of us is a coder of any sort.

Thanks in advance for your help and suggestions!

Have a great day,

Jo-Lynn

KJ Partners

2

Hi @kjpartners

a subdomain can make sense if it’s premium , or b2b or for other businesses/organizations type accounts.

For individuals /customer pages are fine just put the data in metafields and display info cards on the customer page, or on the individual products pages for logged in customers.
There are several automation apps that can be scripted or confgured to track purchase data.

Some businesses elect to use /pages to have custom templates , common with wholesale signups or order forms.

Or giving customers their own literal collection /collections/username could make sense

There’s also building a proxy app and using the /a/ path to build custom url names /a/tiers .

Apps are there to make you money by saving development time especially if you aren’t a coder.

If these features you want do not generate enough value to justify the cost of ready made solutions reconsider if you actually need these bells and whistles.