BigCommerce B2B Edition: Is It the Right Foundation for a Complex Wholesale Ecommerce Platform?

Complex wholesale ecommerce is not a consumer store with larger order quantities.

The customer may be a company rather than an individual. Several users may buy under the same account. Prices can depend on contracts, customer groups, quantities and currencies. Junior buyers may prepare an order that a manager approves. Payment may use a purchase order or agreed terms. Sales representatives may quote, assist or act on behalf of customers. Product, stock, credit and fulfilment data may live in ERP, PIM, WMS, CRM and accounting systems.

BigCommerce B2B Edition is designed to add business-account and buyer-workflow capabilities to the BigCommerce platform. Its Buyer Portal supports activities such as account management, quote requests, order history and invoice payments, and it can be used with Stencil, Catalyst or custom headless storefronts. BigCommerce developer documentation: B2B Edition overview

That makes it a credible platform to evaluate. It does not make it the correct platform for every wholesaler.

The decision should be based on the match between the organisation’s commercial rules and the platform’s account model, APIs, buyer experience and operating responsibilities. A feature that exists may still require configuration, extension, integration or customisation. A feature that looks close may encode a different rule.

This guide explains how to evaluate fit before treating B2B Edition as a fixed implementation answer.

Begin with the wholesale operating model

Map how the business sells today and how it intends to sell.

Customer structure

• Is each customer one legal entity, or a hierarchy of branches and subsidiaries?
• Can users act across several locations?
• Who manages addresses and users?
• Can sales representatives access or assist accounts?
• Do different entities share credit, pricing or reporting?

Catalogue and product access

• Does every company see the same products?
• Are catalogues restricted by contract, market, certification or branch?
• Are products simple, variable, configurable or made to order?
• Are documents and technical data restricted?

Pricing

• Are prices set by company, group, product, quantity, currency or contract?
• What is the precedence when rules overlap?
• Can sales representatives override price?
• How are quotes converted into orders?
• Which system is authoritative?

Ordering and approval

• Can buyers create shopping lists?
• Who can submit, approve or pay?
• Are purchase orders mandatory?
• Are order limits based on user, company or credit status?
• Can an order ship to several addresses?

Finance and fulfilment

• Are terms and invoices managed online?
• How is available credit determined?
• Which payments are allowed by company?
• Where do tax, stock, freight and fulfilment status originate?

The platform evaluation begins only after these rules are explicit.

Understand the company-account model

BigCommerce B2B Edition organises B2B customers into Companies. Company users are buyers associated with those business accounts, and roles determine their permissions in the Buyer Portal.

The official documentation identifies default roles including Junior Buyer, Senior Buyer and Admin. Junior Buyers can prepare shopping lists for approval; Senior Buyers can approve and place orders; Admins can manage broader company-account functions. Custom roles and permissions are also supported. BigCommerce B2B developer course: company entities and relationships

This can fit many wholesale models, but confirm:

• whether the role permissions match the organisation’s actual approval matrix
• how users are invited, removed and transferred
• whether approval applies to shopping lists, orders, values or categories as required
• whether identity must connect to SSO
• how customer accounts and company users remain synchronised

BigCommerce documents a one-to-one relationship between a Company user and a storefront customer account, with each record authoritative for particular fields. That distinction matters when integrating identity or CRM data. BigCommerce B2B Storefront API: companies and users

Evaluate account hierarchy carefully

Account hierarchy supports parent-child relationships between Companies. BigCommerce’s current management documentation describes up to five hierarchy layers and a maximum of 500 Companies within one hierarchy. Higher-level buyers can access subsidiaries according to the platform’s hierarchy behaviour and permissions. BigCommerce B2B API: company management

Do not treat those numbers as the only test. Model realistic cases:

• national customer with state and branch entities
• franchise network
• buying group
• hospital or university departments
• corporate head office with local purchasing
• sales representative assigned to selected subsidiaries

Check what should be inherited:

• price lists
• catalogue access
• credit
• addresses
• users
• payment terms
• reporting
• approvals

Hierarchy access does not necessarily imply that every commercial setting aggregates or inherits exactly as the business expects. Validate each rule with current documentation and, for critical cases, a configured proof of concept.

Separate Companies from customer groups

Companies represent business accounts and users. Customer groups can help determine catalogue access and pricing.

