Theme drift
Stores diverging visually because changes were made in one and not the other.
WHEN A MARKET NEEDS ITS OWN
Local market store launches
Sometimes a market needs its own storefront rather than a slice of a shared one. Teabox India launched separately from the global Teabox store, and Eat Cake Today was built for Malaysia specifically.
IN SHORT
- A market earns its own store when catalogue, legal entity, currency handling or fulfilment genuinely diverge — not just because it has a different language.
- Until then, Shopify Markets is cheaper to run and far less to maintain.
- Two stores can share one theme: we keep it in a single repository and deploy to each store, so a design change is made once.
- The rule for what lives in the shared store and what does not should be written down before the second store exists.
- Teabox India launched separately from the global Teabox store, and Eat Cake Today was built for Malaysia specifically.
The four tests
Does this market actually need its own store?
Entity. Are you trading through a separate legal entity, with its own invoicing, tax registration and consumer obligations?
Catalogue. Is the product range materially different — not a few restrictions, but a genuinely different assortment?
Fulfilment. Does the market ship from its own warehouse, with its own stock pool and its own returns process?
Payment. Does it need local payment rails or an acquiring relationship that cannot sit on the main store?
One clear yes usually justifies a store. None of them, and Shopify Markets is the cheaper, saner answer — and we will say so.
One store or several
| Markets on one store | A dedicated local store | |
|---|---|---|
| Setup cost | Configuration | A build |
| Ongoing maintenance | One theme, one app stack | Two of each, forever |
| Catalogue independence | Availability rules per market | Complete |
| Separate entity or invoicing | Awkward | Native |
| Local fulfilment and stock pool | Possible but constrained | Clean |
| Reporting | One admin, split by market | Needs consolidating |
How a local launch runs
Six stages. The first is a genuine attempt to talk you out of it.
- 01
Test the divergence
We check whether the market actually needs its own store, against four tests: entity, catalogue, fulfilment and payment. If none apply, we will tell you Markets is the better answer and save you the build.
- 02
Draw the boundary
What is shared between stores and what is local, written down. Products, content, customer data, reporting — this rule prevents two stores quietly becoming two businesses.
- 03
Set up the shared theme
One theme in one repository, deployed to both stores with per-store settings. This is what stops the second store drifting visually within a year.
- 04
Local commerce setup
Local payment methods, tax and invoicing rules, shipping and returns handled the way that market expects rather than the way the home market does.
- 05
Local content and compliance
Regulatory copy, consumer rights information and the content that genuinely needs to differ. Not a wholesale translation of everything by default.
- 06
Consolidated reporting
Reporting brought back together across stores from day one, so you can still see the whole business rather than two halves of it.
What stays shared
- The theme — one repository, deployed to each store with per-store settings
- The design system: tokens, components and section library
- Brand content that does not need to differ, so it is not maintained twice
- Development process, QA standards and release approach
- Consolidated reporting across stores
- The team, so knowledge does not fragment by store
The failure mode for multi-store brands is drift. Two stores start identical, and eighteen months later one has a redesigned product page, a different app for reviews and a checkout nobody has looked at. Shared theme and shared team is how that is prevented.
Brands with dedicated local stores
Eat Cake Today
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
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.
Teabox India launched separately from the global Teabox store, which runs on Shopify Markets. Eat Cake Today was built for Malaysia specifically, where the vendor network and delivery model are the business — see multi-vendor marketplaces.
What we watch for
Duplicated content work
The same campaign built twice, slightly differently, with one version going stale.
Fragmented reporting
Two admins, two sets of numbers, and nobody able to see the whole business.
App stack sprawl
Different apps solving the same problem in each store, doubling cost and support surface.
Who we have done this for
Clients from the roster whose work this page describes. Each links to what we actually built.
Teabox
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.
Eat Cake Today
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.
Local launch questions
When does a market deserve its own Shopify store?
When the catalogue, legal entity, currency handling or fulfilment differ enough that per-market settings on one store start fighting you. Until then, Markets is cheaper to run.
Can two Shopify stores share a theme?
Yes — we keep the theme in one repository and deploy it to each store, so a design change is made once.
When does a market deserve its own Shopify store?
When the catalogue, legal entity, currency handling or fulfilment differ enough that per-market settings on one store start fighting you. A different language or currency alone is not enough — Shopify Markets handles both, and running a second store costs you a theme, an app stack and an admin forever.
Can two Shopify stores share a theme?
Yes. We keep the theme in one repository and deploy it to each store with per-store settings, so a design change is made once rather than twice with one of them going stale.
How do we report across multiple stores?
Reporting is consolidated outside Shopify, usually into whatever analytics or BI tool you already use. Planning this before the second store launches is much easier than reconstructing it a year later.
Related
Shopify Markets
One storefront serving every market, with pricing, catalogue and content handled per region. Teabox runs this way.
Regional Rollouts
Launch one market, prove it, then repeat — the sequence Moonglow followed from the US into Australia and beyond.
Marketplace Models
Multi-vendor stores where each vendor brings their own catalogue, capacity and fulfilment window.
NEXT STEP
Markets review
We look at how your regions, currencies and catalogue are split today and what Shopify Markets would collapse into one.