When we tell merchants that HI Engine writes and publishes theme changes, the first question is always the same: will it break my store?
It’s the right question. Your theme is your storefront: a broken product page during a campaign costs real money and real trust. So instead of answering with a promise, we think the answer has to be an architecture.
1. Nothing publishes to live without a human approval
The AI proposes; the merchant disposes. Every change starts as a described action: what will change and why, and what it’s estimated to be worth. Nothing is written until someone approves that specific action.
2. Draft theme first, always
Approved changes publish to a separate draft theme (named after the task), never directly to the live theme. You preview the change on your actual store, with your actual products, before a single customer sees it.
3. Theme Check before publish
Every modification runs through Shopify Theme Check before it ships: schema violations, constraint errors and block ID collisions when multiple patches apply at once. These are the boring failure modes that actually break stores, and they’re all catchable by machine, before publish, every time.
4. Logs and one-click rollback
Every change is logged: what changed and why, and how to undo it. Reversibility is what makes the whole system usable. Teams approve fixes faster when the cost of being wrong is one click.
The checklist
When you evaluate any tool that writes to your theme, ours included, ask four questions: Does anything reach live without my approval? Is there a draft/preview step on my real store? Is the code validated against Shopify’s own checks before publish? Can I see and revert every change? Four yeses, and AI-written theme changes are arguably safer than the average Friday-afternoon hotfix. Any no, and keep looking.