Shopify Markets vs Expansion Stores: Which Architecture to Choose

Every brand selling into a second country hits the same fork: run one store that handles multiple markets, or run a separate store per region. On Shopify that is the Shopify Markets vs expansion stores decision, and it is an architecture choice rather than a settings choice — it determines how your catalogue, pricing, content, tax logic and reporting behave for years afterwards.

This Shopify Markets vs expansion stores guide covers what each approach actually does, where each one breaks, and the four questions that decide it faster than any feature comparison.

What Shopify Markets does

Markets lets a single Shopify store sell into multiple countries from one admin. You configure which markets you sell to, then per market you can control currency and pricing, domains or subfolders, language, duties and import taxes, and which payment methods appear.

The important word is single. One product catalogue, one inventory position, one set of orders, one theme. Everything is a variation on that shared foundation rather than a copy of it.

What an expansion store is

An expansion store is a separate Shopify store for a region, sharing your Shopify Plus contract. Its own admin, own catalogue, own theme, own apps, own staff permissions and own reporting.

Complete independence is the feature and the bill. Each store is a real store that somebody has to run — and the operational load is roughly linear in the number of stores, which is the part that gets underestimated.

Shopify Markets vs expansion stores, side by side

The four questions that decide Shopify Markets vs expansion stores

Skip the feature list and answer these.

1. Is the catalogue meaningfully different per region? Not “slightly” — meaningfully. Different products, different compliance labelling, different bundles. If yes, expansion stores. If the difference is price, currency and a handful of unavailable SKUs, Markets handles it.

2. Is inventory shared or genuinely separate? One warehouse serving several countries points to Markets. Regional entities holding their own stock and their own P&L point to expansion stores.

3. Who operates the store day to day? One central team is a Markets answer. Autonomous regional teams who need to publish without asking anyone are an expansion store answer, and this is more often the deciding factor than anything technical.

4. Is there a legal entity per region? Separate entities, separate tax registrations and separate payment processing frequently force separate stores regardless of what would be technically elegant.

Most mid-market brands answer “no, shared, central, one” and should therefore start with Markets. Most who chose expansion stores first did so because a single regional requirement was allowed to dictate the whole architecture.

The SEO consequences are not symmetrical

This is where the Shopify Markets vs expansion stores choice has the longest tail.

With Markets you run subfolders or country domains from one store, and hreflang is generated for you. Authority accumulates in one place, which is a real advantage when you are entering a market rather than dominating it.

With expansion stores, each store is a separate site to search engines. Authority is built separately per domain, duplicate content across regions needs deliberate handling, and hreflang becomes cross-domain configuration you own. Done properly it works. Done casually it produces several thin sites competing with each other.

Our Shopify Markets SEO guide covers the subfolder versus subdomain versus ccTLD question in more depth, since that decision compounds faster than the platform one.

Shopify Markets vs expansion stores on cost, honestly

Expansion stores are included in the Shopify Plus contract, which makes them look free. They are not.

Apps are billed per store, and for a brand running fifteen apps that multiplies quickly. Theme changes are deployed per store, so a design update becomes five deployments. QA multiplies the same way. Staff training multiplies. Reporting consolidation becomes a data project rather than a tab in the admin.

Markets concentrates that cost differently: the complexity lands in your theme and your data model instead of in your operations. Localisation logic, market-specific merchandising and per-market content all live in one codebase that has to stay readable.

One store is cheaper to run. Several stores are cheaper to differentiate.

Tax, duties and landed cost

This is the area merchants most often assume is handled and most often is not.

Markets can calculate and collect duties and import taxes at checkout, which turns an unpleasant surprise at the customer’s door into a line on the order. That single capability does more for international conversion than most merchandising work, because unexpected charges on delivery are a leading cause of refusals and chargebacks.

Expansion stores give you complete control of tax configuration per store, which matters when a regional entity has its own registrations and files its own returns. The cost is that each store’s tax setup is maintained separately, and a rule change in one is not a rule change in the others.

Neither approach removes the need for advice on where you are registered and what you owe. The Shopify Markets vs expansion stores decision determines who maintains the configuration, not whether you need to get it right.

Payments and local methods

Conversion in a new market often depends less on language than on whether the payment method people expect is present. iDEAL in the Netherlands, Klarna across much of Europe, Bancontact in Belgium, and local card schemes elsewhere.

Markets lets you surface different payment methods per market from one store, which covers most needs. Where it runs out is when a region requires a separate merchant account or a local acquiring relationship that is store-level rather than market-level — at which point an expansion store stops being a preference and becomes a requirement.

Check this before you choose. It is one of the few constraints that can invalidate an otherwise sound architecture after the build has started.

Translation and content operations

Markets handles translation through Shopify’s localisation layer: one theme, translated strings, translated product content, and per-market content where needed. It works well when the message is the same everywhere and only the language changes.

It works less well when regions want genuinely different marketing — different hero campaigns, different category emphasis, different tone. You can build that into one theme with market conditionals, but each conditional makes the theme harder to reason about, and there is a point past which the theme becomes the bottleneck rather than the platform.

Expansion stores solve that by separation, at the cost of duplicating every change that is not region-specific. The question to ask is what share of your content is genuinely regional. If it is under a quarter, conditionals are cheaper. If it is over half, separation probably is.

Moving between the two later

Both directions are possible in a Shopify Markets vs expansion stores move; they are not equally painful.

Splitting a market out of Markets into its own store is the easier path. You export the region’s catalogue and customers, stand up a new store, redirect the relevant URLs and accept a period of rebuilding local authority. Disruptive but bounded.

Consolidating several expansion stores into one Markets setup is a genuine project. Catalogues must be reconciled where the same product exists under different handles, customer records deduplicated across stores, order history merged for reporting, and URL structures mapped across domains without losing rankings. We quote these regularly and they are consistently larger than merchants expect.

That asymmetry is the strongest practical argument in the whole Shopify Markets vs expansion stores debate: start consolidated, split deliberately when a region earns it.

Where Markets runs out in a Shopify Markets vs expansion stores setup

Being specific matters more than being balanced here. Markets struggles when regional catalogues genuinely diverge; when a region needs a substantially different theme rather than a localised one; when local teams need publishing autonomy that a shared theme cannot grant; when app requirements differ sharply per market; and when local payment or fulfilment logic demands settings that are store-level rather than market-level.

Hitting one of those is not a reason to abandon Markets. Hitting three usually is.

The hybrid most brands end up with

The common mature answer to Shopify Markets vs expansion stores is not either-or. It is a primary store running Markets for the majority of countries, plus one or two expansion stores where a region genuinely needs independence — typically a market with its own legal entity, its own warehouse and its own team.

That works well as long as the split is deliberate. What does not work is drifting into it: adding an expansion store because one requirement was inconvenient, then another, until you are running five stores nobody planned and cannot consolidate.

Choosing between Shopify Markets vs expansion stores today

Start with Markets unless one of the four questions above forces otherwise. It is markedly easier to split a market out of a single store later than to merge five stores into one — the second migration involves reconciling five catalogues, five customer bases and five sets of URLs, and it is one of the more expensive projects we get asked to quote.

If you are already running several stores and suspect the structure has outgrown its reasoning, our migration and replatforming team audits multi-store setups specifically for consolidation opportunities — and will tell you plainly when the answer is to leave it alone.