BigCommerce B2B Edition pairs Multi-Storefront (MSF) with a shopper-facing Buyer Portal, company accounts, and sales quotes so merchants can run separate retail and wholesale experiences from one control panel. Official product and developer docs describe channel-level product assignment, per-storefront B2B settings, company approval gates, customer-group catalog controls, and quote workflows that matter when wholesale SKUs must stay off public DTC shelves.
This explainer is for website owners and developers who sell regulated or higher-risk products and need a documented way to separate restricted wholesale catalogs from consumer storefronts, without inventing compliance guarantees the platform does not claim.
What BigCommerce documents for B2B Edition
BigCommerce's Stencil docs state that the Buyer Portal experience is channel-aware and MSF-optimized. The backend can manage B2B functionality on multiple storefronts, which the docs say allows region- or brand-specific B2B experiences, or separate B2B and B2C storefronts. New B2B Edition stores get the Buyer Portal enabled by default.
Multi-Storefront as the retail versus wholesale split
Multi-Storefront lets one BigCommerce store power multiple storefronts, each with its own domain, theme, categories, pages, price lists, email templates, and related settings, all managed from one control panel. Storefronts share the store catalog, but merchants choose which products appear on which storefronts. BigCommerce explicitly notes MSF is useful for merchants who serve multiple segments such as B2C, B2B, retail, and wholesale.
Developer docs add a cardinal rule for catalog channels. Products must be explicitly assigned to a channel to be sold on that channel. On native Stencil storefronts, products that are not assigned to a storefront's channel are hidden from that channel. Channel assignments are managed through the Catalog API and control-panel bulk actions. Headless B2B setup docs similarly instruct merchants to add selected products to the new channel after activating B2B on that storefront.
According to the B2B Edition app listing, B2B Edition adds multi-storefront capabilities, a Buyer Portal, and headless support (listed as beta on that page) on top of the BigCommerce Enterprise Plan. The listing and developer courses describe core capabilities that include corporate (company) account management, sales representative masquerade, quoting, shared shopping lists, invoice portal tools, company address books, payment method visibility controls, quick order and buy-again flows, plus wholesale customer approval and trade professional application paths.
For B2B Edition specifically, BigCommerce's Multi-Storefront developer lesson says MSF must be activated for the BigCommerce store before (or ideally before installing) B2B Edition, and that B2B still must be enabled for each storefront individually under the B2B Edition Storefronts menu. Per-channel overrides include whether B2B is allowed, Buyer Portal type (default or custom), logo and account login or registration settings, login-page customization, quote settings and floating action buttons, shopping-list settings, and translations.
Companies can operate across multiple channels, but company users must be assigned to specific channels. A user limited to channels 1 and 3 cannot work across other company channels unless given explicit access. That channel scoping is the documented mechanism for keeping wholesale buyers on the wholesale storefront while retail shoppers stay on the consumer channel.
Buyer Portal, company accounts, and catalog gates
The Buyer Portal is the shopper-facing B2B UI. It replaces the default BigCommerce account area and provides out-of-the-box support for quotes, invoices, multiple company users, user roles, shared company address books, shopping lists, quick order by SKU or prior purchase, super-admin masquerade, and company hierarchy. It works on Stencil automatically when B2B Edition is enabled, on custom headless storefronts with documented loader steps, and on Catalyst through an integration BigCommerce labels experimental.
Company accounts organize B2B buyers by company rather than as isolated customers. Per the company entities lesson, registration can require manual approval. While an account is pending, settings can require approval before new companies place orders, and require approval before new companies see products and pricing. Automatic approval can also be enabled. Those gates are the documented levers for keeping restricted wholesale visibility behind an approved company relationship.
Company accounts relate to BigCommerce customer groups for pricing and viewable catalog. With independent Companies behavior (Buyer Portal experience), companies do not automatically get a dedicated customer group. Merchants can assign an existing group, reassign groups, share one group across many companies, set a default group for new companies, import assignments by CSV, or leave a company unassigned so it sees default storefront catalog and pricing. Price lists then attach negotiated pricing to customer groups (and, via price-list assignments, to channels and groups). Default company user roles are Junior Buyer (shopping lists that need approval, no solo purchases), Senior Buyer (approve lists, place orders, view company order history), and Admin (plus company addresses, users, and invoices). Custom roles with unique permissions are also supported.
Quotes for negotiated and non-catalog wholesale lines
B2B Edition sales quotes are individualized offers that buyers can request and sales representatives can curate. Server-side quote tools can add custom line pricing and discounts (optionally hidden from the recipient), offer custom products, catalog-only items, or items that are out of stock for typical checkouts, attach bespoke shipping methods, and set expiration dates. Buyer Portal permissions control who can view, create, message about, checkout, or export quote PDFs. Non-purchasable custom items in buyer-requested quotes require the Buyer Portal experience, plus Quotes settings that allow custom items and custom shipping.
For regulated wholesale operations, quotes are the documented path for one-off SKUs, negotiated packs, or items that should not sit on an open catalog page, while still moving the buyer to a checkout URL when the quote is accepted.
Headless and Catalyst notes for developers
Official Catalyst documentation for B2B Edition treats Catalyst plus Buyer Portal as experimental and subject to change, and advises working with BigCommerce professional services for that path. Prerequisites include multi-storefront enabled in both BigCommerce and B2B Edition, a V3 API token with the B2B Edition scope, and Customer Access Tokens (default on new B2B stores; older stores may need support to enable them). Merchants enable B2B on the Catalyst channel, set Buyer Portal type to Custom for a forked portal, and can run the hosted portal or a locally developed open-source Buyer Portal. Non-Catalyst headless frameworks follow a separate channel-setup guide that also requires MSF seats and explicit product-to-channel assignment after activating B2B on the headless channel.
How this helps restricted retail versus wholesale ops
The following points are editorial interpretation grounded in the documented behaviors above, not additional BigCommerce legal claims.
Separating a public DTC storefront from a B2B-enabled wholesale storefront lets teams assign restricted SKUs only to the wholesale channel, while consumer channels keep a narrower assortment. Company approval before product and price visibility, plus customer-group catalog limits, reduces casual browsing of wholesale-only lines. Buyer roles and shopping-list approvals create an internal purchase trail useful when distributors need junior staff to draft and seniors to buy. Quotes handle negotiated or non-catalog lines without publishing them on the retail theme. Invoice portal, PO visibility controls, and company address books support repeat wholesale ops that DTC checkouts do not. None of these features alone certify age gates, licensing, state shipping bans, or payment-network rules. Those remain merchant and integrator responsibilities layered on top of channel, company, and group configuration.
Practical checklist drawn from official docs
Enable Multi-Storefront on the store, then enable B2B per wholesale storefront in B2B Edition Storefronts. Assign wholesale-only products to the wholesale channel and omit them from retail channels. Configure company registration approval, including whether pending companies can see products and pricing. Map companies to customer groups and price lists that match wholesale contracts. Assign buyers only to the channels they should use. Turn on Quotes settings needed for custom items if negotiated lines matter. Treat Catalyst Buyer Portal work as experimental until BigCommerce's own guidance says otherwise. Stage channel assignments and company gates on a sandbox before production cutover.
Sources
- B2B Edition app listing
- Multi-Storefront (Help Center)
- Multi-Storefront for B2B Edition (developer course)
- Introduction to the Buyer Portal