B2B Pricing on WooCommerce: Four Models and Their Limits
Wholesale is not D2C with a discount role. Price protection, net terms, MOQ and pack sizes, reverse charge, and why reordering matters more than anything else.
B2B and D2C are different businesses sharing a database. Most stores try to serve both with D2C logic plus a discount rule, and that works until the first wholesale customer asks for net terms, tiered pricing, or a quote.
This is what needs deciding, and where the platform will fight you.
The four models, from simplest to hardest
| Model | Implementation | Limits |
|---|---|---|
| Single wholesale role, % discount | Customer role plus a discount rule | One tier, one discount, no exceptions |
| Tiered by quantity | Pricing rules per product or category | Gets hard to maintain past ~50 products |
| Per-customer price lists | Customer-specific pricing, often a plugin or custom table | Real work, but matches how wholesale actually works |
| Quote-based | No prices shown, enquiry flow | No self-service; scales poorly |
Most exporters start at the top and discover they need the third row. Plan for it; the migration from row 1 to row 3 after 200 orders is considerably more painful than building for it.
Prices must be hidden from the wrong audience
If wholesale pricing exists on the site, retail customers can usually find it — through search results, cached pages, or a filter parameter. Two consequences: retail customers feel cheated, and competitors know your terms.
The configuration that works: wholesale prices are not rendered for logged-out users at all, the page does not cache personalised prices, and wholesale-restricted categories return 404 or a login prompt rather than a partial price. Caching is the failure point here — see the caching layer notes for why fragment caching exists.
Net terms, and why the platform resists
Wholesale customers expect 30-day net terms. WooCommerce is built around payment at checkout.
Three approaches, all with trade-offs:
- Invoice payment method — order placed, payment recorded later. Requires accounting discipline and a credit decision per customer
- Deposit plus balance — partial payment now, remainder on terms. Better cash flow, more complexity
- No terms, card only — simple, and loses customers who need terms
Whichever you choose, the credit decision is a business process, not a plugin setting. Stores that enable net terms for everyone discover the problem when invoices go unpaid.
MOQ and pack sizes
Wholesale buyers order in cases of 6, 12 or 24. D2C buyers order in ones.
Quantity rules need to apply by customer role and by product. Minimum order quantity, quantity step (must order in multiples of 12), and cart-level minimum value are three different rules, and stores often implement one and assume it covers the others.
Also worth deciding: what happens when a wholesale buyer adds 13 units of a case-of-12 product. Rounding up silently is better than rejecting, but either needs a decision and a message.
Tax and documentation
B2B cross-border means reverse charge: the invoice shows no VAT, and the buyer accounts for it. This requires a validated VAT number, checked at the time of order — a format check does not satisfy the requirement.
It also means your invoices need the buyer’s VAT number on them, and the wording stating reverse charge applies. A D2C invoice template will not have these fields.
The parts that surprise people
Shipping is calculated differently. Wholesale orders are pallets, not parcels. Per-unit shipping rules produce absurd totals on a 400-unit order. Pallet rates, freight quotes, or “shipping arranged separately” are all viable, but they need to be deliberate.
Catalogue visibility differs. Some lines are wholesale-only, some retail-only, some both at different prices. If the catalogue is shared, the navigation must differ by role, and search must respect it.
Reordering is the feature that matters most. A wholesale buyer’s workflow is “same as last time, plus two cases”. If the account area does not support reordering from history, every order becomes a support conversation. This is one of the few places where import of historical orders is genuinely justified — see the customer and order notes.
One customer, multiple delivery addresses. Buyers ship to stores, warehouses or projects. A single billing and shipping address pair is not enough.
A workable sequence
- Decide the pricing model and write down the exceptions you already know about
- Decide how prices are protected from retail view
- Decide net terms policy and who approves them
- Implement MOQ and pack size rules by role
- Handle reverse charge and invoice fields
- Build reordering before launch, not after
- Test with a real wholesale order of realistic size — 40 lines, not 2
Item 7 catches the shipping and rounding problems that small test orders hide.
The honest summary
WooCommerce can do B2B, but it does so through configuration and custom code rather than as a native mode. Stores that treat it as “D2C with a discount role” end up with a system where the sales team quotes manually and the site is a catalogue.
If wholesale is a serious channel, design it as one. That work is squarely in the WooCommerce development territory, and the most useful first deliverable is a written pricing model rather than a plugin list.