BigCommerce B2B Edition in 2026: What Actually Changed and What to Do About It
If you run a wholesale or distribution business on BigCommerce, 2026 has quietly been one of the busiest years the platform's B2B tooling has ever had. Not in the way a keynote is busy, with big names and bigger promises, but in the way that actually costs you a weekend: a pricing model that changed shape, a GraphQL field marked deprecated, a webhook payload that gained a timestamp, a checkout default that flipped for new stores.
None of these made headlines. All of them land on whoever maintains your store.
This is a working review of what changed in BigCommerce B2B Edition through 2026, what each change actually means, and what we would check on a client store this quarter. It is written for the person who has to make the decision, not for the person writing the press release.
Where BigCommerce B2B Edition sits in the 2026 lineup
First, a naming note that still trips people up on sales calls. BigCommerce's plan names changed. The lineup is now Core at $29 a month, Growth at $79, Scale at $299, and Performance starting from $1,499, all billed annually. If you are reading a 2024 comparison post that talks about Standard, Plus, Pro and Enterprise, you are reading about the same ladder under old names.
BigCommerce B2B Edition itself has no public list price. It is sold against a Performance contract, which means the real question is never "what does B2B Edition cost." It is "what does B2B Edition replace." For most of the merchants we work with, the honest answer is a spreadsheet, a rep's inbox, and about fifteen hours a week of someone retyping purchase orders.
The architectural fact that matters more than the price: a Company in B2B Edition carries a customerGroupId that maps it to a BigCommerce customer group, and that group is what determines the catalog and the pricing its buyers see. Companies can share a group, or stay unassigned and fall through to the default catalog. Everything else in this article is downstream of that one relationship.
If you are on the legacy Dependent Companies behavior, be aware of the trap: each Company maps one to one with a customer group, and once created you cannot reassign it to a different group. You can only delete it. That constraint is the reason so many older B2B stores carry hundreds of near identical price lists, and it is the reason the next change is the most important one on this list.
Cascading price lists end the one list per account problem
Here is the shape of the problem. You have 400 contract accounts. Most of them get standard wholesale pricing. About thirty of them negotiated something special, and of those, maybe eight negotiated something special on only a handful of SKUs. Under classic price lists, modeling that cleanly meant a full price list per account, because a price list either had a record for a variant or it did not, and if it did not, you dropped straight to the catalog price.
So you duplicated. And then every time your base wholesale pricing moved, you updated 400 lists.
Cascading price lists, in open beta since 10 July 2026, fix this by letting a price list fall back to other price lists before it falls back to the catalog. A layers field on the existing Price Lists create and update endpoints defines the fallback chain. There are no new endpoints to learn, which is a good piece of API design.
Resolution works like this. The shopper's channel and customer group select a primary price list. If that list holds a price record for the requested variant, it wins. If not, each fallback layer is checked in the order it appears in the array, and the first layer holding a record supplies the price. If no layer has one, the catalog price applies. You get up to five layers.
This means you can keep one real base wholesale list, layer it under every account specific list, and let each account list contain only the SKUs that account actually negotiated. An account list with eleven rows in it instead of nine thousand. When base pricing moves, you update one list.
There are four constraints worth writing on a sticky note before you start:
- Tax types must match. Inclusive price lists can only layer with inclusive lists, exclusive with exclusive. A mismatch returns a 422, not a silent fallback.
- Layering locks the tax setting. You cannot change
prices_entered_with_taxon a list that participates in a layer relationship, as primary or as layer. You have to unpick the relationships first. If you sell into both tax inclusive and tax exclusive markets, decide this before you build, not after. - The primary must be active. An inactive layer is skipped rather than treated as an error, which is useful, but if the primary list is inactive none of its layers are evaluated at all.
- Update semantics will bite you. On update, omitting
layersleaves existing layers untouched, an empty array removes all of them, and a populated array replaces rather than appends. A sync script that sends an empty array as a default will quietly flatten your entire pricing model.
That last one is the one we would guard with a test. It is open beta, so behavior can still change before general availability. Build it, but build it behind something you can roll back.
Account hierarchy models buyers who have branches
The second structural change addresses the customer who is not one customer. A franchise group with forty locations. A contractor with regional offices that each have their own budget but share a master agreement. Historically you either modelled each location as an unrelated Company and lost the group view, or modelled the group as one Company and lost per location control.
Account hierarchy lets Companies hold parent and child relationships, up to five layers deep, with up to 500 Companies in a single hierarchy. It is enabled by default on new BigCommerce B2B Edition stores. Existing stores can request it through support, and it requires the Buyer Portal experience along with Independent Companies behavior.
The part that changes day to day work is representation. A buyer with the right role can select a child Company and act on its behalf in the Buyer Portal and on the storefront: view its orders, its quotes, its invoices, and pay across them. A regional manager stops emailing your sales rep to ask what the Denver branch ordered last month.
Permissions got a matching upgrade. Hierarchy adds a scope level to buyer permissions, so you can build custom roles for people who oversee subsidiaries, and enable or disable subsidiary access per buyer. B2B Edition ships predefined roles, and you can define custom ones. One caveat for anyone planning complex role based access control: custom permissions through the Company Roles and Permissions API cannot be configured in the B2B Edition control panel. If you build them by API, they are maintained by API, and whoever inherits the store needs to know that.
Worth checking while you are in there: companyStatus is a small enum with real consequences. Zero is pending, one is approved, two is rejected, three is inactive. We have seen more than one store where self registered companies sat at pending for weeks because nobody owned the approval queue.
The storefront GraphQL deprecation you should not ignore
This one is a warning rather than a fire, but it is the change most likely to break a custom storefront eighteen months from now, when nobody remembers reading about it.
On 17 September 2026, BigCommerce deprecated the root company query on the Storefront GraphQL API, along with CompanyQueries.addresses. The replacement is customer { activeCompany { ... } }, which was introduced on 31 July 2026.
This is as gentle as a deprecation gets. There is no behavior change today, the deprecated fields still resolve, and pagination, address filtering and address sorting all work the same way on the new path. No sunset date has been announced.
That is also the problem. Nothing breaks, so nothing gets prioritized, so the migration sits in the backlog until the removal notice lands with a ninety day clock on it. We have watched this movie on three platforms now.
Two practical notes. First, the conceptual shift is worth understanding, not just the syntax: the old root query treated the company as a top level thing you asked about, while the new path treats it as context hanging off the authenticated customer. That is a more honest model, and it is a strong hint about where the API is heading. Second, be careful which fields you reach for. Several fields on ActiveCompany, including companyName, currentUser and companyRoles, are currently marked as alpha and labeled not for production use. Read the schema before you build against one, and expect companyName to return null for a super admin who is not masquerading as a company.
If you needed confirmation that activeCompany is where the investment is going, the last week of October supplied it. On 27 October, B2B Edition shopping list queries started returning totals and full item details. On 28 October, BigCommerce added Company user queries and mutations under activeCompany, with access governed by the caller's Company role. New capability is landing on the new path and not on the old one, which is the clearest signal you get short of a removal notice.
If you have a headless or Catalyst storefront with B2B features, grep your codebase for the root company query this week. The migration is usually an afternoon. Finding out you needed it is usually not.
Quote webhooks, and the timestamp that makes them usable
BigCommerce B2B Edition's webhook coverage expanded in March 2026 with a second phase that put quotes on the event bus: store/quote/created, store/quote/updated, store/quote/statusUpdated and store/quote/deleted, plus two events covering Super Admin assignment changes.
That is the raw material for the integration most distributors actually want, which is: when a quote moves, tell the ERP, tell the rep, and start the approval clock.
The September addition is small and disproportionately useful. As of 29 September 2026, GET /api/v3/io/rfq/{quote_id} returns updatedAt as a Unix timestamp integer, and archiving a quote with a PUT returns it too. The change is backward compatible, so nothing you built last year stops working.
Why it matters: webhook delivery is not ordered and not exactly once. Without a reliable last modified value, an integration either compared whole payloads to detect real changes or trusted the order events arrived in, and the second of those is a bug waiting for a traffic spike. With updatedAt, you can discard an event that describes a state older than what you already stored, and you can replay a backlog in the right sequence after an outage.
The pattern we would build: acknowledge the webhook immediately with a 2xx and queue the work, re-read the quote from the API rather than trusting the event payload, compare updatedAt against your stored value, and only then write to the ERP. Boring, and it survives Black Friday.
Checkout changes that reach B2B stores sideways
Three platform level changes landed in September that are not labeled B2B but will find you anyway.
Enhanced Checkout is now on by default for new stores. Store owners can turn it off under Settings, then Checkout, and on new stores the Checkout Settings API returns enhanced_checkout_experience as true. If you are launching a new B2B store, confirm which checkout you are actually testing against before you sign off on a purchase order flow.
Catalyst 1.12.2 gave each channel its own cart. The cookie now maps channel IDs to carts, and existing cookies migrate on the shopper's next cart action. For a single storefront this is invisible. For a multi channel B2B setup where the same buyer shops a retail channel and a wholesale channel, this is the behavior you always wanted and may have previously faked. Catalyst also now emits channel_id and hosting meta tags on every page, which makes support tickets considerably less mysterious.
Wallet shipping options can be filtered. Since 17 September, custom checkouts built on checkout-js can pass a filterAvailableShippingOptions callback to limit which shipping rates appear in Apple Pay, Google Pay and Stripe Link V2. This requires @bigcommerce/checkout-sdk 1.978.0 or later. For B2B stores carrying freight, LTL or customer-arranged shipping rates that a wallet cannot sensibly handle, this is the clean fix. Note the fallback behavior: if the callback rejects or throws, the wallet shows the unfiltered list, so a broken filter fails open rather than blocking checkout.
One more to grep for: a September documentation correction confirmed that Promotion Settings requires the store_v2_information scope rather than store_v2_marketing, and that site_id and channel_id are integers rather than strings. The APIs did not change, the docs did, which means any integration built from the old documentation may have been working by luck.
A short audit to run on your store this quarter
If you only have an hour, do these in order:
- Count your price lists. If the number is close to your number of contract accounts, you are the exact case cascading price lists were built for. Model one account as a proof before you plan a migration.
- Grep for the root
companyGraphQL query. Custom storefront, Catalyst app, mobile client, anything that talks to the Storefront API. Migrate tocustomer { activeCompany }now while there is no deadline pressure. - Check whether any integration writes
layers. Confirm it never sends an empty array as a default. This is a one line check that prevents a very bad afternoon. - Look at your pending company queue. Anything sitting at
companyStatuszero for more than a few days is a buyer who gave up. - Confirm your quote integration re-reads before it writes. If it trusts the webhook payload, add the
updatedAtcomparison. - Ask whether account hierarchy is enabled. If you have multi-location customers and the answer is no, that is a support request, not a development project.
Where this is heading
The direction of travel is clear enough from what BigCommerce said at Commerce Live in April 2026. Alongside cascading price lists and event driven webhooks, the company described AI driven purchase order automation and, more significantly for anyone planning a build, a roadmap that unifies B2B and B2C under one control panel and one storefront API layer.
That last item is the one to architect around. Today B2B Edition is, in places, a well integrated system sitting beside the core platform rather than inside it, which is why you deal with a separate API surface and separate documentation. If those layers converge, the stores that did well are the ones that kept their B2B logic in the platform's own primitives, companies, customer groups, price lists and roles, rather than in a custom layer bolted alongside.
Put differently: every change on this list rewards merchants who modelled their business in BigCommerce's objects instead of around them. That has not always been true of this platform. In 2026 it is.
Where oBundle fits
We are a BigCommerce partner with B2B specialized certification, and most of what is described here we have run on live stores rather than read about. If you are weighing a cascading price list migration, planning an account hierarchy rollout, or you just want someone to grep your storefront for that deprecated GraphQL query and tell you whether it is a problem, that is a conversation worth having.
Tell us what your pricing model looks like today and how many price lists you are maintaining. That one answer usually tells us most of what we need to know.