Shopify Markets vs duplicate stores: which international setup wins in 2026

Selling internationally on Shopify in 2026 — single store with Markets, or multiple stores per region? The trade-offs nobody talks about.

If you’re selling internationally on Shopify, the question always comes down to: one store with Markets, or one store per country? Shopify wants you on Markets. The right answer is usually that — but not always. Here’s the version with the asterisks.

What Shopify Markets does

Markets lets a single Shopify store sell to multiple regions with:

  • Per-market pricing (USD in the US, GBP in the UK, EUR in EU)
  • Per-market domains or subfolders (example.com/uk, uk.example.com)
  • Per-market language
  • Per-market checkout (with local payment methods, taxes, duties)
  • Per-market product visibility (hide a product from the EU)

For most stores starting to expand, that’s enough.

When Markets is clearly right

  • You have one brand worldwide. Same product line, same brand voice, just translated.
  • Your inventory is centrally fulfilled. One warehouse ships globally, or you use 3PLs that can fulfil from any of them.
  • Your team is small. One store = one admin, one set of products, one set of orders. Sanity intact.
  • You don’t need radically different content per region. Maybe homepage banners change, but the product catalog is the same product catalog.

For 80% of DTC brands, Markets is the answer. End of debate.

When duplicate stores are the right call

Sometimes Markets isn’t enough:

  • You have separate legal entities per country. Each entity needs its own Stripe / payment gateway, its own bank account, its own tax compliance. Markets supports much of this, but if your auditors require complete separation, separate stores reduce risk.
  • You have radically different catalogs. Your US store sells fitness equipment; your UK store sells the same brand but pivoted into supplements. Different products, different categories, different team.
  • You have separate brands. Same parent company, different consumer-facing brands. This is multiple stores, full stop.
  • Region-specific app stacks. Your fulfilment app exists for the US but not for the UK; your loyalty app supports US dollar but not pounds. Sometimes Markets papers over this; sometimes it doesn’t.
  • B2B + B2C in different regions. Markets handles B2B, but if your US business is consumer and your UK business is wholesale-only, separate stores keeps the operating model clean.

The hidden cost of separate stores

People underestimate this. Per region:

  • Separate theme = separate maintenance. Update once = update three times.
  • Separate apps = separate billing.
  • Separate inventory = data sync layers (Stargate, Bold, custom).
  • Separate customer accounts = customers can’t move regions easily.
  • Separate analytics = harder global reporting.

We have a client running four stores who pays roughly 4× what they’d pay on one Markets store, plus a part-time engineer just to keep them in sync. They have reasons — but they’re real reasons, not just “we want separate stores.”

The Markets gotchas

Markets is good. It also has corners:

  • Currency switching is per-cart, not seamless across the session in older themes. Newer themes (Dawn 11+, Horizon) handle this; older customs may not.
  • Local payment methods need explicit enabling per market. Don’t assume Bancontact and iDEAL just work.
  • Duties and import taxes — Markets supports DDP, but you have to configure HS codes per product. Doing this for 5,000 SKUs is a project.
  • Discount codes are per-market by default, but customer-facing UX can be confusing if you accidentally publish a US-only code on the EU site.
  • Subscriptions can break. If you use a subscription app, verify it supports per-market pricing before launching.

A practical decision tree

  1. One brand, one product line, central fulfillment? → Markets.
  2. Different brands or radically different catalogs? → Multiple stores.
  3. Legal/audit constraints requiring entity separation? → Multiple stores.
  4. Everything else? → Markets, but pilot one secondary region first before opening five.

If you’re already running multiple stores and considering consolidating: it’s almost always worth it once your team can absorb the migration project. The maintenance savings compound.

What Shopify is doing next

Shopify keeps shipping Markets features that close the gap with multi-store: B2B per-market, per-market metafields, per-market subscriptions. The gap is shrinking. In 12 months, more “we need separate stores” use cases will fit Markets cleanly.

If you’re starting fresh today, default to Markets. You can always split later. You can rarely consolidate gracefully.

— Read next

Shopify Customer Accounts vs Classic Accounts — what changed and what breaks

— Hit a wall?

We can help building properly?