Shopify Plus multi-store, built so a change ships once.
When does one store stop being enough?
- You sell in several countries, and pricing and content differ by market.
- A wholesale or professional channel needs its own catalog, prices and access.
- A new brand would share operations, but not its storefront design.
- Each store runs its own copy of the theme, and fixes drift apart.
- The same app is set up differently in every store, and nobody knows why.
How does a multi-store build run?
- 01Map the storesBrands, markets, channels and entities, and where each one must differ.
- 02Choose Markets or storesUse Shopify Markets where one store can serve; add stores where it can’t.
- 03Share the foundationsOne theme codebase, one content model, custom apps built once for every store.
- 04Connect the dataProducts, prices and inventory kept aligned through your ERP, PIM or a sync.
- 05Roll out in phasesLaunch store by store or market by market, each phase priced first.
One setup, every store kept in step
- A map of stores and markets, with the reasoning
- One theme codebase deployed to every store
- A shared content model in metafields and metaobjects
- Custom apps built once, installed where needed
- Currencies, languages, domains and pricing set per market
- A release process that ships to all stores
- A record of what differs per store, and why
What usually goes wrong.
- Cloning the theme for each new store. Copies drift; deploy one codebase with per-store settings.
- Opening a store when Markets would do. Every extra store adds catalogs, apps and admin to maintain.
- Forcing different businesses into one store. Different catalogs, teams or rules can justify separate stores.
- Syncing data by hand between stores. Pick one source of truth and sync from it.
Retail and wholesale storefronts on one organisation
We moved a clinical skincare brand’s retail and wholesale business onto Shopify Plus: one consumer storefront and four B2B storefronts on one organisation and one theme, with checkout rules as Shopify Functions, programs as custom apps, and an ERP integration. In production, ongoing.
See case studiesWhat teams ask about multi-store Shopify Plus.
When should we use expansion stores instead of Shopify Markets?
Use Shopify Markets when one store can serve every country, with local currencies, languages, domains and pricing. Add expansion stores when a market or channel needs its own catalog, team, operations or brand. Many brands use both; the review decides where the line falls.
Can several storefronts share one theme?
Yes. One theme codebase is deployed to every store, and each store keeps its own settings, content and look. A fix or a new section ships once and reaches every storefront, instead of being rebuilt store by store.
How are apps and data shared across stores?
Each Shopify store has its own apps, products, prices and inventory. We build custom apps once and install them on every store that needs them, and keep data aligned from one source of truth, usually your ERP or PIM.
What does running several Plus stores cost?
Shopify’s fees for additional stores depend on your Plus plan, so we leave that line to you and Shopify. The cost we control is upkeep: we design the setup so a new store adds configuration, not another codebase to maintain.
How long does a multi-store build take?
It depends on how many stores, markets and integrations are in scope. The three-week Architecture Review produces the plan. The build then runs in phases, often a store or market at a time, each priced in writing before it starts.
Next steps
Related programs- Start hereArchitecture ReviewThree weeks, a fixed fee, and a roadmap your team can act on.
- B2B and wholesaleWholesale portals and B2B storefrontsWe design and build wholesale portals on Shopify that look like the brand, not back-office software: company accounts, catalogs and…
- B2B and wholesaleERP integrationWe connect Shopify and Shopify B2B to ERPs such as NetSuite and Microsoft Dynamics 365, so the ERP stays the source of truth for…
Start here
Plan every store before you open the next
In a three-week Architecture Review, the founder maps your stores, markets and data, and decides with you what to share and what to separate.