BigCommerce introduced the B2B Edition account hierarchy feature on March 5, 2025 with support for up to five parent-to-child layers of company accounts sharing a single buyer portal, a scale that covers most mid-market distribution and manufacturing structures. That feature alone is the reason a meaningful share of mid-market B2B stores migrated from legacy carts onto the platform in 2025 and 2026. B2B Edition is not the same thing as the native B2B features built into standard BigCommerce plans, and the distinction matters for scoping.
This guide covers the setup decisions and platform specifics that determine whether a B2B build ships on time. The parent guide connects this to the broader development topic. Cost questions for B2B builds sit in the customization cost breakdown, and the agency selection guide covers the specific partner qualifications that matter for B2B scope.
B2B Edition versus native B2B features
Every BigCommerce plan from Plus upward includes a set of native B2B features: customer groups, price lists, tax-exempt configuration, net terms at checkout with manual processing, and basic account-based discounts. Those features are enough for a small distributor with under 50 active accounts and no quote workflow. B2B Edition is an add-on that layers a full buyer portal and a set of B2B-specific objects on top of the native storefront.
The B2B Edition feature set that is not available natively includes company accounts with multi-user roles, account hierarchies up to five levels as of 2025, sales rep masquerade, a buyer-side quote management workflow, purchase order payment with configurable net terms, invoice portal with payment visibility controls, shared shopping lists across company users, CPQ-style configure-price-quote flows, and the open-source Buyer Portal codebase that can be extended and self-hosted. Most partners summarize the feature list on the BigCommerce B2B page, though the authoritative feature deltas surface in the admin console once B2B Edition is enabled on the store.
Activation of B2B Edition on an existing Enterprise store typically requires contacting the BigCommerce account team. New B2B purchases receive the welcome email from [email protected] and surface the admin panel under Apps, then B2B Edition. Teams running the activation in-house can follow the platform documentation; teams bringing in outside help usually pair activation with a B2B discovery workshop that maps business requirements to the B2B Edition feature set before any code changes start.
The practical reason agencies with prior B2B Edition work charge more is that the setup decisions cascade. Choosing customer groups over B2B Edition company accounts is fast to set up and hard to reverse. Choosing the wrong price list inheritance pattern locks downstream catalog integrations into assumptions that surface as reconciliation errors against the ERP six months later. Platform-specific knowledge saves the project from revisiting those decisions. An ecommerce development agency with B2B experience in BigCommerce typically runs discovery against a B2B-specific checklist that covers hierarchy depth, customer group boundaries, price list inheritance, quote approval routing, and payment terms before any build work begins.
Company account hierarchies
A company account in B2B Edition represents a single buying organization with multiple users, defined roles, and its own pricing context. Roles commonly include Administrator, Sales Rep, Accountant, Financial Manager, and Store Owner at the BigCommerce side, plus company-side roles for each buying user. Each user can be attached to one or more company accounts, which matters for agencies and distributors where one buyer serves multiple end customer organizations.
The account hierarchy feature lets a parent company contain subsidiary companies up to five layers deep. A typical structure for a franchise distributor looks like a parent national entity, regional distribution centers as first-level children, franchise operators as second-level children, and individual franchise locations as third-level children. Each level can inherit or override the pricing and catalog rules of the level above. That inheritance is the reason hierarchies scale operationally. Without inheritance, maintaining 400 franchise location pricing setups is a full-time job.
Activation of the hierarchy feature requires a support request on stores provisioned before the March 2025 cutover, because the buyer portal experience has to be toggled on. New stores have it enabled by default. The hierarchy requires the Buyer Portal to be active, which matters if the build has a legacy storefront checkout layered over B2B Edition. Buyer portal and legacy checkout do not align cleanly, and the agency should plan a test matrix that exercises every role at every level before go-live.
Price lists and customer group pricing
Pricing on BigCommerce B2B works through two mechanisms that overlap. The first is price lists, which are named collections of SKU-to-price mappings that can be assigned to a customer or a customer group. The second is customer group discounts, which are percentage or fixed-amount adjustments applied on top of product prices for a specific group. Price lists are more precise. Customer group discounts are faster to set up for broad-stroke pricing.
A common pricing architecture for a 200-account B2B store uses three price lists: a standard wholesale list at published wholesale prices, a tier-two list for volume accounts at roughly 5 to 8 percent below wholesale, and a tier-three list for national account contract pricing that is negotiated per account. Assignments run through customer groups. The architecture holds up until a new account needs a custom price on a subset of SKUs, at which point a fourth price list gets created. Stores that end up with 40 price lists by year three usually would have been better served by a customer-specific pricing tier in B2B Edition from the start.
Price list reconciliation against an ERP is where most integrations run into trouble. NetSuite matrix items, SAP Business One price levels, and QuickBooks price levels each model the pricing hierarchy differently. Mapping requires a field-by-field integration map during discovery. The API integrations guide covers the specific webhook and API surface involved.
Quote management and purchase order workflows
B2B Edition quote management lets buyers request a quote from the storefront, the assigned sales rep review and adjust pricing, and the buyer accept the quote as a cart that can be converted to an order. The flow supports attachments, internal notes, and expiration dates on quote offers. Quote approval routing is configurable. A typical configuration sends all quotes over a threshold dollar amount to a sales manager for review before the buyer sees the response.
Purchase order as a payment method is a separate feature. PO checkout lets a buyer submit an order against their company's negotiated net terms (typically net 30, net 60, or net 90) and receive an invoice from the invoice portal. Invoice portal handles partial payments, credit limit enforcement, and payment visibility controls that let an accountant at the buying company see open invoices without seeing checkout pricing. The workflow looks straightforward in the admin console. The integration side is harder. Orders paid via PO need to post to the ERP accounts receivable ledger and reconcile when the payment clears, which is another webhook plus middleware pattern rather than a native capability.
Credit management is the third piece. Each company account can carry a credit limit and a balance. Orders that exceed the credit limit either block automatically or flag for review depending on configuration. Agencies that have shipped credit management typically build a small internal dashboard for the finance team to review holds, because the native admin surface does not group by pending credit review efficiently.
Sales rep masquerade and shared lists
Sales rep masquerade lets a BigCommerce staff user log in as a specific company buyer to place an order on their behalf, with the sales rep identity captured on the order record for attribution. This matters because a large share of B2B orders still come in via phone, email, or field sales rather than through the storefront. Without masquerade, those orders either get entered manually into the admin (losing all the buyer-side workflow benefits) or get routed through the buyer's own storefront login (losing attribution and commission tracking).
Shared shopping lists let any user on a company account save a cart template that other users on the same company can reuse. The feature is heavily used in repeat ordering scenarios: hospital systems reordering the same supply kit weekly, restaurant chains reordering the same pantry staples daily, MRO distributors reordering parts against a blanket PO. Shared lists are a small feature with outsized conversion impact in the industries where it fits.
B2B checkout requirements that break generic agency assumptions
The native Optimized One-Page Checkout was designed for DTC. B2B scenarios put pressure on it in three ways the generic build does not anticipate. First, buyers need to select a purchase order payment method that does not take a credit card, which requires configuring PO as a payment option and routing the order to the invoice portal rather than the payment gateway. Second, buyers need to see contract pricing applied during checkout, which requires the price list logic to cascade into the cart total calculation. Third, buyers need to enter a PO number and optionally attach a document, which requires a checkout form extension rather than a theme-level change.
Building these extensions is typically a Checkout SDK job. The SDK's CORS constraint means the customization runs inside the BigCommerce storefront host, not on a separate origin. Stencil themes require Optimized One-Page Checkout to be enabled to preview SDK changes locally. Teams that try to build a standalone B2B checkout on a separate domain hit the CORS wall fast. The checkout optimization guide covers the SDK surface area in detail.
Case study
A North Carolina MRO (maintenance, repair, operations) distributor serving industrial customers across six states migrated from a legacy cart onto BigCommerce B2B Edition in early 2026. The business had 340 company accounts, a three-level hierarchy through regional distribution centers, and a NetSuite ERP integration requirement. Initial scope was $62,000 for the core build plus $24,000 for NetSuite integration, with a 14-week timeline.
Week one discovery surfaced two structural issues. The legacy cart handled customer-specific pricing at the line-item level, which B2B Edition handles at the price-list level. Reconciling the data model required building a migration script that consolidated 2,800 customer-specific prices into 18 price lists plus 340 overrides stored as customer group discounts. That work added 60 engineering hours. Week eight discovery surfaced the second issue: the PO approval workflow the business had described needed to route through a Slack approval chain that did not exist in B2B Edition natively, which required a small app bridging the quote-request webhook to a Slack workflow with an approval-callback endpoint.
The project shipped in 17 weeks at a final invoice of $104,000, with a retainer of $4,200 per month covering ongoing NetSuite integration drift, B2B Edition feature updates, and quote workflow adjustments. Conversion rate on the storefront rose 34 percent in the first 90 days compared to the legacy cart, driven primarily by the shared shopping lists feature and the faster repeat-order path for the top 40 company accounts.