Going international on Shopify: You're probably using Markets wrong

Most stores I work with know Shopify Markets exists. The problem isn't awareness, it's scope. They think of it as a currency converter with some language support bolted on. So when a real internationalization problem shows up, they reach for something else.

A client wants to block visitors from a specific country: they install a geolocation app. They want separate pricing logic per region: they spin up a second store. And then there's the one that still puzzles me: a client with serious name recognition that had a dedicated draft theme for the UK market. Different layout, different content. How they were activating it, I honestly never asked. I didn't want to know.

All of these are real solutions I've seen in production. None of them were necessary.

What Markets actually does

Markets lets you run a single Shopify store that behaves differently per region. Different currencies, languages, domains or subfolders, pricing, tax and duty calculations, and payment methods. All from one admin, one catalog, one codebase.

Beyond the basics, per-market checkout customization lets you add or remove checkout extensions, change branding, and tailor the entire checkout experience per region without touching code. Country and region restrictions let you control exactly who can access each market, no third-party geolocation app needed. And with multi-entity support you can map each market to its own legal entity with separate Shopify Payments onboarding and local payout currencies, which used to be the main reason people ran separate stores.

That last one matters. Needing separate legal entities used to be the most common reason to spin up a separate store. That blocker is largely gone now.

What I see in production

I've seen stores running three separate Shopify instances for three regions, tripling their app costs, integration complexity, and catalog maintenance overhead. In most of those cases, Markets would have handled it from day one.

The pattern is always the same: someone hit a problem, googled a solution, and implemented whatever came up first. Nobody stopped to check what the native tooling could actually do.

When multistore actually makes sense

Markets handles the vast majority of cases. But there are legitimate reasons to run separate stores:

• Distinct teams per region with separate roadmaps: A shared admin doesn't work when two teams are making conflicting decisions about the same store.
• Apps that need to behave differently per region: Apps install at the store level, not the market level. If you need an app active for one market and off for another, Markets can't do that natively.
• Genuinely different catalogs: Markets lets you publish products per market, but if the product range and business rules are fundamentally different across regions, a single catalog creates more problems than it solves.
• Data isolation: One admin means one analytics view, shared customer data, and no access controls per region. If regional teams need separation, you need separate stores.
• Customer support tooling: Shopify Inbox doesn't support language routing or per-market team assignment. If you're running a single store with Markets and have support teams for different regions, all conversations land in the same inbox. With separate stores, each store has its own Inbox and its own team. Not a dealbreaker for most, but worth considering if regional support is a real operational requirement.
• Complex B2B alongside B2C: Markets has B2B support, but deep wholesale logic with company-specific catalogs and checkout rules often works better in a dedicated store.

The default

Before installing a geolocation app, spinning up a second store, or creating a draft theme per country, check what Markets can do. The answer is usually more than you think, and the operational overhead of multistore is real. Tripled apps, tripled integrations, tripled maintenance.

Most stores running multiple instances for international markets set them up before Markets was capable enough, or before someone sat down to actually read the docs. If you're starting fresh, start with one store.