BigCommerce documentation explains that independent Companies can be assigned to customer groups, several Companies can share a group, and a Company can use the default catalogue and pricing when unassigned. Price lists can then apply company- or currency-specific pricing through customer-group relationships. Older B2B Edition configurations may use different dependent-company behaviour, so an existing store must be assessed in its actual mode. BigCommerce B2B developer course: company accounts and customer groups

Before implementation, design:

• the number and purpose of customer groups
• company-to-group assignment
• price-list ownership
• catalogue visibility
• default behaviour for unassigned accounts
• migration from any legacy company mode
• bulk onboarding and change processes

Avoid creating one customer group per company by habit if a more governable shared model meets the requirement.

Test pricing with real commercial cases

A B2B platform can support price lists and still fail the business’s complete pricing model.

Create acceptance scenarios for:

• contract SKU price
• quantity break
• promotional override
• currency-specific price
• negotiated quote
• customer group
• sale price
• sales-representative adjustment
• tax display
• rounding

For each case, state the expected price on category, product, cart, checkout, quote, order and invoice views.

Decide which system owns each value. If the ERP owns contract pricing, the architecture must define how prices reach BigCommerce, how fresh they must be, what happens during an outage and how discrepancies are reconciled.

Do not rely on a screen demonstration using one simple company. Pricing defects often appear when several rules overlap.

Assess the Buyer Portal as an operating workspace

BigCommerce describes the Buyer Portal as a React-based application supporting advanced B2B workflows including account management, quote requests and order history. It can be customised and deployed across supported storefront approaches. BigCommerce developer documentation: Buyer Portal setup

Evaluate it through tasks, not screenshots:

• apply for a business account
• invite and remove users
• assign roles
• manage several addresses
• build and share a shopping list
• request and revise a quote
• convert a quote to order
• find and repeat a past order
• view and pay invoices
• act across subsidiary accounts
• understand credit or hold status

Measure task clarity, permissions, error handling and mobile usability.

The Buyer Portal source is publicly available under an open-source repository, which gives developers a basis for custom experiences. That does not make customisation free or automatically upgrade-safe. Changes need a source-control, release, testing and support model. BigCommerce GitHub: B2B Buyer Portal

Quotes, invoices and payment terms need end-to-end validation

A quote is not only a price document. It may include:

• product configuration
• expiry
• negotiated freight
• minimum quantity
• payment terms
• salesperson approval
• customer acceptance
• revision history
• conversion to order

B2B Edition’s APIs expose resources including Companies, users, sales quotes and invoice payments, enabling integrations and custom experiences. BigCommerce developer documentation: B2B APIs

Validate the complete lifecycle and system of record. If the CRM or ERP creates quotes, decide whether BigCommerce mirrors them, edits them or only presents them. Prevent two systems from issuing conflicting versions.

BigCommerce’s documentation describes company payment terms and credit settings, including order-value controls for purchase-order payments and account credit holds. It also notes that the configured credit amount is not a continuously decreasing balance ledger; organisations needing credit-usage monitoring may need to synchronise an ERP or accounting system. BigCommerce B2B developer course: company credit and terms

That is exactly why feature names must be tested against the underlying business meaning.

Plan integrations around authority and reconciliation

Complex wholesale commonly involves:

• ERP for product, price, customer, order or finance
• PIM for enriched product information
• WMS for stock and fulfilment
• CRM for relationships, sales activity and opportunities
• identity provider for SSO
• tax and freight services
• EDI or procurement systems

For each data object, define:

• authority
• direction
• frequency
• acceptable latency
• conflict rule
• duplicate protection
• failure state
• retries
• monitoring
• reconciliation
• owner

The availability of an API does not prove the external system exposes the required data or can accept the required transaction. Review both sides.

Where integration, data, roles, markets or security remain unresolved, paid Discovery should produce the architecture and staged implementation plan before a fixed build is quoted.

Decide between Stencil, Catalyst and headless deliberately

B2B Edition can support hosted and headless storefront approaches, but they create different ownership.

Stencil

Can provide a more conventional BigCommerce theme and hosted-storefront pathway with a lower custom frontend burden for many requirements.

Catalyst

BigCommerce’s composable storefront framework may suit organisations wanting a modern React/Next.js-based experience within the platform’s evolving ecosystem. Current feature and B2B compatibility must be verified for the intended release.

Custom headless

Provides greater frontend control but moves more application hosting, routing, deployment, caching, preview, search and integration responsibility to the implementation team and client.

Do not select headless because it sounds more enterprise. Use it when the required experience, content architecture, multi-channel reuse or frontend constraints justify the additional operating surface.

