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

The Buyer Portal Customization Triage: What Happens to Your Legacy B2B Customizations

StrikeTru's method for deciding what happens to each legacy B2B Edition customization when you move to the Buyer Portal.

Each customization lands in one of four buckets: a standard Buyer Portal feature, a standard BigCommerce feature, a theme customization, or integration work. Most stores find a large share of their custom code can simply be retired.

Why first

Why triage comes first

Legacy B2B themes aren't compatible with the Buyer Portal. You switch to an uncustomized Stencil theme, or remove the B2B Edition customizations from your current one, so every customization has to go somewhere.

Sorting them before you start is what keeps a migration on budget, and how you avoid losing a business rule your buyers depend on (BigCommerce).

The method

Three questions, four buckets

Ask the three questions in order. The first "yes" decides the bucket. A customization that's "no" to all three stays in the theme.

Examples

The four buckets, with examples

These examples are typical of the legacy B2B stores we assess.

Legacy customizationBucketWhat happens
Manual setup of each business account1 · Buyer PortalCompany registration and approval are standard
User management, buyer roles and delegated purchasing1 · Buyer PortalStandard, with custom buyer roles
Different account screens for single- and multi-location buyers1 · Buyer PortalOne consistent portal shows each buyer only what they're allowed to use
Buyers in one organization who can't see each other's orders1 · Buyer PortalAccount Hierarchy gives combined views across Companies
One customer group per Company1 · Buyer PortalIndependent Companies lets Companies share groups
Payment options per account (PO, card, ACH)1 · Buyer PortalPayment method visibility is set per Company
Custom shared wish lists1 · Buyer PortalShopping Lists, for B2B and B2C buyers
Promotions that customizations prevented2 · BigCommerceStandard promotions, once the custom code is gone
Custom email templates or blog2 · BigCommerceStandard BigCommerce features
Supplier minimums and minimum order quantities3 · ThemeRebuilt in the new theme, including Shopping List rules
Supplier labels and delivery estimates on product, category and cart pages3 · ThemeRebuilt in the new theme
Product page changes (custom tabs, fields, unit pricing)3 · ThemeRebuilt in the new theme
Restricting new shipping addresses at checkout3 · ThemeRebuilt as a checkout customization on the latest B2B Edition checkout source
Order cancellation that updates the ERP and supplier systems4 · IntegrationRebuilt in the integration layer
Supplier IDs passed to the ERP with each order4 · IntegrationKept in the BigCommerce → SCM → ERP flow and retested
Out-of-stock and price updates from suppliers4 · IntegrationKept in the integration and retested
Returns handled through a form and the ERP4 · IntegrationKept outside BigCommerce; returns aren't supported in either experience

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

How to run it

How to run the triage

01

List every customization

Check the theme's templates and JavaScript (including any window.b3themeConfig settings), storefront scripts, checkout, and the apps and integrations connected to the store.

02

Note whether each one works today

Broken customizations are often the easiest wins, because the Buyer Portal replaces them.

03

Ask the three questions

Assign one bucket per customization.

04

Decide the action

Configure, rebuild in the theme, rebuild in the integration, or retire.

05

Size the work

Buckets 3 and 4 drive most of the cost and timeline. See also theme compatibility and integrations to retest.

Worksheet

The triage worksheet

One row per customization. A preview with sample rows:

CustomizationWhere it livesWorks today?BucketActionOwner
Supplier minimum order quantityThemeYes3 · ThemeRebuild, incl. Shopping ListsDeveloper
Shared wish list for approversThemePartly1 · Buyer PortalReplace with Shopping ListseCommerce
Supplier ID on ERP ordersIntegrationYes4 · IntegrationRetestIntegrations

Sample rows for illustration.

FAQ

Customization Triage Questions

Will my legacy B2B Edition customizations work on the Buyer Portal?

Not as they are. Legacy B2B themes aren't compatible with the Buyer Portal. Each customization becomes a standard feature, is rebuilt in an uncustomized theme, or moves to an integration.

What is the Buyer Portal Customization Triage?

It's StrikeTru's method for sorting legacy customizations into four buckets: standard Buyer Portal feature, standard BigCommerce feature, theme customization, or integration work. Three questions, asked in order, decide the bucket.

Which customizations usually become standard features?

Account setup and approval, user roles and delegated purchasing, per-account payment options, shared lists and multi-buyer visibility usually become standard Buyer Portal features.

Which customizations usually stay custom?

Business rules specific to your catalog or suppliers, such as minimum order quantities, supplier labels and custom product page content, usually stay theme customizations. Anything that changes data in an ERP or supplier system stays integration work.

Free readiness assessment

We'll fill in the triage with you

Your customizations sorted, sized and priced, with a dated plan for the migration.