Horizon for multistore and multimarket brands
Running several storefronts turns a migration from a project into a program.
Most published guidance doesn’t account for it. The reason is arithmetic. Every decision made once on a single-store migration gets made several times, and every change that follows gets made several times too — which is both why the migration costs more and why the case for doing it is stronger.
What’s different about migrating more than one storefront?
Migrating multiple storefronts multiplies the work rather than adding to it, because each storefront carries its own theme, its own customizations, its own app configuration, and its own accumulated drift.
Four things scale with storefront count:
Each storefront needs its own inventory. Two storefronts that started identical rarely stayed identical — someone made a change on one and not the other, and the difference is undocumented.
Shared architecture helps enormously, but per-storefront configuration, content and testing do not disappear.
Each storefront’s app stack needs mapping and re-integrating separately, and stacks diverge over time even under one brand.
Every storefront gets a full review pass. This is the part most often underestimated.
The compensation is that a well-built multistore migration installs shared architecture that makes the next several years cheaper. That’s the actual return, and it doesn’t show up in a single-project comparison.
How does Horizon handle multiple languages?
Horizon ships with native translations in several major European languages and does not require Shopify Markets to serve multiple languages.
For languages outside the built-in set, you use Shopify’s Translate & Adapt or a translation app, which is the same approach as any other theme.
The detail worth knowing is that theme-level string translations are only part of the picture. Custom string overrides that live in your current theme’s locale files are theme content, and they do not carry across on their own. Every override needs identifying and reproducing — and because overrides are usually added one at a time over years, they’re rarely written down anywhere.
Do you need Shopify Markets?
Shopify Markets is not required to serve multiple languages on Horizon, but it is what you use for market-specific pricing, currency, domain routing and product availability.
The practical distinction: language alone can be handled at the theme and translation layer. Market-specific commercial behavior — different prices, different currencies, different products available, different legal or shipping messaging — is a Markets configuration.
Most brands running genuinely international operations need both, and a migration touches both. The theme rebuild has to reproduce whatever market-conditional display logic exists today, and that logic is frequently embedded in theme code rather than documented anywhere.
How do you keep several storefronts consistent without rebuilding each one?
Global blocks are the mechanism that makes multistore consistency practical on Horizon, because a global block is defined once and applied wherever it’s used.
The architectural decision to make early is which components should be global and which should be per-storefront. Getting this right is most of the long-term value of a multistore migration. Getting it wrong means you’ve rebuilt the same problem you had before, with newer syntax.
| Global | Per storefront |
|---|---|
| Header, footer and navigation patterns | Regional legal copy |
| Promotional bars | Market-specific merchandising |
| Standard content modules | Locally required disclosures |
A reasonable default. Brand-level components global; anything genuinely market-specific local.
This decision belongs in the requirements phase, not the build. It’s an architecture question, and it’s expensive to reverse once several storefronts are built against it.
What does the timeline look like?
A multistore or multimarket migration typically runs six to ten weeks, against three to six for a single storefront in a single market.
The extra time is not proportional to storefront count, because the first storefront establishes the shared architecture and subsequent ones benefit from it. In practice the second storefront costs meaningfully less than the first, and the fourth costs less again.
What doesn’t compress is testing and market-specific configuration. Each storefront and each market needs a genuine review pass, and those hours are close to linear.
Why does this cost more?
Multistore and multimarket migrations are priced as a separate tier because the requirements, configuration and testing work scales with the number of storefronts and markets, rather than being fixed.
The dominant costs are per-storefront requirements documentation, per-market conditional logic, translation and locale handling, and per-storefront testing. The shared build architecture is the part that benefits from scale; almost nothing else does.
The offsetting argument is worth making honestly: brands running several storefronts are usually paying the highest ongoing price for a rigid architecture, because every change is currently made several times. If a merchandising change takes three weeks on one storefront, it takes three weeks on each of them.
What should you decide before starting?
Four decisions shape a multistore migration and are much cheaper to make at the start than midway through.
The architecture question above.
Sequencing reduces risk and extends the timeline. Migrating together is faster and concentrates the launch risk into one event.
Not the biggest one. Choose the one that best represents your shared architecture, so what you learn applies to the rest.
Some brands want visual and structural uniformity across markets; others deliberately diverge for local relevance. Both are valid, and building for one when you wanted the other is an expensive discovery.
Frequently asked questions
Does Shopify Horizon support multiple languages?
Yes. Horizon includes native translations for several major European languages, and additional languages can be added using Shopify Translate & Adapt or a translation app.
Do you need Shopify Markets to run multiple languages on Horizon?
No. Multiple languages can be served without Markets. Markets is what you use for market-specific pricing, currency, domain routing and product availability.
How much longer does a multistore Horizon migration take?
Typically six to ten weeks, against three to six for a single storefront in a single market. Subsequent storefronts cost less than the first because they inherit the shared architecture.
Can several Shopify storefronts share a Horizon theme?
Storefronts can share a theme codebase and global block architecture, with per-storefront configuration and content layered on top. Deciding what is shared and what is local is the most important architectural decision in a multistore migration.
Why does a multistore migration cost more?
Requirements documentation, market-specific configuration and testing all scale with the number of storefronts and markets. Only the shared build architecture benefits from doing several at once.
Multistore migrations are scoped, not estimated.
Five days, a written assessment across your storefronts: what each one does, what would break, what shared architecture would look like, and what it would cost. $2,500, credited in full against the migration.
Multistore and multimarket work is priced as a separate tier — see the published pricing for what sits behind it.
