Shopify Markets vs a Separate Store: When One Admin Is Enough

Shopify Markets is enough for most mid-market brands expanding internationally. You keep one Shopify admin, define markets (countries or regions), and localize currency, domain strategy, language, pricing, and catalog availability from Settings → Markets. You do not need a second store to show GBP prices, use a .co.uk domain or /en-gb/ subfolder, or hide SKUs that cannot ship to the EU. A separate store is the right call only when legal entities, conflicting catalogs, or ops ownership make one admin a liability. Managed Markets is a third path: same store, higher per-order fees, and Shopify (via Global-e) handles duties, customs paperwork, and more local payment methods.

This is a Shopify-only deep dive for operators in the $100K–$10M band who are past “should we sell abroad?” and stuck on architecture. It sits under Shopify Build & Growth — the same work that covers theme, checkout, and international configuration without bolting on redundant currency apps.

What Shopify Markets actually is

Shopify Markets is the native international layer on every plan. You create a market, attach countries, and configure what shoppers in that market see and pay. Markets is not a shipping app, not a currency converter theme snippet, and not a second Shopify subscription. It is the admin surface that replaced the old patchwork of geo-IP apps, duplicate products, and “please convert at checkout and hope.”

In practice, a market can control:

• Currency and rounding. Show and (with the right gateway) charge local currency, with rounding rules so prices end the way that market expects.
• Pricing. Percentage adjustments or fixed prices per market so a UK price is a margin decision, not a blind FX swap of your USD MSRP.
• Domains and URL structure. Primary domain plus market-specific domains, subdomains, or subfolders for language–country combinations.
• Languages. Paired with Translate & Adapt (or another translation workflow) so storefront copy matches the market.
• Catalogs. Include or exclude products and collections per market when you cannot or should not sell everything everywhere.
• Duties and taxes. Estimate or collect duties and import taxes at checkout depending on plan and whether you use standard Markets or Managed Markets.

Shopify Markets

Shopify’s built-in system for configuring how a single store sells to different countries or regions — currencies, domains, languages, catalogs, pricing, and duty settings — from one admin.

If you still have a third-party currency app running next to Markets, treat that as debt. Native multi-currency is one of the clearest app-kill opportunities in a Shopify app audit: one job, zero extra scripts once Markets and Shopify Payments are configured correctly.

Markets vs separate store vs Managed Markets

Three architectures get confused in kickoff calls. They are not interchangeable.

One store + standard Markets

Best default for a brand with one legal seller entity, one catalog spine, and expansion into a handful of countries that share fulfillment logic. You localize the buyer experience; you do not duplicate the operator experience. Inventory, metafields, discounts, and reporting stay in one place. Brand Agents and other Plus-gated features (when you have them) also stay on one storefront instead of splitting across admins — a detail that matters if you are already weighing Shopify Plus for agentic commerce.

One store + Managed Markets

Same admin, different commercial layer for cross-border orders. Managed Markets (the managed cross-border service powered by Global-e) guarantees the duty and tax shown at checkout, handles customs documentation, and expands local payment methods. Shopify’s published fee is about 3.5% per transaction on Basic through Advanced, or 3.25% on Plus, on top of payment processing and currency conversion — not a second monthly plan. Choose it when surprise duties and customs tickets are a bigger problem than the fee, or when you cannot staff HS codes, DDP shipping, and returns compliance yourself.

Separate Shopify stores

A second store means a second catalog, second theme, second app stack, second analytics truth, and usually a second ops owner. Use it when you have a real reason Markets cannot express: a different legal entity that must be the merchant of record, a wholesale or marketplace catalog that must never leak into DTC, a brand architecture that requires separate domains and separate product lines with no shared inventory logic, or a country that needs an entirely different ops and support playbook. “We want GBP prices” is not that reason.

When one Markets setup is enough

For a typical DTC brand shipping from one or two warehouses into Canada, the UK, the EU, or Australia, Markets should be the first architecture you try. The checklist is operational, not aspirational.

You have a single merchant-of-record story. One company sells; markets are distribution, not separate businesses. Tax registration and VAT may still be required by country — Markets does not erase tax law — but you are not spinning a new Shopify org for every VAT ID.

Shopify Payments or Adyen is your primary gateway. Local currency display works more broadly; local currency settlement needs a supported gateway. Without it, shoppers see local prices and still pay in your home currency (or take a card issuer FX hit). That is a conversion leak dressed up as localization.

You can set market prices on purpose. A straight FX conversion of a $48 USD hoodie can land on awkward endings or wipe margin once shipping and duties enter the math. Markets lets you set percentage adjustments or fixed prices per market. Use them. Treat pricing as a decision, not a side effect of the exchange rate.

Catalog exceptions are the minority. If 90% of SKUs can sell everywhere and a handful need market-specific availability (voltage, sizing systems, regulatory claims), market catalogs handle that. If half the catalog is country-specific and the rest must never cross, you are closer to a second-store problem.

Domain strategy is clear. Subfolders (/en-gb/) are usually the fastest SEO-safe start on one store. Country TLDs and subdomains work too when brand or legal needs demand them — but they still sit on one Markets config. If you are migrating domains into Shopify, keep the same redirect discipline you would use in any Shopify migration: one hop to the final URL, no chains.