BigCommerce’s documentation notes that Buyer Portal custom builds can support Stencil and headless storefronts. The implementation detail, authentication and upgrade path differ, so the front-end decision belongs in architecture rather than visual design alone. BigCommerce B2B Edition overview

Understand SaaS boundaries

BigCommerce operates the core SaaS commerce platform. The merchant still owns decisions and integrations around:

• platform subscription and commercial terms
• apps and external services
• custom storefronts
• data quality
• configuration
• identity
• ERP and other integrations
• analytics and consent
• content and merchandising
• release acceptance
• business continuity outside the core platform

Emote does not resell hosting infrastructure. The client contracts directly with BigCommerce and any relevant hosting or service providers. For a custom headless frontend, the client also contracts with an appropriate frontend host, while Emote can define requirements and coordinate implementation.

Calculate total ownership cost

Include:

• BigCommerce plan and B2B Edition commercial terms
• apps and connectors
• Discovery and solution design
• UX/UI and frontend implementation
• portal customisation
• data migration
• ERP, PIM, WMS and CRM integration
• quality assurance
• training
• support and optimisation
• headless hosting where applicable
• future upgrades and roadmap changes

Compare this with the cost of manual work, errors, sales administration and the incumbent platform. A lower licence does not create value if the organisation recreates critical workflows in spreadsheets.

Use a fit-gap matrix

Classify every requirement:

• Native: supported as required through standard configuration.
• Configured: supported with non-code setup and governance.
• Extended: requires a marketplace app or supported extension.
• Customised: requires portal or storefront development.
• Integrated: depends on another system and data contract.
• Not credible: conflicts with the platform or creates unacceptable risk.
• Deferred: intentionally moved to a later release.

For every non-native item, add owner, cost, dependency, test method and ongoing support responsibility.

Common selection mistakes

Choosing from a feature checklist

Feature names conceal differences in rules, permissions and lifecycle.

Designing the storefront before account architecture

Roles, company hierarchy and catalogue access shape the experience.

Assuming the portal eliminates integration work

The portal presents workflows; authoritative data may still live elsewhere.

Treating a headless build as a theme choice

Headless changes hosting, deployment, routing, preview and support responsibilities.

Ignoring internal onboarding

Staff need processes for company approval, pricing, quoting, user support and exceptions.

Expecting platform implementation to include indefinite support

Emote’s standard 30-day functional warranty covers agreed implementation functionality from production go-live. Ongoing monitoring, platform changes, apps, integrations, content, optimisation and enhancements are separate support activities.

Frequently asked questions

What is BigCommerce B2B Edition?

It is a set of B2B capabilities layered on BigCommerce, including Company accounts, buyer roles and a Buyer Portal for workflows such as account management, quotes, orders and invoices.

Is B2B Edition suitable for both B2B and B2C?

It can support mixed models, but catalogue, pricing, account and storefront requirements need to be designed explicitly rather than assumed.

Can buyers have different permissions?

Yes. B2B Edition provides default Company roles and supports custom roles and permissions. Validate the exact approval and access rules required.

Can it support company hierarchies?

Current documentation supports parent-child Company hierarchies with defined platform limits. Test inheritance, cross-company access and sales-representative behaviour against the proposed model.

Does it integrate with an ERP?

APIs make integration possible, but a specific ERP connection depends on the ERP, data model, connector, latency, error handling and ownership.

Is the Buyer Portal customisable?

Yes. BigCommerce provides an open-source React-based Buyer Portal foundation. Customisation creates ongoing code, testing and upgrade responsibilities.

Does BigCommerce provide hosting?

BigCommerce operates its SaaS platform. Custom headless frontends and external services may require separate providers. Emote does not resell hosting; clients contract with providers directly.

Can Emote provide a fixed quote before requirements are defined?

Only where the requirement is sufficiently clear. Material unknowns in company structures, pricing, integration, data, security or multi-storefront architecture should be resolved through paid Discovery first.

How Emote can help

BigCommerce B2B Edition can provide a substantial foundation for wholesale ecommerce. Its value comes from how well Companies, roles, pricing, quotes, invoices, portal tasks and integrations match the business, not from adopting the platform name.

Emote’s BigCommerce website design and development services bring experience design, commerce and integration planning together for complex B2B requirements.

If you are assessing BigCommerce B2B Edition against your wholesale operating model, book a meeting with Emote to talk through the questions that need resolving first.