Markets and currencies
Configured against how you actually sell, with rounding rules that do not produce prices like 47.83.
SHOPIFY MARKETS AND REGIONAL ROLLOUTS
Shopify Markets setups, regional launches and the market-by-market rollouts that follow — the work behind stores selling across the US, UK, Australia, Malaysia and India.
IN SHORT
Four areas, each with its own page.
One storefront serving every market, with pricing, catalogue and content handled per region. Teabox runs this way.
Launch one market, prove it, then repeat — the sequence Moonglow followed from the US into Australia and beyond.
A dedicated storefront when a market needs its own, as with Teabox India and Eat Cake Today in Malaysia.
Multi-vendor stores where each vendor brings their own catalogue, capacity and fulfilment window.
One storefront or one per country. Almost every other international decision follows from this one, and most brands make it by accident — usually by opening a second store for a market that did not need one, then discovering they now maintain two themes, two app stacks and two sets of content forever.
The honest rule: share the store until something genuinely diverges. A different language and currency is not divergence — Markets handles that. A different legal entity, a materially different catalogue, or fulfilment that works completely differently is divergence.
| Shopify Markets | A store per country | |
|---|---|---|
| Themes to maintain | One | One per store, or a shared deploy pipeline |
| Catalogue | Shared, with per-market availability | Fully independent |
| Pricing and duties | Per market, duties at checkout | Per store |
| Apps | One stack | Paid for and configured per store |
| Admin and reporting | One admin, split by market | Separate, needs consolidating |
| Best when | Brand and catalogue broadly shared | Own entity, catalogue or fulfilment model |
Six stages. The first two are decisions; getting them wrong is what makes international expensive.
One storefront with Markets, or a store per country. This decision shapes cost, maintenance and team structure for years, so it gets made deliberately rather than by default.
Subfolders, subdomains or country domains, with hreflang planned alongside. Decided before launch, because changing international URL structure later means redoing the SEO work twice.
Per-market pricing, rounding rules, and whether duties and import taxes are collected at checkout or left as a surprise on the doorstep. The second option costs you repeat customers.
Which products are available where, and which content varies. Handled per market rather than by duplicating the store, which is what keeps maintenance sane.
Local payment methods assessed per region, shipping and returns modelled honestly. A market with no viable return path is a market that will generate complaints, not revenue.
One market first, analytics split by market from day one, then the next launch uses what the first one taught rather than repeating it.
Duties as a surprise. A customer buys, the parcel arrives, and the courier asks for money before handing it over. That customer does not come back, and they tell people. Collecting duties at checkout costs a little conversion and saves the relationship.
Payment methods assumed. Card-only works in some markets and quietly caps you in others where local methods dominate. This is the single most common reason a market underperforms with no obvious cause.
URL structure retrofitted. Launching markets without deciding domain structure and hreflang means redoing it later — with redirects, lost equity and a period of search engines serving the wrong version to the wrong country.
Configured against how you actually sell, with rounding rules that do not produce prices like 47.83.
Decided before launch, so international SEO is built in rather than retrofitted.
Assessed per market rather than assumed, because the wrong method quietly caps a region.
Reporting separated by market from day one, so the next launch decision has evidence behind it.
Moonglow sells jewellery set to the moon phase of a date that matters to you. We built Find Your Moon: the customer enters a date of birth or other significant date, the store renders that moon phase, and it drives the personalised product.
A cake marketplace connecting customers to vendors across Malaysia. We built the back end that decides what can actually be delivered: each vendor has a daily capacity and each cake a lead time, and together they determine which dates and time slots a customer is offered at checkout.
Teabox sells tea from India to the rest of the world. We launched the store on Shopify Markets so one storefront serves every market, alongside a dedicated Teabox India launch.
Clients from the roster whose work this page describes. Each links to what we actually built.
Teabox sells tea from India to the rest of the world. We launched the store on Shopify Markets so one storefront serves every market, alongside a dedicated Teabox India launch.
Moonglow sells jewellery set to the moon phase of a date that matters to you. We built Find Your Moon: the customer enters a date of birth or other significant date, the store renders that moon phase, and it drives the personalised product.
A cake marketplace connecting customers to vendors across Malaysia. We built the back end that decides what can actually be delivered: each vendor has a daily capacity and each cake a lead time, and together they determine which dates and time slots a customer is offered at checkout.
A Shopify feature that lets a single storefront sell into multiple countries, with per-market pricing, currencies, catalogue availability, domains and duty handling — rather than running a separate store for each country.
Markets when the brand and catalogue are broadly shared: one theme, one admin, far less maintenance. A separate store when a region needs its own catalogue, legal entity or fulfilment model. Most brands over-buy here and end up maintaining stores they did not need.
Yes, duties and import taxes can be collected at checkout, with more control available on Plus. Getting HS codes and country settings right is the work that determines whether it behaves correctly.
Often not to begin with. Cross-border selling with duties handled at checkout gets most brands to the volume where a local entity starts to make commercial sense.
Through URL structure and hreflang. Each market needs a distinct URL — subfolder, subdomain or country domain — with hreflang telling search engines which version serves which audience. Decide this before launch; changing it afterwards means doing the work twice.
Moving platform and going international together? See migration services — Shopify Markets is often the reason an enterprise platform is no longer necessary. Multi-region inventory usually needs ERP integration.
NEXT STEP
We look at how your regions, currencies and catalogue are split today and what Shopify Markets would collapse into one.