monkeyman.agency
redesigns

Why Shopify's 'Generate With AI' Button Disappears (and How to Recover Lost Sections)

The Generate with AI button vanishes from Shopify's theme editor more often than you'd think. Here's why it hides, and how we recover sections that vanish after saving.

June 12, 2026 8 min read

Priya runs Cedar Loom, a home-textiles brand on Shopify doing roughly $80K a month. In March she built six landing sections with the theme editor’s Generate with AI button, shipped a spring campaign in an afternoon, and felt good about it. Mid-May she opened the editor to build the summer version. The button was gone. Two of the six sections had vanished from her homepage too, and nobody on her two-person team had touched the theme.

The button that was there last Tuesday

A merchant we hopped on a discovery call with last month put it almost word for word: “Generate with AI button missing after I used it to create sections. Created sections sometimes go missing as well.” Same story as Priya, different store, different month.

We’ve now audited enough of these that we can say the pattern out loud. The button disappearing and the sections disappearing feel like one catastrophic bug, but they’re two separate behaviors with two separate explanations. And neither of them is data loss in the way merchants fear.

That distinction matters because the panicked response, rebuilding everything from scratch in a new section, is usually wasted work. The code still exists somewhere. The job is finding it.

Where the AI generator actually lives

The button is part of Shopify Magic, the umbrella for Shopify’s native AI features. Inside the theme editor it shows up when you add a new section, offering to generate a layout from a text prompt instead of picking from your theme’s section library.

The key word is “offering.” It’s a conditional surface, not a permanent fixture. Shopify decides per store, per theme and per session whether to show it. Your store’s primary language matters (English stores see it most reliably). Your theme matters, since the generator targets Online Store 2.0 section architecture. Your plan and region matter. Even the rollout flags Shopify flips during feature updates matter.

So the button isn’t a tool you own. It’s closer to a feature Shopify lends you when the conditions line up. That framing changes how you treat the output, which we’ll get to.

The quiet conditions that switch it off

When the button vanishes, we run the same checklist on every client call, and it kind of always lands on one of five things.

The store switched or updated its theme, and the new theme version doesn’t expose the same AI surfaces. The staff account in the editor has narrower permissions than the owner account that used it last time. The store’s language or market settings changed during an expansion push. Shopify adjusted the rollout, which happens quietly and without a changelog entry. Or, most common of all, someone’s testing in a duplicate or trial theme where the feature was never enabled.

On a March sweep across 14 client stores, 11 of the “missing button” cases traced back to theme updates or duplicate themes. Not one was an account-level removal.

There’s no setting to force it back. What works is eliminating the conditions you control. Open the editor as the store owner, on the published theme, in a supported browser, with the store language set to English, and check again after the next theme update lands.

When a saved section just vanishes

The scarier half of Priya’s morning was the missing sections. Here’s what we find on nearly every one of these audits: the sections aren’t gone, they’re somewhere you’re not looking.

AI-generated sections get added to the specific template you were editing. Build one on a product template and it won’t appear on your homepage, and the reverse is also true. Merchants who were experimenting across templates in March genuinely can’t remember which template got which section by May.

The second hiding spot is duplicate themes. If you generated sections while previewing an unpublished copy (a redesign draft, a seasonal duplicate, a developer’s working copy), the saved sections live in that copy’s files. Publish a different theme and they seem to evaporate.

We ran recovery on nine stores in April. Seven of the “lost” sections were sitting in a duplicate theme in the library, untouched.

Why the prompt stops working after you save

The other complaint we hear on onboarding calls, almost verbatim: “After saving AI-created sections, how can I edit them via the AI prompt?” The short answer is you can’t, and that’s by design rather than by failure.

During generation, the prompt is live. You can iterate, regenerate, nudge the layout. The moment you save, Shopify writes the result into your theme as ordinary section code, Liquid and JSON settings like any hand-built section. The AI’s involvement ends at that commit. There’s no thread to reopen.

From then on you have two options. Edit the saved section by hand through the editor’s settings panel or the code editor, like any other section. Or generate a fresh section from a new prompt and rebuild your content inside it, which means re-entering text and images.

Neither feels great if you expected a conversational editing loop. But once you know save is a one-way door, you start treating the pre-save state as your editing window and the saved file as frozen output.

