Shopify Markets vs Separate Stores for Selling Abroad

Start with Markets on one store. It gives you per country domains or subfolders, local currency pricing with rounding rules, duties and tax calculation, and translated content, all from one inventory and one admin. Open a separate store when the local operation is genuinely separate: a different brand or license holder, a local entity that must own the revenue, a catalog that barely overlaps, or a team that needs its own checkout and apps. Separate stores multiply every cost, apps, maintenance, and reporting, so they need a structural reason, not just growth.

The question usually arrives dressed as a technical one and is really an operating model decision. One admin or many decides how many times you pay for apps, rebuild a theme fix, reconcile inventory, and train a team. Markets was built to collapse the old expansion store model, where every country meant a clone store and a clone workload, into settings on a single store. For most merchants selling abroad, it succeeds, and the clone stores are legacy weight.

That said, Markets has edges, and pretending otherwise sets merchants up to discover them mid expansion. Checkout customization tiers, some local payment and entity requirements, and catalog differences all push certain businesses toward separate stores for certain regions. The decision should be made on those specifics, not on how international the org chart feels.

What Markets actually covers on one store

Markets assigns countries to market definitions, each with its own products and pricing, domains or subfolders, duties and import tax handling, and language. Inventory pools stay shared, orders land in one admin, and customers can be routed by location to the right storefront version. Price adjustments can be set per market as percentage changes or fixed prices per product, with exchange rate based rounding so local prices end in sensible figures instead of conversion confetti.

For a merchant testing two or three new countries, this changes the economics completely. The experiment costs configuration time, not a store build. If a market disappoints, it is switched off. The learning, which products travel, which price points hold after duties, arrives before any structural commitment, which is exactly when you want it.

Where separate stores still win

Licensing and entity structure are the cleanest reasons. If a local partner or subsidiary must sell under its own entity, with its own payment accounts and tax registrations owning the transactions, that is a separate store's job. Brand separation is another: two brands sharing a warehouse still need separate storefronts, checkouts, and customer accounts, and Markets was never meant to merge them.

Deep catalog divergence is the quieter reason. When the regional assortment shares almost nothing, different suppliers, different compliance labeling, different content, the shared store stops being simpler and becomes a permissions and publishing tangle where every change risks the wrong region. At that point separate stores give each team a clean room. Notice what is absent from this list: wanting local looking design. Markets themes and domains handle presentation. Do not buy a second operation to solve a styling preference.

The costs people forget to count

Every additional store duplicates app subscriptions, and many apps price per store. Theme maintenance multiplies: a checkout or accessibility fix is built and tested once per store, forever. Reporting fragments, so the business loses a single view of the customer, and a shopper who buys in two regions becomes two strangers in two admins. Support teams context switch between stores with subtly different settings, which is where fulfillment errors breed.

Count those honestly against the Markets limitations for your case, in writing, before deciding. Stores opened for vague international ambitions and closed two years later are a common and expensive pattern. The reverse migration, consolidating clone stores into Markets, is also real work, but it trends in the direction of less overhead, which is why starting consolidated and splitting only on evidence is the safer sequence.

Frequently asked questions

Can I use different domains for each country with Markets?

Yes. Markets supports country specific domains, subdomains, or subfolders, and can redirect or recommend based on visitor location. Subfolders are the fastest to launch; separate domains carry more local trust in some markets and more setup.

Does Markets handle duties so customers are not surprised?

With duties and import taxes enabled, Shopify calculates and collects them at checkout for supported countries, so the customer pays a landed total instead of a courier bill on delivery. Coverage and requirements vary by country and shipping setup, so verify your main lanes.

Can I set completely different prices per country?

Yes. You can set fixed prices per product per market, or percentage adjustments on top of your base price, with rounding rules applied. Fixed prices give full control for key products; percentage adjustments scale across a large catalog with less upkeep.

When should I split a market into its own store?

When a structural reason appears: a local entity or licensee must own the sales, the brand or catalog genuinely diverges, or a regional team needs independent operation. Split on evidence from selling there, not in anticipation of it.