Shopify Markets vs Separate Stores: The Real Decision Factors

If you have spent any time in Shopify communities you will have seen the same advice repeated with increasing confidence. Just use Markets. Don't split your store. Keep everything in one admin and let Shopify handle currency, language, and geolocation for you. Much of the time that advice is correct. Markets has genuinely improved since its general availability rollout and for the majority of merchants under roughly five million in annual GMV, a single store with Markets turned on is the right architecture. It concentrates SEO equity, keeps app bills manageable, and gives operations a single pane of glass.

But the advice breaks down the moment a merchant's situation touches one of five specific tripwires. When it does, sticking with Markets costs more than the tooling saves, and the consequences usually show up months later as a missed checkout flow in the Netherlands, an unplanned VAT audit in Germany, or a Meta campaign that insists on attributing French sales to an American pixel. The goal of this piece is to give you the checklist that experienced international operators actually use, so you can make the decision with eyes open rather than defaulting to the forum consensus.

How Shopify Markets actually works in 2026

Before the decision factors make sense, it helps to be precise about what Markets does and does not do today. Markets is a layer inside a single Shopify store that lets you target regions or countries with their own domain structure, currency, language, pricing uplift, and tax treatment. One admin, one catalogue, one product ID space, one inventory pool. You can geolocate visitors, serve localised URLs via subfolders or subdomains, apply per-market price lists including per-product overrides, and display duties inclusive pricing at checkout when you elect to collect them. Translate and Adapt covers basic translation and local content swaps.

Markets Pro goes further. In supported origin-destination pairs Shopify becomes the merchant of record for your international transactions, which means Shopify assumes compliance responsibility for landed cost calculation, local sales tax or VAT remittance, fraud, FX hedging, and cross-border returns. For merchants entering a new region without a local entity, Markets Pro removes most of the friction that used to require a customs broker, a fiscal representative, and a separate payment processor. The caveat is that Markets Pro availability remains uneven. Some destinations merchants most want, such as Japan or Brazil, still require workarounds or local registration.

Expansion stores, by contrast, are the Shopify Plus feature that lets you spin up additional Shopify stores under the same Plus organisation. Each expansion store is a fully independent Shopify instance with its own admin, catalogue, theme, apps, payment gateways, fulfilment setup, and analytics. You can share some staff access and get consolidated billing, but operationally each store stands alone. Plus plans include up to nine expansion stores at no extra licence cost.

Understanding that distinction matters because the conversation is almost never Markets versus no internationalisation. It is Markets versus operating two or more independent Shopify stores that each serve a specific region. The rest of this article works through the five factors that actually flip the answer.

Factor one, local payment gateway coverage

The most under-discussed gap in Markets is that not every local payment method your customers expect is available through Shopify Payments in every country. This matters because conversion rates for cross-border checkout collapse when a shopper does not see their preferred local method. Dutch shoppers expect iDEAL. Belgian shoppers expect Bancontact. Brazilian shoppers expect PIX and Boleto. Polish shoppers expect BLIK. Japanese shoppers expect Konbini and Pay-easy. Mexican shoppers expect OXXO. German shoppers often want SEPA direct debit or Klarna invoice.

Shopify Payments has expanded its local method coverage meaningfully over the last two years, and in many EU countries the common methods are now routed natively through Shop Pay and the accelerated checkout. But routing a local method through Shopify Payments usually requires a local business entity, local banking, and in some jurisdictions local tax registration before the acquiring relationship is even opened. A UK or US merchant cannot simply flip on iDEAL in the Netherlands from their existing Shopify Payments account. The acquirer needs a Dutch KVK number or an EU passportable equivalent.

You can add third-party gateways to cover the gap, and Markets does let you enable multiple gateways. The problem is two-fold. First, Shopify charges a transaction fee on payments not processed through Shopify Payments, typically between 0.2 and 2 percent depending on plan, which stacks on top of the gateway's own fee. Markets Pro removes that fee because Shopify is the merchant of record, but Markets Pro is not available everywhere you need it. Second, the native checkout experience, including Shop Pay acceleration and one-tap mobile flows, only runs at full fidelity when Shopify Payments is the rail. A third-party gateway routed through Markets still works, but the checkout looks and behaves like a bolted-on flow rather than the tuned native one. For a merchant whose conversion edge depends on Shop Pay, that difference is measurable.

