If you’re evaluating BigCommerce for a B2B project, the question that determines most of your build is whether you’re using B2B Edition. It’s the layer that turns BigCommerce from a B2C platform with B2B add-ons into something that genuinely belongs in a B2B conversation. After several B2B Edition builds, here’s the practical view.
What B2B Edition gives you out of the box
Corporate accounts and buyer hierarchy
The fundamental B2B feature is that a "customer" isn’t a person — it’s a company with multiple people inside it, each with different permissions. B2B Edition models this natively:
- A Company is the top-level entity (mapped to your ERP customer).
- Inside the company are Buyers with role assignments — admin, senior buyer, junior buyer, view-only — each with different ordering and approval rights.
- Buyers can be tied to specific ship-to addresses (so a buyer for the Cleveland warehouse can’t accidentally ship to Dallas).
If your business sells to companies-as-customers and not consumers, this alone is worth the B2B Edition license.
Quote-to-order workflow
Buyers can request a quote on a cart, sales reps can edit pricing and approve, and the quote becomes a converted-order with the agreed prices. The flow is built in. What you customize is who gets quote requests, what overrides are allowed, and how approvals flow through ERP.
Price lists
Each company can be assigned a price list, which can have completely different prices, currencies, or visible product sets. This is the workhorse for "Customer A sees a different catalog than Customer B" without needing a separate site.
Requisition lists / saved orders
Frequent re-orderers (warehouses, MRO buyers, anyone who orders the same SKUs every month) can save lists, share them across the corporate account, and reorder with one click. This is the single feature that’s most loved in our user testing — buyers actually appreciate when their daily workflow is shorter.
Account dashboards
Order history scoped to the corporate account (with optional buyer-level filtering), open invoices view, ship-tracking, and a request-form for the sales rep. Standard, but real.
What B2B Edition doesn’t do
Equally important to scope honestly:
- Real-time ATP from your ERP. B2B Edition uses cached inventory like the rest of BigCommerce. If your B2B model demands real-time available-to-promise from the ERP at request time, you’ll need a custom integration (or you’re really looking at Sana Commerce, not BigCommerce).
- Complex tier pricing in formulas. Price lists are flat per-SKU. If your pricing rule is "5% off list, then 2% if quantity ≥ 100, then a customer-specific override," you’ll be flattening those formulas into resolved prices on the price list.
- Customer-specific catalog visibility beyond price lists. Hiding products from specific customers is doable but requires the price list to specify product visibility — there’s no separate "this customer can see these categories" model.
- Native multi-currency for a single company. A company is one currency. If a customer trades in EUR and USD with you, that’s two companies in B2B Edition, not one with two currencies.
Integration patterns that hold up
ERP → BigCommerce sync
Most B2B Edition projects pull customer + price list data from the ERP on a schedule (hourly is typical, real-time for high-stakes data). The integration we recommend is:
- A small middleware service (.NET or Node, your choice — we usually pick .NET because the rest of the stack is .NET) that owns the sync logic, not the ERP and not BigCommerce.
- Idempotent syncs keyed on a stable customer/SKU identifier — never on names or addresses.
- An audit log of every sync action so when a customer says "my price changed yesterday and nobody told me," you can answer.
Quote-to-order → ERP back-flow
When a quote converts, you need that order to land in the ERP. The order’s line-level pricing already has the negotiated values; the ERP just creates a sales order with those prices and skips its own pricing engine. This is one of the few places we routinely build custom — every ERP’s sales-order API has its quirks.
Buyer SSO
For mid-market and up, buyers expect to log in via their corporate identity provider. B2B Edition supports SSO via standard SAML — but production-ready integration is meaningful work. Plan 1–2 weeks for it, plus the configuration in the customer’s IdP that you don’t control.
Stencil vs Catalyst with B2B Edition
We’ve covered Stencil vs Catalyst more broadly. For B2B Edition specifically: Stencil has more polished out-of-the-box B2B Edition UI integration. Catalyst is improving fast but you’ll be wiring a few B2B Edition screens (quote management, masquerade) yourself. If B2B Edition is core to your launch and your team is small, that’s a Stencil tilt. If you have a frontend platform team and B2B Edition support in Catalyst is "good enough" for your screens, Catalyst gives you headless freedom.
The takeaway
B2B Edition is genuinely good. It’s also a layer of complexity you don’t need if your business is closer to B2C-with-bulk-orders than to multi-buyer corporate accounts. Be honest about which you are. The wrong reason to buy B2B Edition is "we’re B2B so we should." The right reason is "our customers buy in teams, and the storefront has to model that or our reps will keep doing the work manually."
Sizing a B2B Edition build? Talk to us — we’ve done several and we’ll tell you which features actually move the needle for your buyers.