Expansion stores are Shopify Plus's pattern for running multiple independent stores under one organisation. Each store has its own catalog, inventory, admin, and operational team, with cross-store coordination handled through the Plus organization admin or middleware. The pattern is the right choice for specific scenarios: brands with genuinely different catalogs per region, separate operational teams, sub-brands with independent operations, or regulatory constraints requiring separation.
This piece is the deep walkthrough on expansion stores. The architecture, common implementation patterns, cross-store coordination, cost model, and where most expansion store implementations underestimate the operational complexity. We covered the choice between expansion stores and Markets separately in our piece on Markets vs expansion stores.
What expansion stores actually are
Shopify Plus expansion stores are separate Shopify Plus stores grouped under one Plus organisation. Each store operates independently: separate catalog, separate inventory, separate admin, separate customer base, separate fulfillment configuration. The Plus contract includes up to 9 expansion stores plus the primary store (10 total). Beyond that, additional stores require contract changes.
The org admin (Shopify Plus organisation admin) provides a single dashboard view across all stores in the organisation. It handles centralised user management, billing visibility, and basic cross-store reporting. It does not handle product sync, inventory sync, or operational coordination between stores. Those require separate solutions.
The architectural pattern fits scenarios where regions, brands, or business models need genuine independence. The pattern is more expensive and more operationally complex than Markets-based alternatives, but provides isolation that Markets cannot.
Common expansion store patterns
Three patterns dominate expansion store deployments on Shopify Plus.
Pattern 1: Regional separation
Separate stores per region with distinct catalogs, fulfillment, and operations. Common when regional product catalogs differ significantly, regional teams need autonomy, or regulatory constraints require separation.
Typical setup: US store, EU store, APAC store. Each with its own product catalog (60%+ different), separate inventory pools, separate operational teams, separate fulfillment networks. Cross-store coordination through the brand's ERP or OMS.
When this fits: brands operating in regions with genuinely different products, supply chains, or operational models. The cost premium pays back through operational independence.
Pattern 2: B2B and DTC separation
Separate stores for B2B and DTC operations. Common when the two business models are operationally very different: different catalogs, different pricing, different team responsibilities, different fulfillment patterns.
Typical setup: DTC primary store with consumer-facing catalog, branding, and pricing. Separate B2B expansion store with wholesale catalog, custom pricing tiers, B2B-specific features, separate sales team.
When this fits: brands where B2B is a major channel with operational independence. Less common in 2026 because Shopify Plus's native B2B features handle most B2B scenarios within a single store. But some brands still benefit from separation for organisational reasons.
Pattern 3: Sub-brand or portfolio separation
Separate stores for distinct brands operated by the same parent. Each brand has its own identity, catalog, customer base, and team.
Typical setup: parent company operates 3-5 distinct consumer brands. Each brand gets its own expansion store with full operational independence. The parent uses the org admin for billing visibility and cross-brand reporting.
When this fits: portfolio companies, multi-brand groups, brands that have acquired other brands and want to maintain distinct identities. The operational independence preserves each brand's identity.
Cross-store coordination
Expansion stores don't share data natively. Brands need explicit coordination strategies for data that crosses store boundaries.
Customer coordination
Each store has its own customer accounts. Customers shopping across multiple stores have separate accounts in each. Brands that want unified customer profiles need either an external CRM that consolidates the data or middleware that syncs customer records between stores. Most brands accept the customer fragmentation as a trade-off; some invest in consolidation.
Inventory coordination
Each store has its own inventory. Brands managing shared inventory pools across stores need either an ERP/OMS that sits between stores and allocates inventory, third-party multi-store inventory apps, or custom middleware. Manual coordination is possible but error-prone at any meaningful scale.
Product coordination
Each store has its own product catalog. Brands wanting shared products across stores need either manual duplication (works for small catalogs and small store counts), middleware that syncs product data between stores, or third-party multi-store product management. The product coordination work scales with catalog overlap and store count.
Order coordination
Each store has its own order flow. Brands wanting unified order analytics, customer service across stores, or shared returns processing need external tools that aggregate order data. Most brands solve this through ERP, OMS, or analytics platforms that consume data from all stores.
The org admin (what it does, what it doesn't)
The Shopify Plus organisation admin is the cross-store dashboard.
What it does well: centralised user management across stores (one place to add users to multiple stores), billing visibility (see Plus invoices for all stores), basic cross-store reporting (aggregate revenue, orders), centralised support contact.
What it doesn't do: product sync between stores, inventory sync, customer sync, order coordination, operational workflow coordination. These all require separate solutions.
Brands sometimes assume the org admin handles more than it does and discover the gap during implementation. Plan for separate solutions for any cross-store data coordination.
Cost model
For a brand running 3 expansion stores:
Shopify Plus licensing: $2.3K-$2.5K/month per store plus revenue share above $800K monthly GMV per store. For 4 stores (1 primary + 3 expansion): roughly $115K-$125K/year baseline platform cost before revenue share.
Implementation per store: $60K-$200K depending on complexity. For 3 expansion stores at typical mid-market scale: $200K-$600K total implementation.
Integration per store: each store needs its own ERP, OMS, marketing tool, analytics integrations. The integration work compounds. Typical cost: $40K-$120K per store for integration setup.
Ongoing maintenance: per-store engineering capacity, per-store operational team or shared coordination team. Typical cost: $80K-$200K/year per store for sustained operations.
Total first-year cost: $400K-$1M+ for a 4-store deployment. Total ongoing annual cost: $200K-$500K+/year.
For comparison, equivalent Markets-based implementation: $80K-$300K initial plus $50K-$150K/year ongoing. The cost gap is meaningful.
Common pitfalls
Five patterns from expansion store implementations we've shipped or audited.
Choosing expansion stores when Markets would fit. The most common mistake. Brands assume their multi-region operation needs expansion stores when Markets would handle it cleanly. Default to Markets unless you have specific reasons.
Underestimating cross-store coordination cost. Each piece of shared data (customers, products, inventory, orders) needs explicit coordination. Brands that don't budget for this discover the gap during implementation and scramble for solutions.
Under-investing in operational team structure. Multi-store operations need either separate teams per store or strong coordination mechanisms across stores. Brands that try to run multi-store with the same team structure as single-store find capacity stretched thin.
Treating each store as a fresh build. Brands rebuilding each store from scratch instead of templating their approach. The right pattern: invest in shared design system, shared theme code (or Hydrogen codebase), shared development practices. Then customise per store rather than rebuilding.
Underestimating reporting complexity. Reporting across multiple stores requires either analytics platforms that aggregate data, custom reporting infrastructure, or accepting fragmented reporting. Brands that defer the reporting decision discover the gap when they try to evaluate cross-store performance.
Implementation pattern
For a typical 3-store expansion store deployment:
Architecture and design system: 4-6 weeks. Define the shared design system, shared theme architecture (or shared Hydrogen codebase), shared component library, per-store customisation patterns. Investment here pays back across every subsequent store.
Primary store implementation: 14-20 weeks. Full Shopify Plus build with the shared architecture.
First expansion store: 8-12 weeks. Faster than primary because the shared architecture is in place. Customisations per store rather than greenfield build.
Subsequent expansion stores: 6-10 weeks each. Progressive efficiency gains as patterns mature.
Cross-store coordination setup: 6-12 weeks. ERP integration, OMS coordination, customer data strategy, reporting infrastructure.
Total: 12-18 months for a 3-store deployment from kickoff to all stores stable in production. Some brands can compress this with parallel implementation; most run sequentially.
Where to start
If you're planning an expansion store implementation, five moves order the work.
One: confirm expansion stores are the right pattern. Most multi-region scenarios fit Markets better. Justify the expansion store decision explicitly.
Two: design the shared architecture upfront. Investment in shared design system, theme code, and component library pays back across every store. Brands that skip this rebuild repeatedly.
Three: plan the cross-store coordination explicitly. Customer, product, inventory, order coordination patterns. Tools (ERP, OMS, middleware). Capacity (team or service to operate the coordination).
Four: budget for the full multi-store cost. Initial implementation plus ongoing per-store maintenance plus coordination overhead. The total is usually 2-4x a comparable Markets implementation.
Five: phase the rollout. Don't launch all stores simultaneously. Sequential rollout lets the operational learnings from earlier stores inform later ones.
Talk to our team if you want help scoping an expansion store implementation or evaluating whether expansion stores or Markets fits your scenario. We've shipped both patterns across AU, UK, US, EU, and APAC and the architecture decision is one of the bigger choices a multi-region or multi-brand operation makes. Worth doing carefully.
What's the difference between expansion stores and Markets?
Expansion stores are separate Shopify Plus stores under one organisation, each with its own catalog, inventory, and admin. Markets is the multi-region feature inside a single Shopify Plus store with shared catalog and inventory. We covered the head-to-head comparison in our piece on Shopify Plus Markets vs Expansion Stores. The default for new multi-region implementations is Markets; expansion stores are right for specific scenarios.
How many expansion stores does Shopify Plus include?
Up to 9 expansion stores included with the base Shopify Plus contract (so 10 total: 1 primary, 9 expansion). Brands needing more contact Shopify for additional capacity, which is negotiable but typically involves contract changes.
Do expansion stores share product data with the primary store?
No, not natively. Each expansion store has its own product catalog. Brands that want shared product data across stores need either manual duplication, middleware that syncs products between stores, or third-party multi-store management apps. The lack of native product sharing is one of the bigger operational considerations for expansion stores.
What does the org admin do?
The Shopify Plus organization admin gives a single dashboard view across all stores in the org. Centralised user management, billing visibility, and basic cross-store reporting. It does not handle product sync, inventory sync, or operational coordination between stores. Those still require separate solutions.
How do brands coordinate inventory across expansion stores?
Three common patterns. Manual coordination through OMS or ERP that sits between stores (most common). Third-party multi-store inventory apps that sync inventory between Shopify stores. Custom middleware built specifically for the brand's coordination needs. The right pattern depends on operational complexity and existing system landscape.
Are expansion stores more or less expensive than a single Markets-based store?
More expensive in total cost of ownership. Each expansion store has its own Shopify Plus license (usually $2.3K-$2.5K/month plus revenue share above $800K monthly GMV), its own development overhead, its own integration work. Markets is one license, one operational instance. For brands running 3-5 expansion stores, the cost gap vs Markets can be 2-4x in TCO.
When are expansion stores worth the extra cost?
When the operational benefit justifies it. Brands with genuinely different catalogs per region, separate operational teams per region, regulatory constraints requiring separation, or fundamentally different business models per store find the cost worthwhile. Brands that pick expansion stores out of caution rather than need usually regret the operational complexity 12-18 months in.
Can a brand evolve from expansion stores to Markets later?
Yes, with meaningful migration work. Consolidating expansion stores into a single Markets store involves data migration, integration reconfiguration, URL strategy decisions, and SEO transition. Plan for 12-20 weeks for a careful consolidation. Less common than the reverse direction (Markets to expansion stores) but does happen as brands' operational models evolve.
A Shopify Plus Agency for Strategic Design & Advanced Engineering
Building something ambitious?
- Expansion stores are Shopify Plus's pattern for running multiple independent stores under one organisation. Each store has its own catalog, inventory, admin, and operational team.
- Plus contract includes up to 9 expansion stores plus the primary store (10 total). The org admin provides cross-store user management and billing visibility but doesn't handle product, inventory, or order coordination.
- Three common patterns: regional separation, B2B and DTC separation, sub-brand or portfolio separation.
- Cross-store coordination requires explicit solutions: ERP/OMS for inventory and orders, middleware for product sync, separate CRM for customer consolidation.
- Cost: roughly 2-4x more expensive than equivalent Markets implementation in total cost of ownership. Each store needs its own license, implementation, integrations, and operational capacity.
- The most common mistake is choosing expansion stores when Markets would fit. Default to Markets and justify expansion stores when they're genuinely the right choice.
