Plenty of brands still run wholesale on something that was never meant to last: a legacy B2B platform, a separate storefront on an old wholesale channel, a spreadsheet emailed to reps, or a password-protected page with a discount code. A Shopify wholesale migration is the move from that arrangement to native B2B in the same admin as your retail business.
This guide covers what native B2B actually replaces, what does not transfer cleanly, how to sequence the move without disrupting trading accounts, and when staying put is the right answer.
What a Shopify wholesale migration starts from
Four starting points, with very different migration shapes.
A legacy B2B platform — the heaviest, with years of accumulated pricing rules and integrations. A separate wholesale store — cleaner data, but a second catalogue that has drifted from the first. Manual order taking — almost no data to migrate and almost no rules written down. A discount-code workaround on the retail store — data is already in Shopify, but the pricing logic exists only in agreements nobody has consolidated.
Which one you are in determines whether a Shopify wholesale migration is mostly a data project, mostly a rules project, or mostly a process project.
What Shopify B2B replaces natively
Native B2B on Shopify covers more than most merchants expect: company records with multiple locations, buyers attached to companies with their own permissions, customer-specific price lists, payment terms, catalogue visibility rules and quantity rules — all inside the same admin and the same checkout as retail.
That last part is the real prize. One catalogue, one inventory pool, one set of orders, one theme to maintain. The duplicated-storefront tax disappears, and it is usually larger than the licence difference that prompted the review.
What a Shopify wholesale migration cannot transfer cleanly
| Element | Transfers? | Notes |
|---|---|---|
| Companies and contacts | Yes | Structure usually needs rethinking, not just importing |
| Price lists | Mostly | Percentage-off rules map well; per-SKU exceptions need review |
| Order history | Yes | As records; reorder functionality is rebuilt |
| Credit limits | No | Lives in your ERP or accounting system |
| Negotiated one-off terms | No | Frequently undocumented — this is the archaeology |
| Custom approval chains | Partly | Depends on complexity; some need building |
| Rep commission logic | No | Usually external |
Row five is where projects overrun. Every wholesale business has accounts on terms somebody agreed verbally years ago. Finding them before launch is unglamorous and non-negotiable — the alternative is discovering them when a long-standing customer is charged list price.
Shopify wholesale migration: model the pricing first
Before touching data, write down how pricing actually works. Not how it is supposed to work — how it works.
Most wholesale pricing is one of three shapes: a percentage off retail by tier, a fixed price list per customer group, or per-SKU negotiated pricing per account. The first two map cleanly onto price lists. The third is where volume determines effort, because a hundred accounts with individual exceptions is a data project rather than a configuration exercise.
Ask one diagnostic question: if a new product launches tomorrow, who decides its wholesale price for each account, and where is that written down? If the answer is a person rather than a rule, the rules need writing before the migration, not during it.
Do you need Shopify Plus?
Native B2B features sit on Shopify Plus. That is a real cost, and it should be weighed against what you are currently paying for a separate platform plus the maintenance of a second storefront.
Merchants running B2B on a workaround inside a standard plan can go a long way without upgrading — customer tags, hidden collections and manual price adjustments cover simple cases. Our guide to Shopify B2B company accounts covers what native accounts do that a workaround cannot, and the answer is mostly: scale without a person in the loop.
Sequencing a Shopify wholesale migration without disrupting trading
Wholesale customers place large, planned orders. A botched cutover is not an inconvenience; it is a missed delivery window for someone else’s business.
- Document the rules — pricing, terms, approvals, exceptions. Weeks, not days.
- Model companies and locations in Shopify before importing anything.
- Migrate a pilot group — five to ten friendly accounts across different pricing shapes.
- Run parallel for a cycle so the pilot can fall back without drama.
- Reconcile pilot orders line by line against the old system’s pricing.
- Migrate in waves by tier, keeping the old system readable but not writable.
- Decommission only after a full billing cycle has closed cleanly.
The pilot is where the undocumented rules surface. Skipping it moves that discovery to the wave migration, where it affects everyone at once.
Integrations decide the Shopify wholesale migration timeline
Wholesale rarely stands alone. ERP holds credit limits and stock, accounting holds invoices and terms, and a rep tool may hold the customer relationship. Those integrations, not the storefront, set the project length.
Map every system that needs to know about a B2B order before estimating anything. Our ERP sync guide covers the failure patterns; the wholesale-specific one is credit — if orders must be blocked against a live credit limit, that check has to happen somewhere, and it is not inside Shopify’s checkout.
When to stay where you are
Three honest cases. When approval chains are genuinely complex — multi-level authorisation with delegation and spend limits — and the current platform models them natively. When contract pricing is so account-specific that price lists become thousands of manual entries with no rule behind them. And when your wholesale business is small enough that manual order entry costs less than the migration would.
That third case is more common than agencies admit. Twenty accounts ordering quarterly is a spreadsheet problem, not a platform problem.
What improves after a Shopify wholesale migration
Beyond the obvious consolidation, three things reliably get better: inventory accuracy, because retail and wholesale finally draw from one pool; catalogue consistency, because there is one product record rather than two that drift; and reporting, because a B2B order and a DTC order are the same object in the same system.
That last one changes conversations. When wholesale and retail revenue sit in one report with the same definitions, decisions about stock allocation stop being negotiations between two sets of numbers.
Training reps and buyers is half a Shopify wholesale migration
Wholesale customers did not ask for your migration. Buyers who have placed orders the same way for six years will judge the new system against the muscle memory of the old one, and reps who lose their workflow will quietly keep using spreadsheets.
Three things reduce that friction more than any feature. Give buyers a short walkthrough of their own account, not a generic guide — their price list, their reorder path, their terms. Keep the first order supervised, with a rep available while it is placed. And migrate the reorder path first, because that is what most buyers do most of the time.
Budget for this explicitly. A Shopify wholesale migration that lands technically and fails on adoption looks identical to a failed migration from the outside.
Retail and wholesale in one admin: the operational catch
Consolidation is the main prize, and it brings one genuine complication worth planning for: a single inventory pool serving two channels with very different order shapes.
A wholesale order for four hundred units can empty stock that retail was relying on, in a single transaction placed at 3am. Retail sells continuously in ones and twos; wholesale arrives in blocks and expects to be honoured.
Decide the allocation rule before launch. The options are a reserved buffer for retail, separate locations feeding each channel, or accepting first-come-first-served and managing it commercially. All three are workable; discovering you never chose one is what produces the awkward call to a wholesale buyer.
What to measure after a Shopify wholesale migration
- Share of orders placed self-serve versus through a rep — the clearest adoption signal.
- Time from order to acknowledgement, which is what buyers actually notice.
- Pricing exceptions raised per month, which should fall as the rules get properly encoded.
- Reorder rate, the metric a good B2B experience moves fastest.
Starting the assessment
The first artefact is not a quote. It is a document listing your pricing shapes, your exception accounts, your approval rules and your integrated systems. Any agency scoping a Shopify wholesale migration without those four is estimating the easy half.
Our B2B and wholesale team starts by reading that document — and will tell you plainly when the honest answer is that your current setup is fine and the money belongs somewhere else.
