International Shopify Migration: Handling Multi-Currency and Multi-Market Stores

Four country storefronts on the old platform do not have to become four Shopify stores. They might become one store with four markets, two stores with several markets each, or one store for retail customers and a second for a business unit that invoices under its own company name. Which of those outcomes an international Shopify migration lands on decides how prices are maintained, where stock is counted, which legal entity takes the payment and whether the search visibility built up in each country survives the move.

For a retailer selling broadly the same catalogue into several countries from one company, a single Shopify store using Shopify Markets is usually the simpler destination, with fixed prices for the main markets and localised URLs that keep each country’s pages indexable. Separate expansion stores earn their extra running cost when catalogues, legal entities, teams or back-office systems genuinely differ by country. Either way, the structure is best settled before any data moves, because currencies, translations, redirects and tax settings all hang from it.

What the Existing Country Stores Are Actually Doing

Older platforms often reached multi-country selling by stacking stores. Adobe Commerce, for example, organises an installation as a hierarchy of websites, stores and store views, where a website can carry its own domain and a store view typically holds translations and currency display. A retailer that grew country by country may have added a website for separate prices and a store view for each language, at different times and for different reasons.

The number of stores therefore rarely matches the number of real differences. Two websites might exist only because prices once had to differ, while the catalogue, warehouse and team are shared. Copying that shape onto Shopify preserves the workaround rather than the requirement, so the better starting point for an international Shopify migration is an inventory of what each storefront does differently:

• Price logic. Whether the country uses converted prices, a maintained price list, or rounded “charm” prices, since each maps to a different Shopify setting and a different amount of ongoing work.
• Assortment. Products that cannot be sold in a country for regulatory, licensing or logistical reasons, because availability will be controlled per market rather than per store.
• Language and URL. The language served, the domain or subfolder, and how many pages rank in that country, as this decides how much redirect work the country needs.
• Tax, duties and the selling entity. Which company sells, whether prices include tax, and whether import charges are collected at checkout or left to the courier.
• Fulfilment and integrations. Which warehouse ships the order and which ERP, accounting or email system expects to receive it, in which currency.

The inventory also tends to expose differences that were inherited rather than chosen, such as a country price list that has not been reviewed in years or a language version with a handful of orders a month. Those are better retired before the move than rebuilt on Shopify.

One Store With Shopify Markets or Several Expansion Stores?

Shopify Markets lets one store present itself differently by country or region. According to Shopify, each market can carry its own catalogues and pricing, currency, theme customisations, domains and languages, and duty and tax settings. Older migration plans sometimes assumed a small cap on how many countries a store could target; Shopify’s Plus plan documentation now states that all Shopify plans include an unlimited number of country or region markets, so the count of countries alone is no longer a reason to split stores.

Expansion stores are the alternative on Shopify Plus. Shopify’s guidance on expansion stores allows one main store and nine expansion stores on the contract, and states that settings, products, collections and inventory are not synced between them by default. Apps are billed per store, so every extra store brings its own catalogue, its own app stack and, often, a sync job through an ERP or third-party tool.

Choose a single store with Shopify Markets when the catalogue and back office are shared and the differences between countries are commercial rather than operational. Expansion stores become the stronger option when a country runs a different assortment from a different warehouse under a different company, or when a regional team needs to change apps and theme independently. A hybrid is also common: one store with markets for most countries and a separate store for the one operation that really is different.

Multi-Currency Pricing: Converted Prices or Fixed Price Lists

Shopify can display and charge in local currencies, but its local currency pricing documentation notes that only stores using Shopify Payments with access to one-page checkout can use all of the feature’s functionality. For a retailer with a long-standing gateway contract, the payment provider is therefore a structural question, and the multi-currency design needs checking against it first.

By default, Shopify converts prices at the current market exchange rate, and merchants can set manual rates to stop prices drifting with currency movements, with rounding to tidy the results. Converted multi-currency pricing is quick to launch and needs little upkeep, but it suits markets where small price movements are acceptable and the store does not compete on a well-known local price point.

Retailers who already maintain country price lists usually want them preserved, which maps to market catalogues. Shopify’s catalog documentation explains that a price set manually in a catalogue overrides its overall percentage adjustment, and that prices can be managed in bulk through CSV. One detail matters for migration scripts: the catalogue CSV only includes fixed-price products, so items priced by adjustment will not appear in it, which is easy to misread as missing data during reconciliation.

The practical choice often ends up mixed: fixed lists for the few markets that carry most revenue, where margin and advertised prices matter, and converted prices for smaller countries where maintaining a list would cost more than it returns. Either way, each old price list should be reconciled against the new catalogue, SKU by SKU, before launch.

Keeping Search Visibility in Each Country During an International Shopify Migration

Search equity in an international store is held country by country, so it can be lost country by country. Shopify’s SEO documentation for Shopify Markets supports subfolders, subdomains and country domains, generates hreflang tags automatically from the market and language configuration, and serves crawlers the URL they requested rather than redirecting them to another market.

The URL structure still deserves deliberate thought. Moving from country domains to subfolders consolidates authority and simplifies administration, but it changes every URL in those countries, and each needs a redirect. Keeping country domains preserves familiar addresses at the cost of more domains to manage. The better option depends on how much traffic each domain earns and how strongly local customers recognise it.

Google’s guidance on localised versions of pages is a useful check: each language version must list itself and every other version, or the annotations may be ignored. Its advice on multi-regional sites also cautions against automatically redirecting users between language versions, so a geolocation redirect carried over from the old platform is worth reviewing rather than simply rebuilding.

Languages carry their own limits. Shopify’s requirements for selling in multiple languages allow up to 20 languages on the Basic, Grow and Advanced plans and up to 30 on Plus, and while product handles can be translated, the products segment of the URL cannot. Localised product URLs from a previous platform will rarely survive unchanged, so each locale needs its own redirect map, built as described in our Shopify 301 redirects migration guide.

Tax, Duties and the Company Behind Each Market

Tax is where an international move tends to slow down, and the difficulty is not unique to migrations. Salesforce’s guide to global ecommerce, citing its State of Commerce research, names tax as the greatest major challenge for businesses selling internationally, at 28%. The figure ranks sellers’ obstacles rather than measuring migration risk, but it explains why tax design usually deserves its own workstream.

That workstream settles whether displayed prices include tax in each market, which changes how price lists are rebuilt, and whether duties and import taxes are estimated at checkout, which Shopify supports so customers avoid unexpected charges on delivery. It also settles which company legally makes each sale, a question that often catches groups with subsidiaries.

Shopify’s developer documentation on multiple business entities explains that markets can be linked to separate legal entities within one store on Shopify Plus, with one legal entity per country, and that only Shopify Payments, PayPal Express and manual payment methods are supported across multiple entities. If a subsidiary depends on a different local gateway, a separate store may be the cleaner answer.

Some merchants can hand much of this to a merchant of record. With Shopify’s Managed Markets, Global-e becomes the merchant of record and handles tax remittance, local payment methods and duties, but availability is limited to merchants based in the continental United States and certain stores in Canada and the United Kingdom. Retailers headquartered elsewhere will usually plan around their own registrations.

Internal expert input required: confirm which tax configurations (for example EU OSS registration, UK VAT, US sales tax) WD Market most often sets up during international Shopify migrations, and any approach the team recommends for tax-inclusive pricing across markets.

Where Integrations Need to Become Market-Aware

Back-office systems connected to several country stores were often built to receive one feed per store, so the store itself told them which country, currency and company an order belonged to. After consolidation, that signal has to come from the order. Shopify’s Admin API represents amounts as a MoneyBag holding both the shop-currency amount and the presentment-currency amount the customer saw, so an ERP connector must decide deliberately which of the two it books.

Marketing systems need the same attention. Klaviyo, for example, describes its Locale Aware Catalogs as syncing language, currency, pricing and region-specific product URLs from Shopify Markets, replacing manually maintained catalogues per country. Capabilities vary between tools, so each connector is worth testing with an order and a product from every market before launch.

Inventory deserves a final check. Separate country warehouses become locations in Shopify, and the Plus plan supports up to 200 of them. The rules deciding which warehouse fulfils which country then need rebuilding in shipping and fulfilment settings, or a shared stock pool may sell units a country cannot ship.

A Market-by-Market Migration Sequence

The order below keeps structural decisions ahead of data work, which is where most rework on multi-country projects tends to originate.

1. Inventory every country storefront. Record price logic, assortment, language, URL structure, tax treatment, selling entity, warehouse and connected systems, and note which differences are genuine requirements rather than inherited workarounds.
2. Decide the store and market structure. Settle single store, expansion stores or a hybrid, and confirm the plan, payment provider and entity setup that structure requires.
3. Rebuild pricing per market. Choose fixed catalogues or converted prices with rounding for each market, load the price lists and reconcile them against the old platform SKU by SKU.
4. Localise content and map URLs. Import translations, choose domains or subfolders, and build one redirect map per locale, checking that hreflang output covers every language version.
5. Configure tax, duties and payments, then test checkout in every market. Place test orders with real addresses from each country and confirm currency, tax, duty, payment methods and the order record received by the ERP.
6. Launch and monitor by market. Track orders, conversion, crawl errors and redirect hits per country for the first weeks, because a fault in one market can be hidden inside healthy totals.

Whether all markets switch on the same day is a judgement call. A single launch avoids running two platforms in parallel. A staggered launch, starting with a smaller market, limits the impact of an early mistake but extends the period in which stock, customers and orders live in two systems. Staggering tends to suit operationally separate markets; a single launch suits countries that share one warehouse and one team.

Key takeaway: count the real differences between countries, not the stores. Price, language and domain differences usually belong in Shopify Markets; different companies, catalogues and warehouses may justify a separate store. Deciding that first keeps pricing, redirects and tax work from being done twice.

Mistakes That Make Multi-Market Migrations Expensive

• Mirroring the old store count. Recreating every legacy website as a Shopify store can multiply app fees and catalogue upkeep for differences that a market setting would have handled.
• Leaving the payment provider decision until late. Multi-currency features and multi-entity support depend on the provider, so a late change can reopen pricing and checkout work already signed off.
• One redirect map for all countries. Locale URLs change in different ways, and a single map tends to send foreign-language visitors to default-language pages, wasting the equity those pages held.
• Testing checkout only from the home country. Tax, duty and payment method behaviour differs by market, and problems often appear only with a real address in that country.

What a Multi-Country Build Has to Account For

Our work with Astra Velo, a bicycle retailer with a large catalogue and physical stores, shows how much country-level logic an international setup can hold. It was a Magento 2 project, not a move to Shopify, and it is mentioned here for the shape of the requirements rather than the platform. The Astra Velo case study describes localised storefronts for 4 countries, “each with its own inventory and pricing rules”, connected to the retailer’s ERP for order processing and stock synchronisation. Any future move of a setup like that would begin with the same country-by-country inventory: which pricing rules differ, which stock belongs where, and what the ERP expects to receive.

For growing into new countries, as opposed to moving an existing international store, see our guide to multi-country ecommerce scaling.

Internal expert input required: add a verified, publishable example from an international Shopify migration, such as how country price lists or locale redirects were handled.

Settling the Structure Before the Data Moves

An international Shopify migration often succeeds or struggles on a decision made before any product is imported: how many stores the business really needs. Commercial differences between countries can usually live as markets inside one store, while operational differences, such as a separate company or warehouse, are what make a second store worth its cost. With that settled, price lists can be reconciled, locale redirects mapped and checkout tested in every market, and integrations can learn to read the market from the order rather than from the store.

From Several Country Stores to One Planned Shopify Setup

Before any development, WD Market’s Shopify migration services start with a feasibility review of the current platform’s functionality and custom logic: which parts move across as they are, which are replaced or simplified, and whether Shopify Plus is genuinely required. For a multi-country store, that is where the market structure, pricing approach and redirect scope are agreed, and where keeping separate stores, or the current platform, is weighed as a legitimate outcome.

To review your own country setup, send us an outline of your markets, including the currencies, languages and back-office systems each country relies on. For ongoing notes on migrations, integrations and international selling, follow WD Market on LinkedIn.

International Shopify Migration: Common Questions

Do we need Shopify Plus to migrate a multi-country store?

Not always. Selling to several countries with local currencies, languages and domains is possible on standard plans. Plus becomes relevant when the business needs expansion stores, wants different legal entities behind different markets, or needs more than 20 languages. The deciding factor in an international Shopify migration is usually entities or separate operations rather than the number of countries, so the plan is easier to choose once each country’s requirements are listed.

Can one Shopify store keep different prices for each country?

Yes. In Shopify Markets, each market can use its own catalogue, where a manually entered product price takes precedence over any percentage adjustment, so existing country price lists can be carried across. Markets without a maintained list can rely on multi-currency conversion with rounding instead. Combining the two keeps maintenance manageable while protecting margin in the countries that matter most commercially.

Will our country domains lose rankings after the move?

Rankings often move for a while after a platform change. Where losses persist, the cause is frequently a gap in the redirects rather than the new platform itself. Each domain or language version needs its own map from old URLs to their closest new equivalents. Shopify supports keeping country domains or moving to subfolders, and it generates hreflang tags for the configured markets. Checking those tags and the redirect hits for each country after launch helps catch problems early.

What happens to customers who bought from more than one country store?

When several country stores merge into one Shopify store, the same person may appear in more than one source database, often under the same email address. The migration needs a rule for combining those records and deciding which address, language preference and marketing consent to keep. Consent deserves particular care, because permission given in one country should not silently extend to messages in another. Order histories can then be attached to the combined record.

Can a European retailer use Shopify Managed Markets?

Generally not at present. Shopify limits Managed Markets, where Global-e acts as merchant of record, to merchants based in the continental United States and certain stores in Canada and the United Kingdom. A retailer headquartered in the EU would typically configure taxes and duties itself or work with a separate cross-border provider. Availability can change, so it is worth confirming against Shopify’s current documentation when planning.