Most multi-region Shopify Plus implementations come down to one architectural choice: Markets or expansion stores. The decision shapes everything downstream - cost, operational pace, integration complexity, content workflow, brand consistency. Brands that make the choice deliberately ship multi-region implementations that match their expectations. Brands that default to one pattern without comparing find themselves rebuilding the architecture 12-18 months in.
This piece is the head-to-head comparison. We covered the broader Markets-based architecture in our piece on multi-region Shopify Plus on one codebase and the expansion store deep-dive separately. This is the decision framework: when each pattern wins, when each pattern loses, and how to choose.
Two architectures, one decision
Shopify Plus offers two architectural patterns for running commerce across multiple regions. The choice is one of the bigger architectural decisions a multi-region brand makes; the implications run through cost, operations, integrations, content workflow, and brand consistency.
Shopify Markets sits inside a single Shopify Plus store. Each market is a region (country or group of countries) with its own currency, language, domain, tax setup, and content. The store has one product catalog and one inventory pool, with per-market visibility and pricing. One admin, one operational instance.
Expansion stores are separate Shopify Plus stores under the same Plus organisation. Each store has its own catalog, inventory, admin, and operational team. Stores operate independently with coordination through the Plus organisation admin or middleware that syncs data between them.
Side-by-side comparison
Eight dimensions where the two approaches differ.
Operational simplicity
Markets wins. One admin, one product catalog, one inventory pool, one set of integrations. Multi-region operations run from one operational instance.
Expansion stores require running multiple operational instances, with separate teams or coordinated teams managing each store. The operational overhead is meaningful and scales with store count.
Catalog flexibility
Expansion stores win when catalogs differ significantly. Each store has its own product catalog with no shared infrastructure constraints. Brands with very different product lines per region run cleaner on separate stores.
Markets handles per-market catalogs but the configuration overhead scales with catalog divergence. When 60%+ of products differ per region, Markets configuration becomes painful.
Cost
Markets wins on total cost of ownership. One Shopify Plus license, one set of integrations, one operational team. Expansion stores compound costs: license per store, integration work per store, operational capacity per store.
The cost gap can be 2-4x for brands running 3-5 regions, larger for more regions.
Brand consistency
Markets wins. One source of truth for brand identity, content structure, design system, and customer experience. Per-market customisations happen on a consistent foundation.
Expansion stores can drift over time. Each store can develop its own design system, content patterns, and customer experience. Maintaining brand consistency across stores requires explicit coordination effort.
Integration complexity
Markets wins. ERP, OMS, WMS, marketing tools, and analytics platforms integrate with one Shopify instance. Per-region configuration happens on the integration side.
Expansion stores require integration work per store. Each store needs its own ERP connection, OMS sync, WMS integration. The integration work compounds.
Independence and isolation
Expansion stores win when regions need genuine operational independence. Different teams making different decisions, different operational priorities, different change cadence. Markets forces alignment across regions.
For brands where regional teams need autonomy, expansion stores provide the isolation Markets doesn't.
Performance at scale
Roughly equivalent at typical mid-market scale. Both architectures handle high traffic and large catalogs without significant performance differences. At very large scale, expansion stores can isolate performance characteristics per region but the difference is rarely the deciding factor.
Migration and evolution path
Markets is easier to start with and harder to split out of. Expansion stores are harder to start with (more upfront work) but easier to evolve independently per region.
The right pattern depends on whether you expect regional independence to grow or stay aligned over time.
When Markets is the right choice
Four scenarios where Markets fits cleanly.
Brands operating multiple regions with the same core product catalog. Most products available in all markets, with region-specific availability for a subset. Standard mid-market multi-region pattern.
Brands managing inventory as a single pool with regional allocation. One source of truth for inventory, regional configuration for fulfillment and shipping.
Brands with strong marketing alignment across regions. Same brand identity, similar campaign cadence, central marketing team.
Brands where the operational team is centralised. One team running all regions through one admin. Markets reduces context-switching overhead compared to multiple stores.
When expansion stores are the right choice
Four scenarios where expansion stores remain the better choice.
Brands with genuinely different product catalogs per region. Different brands operating in different regions. Different category mixes per region. Different sub-brands targeting different markets.
Brands with separate operational teams per region. Different local teams running different regional operations with their own decision-making authority. The shared admin in Markets becomes a coordination overhead rather than a simplification.
Brands with regulatory or operational constraints requiring separation. Some regulatory environments require data residency or operational separation that Markets doesn't provide.
Brands running fundamentally different business models per region. DTC in one region and pure B2B in another. Wholesale only in some regions and DTC in others. The business model differences are deep enough that one architecture can't serve both.
The hybrid approach
Many brands run hybrid setups. Markets for closely related regions, expansion stores for genuinely different regional operations. Examples we've seen:
Markets for EU countries (closely related, shared catalog, central team), plus a separate expansion store for the US (different fulfillment, different pricing model, separate team).
Markets for B2C across regions, plus a separate expansion store for B2B (different operational model, different catalog, different pricing).
Markets for the core consumer brand, plus separate expansion stores for sub-brands (different identity, different team, different operational priorities).
Hybrid setups need clear architectural decisions about which pattern applies where. Done well, the hybrid model combines the operational simplicity of Markets where it fits with the independence of expansion stores where it's needed.
How to actually decide
Three questions order the decision.
One: how much does the catalog differ per region? Less than 30% divergence: Markets is comfortable. 30-60%: Markets works but configuration is meaningful. Over 60%: expansion stores usually win.
Two: how independent do regional teams need to be? Aligned, centrally coordinated teams: Markets. Genuinely autonomous regional teams: expansion stores.
Three: what's the cost tolerance? Markets typically 2-4x cheaper TCO for equivalent multi-region operations. If cost is a primary driver, default to Markets unless there's a specific reason to spend the premium for expansion stores.
Common mistakes
Three patterns from the decisions we've seen go wrong.
Choosing expansion stores for the operational independence it provides without budgeting for the operational cost. Independence sounds good in theory and costs real money in practice. Make sure the budget supports the choice.
Choosing Markets for the cost savings without thinking through whether the unified admin will work for the team structure. Markets requires coordinated regional operations. Brands with genuinely independent regional teams find the unified admin creates friction rather than simplification.
Avoiding the decision and starting with whichever pattern the initial implementation team is most familiar with. The default decisions get locked in by inertia. Make the choice deliberately, not by default.
Where to start
If you're choosing between Markets and expansion stores, four moves order the work.
One: map your regional catalogs. How much overlap, how much divergence. The catalog answer drives much of the decision.
Two: map your team structure. Centralised vs regional. The team answer determines whether the unified admin in Markets fits.
Three: estimate the TCO of both approaches. Include licensing, integration, operational, and capacity costs. The cost gap is usually larger than initial estimates suggest.
Four: consider the hybrid approach explicitly. Most brands assume they need a single pattern across all regions; many would be better served by a hybrid.
Talk to our team if you want help working through the decision for your multi-region implementation. We've shipped Markets-based, expansion store-based, and hybrid implementations across AU, UK, US, EU, and APAC markets. The architecture conversation is one of the bigger decisions a multi-region brand makes. Worth doing carefully. The broader multi-region context is in our piece on multi-region Shopify Plus on one codebase.
Can I run Markets and expansion stores at the same time?
Yes. Hybrid approaches are common. Brands often use Markets for closely related regions (EU markets within one store, North American markets in another) and expansion stores for genuinely different regional operations (separate B2B and DTC, separate sub-brands, regions with very different catalogs). Hybrid setups need clear architectural decisions about which pattern applies where.
If I start with Markets, can I switch to expansion stores later?
Yes, but it's meaningful work. Splitting a market out of a Markets store into a separate expansion store involves migrating data (or duplicating it), reconfiguring integrations, redirecting URLs, and handling the SEO transition. Plan for 8-16 weeks for a careful migration. Easier to make the right architectural choice upfront than to migrate later.
Do expansion stores cost more than Markets?
Significantly more in total cost of ownership. Each expansion store has its own Shopify Plus license (typically $2.3K-$2.5K/month plus revenue share), its own development and maintenance overhead, its own integration work to operational systems. Markets is one license, one operational instance, one set of integrations. Brands underestimating expansion store TCO end up surprised by the ongoing cost.
Which approach is better for SEO?
Both work well with proper implementation. Markets supports country-specific domains for SEO localisation. Expansion stores have separate domains by default. The SEO outcomes depend more on content quality, link strategy, and technical implementation than on the architectural choice. Don't pick based on SEO unless you have specific SEO requirements that one approach addresses and the other doesn't.
What if my regions have very different product catalogs?
Markets handles this through per-market catalogs but the configuration overhead scales with catalog divergence. When 60%+ of products differ per region, Markets configuration becomes painful. When 80%+ differ, expansion stores are usually cleaner. The threshold isn't bright; it's a gradient where you should evaluate the operational overhead of either approach.
What about B2B in multi-region?
Both approaches support B2B. Markets handles per-market B2B catalogs, pricing, and customer accounts within one store. Expansion stores can run dedicated B2B stores alongside dedicated DTC stores per region. Hybrid approaches (Markets for DTC, expansion stores for B2B) are common for brands where the B2B operation is genuinely different from DTC.
How do payments and currencies work across the two patterns?
Markets handles multi-currency natively with Shopify Payments. Each market has its own currency and payment methods. Expansion stores have separate Shopify Payments setups per store, which means separate payment processing relationships and (sometimes) separate settlement currencies. Markets is operationally simpler for multi-currency.
How do I decide if I'm not sure?
Default to Markets and justify expansion stores if you go that path. The operational simplicity of Markets is meaningful, and most multi-region scenarios that initially seem to need expansion stores actually fit Markets fine with proper configuration. The bias should be toward Markets unless you have specific reasons to choose otherwise.
A Shopify Plus Agency for Strategic Design & Advanced Engineering
Building something ambitious?
- Markets vs expansion stores is one of the bigger architectural decisions a multi-region brand makes. The choice shapes cost, operations, integrations, content workflow, and brand consistency.
- Markets wins on operational simplicity, cost (2-4x cheaper TCO), brand consistency, and integration complexity. One admin, one catalog, one operational instance.
- Expansion stores win on catalog flexibility (when catalogs differ significantly per region), operational independence (when regional teams need autonomy), and regulatory separation.
- The hybrid approach is common: Markets for closely related regions, expansion stores for genuinely different regional operations. Most brands underconsider this option.
- Default to Markets and justify expansion stores if you choose that path. The operational simplicity is meaningful and most multi-region scenarios fit Markets fine with proper configuration.
- Three questions order the decision: how much does the catalog differ per region, how independent do regional teams need to be, what's the cost tolerance.
