Most merchants scaling a Shopify store internationally hit the same fork in the road: keep everything in one store and switch on more markets, or spin up a separate store for each region. Shopify supports both, they solve different problems, and picking the wrong one costs you months of migration later. The decision is not really about translation, but translation is where the cost of the wrong choice shows up first, because a duplicated storefront means duplicated language work forever.
This guide compares Shopify Markets and expansion stores the way a merchant or agency actually has to decide: by catalog, inventory, team, legal entity, SEO, and total maintenance load. We focus on the architecture trade-off and the operational reality of running each one. Legal-entity formation, tax registration, and banking are out of scope; talk to a finance and legal advisor for those, because as you will see, they are often the deciding factor.
What is the difference between Shopify Markets and expansion stores?
Shopify Markets runs multiple countries from a single store: one admin, one product catalog, one inventory pool, one theme, one checkout, and one set of apps. Each market gets its own currency, language, pricing adjustments, domains or subfolders, and (on higher plans) catalog customizations. You manage the whole operation from one place.
Expansion stores are separate Shopify stores, each with its own admin, catalog, inventory, theme, checkout, customer data, and app stack. They are provided to organizations on the Shopify Plus plan as a way to run distinct storefronts under one organization; on other plans, opening another store simply means another standalone subscription. Nothing is shared by default, which is the point.
The one-line rule: Markets centralizes, expansion stores isolate. Everything else follows from that. Markets minimizes duplicated work and consolidates data; expansion stores maximize independence at the cost of duplicated work. Neither is universally correct, and the right answer depends on how much your regions actually have in common.
When to use Shopify Markets
Choose Shopify Markets when your regions are variations of the same business rather than different businesses. Concretely, use Markets when the following are true:
- Shared brand and catalog. You sell mostly the same products under the same brand, with regional differences limited to price, currency, language, and availability.
- One team, one operation. The same people manage merchandising, content, and fulfillment across regions, and you want one dashboard, not five.
- Consolidated reporting matters. You want orders, customers, and performance in a single store so basic questions (“what is our best product globally?”) have a single answer.
- SEO authority should compound. Serving locales as subfolders on one domain keeps link authority on a single domain and makes hreflang far simpler to maintain.
Markets is built into every Shopify plan and is Shopify’s recommended path for most international expansion in 2026. The operational savings are real: one theme to update, one app stack to pay for and maintain, one checkout to test. When every store has its own theme, apps, and settings, your team spends a large share of its time just keeping them aligned. Markets removes that drag.
The trade-off is that markets share a foundation. If Germany needs a genuinely different product assortment, a different fulfillment model, and a different legal seller than the US, bending Markets to fit fights the tool.
When to use expansion stores
Choose expansion stores when a region is not a variation of your business but effectively a different business. Use separate stores when one or more of these is true:
- Separate legal entity or tax obligation. A different registered company sells in that market, with its own tax registration, contracts, and bank account. This is the single most common legitimate reason.
- Radically different catalog. The assortment barely overlaps between regions (different SKUs, different suppliers, different compliance labeling), so a shared catalog would be mostly exceptions.
- Full operational independence. Separate country teams, separate customer service, separate fulfillment rules that cannot be shared, or separate brands that should not touch each other’s data.
- Region-specific compliance. Local rules require isolated customer data, checkout behavior, or storefront content that a single store cannot cleanly express.
Expansion stores give you a clean slate per region, which is exactly what you want when the regions genuinely diverge. The cost is that every shared thing is now duplicated: product edits, theme changes, app configuration, and translation all happen N times instead of once. That duplication is manageable when regions are truly independent and painful when they are not, which is why Shopify’s own guidance leans toward merging expansion stores into Markets when the stores mostly sell the same brand and experience.
Head-to-head comparison
The table below summarizes the practical differences merchants care about when scaling.
| Dimension | Shopify Markets | Expansion stores |
|---|---|---|
| Stores to manage | One | One per region |
| Catalog & inventory | Shared | Separate per store |
| Theme & apps | One set | One set per store |
| Currency & pricing | Per market | Per store |
| Languages | Per locale, one store | Per store, translated again |
| Domains | Subfolders or ccTLDs on one store | Separate domain per store |
| Reporting | Consolidated | Split across stores |
| Legal entity | Typically one | Can differ per store |
| International SEO | Authority consolidated | Authority split |
| Maintenance load | Low | High (multiplies per store) |
| Best for | Same brand, similar catalog | Genuinely separate businesses |
Read the table top to bottom and a pattern appears: almost every row favors Markets on effort and favors expansion stores only when isolation is a hard requirement. That is the whole decision in miniature. If you cannot point to a specific row where isolation is mandatory (usually the legal-entity or catalog row), you probably want Markets.
The translation layer is the real work either way
Here is the part both architectures share and neither solves for you: translation is the layer that determines whether the second market actually sells. Shopify Markets lets you attach a language to each market, but attaching a language is not the same as having translated, native-quality content. You still need every product, collection, page, menu, and metafield rendered correctly in each locale.
In the Markets model, you translate once per locale inside one store, and shared products carry their translations across markets that use the same language. In the expansion-store model, the same product has to be translated inside each store that sells it, so a five-store setup translating into the same language can mean paying for and maintaining that translation five times. This is the hidden multiplier that makes the wrong architecture expensive: it is not the store count, it is the language work times the store count.
This is where LocaleFlow fits. In the recommended Markets architecture, LocaleFlow translates the full resource set (products, collections, pages, blogs, menus, metafields, and image alt texts) across all your locales from one configuration, and re-syncs when your content changes. You can see the exact field-level controls for which resource types are in scope. Setup takes about five minutes, and pricing is clear tiers — $49/month for 2 languages, $150/month for unlimited (Global) — with no word counts or per-word overages, so adding a locale does not add a bill. The translation layer is work you own in either architecture; the goal is to do it once, not once per store.
How to decide: a short checklist
Work through these in order. The first “yes” that forces isolation points you to expansion stores; if you reach the end without one, use Markets.
- Does a different legal entity sell in the new region? If yes, and finance confirms it must be separate, lean expansion store.
- Does the region need a fundamentally different catalog (not just different prices or availability)? If yes, lean expansion store.
- Do local compliance rules require isolated customer data or checkout? If yes, lean expansion store.
- Will a separate team run the region as its own business with its own brand and support? If yes, consider an expansion store.
- If none of the above are true, use Shopify Markets, serve locales as subfolders, and translate once per locale.
- Whichever you choose, budget for the translation layer explicitly, and plan for native-quality output on your top products rather than raw machine output.
For a deeper walk-through of translating inside the Markets model, see our Shopify Markets translation guide. For a worked example of how much a single high-value market can demand beyond language, our Shopify localization guide for Japan shows why “attach a language” is only the first layer.
The mistakes we see most often
Opening expansion stores by default. Teams reach for a new store because it feels clean, then discover they are maintaining the same catalog and theme three times. Start from Markets and justify the exception.
Underestimating the translation multiplier. The store count looks like the cost. The real cost is translation times store count. Two stores selling into German and French is four translation surfaces to keep in sync, not two.
Splitting SEO authority without meaning to. Separate domains per region divide your link authority and multiply hreflang maintenance. Unless a region needs its own brand domain, subfolders on one store usually win for SEO. See our multilingual SEO guide for the hreflang details.
Migrating before finance and legal weigh in. The one input that genuinely forces expansion stores is the legal-entity and tax picture. Confirm which entity sells in each market before you pick an architecture, not after.
Conclusion
Shopify Markets and expansion stores are not competing products; they are two answers to “how independent is this region?” If your regions share a brand, a catalog, and a team, Markets is the 2026 default: less to maintain, consolidated reporting, and SEO authority that compounds on one domain. Expansion stores are the deliberate exception you choose when a region is legally or operationally a separate business, and you accept the duplicated work that comes with isolation.
Whichever you pick, the translation layer is yours to own, and it is where the wrong architecture quietly gets expensive. LocaleFlow handles that layer in the Markets model: full-resource translation across every locale, auto-synced, at a flat price that does not grow when you add a language. Start translating when your market structure is set, and talk to a finance advisor before you commit to separate stores.