B2B Ecommerce Replatforming: What Actually Changes

B2B ecommerce replatforming fails for a reason that has almost nothing to do with which platform you pick. Teams plan it like a D2C migration with more SKUs. It isn’t one. In D2C the storefront is the commercial logic — one price, one checkout, one buyer. In B2B the storefront is a thin window onto contracts, credit terms, approval chains and an ERP that has been the system of record for years. Move the window, forget the wiring, and you launch a store that technically works and commercially cannot take an order.

So here is the short version: budget as much discovery for the commercial model — price lists, company accounts, payment terms, ERP sync — as you do for the storefront itself. Everything below is what that means in practice.

Why B2B ecommerce replatforming is a different project

The general case for moving is well covered — we wrote up the seven signs it’s time to replatform, and every one of them applies to wholesale too. What’s different in B2B is the failure mode. A D2C migration that goes wrong loses traffic. A B2B migration that goes wrong loses accounts: a buyer logs in, sees list price instead of the price they negotiated, and phones your sales rep instead of ordering. You don’t get an A/B test with wholesale customers. You get one impression.

Three structural differences drive everything else:

• Price is a relationship, not an attribute. The same SKU carries a different number for every account — sometimes for every location of every account.
• The buyer is a committee. A purchasing assistant builds the basket, a manager approves it, finance pays it on terms, and none of them is the person who negotiated the contract.
• The store sits downstream of the ERP. Stock, credit and pricing usually live elsewhere. The storefront’s job is to reflect them accurately, not to own them.

Miss any one of those and the migration plan is wrong before the first sprint.

The five things that never migrate cleanly

1. Customer-specific pricing

On legacy platforms, negotiated pricing is usually sediment: a discount table here, a plugin there, a hard-coded exception for the account nobody wants to lose, and a rep who applies a manual adjustment when the system won’t. None of that exports. Before you migrate anything, get the pricing model out of the platform and into a document you can reason about — which accounts, which products, which basis (percentage off list, fixed price, volume break), which expiry date. That document is the real deliverable of discovery.

2. Company accounts, not customer accounts

D2C platforms model one person, one login, one address book. B2B needs a company with multiple buyers, multiple ship-to locations, per-user permissions and a shared order history. If your current platform simulates that with customer tags or a bolt-on plugin, the structure will not survive an export — you are rebuilding it. Decide the model (who can order, who approves, who is even allowed to see pricing) before you decide where it lives.

3. Payment terms and credit

Card-on-checkout is the exception in wholesale. Net terms, purchase orders, credit limits and invoicing are the norm, and they are usually enforced by finance systems rather than by the store. Decide early whether the new platform holds the credit limit or simply asks the ERP for it at checkout. Both approaches work. Only one of them stays accurate.

4. The ERP integration

This is the line item that gets under-scoped in every B2B replatforming budget. The old integration was built for the old platform’s data shapes; the new one needs a fresh contract covering products, inventory, customers, pricing, orders and invoices — plus an explicit decision on direction and frequency for each. “Real-time inventory, nightly pricing, orders pushed on placement” is a normal answer. “We’ll point the existing middleware at the new API” is not. In practice this integration work consumes more of the timeline than the theme does.

5. Quotes, minimums and case packs

Request-for-quote flows, minimum order quantities, order multiples, case-pack units and mixed-pallet rules encode years of operational reality. They rarely exist as clean data — they exist as rules somebody wrote down once and everyone now remembers. Inventory them explicitly, because a storefront that happily accepts an order for seven units of a twelve-pack has created a warehouse problem, not a UX problem.

Shopify vs Magento for B2B: the honest read

This is the fork most wholesale teams actually face. Our full Shopify vs Magento comparison covers the general case; here is the B2B-specific cut.

The pattern is fairly consistent: if your pricing and approval rules can be expressed as price lists and roles, Shopify Plus removes an enormous maintenance burden. If your commercial model genuinely needs bespoke logic living inside the platform — and sometimes it does — Adobe Commerce earns its cost. The mistake is assuming you are in the second group because your current platform trained you to be. The platform-fit quiz is a fast sanity check, and if the decision is already made, our Magento to Shopify migration page covers how that particular move runs.

Sequencing the migration so it survives launch

Here is the structural advantage B2B has over D2C, and almost nobody uses it: you know exactly who your customers are. You can migrate them in cohorts instead of flipping the entire business on one night.

1. Model first, build second. Companies, locations, roles, price lists, terms. Sign it off with sales before a theme exists.
2. Contract the ERP integration. Every field, direction and frequency, agreed in writing. This is the critical path, so start it on day one.
3. Migrate data in dry runs. Products, companies, contacts, price lists, open orders, order history. Run it more than once — the second run finds what the first one hid.
4. Pilot with three to five accounts. Pick friendly, high-frequency buyers spread across different pricing tiers. Let them place real orders on the new platform while the old one is still running.
5. Reconcile before you widen. Every pilot order should match the ERP on price, tax, terms and stock.
6. Cut over in cohorts, with the redirects already live. Then decommission — not before.

Our free Shopify migration checklist covers the storefront and SEO tasks underneath all this; the B2B-specific work above sits on top of it.

The SEO part wholesale teams skip

There is a persistent assumption that B2B stores don’t need migration SEO because “customers log in anyway.” Two problems with that. First, most wholesale catalogues have a public layer — category pages, product pages, spec sheets, compatibility tables, technical guides — and that layer is frequently the top of the funnel for accounts you don’t have yet. Second, the logged-out URLs are the ones that have been accumulating links for years.

Treat it exactly like any other migration: crawl the old site, map every URL to its new home, and ship the 301 redirect map at cutover rather than the week after. If a product is discontinued, redirect it to its category rather than the homepage. And keep the pages that were never really product pages — the datasheets and compatibility tables — because in B2B those are often the best-ranking assets you own.

Frequently asked questions

How long does a B2B replatforming project take?

Longer than the storefront work suggests, and the variable is almost always the ERP integration and the pricing model rather than the design. Sequence it so integration discovery starts on day one; anything that waits for the theme to be ready delays launch by however long it waited.

Can we replatform without changing our ERP?

Yes — and usually you should. Replacing the storefront and the system of record simultaneously doubles the failure surface and makes every discrepancy ambiguous. Replatform, stabilise, then revisit the ERP if it turns out to be the real constraint.

Do we need Shopify Plus to sell B2B?

For Shopify’s native B2B features — company profiles, company-specific catalogs and price lists, payment terms at checkout — yes, those sit on Plus. Simpler wholesale setups can run on lower plans using apps or a separate wholesale channel, but you are trading platform-native behaviour for app dependencies, which is the same trade that made your current platform hard to leave.

The takeaway

B2B ecommerce replatforming is a commercial-model project wearing a web-project costume. The storefront is the easy half. Spend discovery on price lists, company structures, payment terms and the ERP contract; migrate your accounts in cohorts rather than in one night; and ship the redirects with the launch, not after it. Do that and the first Monday on the new platform looks like an ordinary Monday — which is the entire point of the exercise.

If you are weighing the move and want a second opinion on what would actually break, our free Shopify store audit is a sensible place to start.