When local payment coverage cannot be solved inside your existing Markets setup, a separate store registered in the target country often becomes the cleaner answer. You open a local Shopify Payments account with a local entity, unlock the full native method set, and eliminate the transaction surcharge. The tradeoff is the entity, the bookkeeping, and the multi-store ops burden, which is why the payment question alone rarely tips the decision unless the destination is material revenue.

Factor two, tax registration thresholds and fiscal complexity

Markets calculates taxes. Markets does not file them. That distinction becomes painful as soon as a merchant crosses a meaningful revenue threshold in a jurisdiction that takes its VAT or sales tax seriously. Germany is the canonical example operators cite. Once you are selling B2C into Germany in size, typically quoted at around five hundred thousand euros though the real trigger varies by structure, the practical reality is that you want German VAT registration, a German tax representative if you are outside the EU, and often German-language bookkeeping that aligns with the local tax office's expectations. The EU One Stop Shop scheme simplifies intra-EU distance selling for established EU sellers but does not eliminate the need for a domestic registration in a country where you hold stock or fulfil from a local warehouse.

France adds extended producer responsibility fees, packaging levies, and specific consumer rights disclosures. Italy has e-invoicing requirements for B2B. The UK post-Brexit requires its own VAT registration for non-UK sellers above the threshold, plus customs and import VAT handling at the border. None of this is impossible to track inside a single store with Markets and an integration like Avalara or TaxJar. Markets will compute the right rate per destination and produce reports you can hand to an accountant.

The argument for separate stores here is operational rather than technical. When a jurisdiction's tax regime demands genuinely different invoicing formats, different customer-facing legal pages, different returns windows mandated by local consumer law, different producer registration numbers displayed on the footer, and different bookkeeping, keeping those artefacts cleanly scoped to a store-per-country setup reduces the chance of a compliance mistake. An auditor in Germany wants a clean trail of German sales, German refunds, German returns, and German B2B invoices. Producing that from a single multi-market store is doable but takes discipline. A dedicated DE store produces it automatically. The breakpoint is usually the moment your finance team hires a local accountant per country, because that accountant will ask for a data feed that looks like a single country's ledger.

Factor three, product catalogue divergence

Markets lets you localise prices, translate content, and hide specific products from specific markets. What Markets does not let you do is maintain structurally different product records per region without workarounds. The canonical product has one set of variants, one set of images, one master SKU list, and one canonical title. Everything you do for a market sits on top of that canonical record.

That works fine when your product is genuinely the same everywhere. The label on a leather tote does not change between France and the US. The bill of materials does not change. The voltage does not change. For those products Markets is almost always the right answer.

It starts to break when regulation or formulation forces the record itself to diverge. Cosmetics sold in the EU need INCI ingredient lists formatted to EU cosmetic regulation and often different formulations than the US SKUs because of restricted substances. Supplements have different permitted dosages, different health claim rules, and different required warnings in each market. Consumer electronics need different plug types, different voltage specs, different regulatory marks, different manuals, and often different SKUs in your ERP. Energy-consuming products in the EU carry an energy label. Products shipped across borders need HS codes and country-of-origin declarations that Markets can hold in metafields but do not live naturally in the canonical product.

You can absolutely bend Markets to handle these cases using metafields, market-specific content blocks, conditional theme logic, and disciplined SKU naming. Experienced operators do it every day. The honest question is whether the cognitive load of maintaining that structure is lower than running a second storefront with a genuinely separate catalogue. For a brand with ten regulated SKUs and marginal differences per market, Markets wins. For a brand where half the catalogue is materially different between EU and US, separate stores are typically easier to keep accurate, and catalogue accuracy is what protects you from product liability and customs seizures.

Factor four, fulfilment geography and 3PL integration

Markets handles shipping profiles gracefully. You can define zones, rates, and carrier accounts per market and route orders to the nearest fulfilment node using Shopify's native logic or Shopify Fulfillment Network partners. For a merchant using one 3PL globally or Shopify's own network, fulfilment does not push the decision either way.

