Multi-store setups: when you need more than one store
The cases that justify a second store, the cases one store with market settings handles, and how to run several without running several businesses.
The short answer
Most reasons that used to require several stores are handled from one. Markets gives each country or region its own language, currency, pricing, domain or path, shipping and tax settings from one catalogue, one stock and one set of operations. A second store is justified by a genuinely different business rather than a different geography: another brand with its own identity, a substantially different catalogue, a separate legal entity whose orders and payouts must be kept apart, or wholesale that cannot share the retail store even with native business features. Every additional store multiplies the operational work: another theme, app set, integration, release process and team attention. Where several are unavoidable, share everything that can be shared and run them as instances of one operation.
One store with Markets versus several stores
| Need | One store with Markets | Several stores |
|---|---|---|
| Several countries, same products | Yes | Unnecessary |
| Local language, currency, prices, domain | Yes | Yes, at higher cost |
| Different catalogue per market | Partly: products can be limited per market | Yes |
| Separate brand and identity | No | Yes |
| Separate legal entity, payouts, accounting | Limited | Yes |
| Wholesale alongside retail | Native B2B features from one store | When B2B needs its own experience |
| Operational cost | One of everything | One of everything per store |
Deciding
- Name the difference that seems to require a second store: geography, language, catalogue, brand, entity, channel.
- If it is geography or language, use Markets from one store.
- If it is partly catalogue, check whether per-market product availability in Markets covers it.
- If it is brand, entity or an incompatible channel, a second store is justified; write down why.
- Design the shared foundations before opening the second store: design system, app list, integrations, team, release process.
- Centralise inventory and orders through the back office integration so stock and fulfilment stay single.
Running several stores well
Shared design tokens and components, so a change to the brand’s shared elements propagates. One approved app list, with the same apps configured the same way. One integration layer between all stores and the back office, so inventory and orders are handled once. One team, one backlog, one release process across stores. Reporting that consolidates across stores by default. And a standing question at each quarterly review: does this store still need to be separate?
What this means for you
Use one store with Markets for international selling and open a second store only for a genuinely different brand, catalogue, entity or channel, with the reason written down. Design the shared foundations before opening it, centralise inventory and orders, and run every store as an instance of one operation. The subscription is the small cost of a second store; the operations are the large one, and sharing is how it stays manageable.
Frequently asked questions
We sell in three countries. Do we need three stores?
Almost certainly not. Markets gives each country its own language, currency, prices, domain or path and shipping and tax settings from one store, with one catalogue, one stock and one set of operations. Separate stores per country were the older answer, and they triple every piece of work. Use Markets unless a country needs a genuinely different catalogue or entity.
When is a second store the right answer?
A separate brand with its own identity and catalogue; a different legal entity whose orders and payouts must be kept apart; wholesale with a catalogue, pricing and experience that cannot live alongside retail even with native B2B features; or a market whose catalogue is mostly different. In each case the difference is in the business, not in the geography.
How do we keep several stores consistent?
Share the foundations: one design system mirrored across themes, one approved app list, one integration layer feeding central inventory and orders to the back office, one team with one release process. Treat the stores as instances of one operation rather than independent shops, or they diverge within a year.
Sources
- Shopify Help Center: Markets (accessed 2026-09-12)