Shopify B2B & the wholesale channel
A wholesale password page is a single shared password that hides a trade area from the public. It takes about ten minutes to set up, it costs nothing, and it is the right answer for a brand with a handful of stockists who just needs trade prices off the public internet.
It is also the gate that leaks. One buyer forwards the email to a friend who runs a market stall, and a month later somebody you have never approved is asking why their order was not shipped at trade prices. Knowing when that risk is acceptable is the whole decision.
What a password page actually does
There are two different things people mean, and they behave differently.
The storefront password locks the entire store. Nobody sees anything without the password, which is what a brand uses before launch. It is not a wholesale tool, because it hides the consumer store that pays your bills.
The page-level gate is what this is really about: one page, or a set of pages, that asks for a password while the rest of the site stays public. Depending on your platform and theme this comes built in, or it comes from a small app, or it comes from putting the line sheet behind a link that is not published anywhere.
The third version deserves more credit than it gets. An unlisted page with an unguessable address, sent only to approved accounts and kept out of your sitemap, is not much weaker than a shared password and is simpler to run.
What it protects, and how well
A shared password protects against two things: a consumer stumbling on trade prices while browsing, and a competitor casually reading your line sheet.
It does not protect against a buyer forwarding the password, which is the most likely leak and the one that matters. It does not tell you who looked, or when, or what they were interested in. It cannot show different prices to different accounts. And it cannot be revoked for one person without changing it for everybody.
So the honest framing is that a password page is a curtain rather than a lock. For most small brands a curtain is enough, because the realistic harm from a leaked trade price list is a slightly awkward conversation, not a lost business.
The exception is if you have stockists who care. A shop that has given you shelf space is entitled to believe consumers are not buying at their cost. If your trade prices leak widely enough that consumers start asking, the damage is to that relationship rather than to a hypothetical margin.
When a password page is the right choice
Three conditions, and if all three hold, stop reading and go set one up.
You have fewer than about ten accounts. Every account pays the same price. And you build orders yourself anyway, by invoice or draft order, so the gated page is only carrying a line sheet rather than a working cart.
In that situation a password page costs nothing, needs no app, breaks nothing on the consumer store and can be dismantled in a minute. Anything more elaborate is configuration you are doing instead of finding stockists. The manual order workflow that pairs with it is in draft orders for wholesale.
Rotate the password once a year and after any account closes. Put the date on the line sheet so you know which version is circulating.
When to use something stronger
Move to per-account access when any of these becomes true.
Accounts pay different prices. The moment a chain gets a better price than an independent, a shared password is actively dangerous, because everyone behind it can see everything.
Buyers order on their own. Self-serve needs an account, because the system has to know who is ordering to price it.
You have accounts you might need to remove. A shop that stops stocking you keeps the password forever unless you change it for everyone.
You want to know who is looking. Account-level access tells you a buyer viewed the new season sheet twice last week, which is a useful prompt for a follow-up email.
The account-level alternative, and the application flow behind it, is covered in the trade login, and the assortment control it unlocks in B2B catalogs.
The mistake: gating the wrong thing
The most common error is hiding the existence of the wholesale channel rather than hiding the prices.
Brands put everything behind the password, including the page that says they sell to shops. The result is a site that gives a buyer no way to discover that stocking you is possible. Shop owners do look. A buyer who liked a product at a market, or saw it on a customer's shelf, will type your name and look for the word wholesale.
So split it. One public page, indexed and linked from your footer and your main navigation, saying that you sell wholesale, listing the categories of shop you work with, the case packs, the minimum order, the lead time and a short application form. No prices. Then the gated page with the line sheet, the actual numbers and the ordering instructions.
That arrangement costs the same and produces applications, which the fully hidden version never does.
Search, links and the practical details
A gated page should not be in your sitemap and should not be linked from your public navigation, because a page that requires a password and appears in search results is a poor experience and tells you nothing.
Two details save trouble later. Make sure the gated page does not break your store's search or collection pages, which can happen when a theme-level password is applied clumsily. And check the page on a phone, because a large share of buyers will open your line sheet on one, and a password prompt that renders badly on mobile loses orders silently.
Keep the file itself current. A password page protecting a line sheet from two seasons ago is worse than no page at all, because the prices in it are the ones a buyer will quote back to you.
What the gate cannot do
None of this creates demand. A gated trade page with two accounts behind it is a sign that effort is going into the wrong half of the channel.
The half that matters is the list of shops: who stocks your category, in which towns, at what price point, and who to contact there. That work is slow, it does not look like progress, and it is the only thing that turns a password page into a channel. The setups it eventually justifies are compared in wholesale without the upgrade.
If you do not yet have that list, paste a product link into WholesalePilot and look at the preview of retailers and distributors that stock comparable products. Ten minutes there is worth more than ten minutes spent choosing a password.
Questions brands ask about wholesale password pages
Does a password page hurt search visibility for the rest of the site? No, as long as only that page is gated and the storefront password is off. Keep one public wholesale page for buyers to find.
How often should the password change? Once a year, and whenever an account you no longer work with had it. Send the new one with a fresh line sheet so the change reads as an update rather than a lockout.
Is an unlisted page as good as a password? Close enough for most small brands, and easier for buyers. Keep it out of your sitemap and do not link to it publicly.
Can you gate a collection rather than a page? On some platforms and themes, yes. Gating the prices is what matters; gating the photographs usually is not.
What should the public wholesale page say? Who you sell to, the case packs, the minimum order, the lead time, where you ship, and a short application form. Everything a buyer needs to decide whether to apply, and no prices.