Members-only is a business model with a marketing problem built into it. The thing that makes it work, that not everyone can buy, is the same thing that makes it hard to grow, because the obvious implementations also stop anyone new from arriving.
This is how to have both.
The contradiction, stated plainly
You want two things that pull in opposite directions.
Exclusivity. Membership has to mean something. If anyone can check out, it is not a members' store, it is a shop with a newsletter.
Discovery. Members have to come from somewhere. Every members' club that lasts is recruiting, and the ones that stop recruiting close.
Most tooling forces you to choose. A password page gives you exclusivity and zero discovery. An open store gives you discovery and no exclusivity. The interesting design is neither.
Where to put the wall
The instinct is to put the wall at the front door: nobody sees anything without logging in. It is the wrong place, and it is worth being precise about why.
Search engines are anonymous visitors. Every one of them. Googlebot does not have an account and never will. Whatever you show to a stranger is the entirety of what search knows about your store, so a store that shows a stranger nothing is a store search knows nothing about.
Move the wall to the till and the arithmetic inverts:
- Products, collections, descriptions and photography are all public, all indexed, all shareable, all accumulating authority.
- Prices and buy buttons are hidden for anyone without access.
- A stranger can look at everything, want it, and discover they cannot have it.
- That discovery is a moment you can do something with.
The wall is doing the same job. It is just not standing between you and every person who has not heard of you yet.
The moment that matters
Everything about a members-only store turns on what happens when someone wants in and cannot get in.
If the answer is "nothing", with the buy button missing and the page saying nothing about why, you have built a dead end, and the visitor leaves without either of you learning anything.
If the answer is a request, the same visitor becomes a name, an email address, and a record of which product they wanted. That is the difference between a store that is exclusive and a store that is merely closed.
The specific things worth having at that moment:
- A form where the buy button was, not a link to a contact page. Every step between wanting and asking costs you people.
- The product they were looking at, captured automatically. What people ask for is your demand data, and it is better than a survey because nobody was being polite.
- A confirmation email that says what happens next, so the wait feels like a process instead of silence.
- Somewhere for the ones you are not letting in yet. A waitlist with a position is a better answer than a no.
Keeping it exclusive while it is public
Two things people worry about here, both fair.
"If everyone can see it, is it still exclusive?" Yes, arguably more so. Exclusivity that nobody can observe is just obscurity. A visible door that most people cannot open is the entire aesthetic of a members' club; an unmarked building is not exclusive, it is closed.
"Can't people just see the price elsewhere?" Sometimes, yes. If the product is also on a marketplace or a stockist, the price is public and hiding it on your own store is theatre. Gating is worth most when the product is genuinely yours to control, and worth least on a widely stocked item.
The part that is not optional
If access is meant to mean something, the enforcement has to be on a server.
Hiding a buy button in the browser stops nobody who cares. Developer tools bring it back in about four seconds. What has to be true is that a checkout by someone without access fails, and that decision has to be made somewhere the visitor cannot reach.
Ask this of anything you install, including Inner Circle. "Does it hide the button, or does it stop the order?" The second one is the product.
Our own answer, since we are on that list. It stops the order for locks that name their products and locks that cover the whole store: a cart built by hand is refused rather than paid for. For locks pointed at a collection, or at conditions like a tag or a vendor, it still only hides the button. And if our check cannot run, the order goes through — we would rather lose a locked sale than hold up a paying customer. Make every vendor answer in that shape, ours included, because "yes" on its own is not an answer.
How to actually build one
In order, because the order matters more than the tooling.
1. Decide what membership means. Not what it is called, but what it entitles. Early access to everything, permanent access to a private range, and trade pricing on a retail catalogue are three different products, and the third one needs a pricing tool rather than a door.
2. Decide what is behind the wall, and what is in front of it. The default should be that everything is in front of it and only price and buy button sit behind. Every product you hide entirely is a page that can never rank, never be shared, and never recruit anybody. Hide a whole collection only when the existence of the product is itself the secret.
3. Build the door. Three routes, in ascending order of effort and control:
- Customer accounts and tags. Free, native, and enough if your members are people you already know and can tag by hand. You edit the theme to show or hide by tag. It stops being fun somewhere around the third template.
- A theme edit alone. Free, and appropriate when the rule is simple and permanent: logged in sees prices, logged out does not.
- A gating app. Worth it once you need people to request access, need more than one level of membership, or need the rule to hold without you editing Liquid every time it changes.
The full trade-offs are in how to hide prices on Shopify; the short version is that the first two are free and manual, and the third is neither.
4. Let the existing members in without making them apply. This is the step people skip. Your current members should never fill in a form to get into the club they are already in. Hand them a code, or tag their accounts, before you turn anything on.
5. Put something where the buy button was. A request form, and a waitlist behind it for the people you are not admitting yet. Covered above, and it is the step that turns the wall from a cost into an asset.
6. Check the flash and the enforcement before you announce it. Load a gated product on a throttled connection with the cache cleared, and try to buy one without access. If the price appears for half a second, or the order goes through, you have a decoration rather than a door.
What this looks like assembled
A working members-only store on this pattern has:
- A public, indexed storefront that a stranger can browse and share.
- Locks on the products or collections that are members-only, hiding price and buy button before the page paints, not a script that tidies up after it.
- A request form in place of the buy button, capturing what they wanted.
- Access codes for the people you already know, so existing members do not have to apply to their own club.
- Access decided on the server, so nobody edits their way into a tier.
- A waitlist for the overflow.
Six things, of which the storefront being public is the one that does the recruiting and the one most implementations throw away first.
If you want to see the shape of it before deciding, the walkthrough shows both sides: building the lock, and hitting it as a shopper.