Shopify Markets store consolidation

Most brands did not choose to run four stores. They opened a UK store, then added a US one because of currency, then a EU one because of tax, then an AU one because a distributor asked. Each decision was reasonable. The result is a maintenance problem that grows with every theme change.

Consolidation is worth doing when the cost of keeping stores in sync is higher than the cost of the move. That is usually the case once you are past two, and almost always past three.

What Markets actually gives you

One store, one theme, one app stack, with per-market variation where it matters.

Catalogues are the main mechanism. A market can have its own catalogue with its own product list and its own prices, so a product can be published in the UK and not in the US, or priced independently rather than by exchange rate. This replaces the main reason people ran separate stores.

Pricing works either as an adjustment from the base price, a fixed price list per market, or rounding rules applied to a converted price. Fixed price lists are the right answer for anyone who cares about price points ending in 95 rather than 87.

Domains can be a subfolder (/en-de), a subdomain, or a separate top-level domain per market. Subfolders concentrate authority on one domain and are usually the better SEO outcome. A brand with an established .de domain and years of links may be better keeping it. That is a judgement per brand, not a rule.

Tax and duties is where consolidation earns its keep. One store handling registration-based tax, and duties calculated at checkout, replaces the per-store tax configuration that nobody quite trusts.

Inventory stays with locations rather than stores, which is the change most operations teams feel first. One stock pool, one source of truth, no more manual rebalancing between stores that each thought they had ten units.

The parts that need care

Redirects. Every URL on every store being retired needs a mapped destination on the consolidated store. This is the same discipline as a platform migration and the same consequence if it is skipped. Multiply it by the number of stores.

Hreflang. Shopify generates hreflang annotations from the market and domain configuration. It generates them correctly for the configuration it knows about, which is not necessarily the configuration you had before. This needs checking after launch rather than assuming.

Customer accounts and history. Customers exist per store. Consolidating means merging customer records, deduplicating people who bought in two regions, and deciding what happens to order history. Passwords do not merge, so this needs the same comms planning as a platform migration.

Subscriptions. If any of the stores being retired has active subscriptions, that is the constraint the whole timeline moves around. Subscription contracts do not transfer cleanly between stores and the answer depends on the app. Establish this before anything else is planned.

Apps. Some apps are licensed per store, some are per market aware and some are neither. An app that does not understand markets will do the wrong thing in every market but the primary one, and it is better to find that in staging.

Timeline

Two stores with a shared catalogue and no subscriptions is [typical timeline]. Four stores with independent catalogues, separate domains and active subscriptions is [typical timeline]. Subscriptions and customer data migration are what move the number, not the theme work.