The pressure shows up when you have genuinely separate 3PL relationships per region. A typical scaled DTC brand runs a US 3PL out of somewhere like Columbus or Las Vegas, an EU 3PL out of Rotterdam or Venlo, and perhaps a UK 3PL handling post-Brexit orders separately. Each 3PL sits behind its own WMS, its own API, and its own billing cycle. Many of them, particularly in the EU mid-market tier, still prefer to integrate against a dedicated Shopify store rather than filter a multi-market feed. Their order importer expects one store handle, one inventory source of truth, one returns webhook. When you feed them a multi-market store they often receive US orders they should not fulfil, or the inventory sync double-counts SKUs that exist in both regions.

Returns compound the problem. A returns platform like Loop or Returnly, or a European alternative like Outvio, typically scopes itself to one store. Running returns policies that differ by country, with different windows, different restocking rules, and different refund methods, is much cleaner when each store holds its own policy rather than when a single Markets store tries to branch logic at runtime. Add extended producer responsibility packaging levies in France and Germany, which require you to report packaging weight per SKU per market to the national compliance scheme, and the case for clean per-store ledgers gets stronger.

The honest test is whether your 3PL and returns stack already works against a Markets-style feed or whether every integration review meeting turns into a conversation about filtering orders by shipping country. If it is the second, you have already paid the separate-store tax in middleware cost and operator time, and an actual separate store would be cheaper.

Factor five, marketing autonomy and pixel ownership

The last factor is the one that most often sneaks up on merchants who chose Markets for SEO reasons and then hit a wall with paid media. Shopify's Pixel API and channel integrations are scoped per store. One Shopify store has one Meta pixel slot, one Google Ads conversion tag slot, one TikTok pixel slot per native integration. You can fire additional pixels via custom scripts or a tag manager, but those additional pixels do not receive the same native event fidelity that the Shopify integration gives to the primary pixel. Server-side events through the Conversions API work for the primary pixel out of the box. Secondary pixels usually require bespoke work.

For a merchant running one global Meta Business Manager and one global ad account, Markets is fine. The pixel fires, audiences aggregate, and you segment by geography inside the ad platform. For a merchant whose media agency runs a dedicated ad account per country, often because local agencies own the relationship or because the brand wants country-scoped budgets with clean attribution, Markets becomes restrictive. You end up with one pixel feeding signal to multiple ad accounts, audience bleed across regions, and reporting disputes about which account deserves credit for a sale.

This is sharper when compliance enters the picture. Some merchants keep France or Germany pixels isolated for GDPR posture reasons, so that consent signals and user data live in regional infrastructure. Some B2B brands want country-scoped LinkedIn campaigns with LinkedIn Insight Tag instances that do not commingle. A separate store gives each region its own native pixel slot, its own channel integrations, and its own reporting perimeter. The cost is fragmenting customer records and audiences, which for some brands is acceptable and for others kills the ability to run global remarketing. The question is which problem you would rather have.

Putting the five factors together

None of these factors work in isolation. The decision is usually the sum. A beauty brand selling clean, regulated formulations from the UK into Germany, Netherlands, and France, using an Amsterdam 3PL, with local ad accounts run by a Dutch agency, will hit four of the five tripwires and should almost certainly run separate stores. A premium apparel brand with one global catalogue, one 3PL running out of Rotterdam serving all EU, one ad account, and a preference to concentrate SEO equity under a single root domain is a textbook Markets candidate. Most real merchants sit between those extremes.

The pragmatic sequencing we recommend is to start on Markets for the first one or two international destinations, because the setup cost is near zero and the learning is real. You discover which of the five factors actually matters for your product, your customers, and your ops team. Then, when the data shows a specific region generating enough revenue to justify the operational overhead and specifically bumping against one of the tripwires, you migrate that region to a dedicated store rather than migrating everything at once. Markets remains the home for the tail of smaller markets.

The cost of getting this wrong is not usually catastrophic, but it is persistent. A store architecture that fights your compliance, fulfilment, or marketing stack creates friction on every release, every campaign, every audit. That friction compounds quietly and shows up in the financials as slightly lower international conversion, slightly higher return rates in mishandled markets, and noticeably more time spent by operations on reconciliation tasks that should be automatic.

→ Book a WitsCode international strategy consultation and we will run the five-factor diagnostic against your actual destinations, payment mix, fulfilment footprint, and tax exposure. You leave with a written recommendation on Markets, expansion stores, or a hybrid, a migration sequence if one is needed, and a realistic view of the operational cost in each path. We have run this process with merchants from eight-figure DTC brands to niche B2B specialists. The right answer is rarely the one the loudest forum voices push.