When Managed Markets earns the fee

Standard Markets can estimate or collect duties depending on plan and setup; the estimates are not a guarantee. Managed Markets is the productized answer when landed-cost surprises are the main international friction.

Use Managed Markets when:

• Customers abandon or open tickets after delivery because duties were not clear at checkout.
• Your team cannot reliably maintain HS codes, country of origin, and DDP carrier workflows for every SKU.
• You need a broader set of local payment methods than your current Payments setup exposes in those countries.
• You would rather pay a known percentage than staff a customs ops role for the first year of expansion.

Do the fee math on real average order value. On a $100 international order, a 3.5% Managed Markets fee is $3.50 before FX and card processing. That is often cheaper than a 15–20% refund rate driven by unexpected customs bills — and cheaper than a second store’s app stack and agency hours. It is expensive if your international volume is tiny and duties rarely apply above de minimis thresholds. Run the last 90 days of international orders before you commit.

Managed Markets is still one store. Do not confuse the fee with “we need a separate Shopify.”

When a second store is the honest answer

Separate stores are justified less often than agencies pitch them, and more often than founders hope when legal structure is messy. Open a second admin when at least one of these is true.

Different merchant of record

If UK sales must invoice from a UK entity and US sales from a US entity, Markets localization is not the same as legal separation. Some brands solve this with careful tax and entity setup on one store; others need separate Shopify stores (or Shopify Plus organization features) because finance and banking require it. Let counsel and your accountant drive this call — not the theme.

Conflicting catalogs that cannot share an admin

A DTC line and a wholesale-only line with different pricing, different imagery, and a hard requirement that B2B SKUs never appear on the consumer site can exceed what market catalogs cleanly express — especially if apps, discounts, and search indexes keep leaking products across audiences. Native B2B on Plus is often the better single-store fix; a second store is the fallback when B2B and DTC truly cannot share a catalog spine.

Ops ownership that cannot share a queue

If a country partner must own merchandising, support SLAs, and promotions without touching the home-market catalog, a second store (or a formal organization split) can be safer than shared Markets permissions. This is an org design problem. Markets will not invent process discipline.

Theme and experience forks that are really different products

Two brands under one holding company, or a market that needs a completely different information architecture (not just translation), often belong on separate themes and separate product graphs. That can still be Markets on one store if the catalog is shared — or two stores if it is not. Decide from the product graph, not from the desire for a second homepage.

1. 1

   Map the expansion countries

   List the first 1–3 countries by trailing demand, not by vanity. Note currency, language, and whether you already ship there.

2. 2

   Confirm gateway and FX reality

   Verify Shopify Payments or Adyen can settle local currency. Price the 1.5% (US) / 2% (non-US) conversion fee into margin.

3. 3

   Choose pricing method per market

   Set percentage or fixed prices; do not ship blind FX. Spot-check five hero SKUs for awkward endings and margin after shipping.

4. 4

   Decide duties path

   Standard Markets with HS codes and DDP, or Managed Markets if you need guaranteed landed cost. Do not leave duties as a surprise.

5. 5

   Only then consider a second store

   If entity, catalog conflict, or ops ownership still fail the one-admin test, scope a second store — with a plan for what stays shared vs duplicated.

How Markets interacts with speed, apps, and AI readiness

International setup fails in quiet ways that look like “Markets is broken” but are really stack problems.

Apps. Geo-IP banners, third-party currency switchers, and duplicate translation widgets fight native Markets detection. They also add scripts on every page. Lean the stack the same way you would for theme performance: fewer embeds, native features first.

Themes. Online Store 2.0 themes that respect Markets and localization APIs beat heavily customized Liquid that hard-codes currency symbols and country logic. If your theme still assumes one currency in snippets, fix that before you buy another international app.

Catalog data. Market catalogs only help if product data is structured enough that a localized storefront — and eventually a Brand Agent — can answer the same questions shoppers ask in every language. Thin descriptions do not become international-ready because you added a /fr/ subfolder. Enrichment still comes first; Markets is distribution of that truth, not a substitute for it.

Reporting. One store with Markets keeps revenue in one analytics surface with market breakdowns. Two stores means you invent the rollup. Prefer one truth until the legal or catalog case forces a split.

A practical decision table for mid-market brands

| Situation | Prefer | |---|---| | First expansion into CA / UK / EU / AU, one entity, one catalog | Standard Markets | | Duties surprises and customs tickets dominate support | Managed Markets | | Need local currency settlement | Markets + Shopify Payments or Adyen | | Still running a currency converter app | Remove app; configure Markets | | Separate legal seller entities required | Second store or Plus org design (confirm with counsel) | | DTC + wholesale catalogs that must never mix | Plus B2B first; second store if still leaking | | “We want it to feel international” only | Markets — not a rebuild |

Most brands in GigaCommerce’s ICP land in the first two rows for twelve to twenty-four months. The expensive mistake is paying for a second store’s theme rebuild, app licenses, and migration risk because Markets was never configured past the default primary market.