Explore Magic WP

What are you looking for?

Search services, articles, projects and more.

Popular searches
Website platforms
Searches every page and article↑ ↓ Browse Enter Open Esc Close
WooCommerce

WooCommerce B2B Development: Custom Pricing, Roles and Private Catalogs

Plan a WooCommerce wholesale store around account approval, customer groups, pricing rules and catalog access, with a practical B2B workflow example.

Approved wholesale buyers connected to price tiers and a locked product catalog.

At a glance

  • Separate customer approval, catalog visibility and pricing into explicit rules.
  • Account-specific data must remain correct across caches, cart and checkout.
  • Test the entire wholesale order workflow, including account changes and integration failures.

A WooCommerce B2B store needs to reflect how the business sells to approved companies. Wholesale access, contract prices, product restrictions and order handling should work as one process. Start with the commercial rules, then decide which parts a supported extension can handle and which need development.

Map the customer lifecycle

Define what happens from registration to the first order. Does a company need approval? Can several employees order for the same account? Who can change the company details? What happens when a contract expires?

Treat a pending applicant differently from an approved buyer. A registration form should not let someone grant themselves a privileged role. Build a clear review process and a way to revoke access when the business relationship changes.

Separate the three core rule sets

Pricing, visibility and permissions answer different questions. A buyer may be allowed to see a product without being allowed to purchase it. A wholesale role may establish a default discount while an individual account has a negotiated price.

Existing extensions can provide parts of this foundation. For example, the Roles & Rules B2B documentation describes role-based pricing and a catalog mode. Its listed features are a starting point for evaluation, not proof that an extension satisfies your particular contract rules.

Example: a supplier serving two trade groups

Imagine a supplier with installers and distributors. Both groups must be approved, but distributors can buy a restricted product range and some companies have individual contracts.

Account state Product access Price rule Order action
Visitor Public range Retail price Retail purchase
Pending applicant Public range Retail price Await approval
Approved installer Installer range Installer default Standard order
Approved distributor Distributor range Contract, then group default Agreed workflow

This is an illustrative design. The real rules should identify precedence, effective dates, quantity breaks and whether contract prices combine with coupons. Decide how previously placed orders behave when a contract changes.

Make pricing consistent throughout the order

Check product listings, variations, cart totals, checkout, emails and customer order history. Avoid changing only the visible price label. Store the agreed order values so that later product changes do not rewrite the meaning of an existing order.

Personalised responses also need account-aware caching. A cached page for one buyer must not expose their contract prices to another. Include logout, role changes and account switching in your tests.

Connect operational systems deliberately

If an ERP owns prices or stock, record that ownership. Plan the update frequency, field mapping and how staff will handle a failed sync. A useful integration shows when information last updated and provides a controlled way to retry.

Do not assume that every order should immediately enter fulfilment. Some companies require manual approval or a purchase order reference. The website should communicate that status clearly instead of implying confirmation before the business has accepted the order.

Test the boundaries before launch

Test approval and rejection, changing roles, expired pricing, mixed carts, variations and attempted access to restricted products through direct URLs. Include orders created by staff if that workflow is part of the scope.

E-commerce development can establish the store rules, while integration solutions connect them to the systems the business already uses.

A B2B catalogue does not always need online checkout. See how WooCommerce development supported Trans-Technik’s quote-only catalogue.

Frequently asked questions

Does WooCommerce include every B2B feature by default?

No. Account approval, negotiated pricing and advanced catalog restrictions may require a suitable extension or custom development. The choice depends on the store's rules.

Can retail and wholesale customers use the same store?

Yes, with deliberate rules for visibility, pricing, taxes, payment options and caching. Test logged-out retail visitors as well as every approved wholesale group.

How we can help

Explore the services related to this guide.

E-commerce Solutions →Integration Solutions →
← Back to all articles