AI theme blocks in Shopify Horizon
The most talked-about capability in Horizon, and the most frequently overstated.
AI block generation lets a merchant describe a storefront element in plain language and receive working code for it, inside the theme editor.
This page covers what it does reliably, where it stops, and — importantly — which Shopify AI features actually require Horizon and which work on any theme at all.
What is an AI-generated theme block?
An AI-generated theme block is a storefront component created from a plain-language description, produced as real theme code rather than as a page-builder object.
The workflow is straightforward. In the theme editor, a merchant describes what they want — a comparison table, a size-guide accordion, a shipping-threshold indicator — and the generator produces the Liquid, HTML and CSS for it, along with a settings schema so the block can be configured afterwards like any other.
The output is a file in your theme. It behaves like a block a developer wrote, appears in the block picker, and can be reused across templates. That’s the meaningful part: this is code generation, not a widget embedded from somewhere else.
How well does it actually work?
AI block generation works well for simple, self-contained components and becomes unreliable as complexity rises.
A block with a clear visual purpose and few moving parts — a formatted content module, a straightforward comparison layout, an accordion, a badge or trust element.
Blocks involving conditional logic, integration with app data, complex responsive behavior across breakpoints, or interaction with the cart. Sometimes more than writing it from scratch would have.
The practical rule: treat the generator as a scaffold rather than a finished product. It gets you a working structure quickly, and someone still needs to review the code, check accessibility, verify responsive behavior, and confirm it doesn’t conflict with anything else on the page.
That framing is neither dismissive nor promotional. It’s a real capability that removes a real category of small development requests, and the small requests are most of the queue in most stores.
What can’t it do?
Five things sit outside what AI block generation currently handles well, and knowing them prevents most disappointment.
A block that needs to read from a subscription platform, a reviews app or a personalization engine needs a real integration, and the generator does not build integrations.
Rules like “show this only to logged-in wholesale customers in Canada during a sale” involve business logic that has to be specified precisely, which is a development task regardless of who or what writes the code.
Generated output follows the theme’s conventions, not the conventions of a bespoke component someone built three years ago.
The generator optimizes for producing something that works, not for minimal render cost. On a page where every kilobyte matters, review the output.
Generated markup is usually reasonable and is not audited. If accessibility is a compliance requirement for your business, that check remains a human one.
Do you need Horizon to use it?
AI theme block generation requires a block-based theme like Horizon, because the output is a nested theme block and the older section model has nowhere to put it.
Two conditions worth knowing about beyond the theme itself. The capability is available across Shopify plans rather than being restricted to Plus. And the admin interface language affects whether the generate option appears — a block created in one language then works on a storefront in any language.
Which Shopify AI features work on any theme?
Most of Shopify’s AI capability is not theme-dependent, and confusing the two is the most common error in coverage of this topic.
| Requires Horizon or another block-based theme | Works on any theme |
|---|---|
| AI theme block generation in the editor | Sidekick |
| Nested block architecture | Agentic storefronts and UCP enrollment |
| Global blocks and cross-template reuse | Shopify Catalog |
| Design presets | Shopify Magic for product descriptions and admin tasks |
| Newer conversion-oriented section presets | Native A/B testing |
The rule that summarizes it: AI that changes your storefront’s structure is theme-dependent. AI that operates in the admin, on your catalog, or at the platform layer is not.
This matters commercially. If someone tells you that migrating to Horizon is necessary to participate in agentic commerce or to use Shopify’s AI assistant, that is not accurate. Those work on Dawn and on premium themes. The theme-gated capability is specifically about what a merchandiser can construct in the editor.
What does this change for a merchandising team?
AI block generation changes which requests become tickets, which is a smaller claim than “AI builds your store” and a more useful one.
Consider a typical week’s requests: a promotional banner with a countdown, a size-guide accordion on a product template, a three-column benefits module for a landing page, a shipping-threshold indicator in the cart. On a section-based theme, every one of those is a development request. Several are trivial to build and all of them queue behind work that genuinely needs an engineer.
On a block-based theme with generation available, most of those become editor tasks. The ones that don’t — anything touching app data or conditional business logic — still go to a developer, and should.
The realistic outcome is not that developers stop being needed. It’s that they stop being interrupted for work that didn’t need them — a throughput improvement for the whole team rather than a headcount argument.
Should this change your migration decision?
AI block generation is a reason to prefer a block-based theme, and on its own it isn’t a sufficient reason to rebuild a working store.
The stronger version of the argument is the architecture underneath it. Nested blocks, global blocks and cross-template reuse deliver most of the throughput benefit whether or not anyone uses generation. Generation makes the architecture more accessible to non-developers — it doesn’t create the capability.
If your team is currently blocked behind a development queue, that queue is the reason to consider migrating, and generation is one of several things that shortens it.
The full decision framework, including when the answer is no →
Frequently asked questions
What are AI theme blocks in Shopify?
AI theme blocks are storefront components generated from a plain-language description inside the theme editor. The generator produces real theme code — Liquid, HTML, CSS and a settings schema — which then behaves like any other block in the theme.
Do you need Shopify Horizon to use AI block generation?
Yes. AI block generation produces nested theme blocks, which requires a block-based theme. Older Online Store 2.0 themes like Dawn use a section model that has no equivalent structure.
Does Shopify Sidekick require Horizon?
No. Sidekick is a separate Shopify product that operates in the admin and works regardless of which theme your storefront uses.
How good is Shopify’s AI block generation?
It works well for simple, self-contained blocks and becomes unreliable as complexity increases. Blocks involving conditional logic, app data or complex responsive behavior typically need developer work. Treat the output as a scaffold rather than a finished component.
Do I need Shopify Plus for AI theme blocks?
No. The capability is available across Shopify plans, though it requires a block-based theme.
Does migrating to Horizon mean I can stop using developers?
No. It means fewer routine content and layout requests need one. Anything involving app integrations, conditional business logic or performance-sensitive work still requires development.
See where your storefront stands today.
We’ll benchmark your store against three competitors on speed, accessibility and technical SEO. Free, two minutes, nothing to install.
If the development queue is the real problem, the migration value calculator puts a number on what it’s costing you.
