WooCommerce Wholesale Store: Define the B2B Buying Rules
A WooCommerce wholesale store needs clear buyer access, pricing and order rules. Define the trade journey first, then choose a B2B extension that supports it alongside any retail storefront.
Read the guide
Search Field Notes
A useful next read.
36 field notes
No matching guide yet. Try “checkout”, “shipping” or “catalog”.
All Field NotesSeparate the buyer groups
List guests, retail customers, trade applicants and approved wholesale buyers. For each group, decide what they can see and buy. A hybrid store might keep the retail catalog public while showing case quantities and trade prices to approved accounts.
Include staff tasks: reviewing applications, changing approval and handling orders that need attention. These rules should be clear before comparing plugins. Tax and contractual policies belong to the business and its advisers; the website implements the agreed result.
Define registration and account approval
Decide what information a trade applicant must provide, who reviews it and what happens before approval. Include rejected, suspended and changed accounts. Collect only the details staff actually need for that decision.
Grant reviewers appropriate access rather than handing every applicant reviewer broad store administration. Test the account transition and the customer-facing messages. A submitted form should not silently become an approved buyer unless that is the intended policy.
Specify catalog visibility and price logic
Write down which products and prices each buyer group sees. Include retail/trade overlap, sale pricing, coupon combinations and account-specific exceptions. Wholesale features come from the chosen extension or custom implementation; compare those capabilities against your actual rules.
Test direct product links, search and any catalog/feed surfaces as well as menus. Hiding a trade category link does not protect its contents. A non-approved visitor should receive the intended access response without restricted prices or private data leaking through another route.
Make quantities and ordering units unambiguous
Define minimum order quantities, case multiples, pack sizes and any product-specific limits. State whether the buyer orders individual units or cases and how stock and fulfilment interpret that quantity. A label reading Case of 12 is not a substitute for an enforced ordering rule.
Test a valid case order and an invalid partial case, including variations where relevant. Check mixed retail/trade carts if they are allowed. The final order and warehouse mapping need the same meaning, otherwise the buyer can pay for one unit interpretation while staff fulfil another.
Check a complete wholesale order
Buyer access, prices and trade rules must still work through checkout.
| Check | What to check | Next step |
|---|---|---|
| Buyer access | Guest, applicant and approved buyers see the intended information. | Test direct links and search as well as menus. |
| Case quantities | Valid pack orders pass and invalid partial cases are rejected. | Check the ordering unit and variation data. |
| Staff order | Prices, payment terms and item quantities have clear fulfilment meaning. | Follow the accepted order to the warehouse. |
Map payment and delivery exceptions
For each buyer group, specify payment methods, delivery choices, purchase references and any order review step. Payment terms or quote requests create staff responsibilities; decide who approves and when fulfilment can start.
Check the selected B2B extension and connected providers for these requirements. Follow an accepted order into staff and warehouse workflows. Also test what happens when buyer approval changes while an account or cart is in use, so stale access does not bypass the current rule.
Compare tools with a buyer-state test set
Use the same guest, retail, applicant and approved-account cases for every proposed solution. Check visibility, prices, quantities, checkout and the resulting order. A generic feature list cannot reveal whether an extension handles your particular combination.
Keep unsupported requirements and custom maintenance work visible in the estimate. Before release, verify backup, permissions and account-data protection. The trade journey is ready when eligible buyers can order correctly and other visitors remain within their intended access boundaries.
Common questions
Does WooCommerce core include wholesale pricing and buyer approval?
These workflows generally need a suitable extension or custom implementation. Define the requirements and check the specific solution rather than assuming every B2B tool covers them.
Can retail and wholesale buyers share one WooCommerce store?
They can when visibility, price, quantity and checkout rules are designed and tested for each group. Mixed carts and account changes need explicit handling.
Is hiding wholesale links enough to keep prices private?
No. Verify direct links, search and other relevant catalog surfaces, with real access enforcement rather than menu styling alone.
What should we test before launching B2B?
Applicant approval, guest/retail/trade access, pricing, valid and invalid quantities, required payment/delivery paths and the order staff will fulfil.