Shopify Markets: selling internationally without a headache

International expansion on Shopify used to mean one of two painful paths: a single store straining under currency and language hacks, or a fleet of region-specific stores that multiplied your operational overhead. Shopify Markets — generally available since late 2022 and now substantially deeper with Markets Pro — collapses most of that complexity into a single-store model that is genuinely production-ready for mid-market and enterprise merchants. This article explains the architecture, the trade-offs, and the moments when a multi-store approach is still the right call.

The Markets data model

A Market is a named group of countries/regions that shares a common storefront experience. Each market carries its own settings for currency, language, domains (or subfolders), product pricing, and — on Plus — tax and duty handling. The primary market is your default store experience; secondary markets are created per region and can diverge on any of these dimensions without affecting each other. You can think of Markets as a layer of configuration on top of your single product catalogue that transforms how that catalogue appears and prices itself for each geographic context.

Each market can be assigned one or more domains or subfolder paths. Subfolders (e.g., example.com/fr-ca) are simpler to set up and keep your SEO domain authority consolidated on a single domain. Country-code top-level domains (e.g., example.de) can earn stronger local SEO signals in markets where Google weights ccTLDs more heavily, but require DNS management, SSL provisioning, and ongoing maintenance for each. Most merchants launching international for the first time start with subfolders and switch to ccTLDs only if their SEO strategy specifically demands it.

Each market also gets its own price list — independent of B2B price lists. You can set a fixed EUR price for every variant sold in the EU market that holds regardless of exchange rate fluctuations, or let Shopify apply automatic currency conversion from your base currency using live exchange rates with configurable rounding rules. Fixed market prices require more management overhead (you are responsible for updating them when pricing changes) but eliminate the "my prices changed overnight" support tickets that automatic conversion can generate when exchange rates move significantly.

Markets vs. Markets Pro

Standard Markets is included with all Shopify Plus plans. Markets Pro is an add-on (powered by Global-e) that layers on guaranteed duties-and-taxes calculation, landed-cost pricing at checkout, international payment method coverage (150+ local methods), and Global-e's fraud liability protection. The practical difference is significant at checkout: standard Markets shows an estimated or excluded duties line depending on your configuration; Markets Pro shows a guaranteed landed cost that the merchant is not liable to adjust post-purchase. For cross-border DTC brands selling into markets with complex customs rules — Southeast Asia, the Middle East, Brazil — the guaranteed landed cost is a meaningful abandonment reducer.

Setting up a new market: the recommended sequence

Creating a market in the Shopify Admin takes minutes, but the devil is in the configuration decisions made afterward. Here is the recommended sequence for a European market expansion that most Plus merchants will encounter.

1. Create the market under Settings → Markets → Add market. Assign countries. Shopify will suggest a default currency based on the country group. You can create a single EU market covering all Eurozone countries, or separate markets for France, Germany, and Spain if you want independent pricing or promotions per country.
2. Choose domain strategy: subfolder (recommended for launch) or dedicated domain. Subfolders are provisioned automatically at no additional cost; ccTLDs require a separate domain, DNS configuration pointing to Shopify, and automatic SSL provisioning through Shopify's integration. The performance difference between the two is negligible on modern CDN infrastructure.
3. Set pricing strategy: choose between automatic conversion (with an optional rounding rule, e.g., round to nearest .99) or fixed per-market prices. Fixed prices require a CSV import or API calls but eliminate exchange rate volatility. For high-AOV or margin-sensitive categories, fixed prices are worth the maintenance overhead.
4. Translate content via the Translate & Adapt app or the Translations API. Translations are tied to the market's locale. A French-Canadian market can have fr-CA translations independent of a France fr market. Machine translation via Translate & Adapt is good enough for initial launch; professional translation for high-traffic pages is worth the investment once the market is validated.
5. Configure duty and tax settings: decide whether to collect duties at checkout or show them as an estimate or exclude them. Each choice has different implications for customer experience and legal compliance in various markets. VAT-inclusive pricing is expected in most European markets; presenting pre-tax prices is a UX failure that will hurt conversion.

Subfolder routing gotchas and hreflang

Shopify automatically generates hreflang tags for all market URLs. These tell search engines which URL to serve for which locale/region combination. The main risk is incorrect x-default assignment. Shopify sets x-default to your primary market's URL, which is correct in most cases. Verify this in Google Search Console after launch by checking the International Targeting report — incorrect hreflang can silently cause your primary market pages to lose ranking in target languages for months before you notice.

Subfolder routing also interacts with your theme's navigation. Internal links in Liquid templates that are hardcoded as absolute paths (e.g., /collections/sale) will bypass subfolder localisation and land the shopper on the primary market, stripping their localised session. Use Liquid's routes object (e.g., {{ routes.collections_url }}) for all internal links. On Hydrogen, the built-in LocaleProvider and Link component handle locale-prefixing automatically, but absolute path strings in custom components will still bypass it. Do a codebase audit for hardcoded href strings before launching.

Single-store multi-market vs. multi-store: when to choose each

Single-store multi-market (the Markets model) is the right default for most merchants. You manage one product catalogue, one theme codebase, one set of apps, and one subscription. Market-specific overrides — pricing, language, product visibility via market-scoped publications, tax configuration — are layered on top without forking your stack. Promotional campaigns, inventory, and fulfilment all remain centralised. For brands that are genuinely one company selling the same products in multiple regions, this is the correct architecture.

Multi-store makes sense when regions have fundamentally different product catalogues (a Japan store that carries 300 unique SKUs not sold elsewhere), when regulatory requirements demand data residency separation (healthcare and financial products in certain jurisdictions), or when regional business units demand independent operational control with their own marketing and merchandising team. The cost is real: separate theme deployments, separate app installations, separate Shopify subscription fees, and cross-store inventory synchronisation via a custom integration. Several Plus merchants use a hybrid approach — one primary store with Markets handling currency and language for most regions, and a single separate store for one high-complexity market like Japan or Brazil where the product mix and regulatory environment genuinely warrant it.

Takeaways

Shopify Markets is mature enough for most international DTC and B2C use cases. The data model is clean — one market, one domain strategy, one price list, one set of translations — and the Storefront API surfaces it all transparently in a single buyer context. Invest time up front on your domain strategy and pricing approach; both are painful to change after your SEO has indexed thousands of localised URLs. Start with standard Markets and subfolders, validate the market before optimising, and consider Markets Pro once cross-border volume justifies the landed-cost guarantee. Only reach for multi-store when single-store complexity genuinely breaks your operational model.

Market-scoped product visibility and catalogs

Beyond pricing and language, Markets also supports market-scoped product visibility. A product can be published to your primary market (US) but not to your EU market — perhaps because you do not have regulatory certification for that product in the EU, or because it requires a different variant with EU-compliant labelling that is a separate SKU. Product-level market exclusions are managed via the publication system: each market has its own publication channel, and products must be explicitly published to it. This is the same mechanism used by B2B catalogs, which means the mental model transfers directly.

When you build market expansion beyond a handful of countries, the per-product publication management becomes a significant operational overhead — especially if your catalogue turns over frequently. The Shopify Markets API and the Translations API both support bulk operations, and several third-party apps (and Shopify's own Translate & Adapt app) provide UI tooling for managing market publications at scale. For catalogues over 500 SKUs with 5+ active markets, a deliberate content operations workflow for international product launches is essential.