BigCommerce B2B: buyer portal and wholesale catalogues

Assess BigCommerce B2B ordering with company accounts, price lists, quotes and buyer permissions, including the role of B2B Edition.

BigCommerce B2B supports business-to-business ordering through customer groups and price lists, with B2B Edition adding company accounts and a self-service Buyer Portal. The right setup depends on whether your trade customers need negotiated prices alone or several buyers sharing an approval process.

A wholesaler moving orders out of email needs to preserve who can buy and what each company can see. Map those rules before choosing the portal and checkout configuration.

Distinguish core wholesale features from B2B edition

Core BigCommerce wholesale controls handle product access and pricing, while B2B Edition adds company purchasing workflows. Customer groups define which categories a customer can see. An assigned price list supplies the applicable product or variant prices.

These controls depend on the plan. BigCommerce’s plan comparison lists customer groups from Growth and price lists on Performance. B2B Edition also needs to be provisioned and enabled. A store with wholesale discounts does not automatically have its company portal.

The Buyer Portal documentation describes shared shopping lists, quotes, invoices and quick ordering. Stencil storefronts integrate the portal automatically when B2B Edition is enabled. A custom headless storefront needs integration work, and the documented Catalyst integration is experimental.

For a broader platform choice, compare the company purchasing workflows in our B2B ecommerce platforms guide. Keep your BigCommerce decision tied to the workflow you need to replace.

Set up companies and buyer roles

Create a company account for each business customer, then give its purchasing staff separate buyer accounts. The company holds the commercial relationship. Each buyer’s role controls their actions within it.

Decide whether new companies need approval before viewing products or placing orders. BigCommerce’s registration guidance explains the available settings. It also distinguishes independent company accounts from customer groups: several companies can share one group, and a company can have no group assigned.

The default buyer roles separate purchasing from account management:

Buyer rolePurchasing actionsAccount management
Junior BuyerPrepares shopping lists for approval and requests quotes. Cannot purchase independentlyWorks within assigned permissions
Senior BuyerApproves lists, places orders and views company order historyDoes not receive the Admin role’s wider management rights
AdminHas Senior Buyer purchasing actions and can pay invoicesManages company users and business addresses

Seller-side staff accounts have separate permissions. Giving a customer the Admin buyer role does not give them access to your store’s control panel. If you create custom buyer roles, define the permitted actions explicitly and test those roles separately.

Match product visibility and prices to the company

Use customer groups for category access and assigned price lists for negotiated prices. Treat visibility and price as separate settings: changing a price does not establish who can see the product.

Consider a hypothetical workwear wholesaler with two trade customers. One customer buys branded uniforms at agreed variant prices. The other buys standard stock at its usual wholesale rate. Separate group assignments let you connect each customer to the relevant price list and category access.

A public promotion gives eligible shoppers a discount. A price list overrides catalogue prices for its assigned audience, down to the variant. BigCommerce’s price-list guide describes those overrides and quantity-based tiers.

For the uniform buyer, record a negotiated unit price and any quantity breaks in the assigned price list. BigCommerce’s pricing calculation rules exclude product-level bulk pricing for variants with price-list prices. Recreate the intended quantity tiers in the price list instead of assuming the catalogue discount still applies.

Minimum and maximum purchase quantities are separate availability settings. A lower unit price for a larger order does not itself require the buyer to order that quantity. Make the selling unit explicit too, so a buyer knows whether one item means one garment or one carton.

Move from quote to approved order

Use a quote to agree commercial terms and a shopping-list approval to control who can purchase. Those steps answer different questions: what the seller will supply and who may commit the company to buying it.

In the workwear example, a Junior Buyer saves the required products in a shared shopping list. A Senior Buyer reviews and approves the list. Where negotiated terms are needed, the buyer requests a quote and sales staff manage it in B2B Edition.

BigCommerce’s purchasing workflow documentation explains how accepted quotes become orders. Keep the quote request, list approval and completed order distinct in staff instructions. An approved list still needs the purchase completed.

Purchase order (PO) payments need configuration. The B2B checkout settings use the underlying Check payment method for PO ordering. You can require a reference field and set invoice terms. The entered reference appears in order comments and, when enabled, the confirmation email.

A PO reference identifies the buyer’s purchase authorisation. It does not prove payment or establish credit approval. BigCommerce’s documented company credit amount caps an individual PO order. It does not automatically fall after purchases or rise after invoice payments. Agree credit separately and specify any accounting integration needed to track the outstanding balance.

Help buyers reorder and resolve order questions

The Buyer Portal helps authorised buyers return to saved shopping lists and previously purchased products. Quick ordering supports repeat purchases without rebuilding every product selection from scratch.

For a repeat workwear order, the buyer opens a saved list or selects previously purchased items. Before submitting, the buyer confirms the required variants and quantities against current availability and pricing. A past purchase is a starting point for the new order, not a promise that its old terms still apply.

Company order history gives permitted buyers a place to find existing orders. Support staff also need the relevant product specifications and the store’s delivery and returns rules. An order record alone cannot answer whether a garment suits a particular job or whether a decorated item qualifies for return.

When a customer asks about an order, establish their company and authority before sharing its details. Use the saved order number to locate the transaction, then answer policy questions from the rule that applies to that purchase.

Verify access and checkout outcomes

Test BigCommerce B2B as separate company buyers, following the same purchase from product selection through confirmation. Use an isolated test store with B2B Edition enabled and test payment settings.

  1. Sign in as the first company’s Junior Buyer. Confirm the assigned prices and permitted categories, including a product this company must not access.
  2. Prepare a shopping list and attempt an independent purchase. The Junior Buyer must follow the configured approval restriction.
  3. Sign in as a Senior Buyer. Approve the list and complete its purchase using the intended checkout method.
  4. For PO ordering, try leaving the required reference empty. Then enter it and confirm that the completed order retains it with the agreed invoice terms.
  5. Open the order history as an authorised buyer. Confirm the order exists with the expected company, quantities and final totals.
  6. Switch to the second company and a signed-out session. Confirm neither inherits the first company’s restricted catalogue or negotiated prices.

For custom development, the BigCommerce B2B application programming interface (API) has its own GraphQL schema and company-user authentication. A connection to the general storefront API does not establish that custom company permissions or quote operations work.

Use the documentation for your exact storefront and B2B Edition version when a checkout or custom role behaves differently. Choose the implementation that preserves the company’s buying rules through the confirmed order, then move staff-assisted purchases into that tested flow.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup