Quick answer
Use Shopify Markets when you need regional pricing, currency, language, domains, and theme content differences without splitting your business across multiple stores. Use Managed Markets when the bigger problem is international compliance, duties, taxes, local payment methods, fraud, and merchant-of-record complexity. Use fully localized expansion stores only when a region needs its own operations, catalog, warehouse, team, legal entity, or merchandising strategy.
International ecommerce should make the customer experience feel local without turning the back office into a mess.
The decision in plain English
International selling on Shopify usually has three levels:
- Shopify Markets: One store, multiple market experiences. Use it for currencies, languages, country-specific domains, market pricing, and localized theme content.
- Managed Markets: Shopify-managed cross-border selling support where duties, taxes, compliance, and merchant-of-record responsibilities are handled through the program.
- Localized expansion stores: Separate stores for separate regional businesses, usually under a Shopify Plus organization.
The mistake is assuming every international problem requires another store. Many stores can localize the shopping experience without splitting products, themes, apps, customers, analytics, and operations into separate systems.
Start with the smallest structure that can support the real business requirement. If the requirement is “show Euros and translate the storefront,” a full expansion store may be too much. If the requirement is “Germany has its own warehouse, customer service, B2B rules, legal terms, product catalog, and marketing team,” a single store may be too cramped.
Use Shopify Markets when localization is the main need
Markets is the first place to look when the business wants to sell to different countries or regions from one Shopify store. It is built for tailoring the customer experience based on location, customer group, retail location, or sales channel.
Good candidates include:
- Different currencies by country or region.
- Translated storefront content.
- International domains or subfolders.
- Market-specific pricing adjustments.
- Localized theme content without separate theme maintenance.
- Simple regional merchandising differences.
Markets is usually the cleanest option when the store team wants international flexibility but still needs one product catalog, one theme codebase, one app stack, and one admin workflow.
The hidden catch is that localization and compliance are not the same thing. Markets can help you present the store differently to different customers, but the merchant still has to understand shipping, duties, tax setup, restricted products, returns, customer support, and regional policy requirements.
Use Managed Markets when cross-border responsibility is the hard part
Managed Markets makes sense when the store wants to reduce the operational burden of selling internationally. The useful question is not just “do we need local currency?” It is “who is responsible for duties, taxes, restrictions, fraud, payment methods, and import compliance?”
Good candidates include:
- US-based merchants expanding internationally without building a full compliance operation.
- Stores that want duties and import taxes handled more predictably.
- Stores that want local payment methods and fraud support for international orders.
- Teams that want Shopify’s program to act as merchant of record for eligible international transactions.
- Brands that need a better landed-cost experience without running separate regional stores.
Managed Markets can be very useful, but it is not free magic. There are transaction fees, payment processing fees, currency conversion considerations, eligibility requirements, and operational changes to review before turning it on.
It is also not always the answer for every business model. If a store has complex B2B, regional warehouses, distributor relationships, or strict legal entity separation, the merchant-of-record model and fulfillment requirements need a careful review.
Use localized expansion stores when the region is a real business unit
A fully localized expansion store is the heavy-duty answer. It is right when the region needs more than a localized experience. It needs its own operating system.
Use a regional expansion store when:
- Each region has a materially different product catalog.
- Inventory, fulfillment, and warehouse logic are separate.
- Regional teams need their own admin workflows.
- Legal entities, tax responsibilities, or policies must be separated.
- Apps, integrations, or checkout rules differ by region.
- Merchandising and marketing are different enough to justify a separate theme and content stack.
The benefit is control. The cost is overhead. Separate stores mean separate store settings, product sync, inventory sync, app configuration, theme maintenance, tracking setup, SEO management, redirects, customer data, and reporting. That overhead may be worth it for a major region. It is usually not worth it just to change currency symbols.
The hidden costs of each choice
| Choice | Hidden cost | Best when |
|---|---|---|
| Shopify Markets | You still own the operational side: shipping compliance, duties, tax setup, returns, regional policies, and support. | The business needs localization without operational separation. |
| Managed Markets | Transaction fees, FX considerations, eligibility rules, operational changes, and program limitations. | The business wants help with cross-border duties, taxes, compliance, fraud, and merchant-of-record complexity. |
| Expansion stores | High overhead, duplicated theme/app updates, product and inventory sync, fractured customer data, and more complex analytics. | The region operates like a separate business. |
A practical decision rule
Use this order before internationalizing a Shopify store:
- Can one product catalog support the region? If yes, Markets may be enough.
- Can one operations team support the region? If yes, avoid splitting stores too early.
- Is the pain compliance or presentation? If it is presentation, Markets. If it is duties, taxes, fraud, and merchant-of-record responsibility, consider Managed Markets.
- Does the region have separate inventory? If yes, evaluate whether inventory logic can be handled cleanly in one store or whether a regional store is justified.
- Will regional teams maintain their own content and apps? If yes, a separate store may eventually be cleaner.
- What happens when a theme update is needed? If the answer is “update five stores manually,” make sure the business understands that cost.
Examples
US store adding Canada and the UK
Start with Markets. If the products are mostly the same and the business needs local currency, localized content, and international domains, keep the architecture simple.
Brand expanding internationally but worried about duties and taxes
Review Managed Markets. If the compliance burden is the real blocker, using a merchant-of-record program may be more practical than opening separate stores.
European region with its own warehouse and catalog
An expansion store may be justified. When inventory, fulfillment, customer service, catalog, and legal requirements are truly regional, the overhead can be worth the control.
One country with a different homepage campaign
Do not open a new store for that. Use market-specific theme content, translations, or landing pages before creating a separate operational system.
Common misunderstanding
Localization is not the same thing as international operations. A localized storefront changes how the customer experiences the store. A localized operation changes how the business runs. Confusing those two is how teams end up with five stores when one store with Markets would have worked.
How to test this
- List what must change by country: currency, language, price, products, inventory, shipping, tax, legal terms, apps, support, or fulfillment.
- Try to model the requirement in Markets before opening a separate store.
- Estimate transaction, payment, and FX costs before enabling Managed Markets.
- Confirm whether the region needs its own warehouse or legal entity.
- Document who owns translations, redirects, SEO, customer support, and returns.
- Test the country selector, domain behavior, currency display, checkout, and fulfillment rules before launch.

