Shipping Shopify Theme Changes Directly to Shopify with Claude
Last updated: October 8, 2026
At a glance
If you don't use GitHub for your Shopify theme, Claude can ship changes straight to Shopify for you. With the Noibu MCP and the Shopify connector turned on in Claude, Claude finds the issue, makes the fix on a theme, and gives you a preview link to test. You approve, and then it goes live.
Use this guide if no developer or agency manages your theme through GitHub. If your live theme is connected to GitHub, follow Shipping Shopify Theme Changes with GitHub instead.
The golden rules:
Back up your live theme before anything goes live.
Test on a preview link first, and approve changes before Claude makes them.
Turn on the Noibu app embed on any theme before it goes live.
The short version
Pick the workflow that matches how your team already ships.
Claude makes the changes on a duplicate or preview theme (or on the live theme, for small fixes).
Test using the preview link.
Back up the live theme.
Publish the theme, or copy the changes to the live theme.
Check the live site and the Noibu app embed, then clean up old themes.
Before you start
Check these once before your first change.
The Noibu MCP and the Shopify connector are both connected in Claude, and the Shopify connector has access to your theme.
Your live theme is not connected to GitHub. If it is, use the GitHub guide instead.
You can publish themes in Shopify admin (Online Store > Themes), or you know who can.
The Noibu app embed is turned on for the live theme (Online Store > Themes > Customize > App embeds). Instructions here.
You know how many themes you have. Shopify limits how many a store can hold, so clear out old drafts you no longer need before creating new ones.
Any code freezes are on your radar (sales, peak season). Don't ship during a freeze.
Pick your workflow
There's no single right way to ship without GitHub. Pick the one that matches how your team already works, and Claude will follow it. In every workflow, you can bundle a series of related changes into one theme instead of creating a new theme for every fix.
Workflow | How it works | Best for |
|---|---|---|
A. Duplicate, change, publish | Claude makes changes on a duplicate of the live theme, then you publish the duplicate | Most teams. The simplest and safest option |
B. Preview theme, then copy to live | Claude makes changes on a preview theme, then copies the same changes to the live theme | Teams who test in one place and ship in another |
C. Edit the live theme | Claude makes small changes directly on the live theme, after a backup | Small, low-risk fixes where this is already how you work |
Workflow A: duplicate, change, publish
Duplicate the live theme (Online Store > Themes, then ... > Duplicate). Do this right before you start, so the copy is as current as possible.
Ask Claude to make the changes on the duplicate. Ask for a short summary of what changed: which files, and why.
Turn on the Noibu app embed on the duplicate (Customize > App embeds), then Save.
Test using the preview link. Check the pages the changes touch.
Check what changed on the live theme since you duplicated it. If anyone edited live in the meantime, ask Claude to carry those edits over to the duplicate. Otherwise publishing will overwrite them.
Publish the duplicate. Your previous live theme is kept as an unpublished theme, which is your backup.
Spot-check the live site and confirm the Noibu app embed is still on.
Keep the gap between steps 1 and 6 short. The longer the duplicate is open, the more likely the live theme changes underneath it.
Workflow B: preview theme, then copy to live
Ask Claude to make the changes on your preview theme, and to keep a list of every file it changes.
Test on the preview theme using its preview link.
Duplicate the live theme as a backup. Leave the copy unpublished.
Check that the live files still match what the preview was built from. If a file changed on live, ask Claude to merge the change by hand and show you the result.
Ask Claude to copy the same changes to the live theme, using the file list as a checklist.
Spot-check the live site. The Noibu app embed should already be on for the live theme, but check.
Delete the preview theme once you're happy.
The file list is what makes this safe. Claude should replay the logged changes on live, not rewrite them from scratch.
Workflow C: edit the live theme
Only use this for small, reversible fixes, like a tracking snippet, alt text, copy, or a small CSS change. Use Workflow A for big design changes, theme upgrades, or anything that touches several templates.
Duplicate the live theme as a backup. Keep it until the change has been live for a few days.
Ask Claude to show you the exact change (file and lines) before it writes anything.
Approve it, then let Claude make the change.
Check the live site right away.
Repeat for the next change. One change at a time.
Match the change to the workflow
Change type | Examples | Which workflow |
|---|---|---|
Low risk | Tracking snippet fix, alt text, copy, small CSS | A, B or C, with a backup |
Medium risk | Section or template logic, cart-related code | A or B, tested on a preview first |
High risk | Redesigns, theme upgrades, checkout-related code, many templates at once | A only, with full testing. Consider GitHub |
What not to do
Don't | Why it causes problems | Do this instead |
|---|---|---|
Publish a theme without checking the Noibu app embed | The embed is set per theme. If it's off, Noibu stops collecting data on your live site | Turn it on for the theme (Customize > App embeds) before you publish |
Publish an old duplicate | Edits made on the live theme after the duplicate was created get overwritten | Duplicate right before you start, and check for live changes before publishing |
Let Claude change the live theme without showing you the change first | There's no staging step, so mistakes reach customers right away | Ask Claude to show the file and lines, approve, then apply |
Ship a big redesign as a live edit | Too many changes at once, and no easy way back | Use Workflow A with full testing |
Create a new preview theme for every fix | You'll hit Shopify's theme limit and lose track of which is which | Bundle related fixes into one theme |
Delete old themes without checking | You may lose your only backup | Keep the backup until the change has been live for a few days |
Important Notes
The Noibu app embed is set per theme
The Noibu app embed has to be turned on separately for every theme. If it's off on the published theme, the Noibu script isn't running on your live site.
New duplicates and preview themes may not have it, so turn it on by hand.
To check: Online Store > Themes > Customize > App embeds, make sure Noibu is on, then Save.
Check it again right after you publish.
The live theme can change while your copy is open
Content, section and app-setting edits made on the live theme don't show up on a duplicate or preview theme. If you publish a copy that's out of date, those edits are overwritten. Keep the time between duplicating and publishing short, and ask Claude to compare the two before you publish.
Shopify limits how many themes a store can hold
Bundle related changes into one theme, finish one before starting the next, and delete themes you no longer need. Don't delete your backup until the change has been live for a few days.
Rolling back
How you roll back depends on the workflow. Start with the smallest fix that restores the site.
Option 1: Restore the changed files (preferred for Workflow B and C)
Ask Claude to restore the changed files on the live theme from your backup theme.
Check the live site.
Confirm the Noibu app embed is still on.
Option 2: Publish the backup theme (Workflow A, or if the whole site is broken)
In Online Store > Themes, publish the backup theme (your previous live theme, or the duplicate you made before the change).
Check the Noibu app embed is on for it.
Ask Claude to fix the change on a new duplicate, test it, and ship it again.
If the backup is older than any recent edits to the live theme, those edits won't be in it. Check before you publish.
FAQ
Do I need GitHub to ship changes with Claude?
No. If no developer or agency manages your theme through GitHub, Claude can ship changes straight to Shopify with the Shopify connector. If your live theme is connected to GitHub, use Shipping Shopify Theme Changes with GitHub instead.
What replaces the pull request?
A preview theme. Claude puts the change on a duplicate or preview theme, you test it with the preview link, and you approve it before it goes live.
Can I ship several fixes at once?
Yes, and it's usually better. Bundle related fixes into one theme, test them together, and publish once. This avoids a pile of draft themes. The tradeoff is that the batch is one unit: if one fix is wrong, you roll back or patch the whole theme.
Can Claude edit my live theme directly?
For small, low-risk fixes, yes, after a backup and with your approval of each change. For big changes, use a duplicate theme and publish it once it's tested.
Which workflow should I pick?
Pick the one that matches how your team already ships. If you're not sure, use Workflow A: duplicate, change, publish.
What if our team grows or we hire an agency?
Talk to your Noibu contact about moving to GitHub. It's the safer setup when several people work on the theme or you need to ship changes independently.