Shopify Markets or separate regional stores?

Most fashion brands on Shopify reach the same point sooner or later. The UK store is trading well, international orders are arriving with little encouragement, and the plan now names specific markets – the EU, the US, perhaps the Gulf. The question becomes whether to serve those markets from the store you already have, or to open separate stores for each region.

Both are legitimate architectures, and brands of real standing run each of them. The right choice depends less on the platform than on how differently the brand intends to trade in each market, and on the legal and operational structure behind it.

The two approaches in brief

One store, several markets

Shopify Markets lets a single store present itself differently to customers in different countries or regions. In general terms, that means local currencies, market-specific pricing, translated content and a dedicated domain or subfolder for each market, all managed from one admin with one catalogue, one order history and one theme. Shopify has also offered managed cross-border services in some regions, taking on more of the tax, duties and compliance handling. The scope and terms of those services change, so they are worth checking against the markets you plan to enter.

Separate stores by region

The alternative is to run distinct stores – for example one for the UK and EU, one for the US and one for the Middle East – each with its own catalogue, theme, apps, payment settings and team permissions. Each store can be configured entirely for its region, at the cost of maintaining several storefronts that must be kept in step wherever the brand wants consistency.

Where the differences show up

Assortment and restricted products

Fashion assortments rarely travel intact. Seasonal ranges may land at different times in different hemispheres, some pieces are regional exclusives, and certain materials or categories face import restrictions in particular countries. A single store can control which products are available in which market, and that is often enough when the differences are a matter of inclusion and exclusion. When regions carry substantially different ranges, with their own product structures, size conventions or descriptions, separate stores start to feel more natural, because each catalogue can be shaped without affecting the others.

Pricing and price lists

Markets supports price adjustments by market and, beyond that, fixed prices for specific products, so a brand can hold deliberate, rounded price points in euros or dirhams rather than accepting converted figures. For many brands this is sufficient. Separate stores give complete independence, which matters when regional pricing is set by different teams, when promotional calendars differ significantly, or when the relationship between regional prices is itself commercially sensitive.

Campaigns, lookbooks and drops

This is where many brands feel the limits of a single store most. One theme serving several markets can vary copy by language and, increasingly, adjust content by market, but a genuinely different campaign in each region – different hero imagery, a different editorial sequence, a drop timed for Dubai rather than London – calls for careful theme development and disciplined content operations. Separate stores make regional merchandising straightforward, but they also make it easy for the brand’s expression to drift apart, which for a luxury house can be the more serious problem.

Inventory and fulfilment

Stock held in several places – a UK warehouse, a US third-party logistics partner, a fulfilment partner in the Gulf – can be represented in a single store, and Shopify’s location and order routing settings give a degree of control over which stock serves which market. Whether that is enough depends on the routing rules the brand needs, its warehouse and ERP integrations, and how returns flow back. Separate stores simplify the picture within each region but make cross-regional stock visibility a job for the ERP or middleware.

Tax, duties, entities and payments

This area often decides the matter. A store’s payments, payouts and financial reporting have generally been tied to a single business entity, so brands trading through separate legal entities in different regions have tended to find separate stores the cleaner fit. Shopify has been extending what one store can handle in this respect, so the current position is worth confirming. Whether a brand should register for tax locally, ship duties paid or establish a regional entity at all are questions for its accountants and legal advisers. The architecture should follow those decisions rather than precede them.

Apps, integrations and reporting

Apps and integrations are usually installed, configured and often billed per store. Reviews, loyalty, search, ERP connectors and marketing platforms may each need setting up several times, and not every app fully understands markets within a single store. Reporting follows the same logic: one store gives a consolidated view that can be filtered by market, while several stores need their data brought together elsewhere, typically in a data warehouse or reporting tool.

Search visibility

With Markets and dedicated domains or subfolders, Shopify handles much of the basic plumbing, such as alternate-language tags linking the versions of each page. Separate stores on separate domains can perform equally well, but the relationships between them have to be managed deliberately, and product content duplicated across regions needs care.

Workload, drift and cost

Every additional store multiplies routine work: product updates, theme releases, app changes, testing and permissions. Without the right tooling, stores drift – a product description corrected in one region but not another, a size guide updated in two stores out of three. Costs rise with platform subscriptions, app fees and development time, although for larger brands the operational clarity of separate stores can justify them.

Hybrid patterns

In practice many established brands settle somewhere between the two. Common patterns include:

One store per legal entity, with Markets inside each. A UK store might serve the UK and Europe through Markets, while a US store serves North America, each aligned with the entity that trades there.
A shared source of truth for product data. A PIM or middleware layer holds the master catalogue, imagery and copy, and publishes to each store with regional variations, which reduces drift considerably.
Shared theme code, regional content. One theme codebase deployed to several stores keeps design and functionality aligned, while each region controls its own campaigns and merchandising.

These patterns ask more of the technical foundations, particularly around integration and deployment, but they often reflect how the business is actually organised.

Questions that point one way or the other

A handful of questions tends to clarify the decision quickly.

Do you trade, or plan to trade, through separate legal entities in different regions?
Will the assortment differ by a few exclusions, or by materially different ranges?
Will regional teams set their own pricing, promotions and campaign calendars?
Do you need distinct payment providers, banking arrangements or accounting by region?
Do you need a single consolidated view of customers, orders and performance?
Can your ERP, warehouse and marketing integrations support several stores cleanly?
Who will maintain content in each market, and how much divergence is acceptable?

Mostly “no” to the first four and “yes” to the fifth usually favours a single store with Markets. Several “yes” answers among the first four suggest separate stores, or a hybrid built around entities. The last two indicate how much a multi-store setup would cost to run well.

The answer changes as the brand grows

A single store with Markets is often the right starting point. It concentrates effort, keeps the brand consistent and lets international demand prove itself. As a market grows and gains its own team, entity or fulfilment operation, a dedicated store may become the better fit. The reverse also happens, with brands consolidating stores once they find one can do more than it once could. It pays to design for movement – clean product data, well-structured themes and integrations that do not assume a single store – so that the next change is a project rather than a rebuild.

If international expansion is on the plan, reviewing your current setup against the markets you intend to enter is a sensible first step. It usually shows quite quickly which architecture fits now, and what would need to be in place for the one that fits later.