WooCommerce for
B2B & Wholesale

The B2B Requirements a Standard WooCommerce Install Cannot Handle

Out of the box, WooCommerce is a retail store: one price per product, checkout with a payment method, open to any visitor. Most B2B and wholesale operations need a different set of behaviors:

• Prices that are hidden from guest visitors and only visible to approved trade accounts
• Different prices for different customer tiers (distributor vs. dealer vs. preferred reseller)
• Prices that change based on quantity purchased (buy 10 units vs. 100 units)
• A quote request process rather than immediate checkout for large or custom orders
• Payment on net terms (net 30, net 60) rather than at the time of order
• Sales tax exemption for resellers with valid exemption certificates
• Minimum order quantities to prevent small retail-style purchases through a wholesale channel
• Company accounts where multiple buyers under the same business can place orders

None of these require custom development. Each is handled by plugins that extend WooCommerce's core functionality.

User Roles: The Foundation of B2B WooCommerce

WooCommerce B2B configuration is built around user roles. WordPress has a built-in role system; WooCommerce adds a "Customer" role by default. B2B plugins extend this to create roles like "Wholesale Customer," "Dealer," "Distributor," or whatever tiering your business uses.

Everything else in a B2B WooCommerce setup — pricing, visibility, payment terms, minimum orders — is typically controlled at the role level. A visitor with no account sees retail prices (or no prices at all). A logged-in user with the "Dealer" role sees dealer pricing. A user with the "Distributor" role sees a deeper discount. The admin approves new account registrations before assigning a wholesale role, preventing anyone from self-assigning trade pricing.

This role-based approach is flexible and does not require custom code — it is configuration work within plugins that are built specifically for this purpose.

Tiered and Role-Based Pricing

Tiered pricing in WooCommerce B2B operates along two axes:

• Customer role: A product priced at $100 retail might be $70 for dealers and $55 for distributors. These are set as fixed prices or percentage discounts from retail, applied per user role.
• Order quantity: A dealer ordering 1–9 units pays $70 each; ordering 10–49 units pays $65 each; ordering 50+ units pays $60 each. These quantity breaks are configured per product or globally.

B2BKing (available at wordpress.org/plugins/b2bking-wholesale-for-woocommerce) is a widely used plugin on the official WordPress plugin repository that handles both dimensions, along with most other B2B requirements discussed in this guide. Wholesale Suite (also on the WordPress plugin repository as woocommerce-wholesale-prices) is another common option focused specifically on pricing. The right choice depends on the specific combination of features your store needs — both have free and paid tiers.

Quote Requests Instead of Add to Cart

For orders above a certain size, custom configurations, or products with variable specifications, many B2B sellers need a quote process rather than an instant checkout. The flow is: buyer adds items and quantities to a quote cart → submits the quote request → seller reviews and responds with a price → buyer approves and converts the quote to an order.

In WooCommerce, this is implemented by replacing the "Add to Cart" button with an "Add to Quote" button for specific products, categories, or user roles. The seller receives the quote request, generates a price within the plugin's interface or adjusts the cart, and sends the buyer a link to approve and checkout. The buyer pays after terms are agreed, not through a standard storefront checkout.

This workflow is handled in B2BKing's quote module and in dedicated quote plugins like YITH WooCommerce Request a Quote. The specifics of which plugin fits best depend on whether you need quoting as a standalone feature or as part of a broader B2B configuration.

Net Payment Terms

Net-30 and net-60 payment terms — where the buyer receives goods and pays later — are a standard expectation in B2B commerce. WooCommerce's default payment methods (credit card, PayPal) do not support this. Implementing net terms requires either a payment gateway that offers trade credit functionality, or a plugin that adds a purchase order payment method to checkout.

The WooCommerce Purchase Order Gateway extension adds a payment option at checkout that generates a purchase order number instead of processing payment. The buyer checks out, the order enters a "pending payment" state, and the seller invoices separately according to agreed terms. Access to net-terms payment can be restricted by user role — so retail customers cannot select it, but approved wholesale accounts can.

Third-party net terms platforms (Resolve, Behalf) also offer WooCommerce integrations and handle credit risk assessment and collections themselves — useful if you want to offer net terms without managing the credit risk in-house.

Tax Exemptions for Resellers

Resellers who purchase for resale rather than end use are often exempt from sales tax in their state. Managing these exemptions in WooCommerce involves two parts: collecting valid exemption certificates from buyers, and suppressing tax at checkout for accounts that have a valid certificate on file.

TaxJar (now part of Stripe) offers a WooCommerce integration that includes exemption certificate management. Avalara AvaTax offers similar functionality. Both connect to WooCommerce's tax system and handle the suppression automatically for accounts flagged as exempt. For businesses selling across multiple states, a dedicated tax platform handles the complexity of which states honor which certificate types — this is not something to manage manually in WooCommerce's settings once you are operating at scale.

Minimum Order Quantities and Order Value

Wholesale operations often need to prevent orders below a minimum quantity or order value — either per product (minimum 12 units of any item) or per cart (minimum $500 order value). WooCommerce does not enforce these out of the box.

B2BKing and most comprehensive B2B plugins include minimum quantity settings per product and minimum cart value settings per user role. These are configuration options within the plugin, not custom development work. When properly set, buyers attempting to checkout below the minimum see a notice and cannot proceed until they meet the threshold.

Hosting Considerations for B2B WooCommerce

A B2B WooCommerce store running role-based pricing and a quote system puts more computational load on the server than a standard retail store — every product page load and cart update involves logic to calculate the correct price for the current user's role and quantity. This is manageable, but it means shared hosting with aggressive CPU throttling is more likely to produce slowdowns under normal use than it would for a simple content site.

A WordPress host with server-level caching (FastCGI or similar), Redis object caching for session and user data, and resources not shared with hundreds of other sites on the same machine is meaningfully better for B2B WooCommerce than standard shared hosting. The performance difference between shared and managed hosting is more pronounced for WooCommerce stores than for informational sites.

What to Ask a WooCommerce Developer

• Have you built B2B WooCommerce stores specifically, not just retail stores? B2B configuration involves different plugin combinations and testing scenarios than retail — a developer without this experience will discover the complexity during your project rather than before it.
• Which plugins are you recommending for pricing, quotes, and net terms, and why? The right answer depends on your specific requirements — there is no universal best plugin, and a good developer will explain the tradeoffs rather than defaulting to one approach.
• How will buyer account registration and approval work? The approval workflow — how a new trade account applies, gets reviewed, and gets assigned the correct role — needs to be defined before development, not after.
• How does the quote workflow integrate with our existing order management? Quotes that are approved need to flow into whatever system you use to manage fulfillment. This integration should be scoped explicitly.
• What hosting are you recommending and why? A developer building a B2B WooCommerce store who recommends shared hosting without qualifications has not thought about performance carefully.