Horizon for Shopify Plus merchants
Horizon is free on every plan, including Plus. What changes at Plus scale is the assessment, not the build.
A handful of Horizon capabilities are Plus-only. More consequentially for a Plus merchant, the migration itself is a different exercise at scale — not because the build is harder, but because establishing what the store currently does is.
What’s Plus-only on Horizon?
A small set of Horizon capabilities require Shopify Plus, with combined listings the one most Plus merchants care about.
Most of what makes Horizon different — nested blocks, global blocks, AI block generation, design presets, the block-first editor — is available on every plan. Plus adds capability at the platform level rather than at the theme level, and the theme surfaces it.
The practical implication for a migration is that Plus status doesn’t change the shape of the work. It changes which features need reproducing and tends to correlate with the things that genuinely do change the work: more markets, more storefronts, more integrations and more custom logic.
How do combined listings actually work on Horizon?
Combined listings work on the product page, where the variant picker connects grouped products, but the collection page behaves differently — each grouped product still appears as its own card by default.
This is worth stating plainly because it’s frequently described as a solved problem and it isn’t quite. If your merchandising strategy depends on a single card per product family in collection views, that behavior needs an additional solution rather than being available out of the box.
For brands where combined listings were a reason to consider Horizon, test this specific behavior against your actual catalog before committing. It’s a good example of why a feature list is a poor substitute for an assessment.
What about B2B storefronts?
B2B on Shopify Plus involves customer-specific pricing, catalogs, payment terms and company accounts, and a theme migration has to reproduce every piece of display logic attached to those.
The exposure is in conditional logic rather than in layout. B2B stores accumulate rules about who sees which prices, which products, which shipping options and which messaging — and a meaningful share of that logic is typically implemented in theme code rather than configured in the platform.
That logic is also, in our experience, among the least documented functionality in any store. It was built to solve specific commercial situations, often by people who have moved on, and it fails in ways that are invisible to anyone not logged in as the affected customer type.
If you run B2B, the requirements phase matters more than the build, and testing needs to happen as each customer segment rather than as a general visitor.
Does anything change about the migration itself at Plus scale?
At Plus scale the requirements phase expands substantially while the build phase expands only modestly.
The reason is that larger stores accumulate more of everything that has to be captured: more custom sections, more app integrations, more metafields, more conditional rules, more markets, more templates that exist for one campaign three years ago and are still live.
Building against a complete specification is not much harder for a large store than a small one. Producing that complete specification is significantly harder, and it’s where a Plus migration is won or lost.
Two consequences follow. Assessment matters more, because the surface area is larger and the unknowns more expensive. And the merchant-side time commitment is front-loaded — more of your team’s involvement lands in the requirements window than in review.
More on documenting current state → · Timelines by complexity →
What about multiple storefronts?
Plus merchants frequently run several storefronts, and storefront count changes migration scope more than any other single factor.
Every storefront carries its own theme, its own accumulated drift, its own app configuration and its own testing burden. The offsetting benefit is that shared block architecture, decided once, makes the following years cheaper across all of them.
Horizon for multistore and multimarket brands →
Is it worth it for a Plus merchant?
For a Plus merchant, the case for migrating tends to be stronger than for a smaller store, because the cost of a rigid architecture scales with the size of the operation.
A single-storefront brand with a small team feels a development bottleneck as frustration. A Plus brand with multiple markets, a merchandising team and a campaign calendar feels it as a ceiling on how much the commercial organization can execute in a quarter.
The counter-argument is equally real. Plus stores have more to lose, more integrations to break, and more people who need to agree. That’s an argument for assessing carefully rather than for not moving — but it does mean the “just try it” approach available to a smaller store isn’t available here.
The full decision framework, including when the answer is no →
Frequently asked questions
Is Shopify Horizon available on Shopify Plus?
Yes. Horizon is free on every Shopify plan including Plus, and a small number of its capabilities — combined listings among them — require Plus.
Do combined listings work on Horizon?
Combined listings work on the product page, where the variant picker connects grouped products. On collection pages, grouped products still appear as separate cards by default, so a single card per product family needs an additional solution.
Does a Shopify Plus theme migration take longer?
Usually, and the additional time is concentrated in requirements rather than in building. Larger stores accumulate more custom sections, integrations, metafields and conditional rules, all of which have to be documented before a build can be quoted or verified.
What should Plus merchants pay most attention to when migrating?
Conditional display logic — B2B pricing rules, customer-segment-specific messaging, market-specific behavior. That logic is often implemented in theme code, rarely documented, and fails invisibly to anyone not logged in as the affected customer type.
Does Horizon support B2B on Shopify Plus?
Yes, though every piece of display logic attached to B2B pricing, catalogs and company accounts has to be reproduced in the new build and tested as each customer segment rather than as a general visitor.
At Plus scale, assessment is the part that matters.
Five days, a written evaluation across your storefronts: what each one does, which integrations are exposed, where your conditional logic lives, and what the project would actually cost. $2,500, credited in full against the migration.
Anatta is a Shopify Platinum Partner and has migrated $3.14B+ in GMV onto Shopify.
