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.
- Lives inside one of six modified themes
- One customer group per Company
- Stencil storefronts only
- Customized in theme JavaScript
- Works with any Stencil theme
- Companies can share customer groups
- Stencil, Catalyst and headless
- Configured in the control panel
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).
Capabilities side by side
| Capability | Legacy B2B experience | Buyer Portal |
|---|---|---|
| Theme | Modified versions of six themes only | Any Stencil theme; 21 support its buttons and sign-in links natively |
| Storefront types | Stencil | Stencil, Catalyst, headless |
| Multiple storefronts | — | Channel-aware, with settings per storefront |
| Companies and customer groups | Each Company needs its own customer group, which can't be reassigned | Independent Companies: many Companies share a group, or have none |
| Parent and subsidiary accounts | — | Account Hierarchy, up to 5 levels (requires Independent Companies) |
| Buyer roles | Predefined roles | Custom roles for finer access control |
| New Company applications | Can't restrict visibility while an application is pending | Restrict visibility and purchasing until the Company is approved |
| Registration | — | Limit registration to B2C, B2B or both |
| Quotes | Can't hide discounted totals or overquoting | Optional Sales Rep review; quote-only custom items |
| Invoices | Changing the invoice display needs substantial theme work | Invoice PDFs; pay several invoices at once |
| Company account pages | Changing the TPA form needs substantial theme work | Tabs, inline editing, unsaved-change warnings, file attachments |
| Wording and translation | Edited in theme JavaScript | Upload a CSV of text strings |
| Updates | Customizations depend on B3 element names and break when theme markup changes | Hosted Buyer Portal is updated by BigCommerce |
Sources: Buyer Portal Migration, B2B Edition, Independent Companies, Account Hierarchy.
What works differently or goes away
Plan for these before go-live, and tell buyers what's changing.
| Feature | On the Buyer Portal | What to do |
|---|---|---|
| Wish Lists | Replaced by Shopping Lists for all customers; storefront Wish Lists must be disabled | Tell buyers where their saved items live now. Existing wish list content must be manually or programmatically recreated as Shopping lists. |
| Order messages | Customers can't send or receive order messages; they can message on open quotes | Move order questions to quotes, email or your service desk |
| Stored payment methods | Usable at checkout, but not manageable in the portal | Buyers should update saved payment methods while checking out or paying open invoices. |
| Store credit | Applies at checkout, but isn't shown in the portal | Show balances another way if buyers rely on them |
| Recently viewed products | Not included | Custom development if you need it |
| Returns | Not supported in either experience | Keep your current returns process |
Source: BigCommerce Buyer Portal Migration.
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 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 →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.
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.