The recovery sequence we run on client stores

When a client calls about vanished sections, the sequence is boring and it works. We check every template in the published theme through the editor’s template switcher, since template-specific sections are the top culprit. Then we open each theme in the library, duplicates included, and scan their customizer for the missing layout.

If the editor shows nothing, we go to the code: AI-generated sections exist as files in the theme’s sections directory, so we pull the theme and grep for distinctive class names or copy from the lost section. A section that rendered on the storefront at any point left a file behind in whichever theme it belonged to.

The last resort is theme version history. Shopify keeps recent backups of published themes, and we’ve restored a client’s entire campaign homepage from one after an app’s theme update overwrote their section files. That client was a 4,200-SKU furniture store, and the restore took 20 minutes against an estimated two days of rebuild.

Total recovery rate across those nine April stores: every section but one. The one true loss came from a deleted duplicate theme, which is the single unrecoverable scenario.

Give every generated section a home in Git

Everything above is triage. The fix that ends the cycle is treating AI-generated sections as code the moment they’re saved, because that’s what they are.

The workflow we set up for clients takes an afternoon. Install Shopify CLI, run a theme pull against the live theme, and commit the result to a Git branch. After every session where someone generates and saves new sections, pull and commit again. The theme architecture docs are worth a read if your team hasn’t worked with section files directly, since knowing what a section file looks like makes the diffs legible.

Now a vanished section is a non-event. Theme update overwrote it? Restore the file from the branch. Duplicate theme got deleted? The code’s in the repo. Want to reuse a generated layout across three stores? Copy the file, not the prompt.

But the deeper win is psychological. Merchants stop fearing the button once its output stops being ephemeral.

What we keep telling clients

The Generate with AI button is a drafting tool, not a storage system. Use it freely to get from blank canvas to working layout, then immediately move the result into the same pipeline you’d use for any theme code. The merchants who get burned are the ones who treat saved sections as if Shopify is keeping a special AI archive somewhere. It isn’t. There’s just your theme, its files and whatever backup discipline you bring.

We also tell clients to stop diagnosing the button’s disappearance as an account problem. It’s a conditions problem, and most of the conditions are checkable in ten minutes. Published theme, owner account, English language, supported browser. If it’s still hidden after that, it’s a rollout flag and it’ll likely come back without you doing anything.

And we tell them the uncomfortable part: this feature will keep changing. Shopify iterates on Magic surfaces quickly, and the behavior you learn this quarter may shift next quarter. The only stable ground is the code the AI leaves behind: own that, version it, and the feature’s churn stops costing you rebuild time.

Priya’s two missing sections turned up in a duplicate theme her old agency had left in the library. We pulled both files into her published theme, set up the CLI-and-Git routine on the same call, and the button itself reappeared two weeks later after her theme’s next update. She’s generated 11 more sections since. Every one of them is committed within the hour.

Questions we get every week

Why did the Generate with AI button disappear from my theme editor?

Almost always a conditions change: a theme update, a duplicate theme, narrower staff permissions, a language setting, or a Shopify rollout adjustment. Check that you’re on the published theme as the store owner with the store language set to English. If it’s still missing, wait out the rollout; there’s no setting that forces it back.

Can I recover a section that disappeared after saving?

Usually, yes. Check every template in the published theme first. Then open the customizer of every theme in your library, duplicates included. If the editor shows nothing, pull the theme code and look in the sections directory, or restore from Shopify’s theme version history.

Can I edit a saved AI section with a new prompt?

No. Saving converts the generated layout into ordinary section code, and the AI prompt only works during the original generation session. Edit the saved section by hand, or generate a new section and migrate your content into it.

Is it safe to build real campaign pages with AI-generated sections?

It’s safe if you back the code up. Pull the theme with Shopify CLI and commit to Git after every generation session, and treat the saved files like any other theme code. The risk isn’t the AI’s output, it’s relying on a conditional editor feature as your only copy.

If you want every AI-generated section on your store inventoried, moved into version control and safe from the next theme update, talk to us about a one-week theme rescue.

Need help with this?

Send us your store. We'll send back an audit.

Send us your store URL. We'll send back a free audit within 48 hours.

Phone (optional)