Videos

BigCommerce B2B Edition Explained: Company Accounts, Price Lists, Quotes and ERP

8:51 · November 19, 2026 · Watch on YouTube

How BigCommerce B2B Edition handles company accounts, buyer roles, catalogs, price lists, quotes and the Buyer Portal, where it stops, and how ERP prices and quote reviews connect.

Read the full write-up: BigCommerce B2B Edition deep dive

Chapters

  • 0:00Intro
  • 0:28Catalogs, tiered pricing and checkout
  • 1:14Company accounts
  • 1:48Buyer roles
  • 2:18Quotes, Shopping Lists and the Buyer Portal
  • 3:06What B2B Edition doesn't do
  • 3:54Getting ERP prices in
  • 4:37Sync rules that hold up
  • 5:22Quote-only flows through the ERP
  • 6:16Buyer single sign-on
  • 6:47Stencil or Catalyst
  • 7:32Do you need B2B Edition
  • 8:18Get help

Shorts from this video

Transcript

Intro

If you're looking at BigCommerce for a B2B project, one question decides most of the build. Are you using B2B Edition? B2B Edition is the layer that handles what separates B2B from B2C: company accounts with several buyers, quotes, company pricing, and Shopping Lists with an approval step. In this video, we'll walk through what it gives you out of the box, where it stops, and the ERP integration patterns that hold up in production.

Catalogs, tiered pricing and checkout

The first question we usually hear is whether B2B Edition does custom catalogs, tiered pricing and customer-specific checkout. It does all three, and each one comes from features working together. Custom catalogs come from customer groups. Each company sits in a group, and the group decides which categories its buyers can see: all of them, a chosen set, or none. Tiered pricing comes from a price list assigned to that group. It sets the customer's price for any variant, in each currency, with optional quantity breaks. And checkout can differ by company. You choose which payment methods each company can use, including Purchase Order against a credit limit, and you can limit shipping to the company's saved addresses.

Company accounts

The basic idea in B2B Edition is that a customer isn't a person. It's a company with several people inside it, each with different permissions. A Company is the account, and it's usually mapped to your ERP customer. Companies can be nested as parents and children, up to five layers deep. That fits chains, franchises, and customers with many locations. Every buyer in a company shares its address book. So if the buyer for one warehouse must never ship to another, set that location up as a child company with its own addresses and buyers.

Buyer roles

Inside each company are buyers, and each buyer has a role. There are three built in. A Junior Buyer can request quotes and build Shopping Lists, but can't place orders. A Senior Buyer can place orders, approve Shopping Lists, and see the company's order history. An Admin can do all of that, plus manage addresses and users, and pay invoices. There's no built-in view-only role, but you can create one as a custom role.

Quotes, Shopping Lists and the Buyer Portal

The quote-to-order flow is built in. Buyers request a quote on a cart, sales reps edit the pricing and approve it, and the buyer checks out at the agreed prices. Shopping Lists are for frequent re-orderers, like warehouses and maintenance buyers who order the same items every month. Buyers share them with teammates, and lists built by a Junior Buyer go to a Senior Buyer or Admin for approval. Buyers can also reorder from a past order or from Quick Order. The Buyer Portal adds company-wide order history, an invoices view with open and overdue balances and online payment, and each shipment with its tracking number. Shopping Lists are the feature buyers liked most in our user testing. A shorter daily workflow matters to them.

What B2B Edition doesn't do

It's just as important to be honest about what B2B Edition doesn't do. It uses cached inventory, like the rest of BigCommerce. If you need real-time available-to-promise from the ERP when the buyer asks, that's a custom integration. Price lists hold a set price per variant and currency, with optional tiers. They don't hold rules like five percent off list. Those get resolved into prices before they reach the price list. Visibility works by category. A product stays visible if it sits in any category the customer's group can see, so hiding one item from one customer takes planning. And company credit is set in one currency. A buyer who checks out in another currency can't use Purchase Order, so PO terms in two currencies still means two companies.

