Shopify Markets vs. Expansion Stores: Pick Markets First, and Know Exactly When to Leave It
Start every international expansion on Shopify Markets, not Expansion Stores — Markets is free on every plan, needs no new contract, and its SEO is handled for you inside one store. Expansion Stores are a Shopify Plus feature for a narrower set of cases: a genuinely separate storefront, catalog, or brand experience per region, and only for store types Shopify's organization admin actually recognizes as "expansion" stores. Here's the eligibility rule that trips people up, the cross-domain SEO work every comparison skips, and why there's no clean way back once you've split.
Start on Shopify Markets, not Expansion Stores, unless you already know you need a genuinely separate storefront per region. Markets runs inside your existing store on every plan from Basic up, needs no new contract, and handles currency, duties, and — this is the part every other comparison skips — your international SEO automatically. Expansion Stores are a Shopify Plus feature for a narrower set of cases, and Shopify won't even let you create one unless it fits a specific list of recognized types.
The comparisons already ranking for this question (Superco, Eastside Co, MindArc, and a handful of agency blogs saying much the same thing) frame it as centralization versus autonomy and leave it there. That framing is correct as far as it goes. It just stops before the three things that actually decide whether the choice is reversible: who owns the eligibility check, what happens to your search rankings when you cross a domain boundary, and what you cannot undo once you've built the wrong one.
What each option actually is
Shopify Markets is a feature of your one store, turned on under Settings > Markets. You define a market — a country or group of countries — and configure its currency, domains or subfolders, language, duties, and pricing from that one place. Products, inventory, customers, and orders all live in a single dataset. A shopper in Toronto and a shopper in Dublin are looking at the same store, routed to different local presentations of it.
Expansion Stores are something else entirely: separate .myshopify.com stores under the same Shopify Plus organization and contract. Shopify's own documentation on expansion stores for Plus organizations is explicit that "store settings, products, collections, and inventory aren't synced between stores" and that they "don't share data by default." Two expansion stores under one organization are, functionally, two independent stores that happen to bill through the same contract and share staff-management screens.
Those are different tools for different problems. Markets is for presenting one catalog to many regions. Expansion Stores are for running what are, in practice, separate businesses — different storefront experiences, different teams, sometimes different product ranges — without separate Shopify subscriptions.
The eligibility rule nobody else mentions
This is the detail that changes the decision for most readers before they get to weigh anything else: you cannot simply spin up a second Plus store and designate it an "expansion store" for the discount and shared management that implies. Shopify's organization admin only automatically recognizes five store types as eligible — international stores (same brand, different language, region, or currency), B2B wholesale stores, D2C stores for merchants who sell exclusively wholesale, employee-only stores, and physical-retail-only stores with no online transactions. Every one of those categories requires "identical branding, name, and products to the main brand." A second store for a genuinely different sub-brand, a totally different catalog, or an acquired business doesn't qualify through this path at all — that requires contacting Shopify Plus Support directly, and it isn't guaranteed.
An organization can run up to ten stores total under one Plus contract, and the B2B and D2C wholesale types are free — one each, per contract. That's a real cost consideration competitor write-ups gloss over: the "extra Plus subscription" framing some of them use isn't quite right for the two most common expansion cases.
The SEO gap every comparison skips
This is the part worth the most to get right, because it's the part that's hardest to reverse once it's live. Inside Markets, Shopify's own international SEO documentation states that canonical URLs and hreflang tags between your markets are "generated automatically based on your market and language configuration" and "update automatically when you add, remove, or change market domain and language settings." You still have work to do — we cover the theme and app patterns that break that automation in our Markets hreflang and canonical architecture guide — but the mechanism itself, and Shopify's awareness of every market variant, is native to one store.
Expansion Stores get none of that, because from Google's point of view they aren't market variants of one page — they're entirely separate websites on separate domains, each starting its own index history and its own domain authority. Any hreflang relationship between your .com store and your expansion store for Australia has to be built and maintained by hand, store by store, the way you'd link two unrelated sites — because that is, technically, what they are. None of the ranking comparisons for this query mention that this work exists, let alone that it scales linearly with every expansion store you add. If your reason for choosing Expansion Stores is autonomy for a regional team, budget for this as a recurring technical SEO task, not a one-time setup step.
Where Markets actually runs out
Markets isn't the answer in every case, and the honest limits are specific rather than a general sense that "serious" international brands eventually need something bespoke:
- You need a genuinely different storefront experience per region — different homepage merchandising, different theme, a different app stack — not just translated copy and local pricing on the same layout. Markets can vary content by market with metafields and conditional Liquid, but a theme built for one audience will always show its seams for a fundamentally different one.
- A regional team needs to operate independently: their own staff accounts scoped to their store only, their own app installs, their own release cadence that doesn't wait on a global content calendar.
- You're acquiring or operating a business that isn't the same brand — this doesn't qualify as an eligible expansion type either, and needs a direct conversation with Shopify Plus Support about your organization structure before you build anything.
- A market requires a payment or compliance setup Shopify Payments doesn't support in a way that's easier to isolate in its own store than to route around inside one.
None of those are "Markets is broken." They're cases where the thing you actually need — operational separation — is what Expansion Stores are for, and Markets was never designed to fake it.
What you can't undo
The comparisons that exist treat this as a preference you can revisit. In one direction, it mostly is: you can run a market inside Markets, decide it needs more autonomy, and stand up an eligible expansion store for it later, keeping the original as your global default. Going the other way is where people get stuck. There is no supported Shopify tool to merge two separate stores' order history, customer accounts, and reviews back into one — if you launch an expansion store and later decide you'd rather have run it as a market instead, you're looking at a manual data migration project, not a settings change. Decide which model a region needs before it accumulates a year of order history under the wrong one.
This decision doesn't change your currency or duties setup
One thing worth ruling out before you treat this as a bigger decision than it is: currency display and duties handling are Markets features either way, not a reason to choose Expansion Stores. Every market — whether it lives inside your main store or inside an expansion store — gets its own Markets configuration for local currency and its own duties settings, because Expansion Stores still use Markets internally to run their own international selling. We've covered exactly what Shopify's native multi-currency conversion does and doesn't handle and the duties-and-DDU decision Shopify pushed onto every merchant in August separately, and both apply the same way regardless of which architecture you land on here. Don't let a currency or duties limitation you've hit push you toward Expansion Stores — check whether the limitation is actually about store architecture first, because most of the time it isn't.
The one place the two decisions do interact: if a region needs a materially different duties strategy — say, delivered-duty-paid by default in one country and a carrier-collected model in another because of how your fulfillment partner operates there — that's configurable per market inside a single store. It's rarely, on its own, a reason to split into a separate store.
A decision checklist
- Testing a new country with the same catalog and brand? Markets. It's free, fast, and the SEO groundwork is already built for you.
- Running an established region with its own team, theme, or app stack? Expansion Store — if it's on Shopify Plus and fits one of the five eligible types.
- Adding a B2B wholesale storefront or a D2C arm for wholesale-only merchants? Expansion Store, and check the free-per-contract allowance before you budget for a second subscription.
- Not on Shopify Plus, or the new business doesn't share your brand and products? Neither option cleanly fits — Markets can't provide the separation you need, and Expansion Stores won't be auto-approved. Talk to Shopify Plus Support before committing to an architecture.
If you're already running Markets and want to know whether your current hreflang and canonical setup would survive a Search Console audit — or you're weighing an expansion store and want the cross-domain SEO plan scoped before you launch — run our free store scanner against your catalog first. For the architecture decision itself, our team scopes Markets and expansion-store builds for merchants who'd rather get this right once than migrate twice.