Shopify Markets vs multiple stores: how to choose
Decide whether to localise one store with Shopify Markets or run independent stores for different operations.
Read articleAI-generated Shopify blocks: how to create and review them
Request a useful block, verify its settings and test it before using it in a store.
Sidekick can generate theme blocks from a description in the Shopify editor. It helps create a first implementation; review whether it works, remains editable and fits the store.
This is not exclusive to Horizon. Compatibility depends on the theme and requirements in the official block generation guide.
When to generate a block
It may help with a specific composition absent from your theme: a feature table, service explanation or campaign element. First check existing sections and blocks, which usually need less maintenance.
For cart, payments, consent or customer data, technical review matters more than for purely informational blocks. Visual demos do not prove behaviour.
What to include in the description
- Objective: what visitors need to understand or do.
- Content: necessary title, text, image, video, buttons and fields.
- Layout: desktop-to-mobile changes.
- Editing: what staff should change without code.
- States: missing images, empty links or long titles.
Create a block explaining three product benefits. Each needs an editable title and text. Use three desktop columns and stack on mobile. Inherit theme colours and typography. Include an optional link per benefit and avoid gaps when fields are empty.
The instruction reduces ambiguity. Still check settings work as intended without unnecessary fixed content or styles.
Create it in the editor
- Start in a duplicate or development theme.
- Open the template and a section supporting the block.
- Select generation and describe the component.
- Review the first result with representative content.
- Request specific adjustments one at a time.
- Retain the block only after testing.
Shopify creates a theme block file. It needs maintenance even though conversation generated it. Developer documentation explains its relationship with block architecture.
Review before publishing
| Area | Test |
|---|---|
| Editing | Change every setting, verify results, save and reopen |
| Mobile | Long titles, buttons and media without overflow |
| Accessibility | Keyboard, focus, contrast and meaningful controls and images |
| Performance | Appropriate images without unnecessary downloads or scripts |
| Coexistence | Two instances without duplicate identifiers or breaking other theme elements |
Also remove and re-add the section in the editor. Interactive components must keep working afterwards.
Errors to correct
AI may solve the specific example but not everyday use: hardcoded links, desktop-only video or designs depending on exact text length. Staff need reusable components, not a screenshot that looks right once.
Code may also affect elements outside the block. Global heading styles or repeatedly registered events can cause failures far from the new section.
When custom development is appropriate
For business rules, app integration or behaviour the tool cannot reliably produce, convert the idea into reviewable development. Small changes may cost more to verify and maintain than to draft.
Before changing your whole store, review theme selection for SEO and performance and main menu organisation. We can review the result in a Shopify audit.
Editorial review: the Migraciones.io team · 30 October 2026. Features, plans and availability are checked against the linked sources.