StrikeTru at AAPEX & SEMA 2026 • Nov 3–6 • Las Vegas • Meet Vik Gundoju, Principal Consultant & Founder • Schedule a Meeting

Legacy B2B Edition vs Buyer Portal: What Changes When You Migrate

The Buyer Portal replaces the legacy experience's modified theme with a standalone React app that works on any storefront.

It adds Independent Companies, Account Hierarchy, custom buyer roles and approval-gated access. In exchange, Wish Lists become Shopping Lists, order messages move to quotes, and a few account features need custom work. Returns aren't supported in either experience.

Architecture

How the two experiences are built

The legacy B2B experience runs inside specially modified versions of six Stencil themes and is customized through window.b3themeConfig settings. The Buyer Portal is a React app loaded through the Scripts API and powered by the B2B GraphQL API.

Because the Buyer Portal doesn't use Stencil's theme objects, it works on any Stencil theme, Catalyst or a headless storefront (BigCommerce, BigCommerce).

What you gain

Capabilities side by side

CapabilityLegacy B2B experienceBuyer Portal
ThemeModified versions of six themes onlyAny Stencil theme; 21 support its buttons and sign-in links natively
Storefront typesStencilStencil, Catalyst, headless
Multiple storefronts—Channel-aware, with settings per storefront
Companies and customer groupsEach Company needs its own customer group, which can't be reassignedIndependent Companies: many Companies share a group, or have none
Parent and subsidiary accounts—Account Hierarchy, up to 5 levels (requires Independent Companies)
Buyer rolesPredefined rolesCustom roles for finer access control
New Company applicationsCan't restrict visibility while an application is pendingRestrict visibility and purchasing until the Company is approved
Registration—Limit registration to B2C, B2B or both
QuotesCan't hide discounted totals or overquotingOptional Sales Rep review; quote-only custom items
InvoicesChanging the invoice display needs substantial theme workInvoice PDFs; pay several invoices at once
Company account pagesChanging the TPA form needs substantial theme workTabs, inline editing, unsaved-change warnings, file attachments
Wording and translationEdited in theme JavaScriptUpload a CSV of text strings
UpdatesCustomizations depend on B3 element names and break when theme markup changesHosted Buyer Portal is updated by BigCommerce

Sources: Buyer Portal Migration, B2B Edition, Independent Companies, Account Hierarchy.

Plan for these

What works differently or goes away

Plan for these before go-live, and tell buyers what's changing.

FeatureOn the Buyer PortalWhat to do
Wish ListsReplaced by Shopping Lists for all customers; storefront Wish Lists must be disabledTell buyers where their saved items live now. Existing wish list content must be manually or programmatically recreated as Shopping lists.
Order messagesCustomers can't send or receive order messages; they can message on open quotesMove order questions to quotes, email or your service desk
Stored payment methodsUsable at checkout, but not manageable in the portalBuyers should update saved payment methods while checking out or paying open invoices.
Store creditApplies at checkout, but isn't shown in the portalShow balances another way if buyers rely on them
Recently viewed productsNot includedCustom development if you need it
ReturnsNot supported in either experienceKeep your current returns process

Source: BigCommerce Buyer Portal Migration.

Custom work

What still needs custom work

Moving to the Buyer Portal removes the need for a modified B2B theme. It doesn't remove your business rules. Supplier minimums, custom product page content or shipment tracking still live in the theme. Order cancellation, supplier routing and stock updates still live in your integrations.

Sort your legacy customizations →
One-way decision

One decision you can't undo

Independent Companies can't be reverted once it's enabled (BigCommerce). Account Hierarchy depends on it. Design your customer groups before you switch it on.

How Account Hierarchy and Independent Companies work →
FAQ

Legacy vs Buyer Portal Questions

What's the difference between the legacy B2B experience and the Buyer Portal?

The legacy experience runs inside six specially modified Stencil themes. The Buyer Portal is a separate React app that works with any Stencil theme, Catalyst or headless, and adds Independent Companies, Account Hierarchy and custom buyer roles.

What do I lose when I move to the Buyer Portal?

Wish Lists become Shopping Lists and order messages move to quotes. Stored payment methods and store credit aren't managed in the portal, and recently viewed products need custom development. Returns weren't supported in the legacy experience either.

Do my legacy theme customizations carry over?

No. Legacy B2B theme customizations aren't compatible with the Buyer Portal. Each one becomes a standard feature, is rebuilt in an uncustomized theme, or moves to an integration.

Do my B2B Edition settings carry over?

Most existing B2B Edition settings carry over from the legacy experience, according to BigCommerce. You can then configure Buyer Portal settings globally or per storefront.

Can I use the Buyer Portal on Catalyst or a headless storefront?

Yes. The hosted Buyer Portal works on any storefront type, though setup differs for Stencil, Catalyst and headless. A custom, open-source version can be deployed alongside a headless storefront.

Free readiness assessment

Want to know exactly what changes for your store?

We map every legacy customization and feature you use to its place on the Buyer Portal.