Expansion Store vs. Shopify Markets: Which Fits a New Region?
Shopify Markets on your main store wins for a new region of an existing brand. One catalog, theme and app stack go live in 1 to 3 weeks, with Managed Markets at 3.25% on Plus for duties and tax. An expansion store wins for a new brand, a dedicated B2B store or a separate legal entity. Nine are included on Plus (verified Sep 2026), but nothing syncs between stores and apps bill again per store.
Your profile — see how the verdict shifts
- Confidence
- High — Read Shopify's expansion-stores page on 2026-09-05: a Plus organization can have a maximum of ten stores at no additional cost, each operating completely independently, with store settings, products, collections and inventory not synced, apps billed per store, and theme licenses required for each production store. Read the Managed Markets overview for the 3.25% Plus fee and Global-e's merchant-of-record role. Browsed six App Store categories (internationalization, currency and translation, shipping solutions, shipping rates, pricing, third-party logistics) and found no self-serve app that replaces the topology decision; Global-e, Zonos and Passport listings could not be located under any tested handle. The cost mechanics are verbatim from Shopify; the edge cases turn on entity, tax and fulfillment facts outside Shopify.
- Reference scenario
- $20M–$100M GMV · one brand on one Plus store today · entering a second region with its own currency, language, duties and shipping, fulfilled from existing warehouses · agency dev bench
- As of
- September 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| Same brand, new region (currency, language, duties) | WAIT | Stay on one store with Markets: market pricing, languages and a local domain on the catalog you already run, live in weeks. A second store re-bills every app for a job Markets already does. |
| Same brand, region traded by its own legal entity | BUILD | Open an expansion store: an entity with its own payouts, books and tax registrations fits a separate store. Expect the theme license and every paid app to bill again, plus a sync build for products and inventory. |
| New sub-brand with its own theme, domain and audience | BUILD | Open an expansion store: a second brand needs its own theme, app stack and checkout configuration, which Markets cannot express on one store. The store is included; budget the stack and the sync layer. |
| Dedicated B2B store or separately operated entity (franchise, JV) | BUILD | Open an expansion store: Shopify itself defines a dedicated store as a separate store used only for B2B customers (verified Sep 2026). Separate operators need separate settings, staff and data. |
What Expansion Store vs. Markets Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Revenue — direct | High | Local currency, local pricing and duties-paid checkout lift conversion in the new region; Markets delivers that on the store you have within weeks, while a second store waits on a stand-up project. |
| Operational efficiency | High | One catalog, one theme and one app stack mean every product change happens once; an expansion store repeats it, because store settings, products, collections and inventory aren't synced between stores (verified Sep 2026). |
| Data & insight | Medium | One store keeps a single customer record and order history per shopper; two stores split them, and Plus organization analytics re-aggregates sales rather than customers. |
| Customer experience | Medium | A region-specific theme, language mix and merchandising story reads as a local brand; an expansion store delivers that fully, while Markets delivers it partly through translations and market catalogs. |
| Retention & LTV | Low | Shoppers who cross regions keep one account and one history on a single store; separate stores fragment loyalty and email programs unless you build the bridge. |
Spend ceiling: Spend on what the region needs: pricing, duties, language, payment methods and local fulfillment. Spend nothing on a second store until a divergence Markets cannot express, such as a different brand, a dedicated B2B model or a separate legal entity, forces it.
What buying enables (top apps)
- + Market-specific pricing, currencies, languages and domains or subfolders on the store you already run, live in weeks rather than months
- + Managed Markets with Global-e as merchant of record for duties, tax remittance, commercial invoices and carrier arrangements, at 3.25% on Plus (verified Sep 2026)
- + Partial market management on Plus: stay merchant of record in chosen markets and use the managed service for the rest (verified Sep 2026)
- + One customer record, one order history and one analytics view per shopper across regions
What building additionally unlocks
- + A completely independent store with its own theme, app stack, checkout configuration, settings and staff, which is what a second brand or a dedicated B2B store needs
- + A separate legal entity's storefront with its own payouts and books, without bending one store's settings around two businesses
- + Isolation: a launch, a theme rebuild or an app failure on one store leaves the other untouched
- + Nine expansion stores included on Plus at no additional store cost (verified Sep 2026), so the store itself is never the expensive part
Find Your Verdict in 3 Questions
Is the new launch the same brand and catalog selling into a new region?
Yes: Your verdict: WAIT — Shopify Markets on your main store carries the region's currency, pricing, language and duties; nine free expansion stores don't make a second store cheaper once apps and themes re-bill.
No: Go to question 2.
Does the launch need its own theme, app stack or checkout configuration, as a second brand or a dedicated B2B store does?
Yes: Your verdict: BUILD — open an expansion store (up to nine are included on Plus, verified Sep 2026) and budget the per-store apps, the theme license and a sync layer.
No: Go to question 3.
Will the region trade through its own legal entity with its own payouts and books?
Yes: Your verdict: BUILD — an expansion store keeps the entity's storefront, settings and data separate; plan the product and inventory sync from day one.
No: Your verdict: WAIT — stay on one store with Markets, and revisit only when a divergence Markets cannot express appears.
The TCC Scorecard — 12 Dimensions
TCC — Total Cost of Capability: what it actually costs to have this capability over three years, whichever way you get it. Each dimension is scored 0–5 for both paths. How we score →
| Dimension | Buy | Build | Why |
|---|---|---|---|
| Cost | |||
| Acquisition & implementation | A new market on the main store is configuration plus theme localization, an estimated $5,000–$20,000; a second store is a stand-up project at $30,000–$90,000 including sync (Deploi estimate, illustrative). | ||
| Recurring fees | One store adds localization apps once; an expansion store re-bills every paid app, because apps are billed on a per-store basis rather than for the entire organization (verified Sep 2026). | ||
| Maintenance & upgrades | One theme and one app stack to update versus two of everything plus a sync layer that needs care every time a field or an app changes. | ||
| Switching & exit | Splitting a market out later or merging a store back are both migrations; orders can't be imported through the admin, so order history stays where it was created either way. | ||
| Risk | |||
| Vendor risk | Both lanes are first-party Shopify; Managed Markets adds Global-e as merchant of record, and a second store doubles the number of app vendors you depend on. | ||
| Security & compliance surface | Managed Markets hands duties, tax remittance and commercial invoices to Global-e (verified Sep 2026); a second store means a second set of staff, app permissions and settings to govern. | ||
| Platform-deprecation exposure | Markets and expansion stores are core platform features; the only code with deprecation exposure is the sync layer between stores, which is yours to move forward. | ||
| Value | |||
| Fit to requirement | Markets fits a region that shares the brand's theme and catalog; a completely independent store fits any divergence, including a different brand, checkout configuration or legal entity. | ||
| Time to market | A market goes live in 1–3 weeks on the store you have; an expansion store with a shared theme pipeline and sync takes 8–16 weeks (Deploi estimate, illustrative). | ||
| Performance & scale | One store serves many markets with up to 200 locations on Plus (verified Sep 2026); separate stores isolate load, settings and API budgets, which helps when regions launch on different calendars. | ||
| Data ownership & AI-readiness | One store keeps one customer record and one order history per shopper; two stores split them, and Plus organization analytics re-aggregates sales, not customers or inventory. | ||
| Focus & opportunity cost | Running a second store is a standing operational commitment, not a project; the team that maintains the sync layer is not building anything else. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Shopify Markets on your main store | Native — First-party Shopify, included on every plan. Market-specific pricing, currencies, languages, domains or subfolders and catalogs on the store you already run. Managed Markets, with Global-e as merchant of record for duties, tax remittance, commercial invoices and carrier arrangements, needs the Basic plan or higher, an online store and Shopify Payments (verified Sep 2026). | Markets included; Managed Markets 3.25% on Plus, 3.5% on Basic, Grow and Advanced, plus Shopify Payments processing (verified Sep 2026) | The same brand entering a new region |
| Plus expansion store | Native — First-party Shopify, Plus only. A Plus organization can have a maximum of ten stores on its contract at no additional cost: one main store and nine expansion stores. Each store operates completely independently; store settings, products, collections and inventory aren't synced between stores; apps are billed per store; theme licenses are required for each production store, staging stores exempt (verified Sep 2026). | Store included (up to nine expansion stores); apps and theme licenses re-bill per store (verified Sep 2026) | A second brand, a dedicated B2B store or a separately run legal entity |
| Easyship - All in One Shipping | Live — Adjacent, not a fit for the topology decision. Cross-border shipping rates, import tax and duty calculation and multi-location global accounts, needed under either lane. 4.1★, 389 reviews. | Free plan up to 50 shipments/month; Scale $99/month for 5,000–10,000 shipments/month with multi-location global accounts; 14-day free trial on paid plans (verified Sep 2026) | Shipping into the new region from existing warehouses, whichever store the order lands in |
| Cross-store sync layer (custom) | Build lane — The cost an expansion store forces and nobody sells as one product: products, inventory, customers and content kept in step between stores through webhooks and the Admin API, or through an ERP as the master record. Shopify's own guidance is to use third-party apps or ERP systems to sync certain data, such as inventory, between stores if required (verified Sep 2026). | $20,000–$60,000 one-time plus upkeep (Deploi estimate, illustrative) | Any organization running two or more stores that share products or stock |
The Build Path
- Stand up the expansion store from a shared theme codebase: Shopify CLI theme environments, configured in shopify.theme.toml and invoked with the --environment flag, push one codebase to development, staging and production instances across stores (verified Sep 2026). Theme licenses are required for each individual production store; staging stores are exempt.
- Re-license and reconfigure the app stack: Every paid app installs and bills again on the new store, so the first task is a stack audit: which apps the region needs, which were legacy, and which vendors will quote organization pricing instead of list price. Reconfigure each one; settings do not travel between stores.
- Build the sync layer: Products, inventory, customers and content drift apart the day store two goes live unless something keeps them in step. A webhook-driven sync through the Admin API, or an ERP as the master record, covers it; Shopify's guidance names both routes (verified Sep 2026). Decide which store, or which system, owns each field before writing code.
- Govern at the organization level: Plus organizations get custom organization-level roles and organization analytics, with multi-store reporting across every store since 2025-09-09 (verified Sep 2026). Both cut the operating cost of two stores; neither syncs a single product.
- Effort band
- $30,000–$90,000 to stand up an expansion store with a shared theme codebase, a reconfigured app stack and a product-and-inventory sync layer — Deploi estimate (illustrative); lands in the $25–75K contact-form band, higher with an ERP as master
- Typical timeline
- 8–16 weeks to a live expansion store with sync; a new market on the main store goes live in 1–3 weeks (Deploi estimate, illustrative)
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate) for the sync layer and the shared theme pipeline, roughly $4,500–$18,000/yr (Deploi estimate, illustrative), on top of the per-store app subscriptions the second store adds.
- What you own — and what you take on
- You own: a fully independent storefront with its own settings, staff, checkout configuration and data. You take on: two of everything to update, the sync layer between them, and app bills that arrive twice.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $5,000–$20,000 | $30,000–$90,000 |
| Years 1–3 (recurring) | $3,600–$18,000 (localization apps) | $85,500–$234,000 (per-store apps plus sync upkeep) |
| 3-year total | ≈$8,600–$38,000 | ≈$115,500–$324,000 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † Buy column = Shopify Markets on the main store: market setup and theme localization once, plus translation and localization apps on one store. Managed Markets at 3.25% on Plus (verified Sep 2026), or your own merchant-of-record setup, costs the same in either lane and is excluded.
- † Build column = one expansion store: theme license, an app stack re-billed per store at an illustrative $2,000–$5,000/month, a product-and-inventory sync build, and sync upkeep; three-year horizon.
What the Sticker Price Hides
On the buy path
- — Managed Markets adds 3.25% on Plus, plus currency conversion, on top of Shopify Payments processing (verified Sep 2026); model it against your own merchant-of-record setup before assuming it is cheaper
- — One theme serves every market, so a region that needs a different merchandising story gets translations and market catalogs, not a different site
- — Store-level settings are shared across markets; check which ones carry a market override before promising the region a different experience
- — Managed Markets eligibility needs the Basic plan or higher, an online store and Shopify Payments (verified Sep 2026), and depends on where the business is based
On the build path
- — Apps are billed on a per-store basis rather than for the entire organization (verified Sep 2026): a $3,000/month stack becomes $6,000/month with store two (illustrative)
- — Theme licenses are required for each individual production store; staging stores are exempt (verified Sep 2026)
- — Store settings, products, collections and inventory aren't synced between stores (verified Sep 2026); the sync layer is a build or an ERP, and it is never finished
- — Orders can't be imported through the admin, so merging two stores back into one later is a migration, not a setting
What Merchants Say
Merchants who opened a regional store for a free expansion slot describe the surprise as the second app invoice rather than the store: the stack they already paid for billed again on day one.
The recurring pain shape on multi-store setups is drift: a price change or a product update lands on one store and not the other, and nobody notices until a customer does.
If You Change Your Mind Later
If you bought and outgrow it
Splitting a market out into its own store later is a real migration: products and customers export and import, orders don't import through the admin, and market-specific pricing has to be rebuilt as the new store's base prices. Start on one store anyway; the split is rare and the merge is worse.
If you built and want out
Folding an expansion store back into the main store means re-homing customers, redirecting the domain, rebuilding regional pricing as market pricing, and accepting that order history stays behind, since orders can't be imported through the admin. The stack you re-licensed simply uninstalls, which is the one cheap part.
When This Answer Changes
We're watching for:
- ▸ Shopify syncing products, inventory or settings between expansion stores natively, which would remove the sync build from the expansion-store lane
- ▸ Shopify moving app billing from per-store to organization-level, which would remove the largest recurring cost of a second store
- ▸ Markets gaining market-level theme or checkout overrides broad enough to serve a second brand from one store
Verdict change log:
No changes since first publication (September 2026).
Common Questions
How many expansion stores does Shopify Plus include?
Shopify Plus includes nine expansion stores. Shopify's help page states a Plus organization can have a maximum of ten stores on its contract at no additional cost: one main store and nine expansion stores (verified Sep 2026). The store is free; the stack is not. Apps are billed per store rather than for the organization, theme licenses are required for each production store, and nothing syncs between stores by default.
When does an expansion store beat Shopify Markets?
An expansion store beats Shopify Markets when the launch needs its theme, app stack, checkout configuration or legal entity kept separate: a second brand, a dedicated B2B store or a separately run business. Shopify's B2B terminology defines a dedicated store as a separate store used only for B2B customers (verified Sep 2026). For the same brand entering a new region, Markets on one store wins on cost and data, live in 1 to 3 weeks.
What does a new region cost on Markets versus an expansion store?
A new region costs roughly $5,000 to $20,000 to set up on Markets and $30,000 to $90,000 as an expansion store (Deploi estimate, illustrative). The recurring gap is wider: every paid app bills again per store, so a $3,000/month stack becomes $6,000/month with store two (illustrative), plus sync upkeep. Managed Markets, at 3.25% on Plus (verified Sep 2026), costs the same in either lane.
Your Next Steps
If you're going with WAIT(matches your selected profile)
- List the region's real divergences: currency, language, pricing, duties, payment methods, fulfillment origin
- Configure the market with its own pricing and domain or subfolder, then localize the theme
- Decide merchant of record: Managed Markets at 3.25% on Plus (verified Sep 2026) or your own registrations
- Keep one customer record and one analytics view; resist a second store until a divergence forces it
- Re-open the topology question only for a new brand, a dedicated B2B store or a separate legal entity
If you're going with BUILD
- Audit the app stack before store two, since every paid app bills again per store
- Set up Shopify CLI theme environments so one codebase deploys to both stores
- Decide which system owns each field, then build the product and inventory sync
- Use organization-level roles and organization analytics to run both stores as one business
- Budget the theme license and the sync upkeep as recurring cost, not a one-time project
Official Docs & Sources
- Expansion stores — Shopify Help Center
- Shopify Markets — Shopify Help Center
- Managed Markets overview — Shopify Help Center
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Should You Build or Buy Bulk Channel Publishing on Plus?
No app bulk publishes products to your own channels and markets. On Plus, a small custom app on two exclusive GraphQL mutations does the job.
Checkout Extension Translations: Build or Buy the Localization?
Shopify states merchants can't override or add translations for a checkout UI extension, so whoever ships the extension owns every language it renders.
Per-Store App Fees or a Shared Hydrogen Front End on Plus?
Apps bill per store and theme licenses repeat per store on Plus. A shared Hydrogen front end removes the theme fee and little else. Go headless for other reasons.
Should You Plan Around Plus's 25-Hydrogen-Storefront Cap?
Plus documents up to 25 Hydrogen storefronts, and no app can lift that entitlement. The ceiling that arrives first is the number of codebases you can maintain.
Should You Build or Buy Multi-Currency & Market Pricing on Shopify?
Multi-currency is native on Shopify. The real decision is the market-pricing layer on top.
Ready to pick the right store topology before the invoices do?
We map the region's real divergences against Markets, and when a second store is the answer, we build the shared theme pipeline and the sync layer so drift never reaches a customer.
Contact us todayVerdict scored for the reference scenario above. Estimates are not quotes; app pricing carries its verification date and gets re-verified quarterly. Full scoring anchors: see the TCC methodology.
Read how we score these decisions (the TCC Framework). No affiliate links, no paid placement — no app vendor pays to appear here.