WooCommerce B2B Wholesale Setup Guide
WHOLESALE OPERATING MODEL
Design the commercial rules before choosing the B2B extension
WooCommerce core manages products, customers and orders, but role pricing, approval, private catalogues and tier rules normally require an extension or custom integration. The operating model should choose the tool.
01 · APPROVE
Define the buyer lifecycle
Set registration evidence, approval status, roles, account ownership and the process for suspending or changing a trade customer.
02 · PRICE
Make terms deterministic
Document price basis, quantity breaks, tax display, minimums, payment terms and conflict priority before configuring rules.
03 · FULFIL
Connect orders to stock and credit
Prove availability, backorders, approval, dispatch and accounting with representative wholesale orders.
Pilot one customer role and one product family
A bounded pilot exposes price conflicts, tax treatment, minimum quantities and order handover before every buyer and SKU depends on the configuration.
A dependable WooCommerce B2B setup begins with customer, price and order rules. Core WooCommerce provides the catalogue and order foundation; capabilities such as buyer approval, role-based or customer-specific pricing, private products, quantity tiers and tax exemptions usually come from a selected extension or tailored build. Do not treat one extension’s feature list as the business specification.
Mitrend groups these decisions under ecommerce implementation. The same data should also connect to inventory and accounting, especially where trade credit, backorders or negotiated prices affect fulfilment.
1. Write the wholesale policy
| Rule area | Decision to document | Owner |
|---|---|---|
| Eligibility | Who can apply and what evidence is required? | Sales or credit control |
| Customer role | Which account type controls visibility, price and terms? | Commercial owner |
| Pricing | Fixed, percentage, tiered or customer-specific; which rule wins? | Commercial and finance |
| Tax | Gross or net display and exemption evidence | Finance with professional advice |
| Payment | Immediate gateway payment, EFT or approved terms | Finance or credit control |
| Fulfilment | Minimum quantity, case size, stock allocation and backorders | Operations |
2. Separate core capability from extension capability
Current WooCommerce Marketplace B2B extensions describe features such as custom roles, approval, price visibility, tiered pricing and tax treatment. Those are extension capabilities, not promises from WooCommerce core. Compare supported versions, data storage, import/export, API behaviour, renewal cost and the recovery path if the extension is removed.
3. Design registration and approval
- Collect only the information needed to assess and service the trade account.
- Keep applicants in a pending state that cannot see protected pricing until approval.
- Record who approved the account and which role or terms were assigned.
- Give rejected, suspended and changed accounts explicit customer communication and internal reasons.
- Test how account changes affect open carts, saved prices and existing orders.
4. Resolve pricing conflicts before configuration
A buyer may qualify for a role discount, category rule, quantity tier, sale price and coupon simultaneously. Write a conflict table that states which rule has priority and whether discounts can stack. Then test the boundary quantities immediately below, at and above every tier.
| Test order | Expected proof |
|---|---|
| Approved buyer, standard item | Correct trade price and tax display |
| Guest buyer | Protected price or product behaviour matches policy |
| Tier boundary | Quantity break applies once and at the documented threshold |
| Mixed cart | Wholesale and excluded products follow the conflict rule |
| Credit account | Order status and fulfilment wait for the intended approval |
| Refund | Credit note, stock and account balance remain explainable |
5. Connect stock and finance
Wholesale orders can be larger than consumer orders and may use cases, packs or minimum quantities. Confirm the selling unit maps to the inventory unit, decide whether stock is reserved before payment approval, and preserve the customer-specific price on the order even if the rule changes later.
6. Launch with one controlled cohort
- One buyer role with named test accounts
- A representative product family including excluded and tier-priced items
- Immediate payment and one approved manual term
- A normal order, backorder, cancellation and partial refund
- Price, tax, stock and accounting evidence retained for every test
Selection warning
Do not install several overlapping pricing or role extensions to cover gaps. Multiple rule engines can make the displayed price difficult to explain. Choose one primary owner for each decision and document any custom code or integration dependency.
Worked wholesale pilot
A distributor sells cleaning products by each to consumers and by case to approved trade customers. The pilot creates one Wholesale role, five products and a controlled case-size rule. An approved buyer sees the trade price and minimum case quantity; a guest sees the consumer offer; an excluded product never receives the role discount. Finance approves the tax display and immediate-payment method before any credit terms are introduced.
Place orders immediately below, at and above the first quantity break. Cancel one order, partially refund another and change the customer’s role with an open cart. Reconcile the resulting price, tax, stock unit and order history. If the extension cannot export the applied pricing rule or explain which rule won, that limitation belongs in the acceptance decision before the full customer base is migrated.
After approval, monitor manual price overrides, orders below minimum, credit holds and stock substitutions. Each exception should identify whether the commercial rule, extension configuration or staff process needs correction. This prevents the B2B store from becoming a polished front end for an uncontrolled spreadsheet workflow. Review price-rule ownership whenever sales introduces a new contract, promotion, territory or customer tier.
Document every negotiated pricing exception before release.
Sources checked
- WooCommerce: B2B Pricing documentation
- WooCommerce: Wholesale for WooCommerce documentation
- WooCommerce: Roles and Rules B2B documentation
Reviewed by
Mitrend Digital editorial team
2026-07-16
Evidence used for this page
Reviewed against current WooCommerce B2B Pricing and Wholesale extension documentation. Core-versus-extension boundaries are identified explicitly.
Turn the guide into a practical next step
This resource provides general implementation guidance. Verify platform settings, tax, legal, payment and operational requirements against the current business context before making a live change.