Getting ERP prices in

B2B Edition doesn't ask your ERP for prices on its own. It stores price lists, and the integration keeps them current. The ERP's pricing decides which of two approaches fits. When ERP prices are lookups, such as price levels, contract price lists and quantity breaks, we resolve them into price lists and sync on a schedule or when a price changes. Then we reconcile on a schedule, so drift gets caught before a customer finds it. When the ERP calculates price at order time, a projected price list is right for most customers and wrong for the exceptions. So we sync price lists for browsing, and ask the ERP for the cart price, cached per customer.

Sync rules that hold up

Either way, a few rules hold up in production. Key every sync on stable identifiers: the ERP customer number and the SKU. Never names or addresses. Log what the ERP returned. When a buyer says their price changed yesterday, you can show what the ERP said and when. If the ERP holds no price for that customer and item, don't allow add to cart. The store shouldn't take an order that will fail downstream. Decide before launch what happens when the ERP is slow or offline, so checkout never stalls waiting for it. And plan around one platform limit: BigCommerce documents that the storefront price filter doesn't show when price lists are in use.

Quote-only flows through the ERP

Many distributors want buyers to see their own price but order nothing until someone reviews it. When that review happens in the ERP, that's integration work, and the flow we build looks like this. The buyer requests a quote from the cart or a Shopping List, and it goes to the ERP as a sales quote. Decide first which system owns the quote. A rep reviews price, stock and credit, and the approved prices come back to the quote in the store. The buyer checks out from the approved quote, and the order posts to the ERP as a sales order at the quoted prices, skipping the ERP's own pricing engine. Check how a fixed-amount discount on the whole quote comes through, because B2B Edition doesn't fold it into the line prices. And a fully quote-only store usually needs theme work, because hiding every cart button for a role isn't one setting.

Buyer single sign-on

For mid-market companies and up, buyers expect to sign in with their corporate identity provider. B2B Edition supports buyer single sign-on, but there's no built-in SAML switch. Your own service, or a marketplace app, accepts the login from the customer's identity provider, such as Okta or OneLogin, then signs the buyer in through BigCommerce. Plan one to two weeks for a production-ready integration, plus configuration in the customer's identity provider that you don't control.

Stencil or Catalyst

There are three ways to run the Buyer Portal. Stock is the portal as BigCommerce ships it, on a Stencil theme. Stencil has the more polished out-of-the-box B2B Edition integration, and it's the quickest route to launch. Customized means changed screens, fields or steps. BigCommerce publishes the portal's source code, so each change is yours to carry through later portal releases. Keep that list short. Catalyst can run the same portal, with quote management and masquerade, where a sales rep shops on a buyer's behalf. BigCommerce still labels that integration experimental, and its B2B starter template alpha. If B2B Edition is central to your launch and your team is small, start on Stencil.

Do you need B2B Edition

So do you need it? B2B Edition is genuinely good, and it's also a layer of complexity you may not need. Standard BigCommerce already has customer groups, price lists and category access by group. That can be enough when each customer account is one buyer ordering in bulk. B2B Edition fits when your customers buy in teams: several buyers per company, parent and child accounts, negotiated quotes, approval before ordering, purchase orders against credit limits, and an invoice portal. The reason to buy it is that your customers buy in teams, and the storefront has to model that, or your reps keep doing the work by hand. BigCommerce quotes the license, and can confirm which plan includes which feature.

Get help

ProjectThunder is a California B2B ecommerce studio, founded in 2004 and a BigCommerce Partner. We set up B2B Edition and connect it to SAP, Microsoft Dynamics and Sage. Your ERP partner implements the ERP, and we integrate the store with it. If you're scoping a project, start with three answers: which ERP you run, how your prices are calculated, and whether buyers need a quote before they order. The full write-up is on projectthunder.com. Thanks for watching.

Narration is an AI voice (Azure). The facts come from the linked write-up.

More videos