How Many Wholesale Price Tiers Do You Actually Need?

Almost nobody designs their wholesale pricing. It accumulates. You start with one trade rate, a big customer asks for better, you say yes, and eighteen months later you have eleven price levels, four of which exist because of a conversation nobody wrote down.

The question worth answering early is not "what discount should I give?" but how many distinct price levels should exist at all. That number drives how much of your pricing your storefront can enforce, and how much lives in a spreadsheet and someone's memory.

Start with three

Three tiers covers most wholesale programmes, and it maps onto distinctions buyers already understand:

Trade / Retailer — your standard wholesale rate. Most accounts sit here, and that is fine.
Distributor — deeper pricing for buyers moving real volume or holding stock.
Key account — your best terms, deliberately scarce.

Three is also the ceiling on Shopify's native B2B on the Basic, Grow and Advanced plans, which state you can assign "up to 3 active catalogs across all your B2B markets". That is not a coincidence so much as a convergence: three levels is genuinely enough structure for a lot of businesses.

The real question: is this a tier or an exception?

Every new pricing request is one of two things, and confusing them is what produces an unmanageable price list.

A tier describes a class of customer. If you'd offer the same terms to the next buyer who looked like this one, it's a tier. Tiers are worth creating because they scale — the fourth and fortieth distributor both slot in.

An exception describes one customer. A retailer who negotiated 3% off your trade rate on two product lines is not a new class of buyer. Creating a tier for them means you now maintain a pricing level that will only ever have one member, and you'll do it again for the next one.

The test: if this customer left tomorrow, would the tier still make sense? If not, it isn't a tier.

Why the distinction has teeth

Tiers are cheap. Exceptions are expensive, and the cost shows up somewhere specific: exceptions are what your storefront usually can't express, so they leak into manual draft orders, emailed price sheets, or a spreadsheet the sales rep keeps.

That spreadsheet is the real symptom. It is not a process problem — it is a count of the prices your system can't hold. Every entry is an order somebody has to remember to adjust, and eventually one of them ships at the wrong price.

So the practical version of "how many tiers do I need?" is: how many distinct answers do I give to "what does this buyer pay?" — including the ones currently living outside your store.

A rule that holds up

Add a tier when the second customer asks for the same thing. One request is an exception; two is a pattern, and a pattern deserves a name, a rate, and somewhere in the system to live.

Until then, resist. A tier created for one account is an exception wearing a tier's clothing, and it will still be there — unexplained — long after that account has churned.

What to do with the exceptions you already have

Count them. Not the tiers on your rate card — the actual agreed prices. The number is usually higher than people expect.
Group them. Exceptions often cluster; three accounts with "roughly distributor plus a bit" are one tier nobody has named yet.
Give the genuine one-offs somewhere to live. Per-product or per-variant overrides on top of a tier default handle "distributor rate, except these two lines" without spending a whole pricing level on one account.

That last point is where a dedicated pricing layer earns its place. Tiers handle classes of customer; overrides handle the exceptions within them. With both, the answer to "what does this buyer pay?" stays inside the system — which is the only version of the answer that survives a busy week.

The short version

Start with three tiers. Add a fourth only when a second customer asks for the same terms. Treat one-off pricing as an override on a tier, not as a new tier. And treat any pricing spreadsheet as a bug report about your storefront, not as a filing system.

Source for the Shopify plan limit: Shopify Help Center — B2B features by plan.