B2B Pricing Tiers in Ecommerce Setup
PRICING RULE DECISION
Define the commercial rule before configuring the discount
A pricing tier is dependable only when the business can explain who qualifies, which unit is priced, which rule wins and how tax, returns and manual orders are handled. The plugin should implement that rule, not invent it.
01 – ELIGIBILITY
Identify the entitled buyer
Use an approved customer, role, contract or territory rule rather than relying on a coupon that can be shared.
02 – PRICE BASIS
Name the priced unit
State whether the tier applies per item, pack, case, category subtotal or complete order and whether tax is included.
03 – PRIORITY
Resolve competing rules
Document what happens when a sale, contract price, coupon and quantity break could all apply to the same line.
Pilot one customer group and five representative products
Test below, at and above every quantity threshold with guest, approved and misclassified accounts before opening the rules to the full catalogue.
The practical answer is to treat B2B pricing as a governed commercial system, not a set of storefront discounts. A sound tier says exactly which customer is eligible, which products and quantities are covered, whether prices include tax, when the rule starts and ends, and what takes priority when another promotion or contract applies.
This guide is the pricing-design companion to the WooCommerce B2B wholesale setup guide. Use the WooCommerce development service when customer approval, order terms or integration behaviour must be designed with the pricing rule.
1. Separate customer tiers from quantity tiers
A customer tier describes entitlement: trade, distributor, reseller, key account or another approved group. A quantity tier describes a line or order condition: for example, a better unit price after a case quantity is reached. They can work together, but they answer different questions. Mixing them into one vague ‘wholesale price’ makes disputes difficult to resolve.
| Rule type | Question it answers | Evidence required |
|---|---|---|
| Role price | What does this approved customer group pay? | Account approval and role assignment |
| Contract price | What was negotiated for this buyer or agreement? | Customer, product, effective dates and approver |
| Quantity tier | What changes at a defined purchase quantity? | Unit, threshold, price calculation and exclusions |
| Promotion | What temporary offer applies? | Campaign dates, audience, stacking rule and margin approval |
2. Choose the pricing basis
Define the base before applying a percentage or fixed amount. A discount calculated from the regular retail price behaves differently from a fixed contract price. A case price can be wrong when the store sells the same SKU by each, inner pack and outer case without an explicit unit conversion. Write the pricing formula in plain language and show one expected calculation.
- Name the selling unit and the stock unit, including every pack conversion.
- State whether a threshold uses one product line, a category total or the whole cart.
- Decide whether the lower tier applies to all units or only the units above the break.
- Record excluded products, sale items, bundles and non-stock services.
- Agree rounding, currency and tax-display treatment with finance.
3. Build a rule-priority table
WooCommerce B2B extensions can target products, categories, roles or customers and may expose priority settings. The business still needs an explicit hierarchy. If a contract customer buys a sale item in a qualifying quantity and enters a coupon, the expected price must be known before the cart calculates it.
| Collision | Recommended decision record |
|---|---|
| Contract price plus quantity tier | Allow, replace or choose the lower result; never leave it implicit |
| Role price plus public sale | State whether the public sale is visible and whether it overrides the role |
| Tier price plus coupon | Define eligible coupons and whether stacking is permitted |
| Manual admin order | Confirm how staff select the customer and recalculate the same rule |
| Role change with open cart | Recalculate or invalidate the cart and explain the customer message |
4. Configure eligibility and approval
Create the smallest number of roles that the commercial policy truly needs. Every role should have an owner, approval criteria and a removal process. Protect private prices from guests when that is the business rule, but do not assume login alone proves entitlement. Test pending, rejected and expired accounts as well as approved ones.
5. Test the complete order, not only the product page
- View the same product as a guest, retail customer, approved B2B buyer and incorrectly assigned buyer.
- Add quantities immediately below, exactly at and above each threshold.
- Test variations, excluded products, sale items, coupons and mixed carts.
- Confirm line price, subtotal, shipping, tax, invoice, order email, refund and export values.
- Create an admin order for the customer and verify staff can reproduce the storefront price.
- Cancel and partially refund the order, then confirm the audit trail still explains the applied rule.
Worked pricing example
A distributor sells cleaning liquid by one-litre bottle and by a twelve-bottle case. Retail customers buy bottles at the public price. Approved trade customers receive a fixed case price from twelve bottles, while one to eleven bottles remain at the trade each price. A key account has a negotiated fixed price that replaces both public and trade quantity prices. Coupons never stack with contract prices, and all customer-facing amounts use the agreed tax display.
Build five test products: a normal bottle, a variable product, an excluded item, a sale item and a bundle. Place orders for eleven, twelve and thirteen bottles under each role. Compare the product page, cart, checkout, order, invoice and refund. The pilot passes only when finance, sales and fulfilment can reproduce every result without inspecting plugin code.
Operating controls after launch
Keep a register of active rules with owner, affected customers, products, start date, review date and priority. Review manual overrides, orders below minimum, unexpected coupon use and customer-role changes. When a new contract or promotion is introduced, add its collision cases to the regression test before publishing it. This keeps pricing explainable as the catalogue grows.
Sources checked
Reviewed by
Mitrend Digital editorial team
2026-07-17
Evidence used for this page
Reviewed against current WooCommerce B2B pricing and role-rule documentation. Includes an original pricing-governance model, conflict matrix and release test.
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.