How to use Claude Code on a Shopify store

Claude Code works on a Shopify store through your theme's code. You download the theme with Shopify CLI, Claude Code edits the Liquid, CSS and JavaScript files on your computer, you preview the changes on a hidden development theme, and a person pushes the reviewed result to an unpublished theme before anyone publishes it. Claude Code does not edit your live store from the inside, and it shouldn't.

Shopify also publishes official tools that make this smoother: a GitHub app that syncs theme code with a repository, a Shopify AI Toolkit plugin for Claude Code, and a Dev MCP server that gives coding agents Shopify's docs and API schemas. This guide covers what works, the commands involved, and the mistakes to avoid, as of October 2026.

What Claude Code can and can't touch on Shopify

Shopify is a hosted platform. You don't get the server's files or database, only your theme's code and Shopify's APIs. That shapes what Claude Code is useful for.

Liquid, as Shopify's docs put it, "is a template language created by Shopify." Claude Code reads and writes it like any other code, but Liquid errors show up only when a page renders, which is why previews and theme check matter.

The Shopify CLI theme workflow

Shopify CLI is "a command-line interface tool that helps you build Shopify apps and themes." Because Claude Code runs terminal commands, CLI is how it gets your theme onto your computer and back.

1. Duplicate your live theme in the Shopify admin so you have a backup before anything else.
2. Pull the theme. shopify theme pull "Retrieves theme files from Shopify." Flags like --theme pick which theme and --only limits the pull to certain files.
3. Commit the pulled files to git on a new branch, so every change Claude makes is a reviewable diff.
4. Write a short CLAUDE.md noting the theme name, which sections matter, brand rules, and "never push to the live theme." Our guide on writing a CLAUDE.md for a website covers the format.
5. Plan, then edit. Ask Claude to propose the change in plan mode, then make it.
6. Preview. shopify theme dev uploads your local theme as a development theme, which Shopify describes as a temporary, hidden theme connected to your store, so you can preview changes without touching what customers see.
7. Check. Run shopify theme check, then look at the affected pages on mobile and desktop.
8. Push to an unpublished theme. shopify theme push --unpublished creates a new unpublished theme and uploads to it. The command returns a preview link you can share.
9. A person publishes. Someone reviews the preview and publishes the theme in the admin.

Shopify's own theme push reference says it "Uploads your local theme files to Shopify, overwriting the remote version." If you don't name a theme, you're asked to pick one. That prompt is where a rushed approval can overwrite the live theme. Two flags deserve extra caution: --publish ("Publish as the live theme after uploading") and --allow-live (needed to push to the live theme in non-interactive runs). Neither belongs in anything Claude runs on its own.

For theme customization basics, see our guide to customizing a Shopify theme without breaking it.

Using Shopify's GitHub integration

The Shopify GitHub app "lets you connect your GitHub and Shopify accounts" to "sync theme code to and from GitHub repositories." It works both ways: it "updates your theme in the Shopify admin whenever the connected branch is updated" and "commits changes made through the Shopify admin to the branch." You can connect only branches that match Shopify's default theme folder structure.

That two-way sync has two implications for Claude Code work:

• Pull before you start. A merchandiser may have changed theme settings in the editor since your last session, and the app has committed those changes to the branch. Start every session from the latest branch, or you'll overwrite their work.
• A merge can be a deploy. If the connected branch belongs to your live theme, merging into it changes the storefront. Connect the live theme to a protected branch that needs an approved pull request, and have Claude work on feature branches.

Claude Code's auto mode allows pushes to branches of the repository you're working in by default, so add an ask rule for git push. Our guide to using Claude Code safely on a live website covers the settings. You can also run review checks on each pull request; see Claude Code in GitHub Actions for website QA.

Shopify's official AI tooling for Claude Code

As of October 2026, Shopify documents three tools relevant to coding agents. Only the first two are for building.

The AI Toolkit deserves care: Shopify says it can "prepare and run supported store-management tasks through Shopify CLI's authenticated store context." Shopify adds that you choose when to execute them, but in plain terms it can act on a real store you're logged in to. Try it on a development store first, keep Claude in a mode that asks before running commands, and read what each task will do before approving it. The Dev MCP server, documented on the same AI Toolkit page as its MCP install option, is lower-risk: it runs locally, needs no sign-in, and connects Claude to Shopify's developer resources. For how to judge any MCP connection, see MCP servers for website teams.

Good jobs for Claude Code on a Shopify theme

• Section and snippet changes: a new homepage section, a reworked product card, a size-guide block.
• Theme cleanup: finding unused snippets, leftover code from removed apps, or duplicated CSS. A person confirms before anything is deleted.
• Structured data in theme templates: adding or correcting product markup, checked against what the page shows.
• Performance fixes: deferring scripts, resizing image calls, removing unneeded assets, then measuring the result.
• Accessibility fixes: missing labels, heading order, focus states, verified with a tester.
• Explaining an inherited theme: asking Claude to map how a theme you didn't build is put together before you change it.

What not to do

• Don't let Claude push to or publish the live theme. Push to an unpublished theme; a person publishes.
• Don't paste store credentials or access tokens into prompts. Let Shopify CLI handle login, and keep any API tokens in files Claude is denied access to.
• Don't skip the pull. Editing a stale copy and pushing it can wipe out theme editor changes made since. We learned the general version of this on our own site, where one session regenerated pages another session had just edited; see common Claude Code mistakes on websites.
• Don't edit third-party app code. Change how your theme uses an app, or ask the app developer.
• Don't run store-management tasks on your live store first. Use a development store, and approve each action.

When to rethink the platform

For most stores, staying on Shopify and improving the theme with Claude Code is the right call. Shopify handles hosting, checkout and security, which is a lot to give up. Some businesses consider moving a content-heavy site off Shopify while keeping commerce elsewhere; if that is your question, our guide on moving from Shopify to an AI-built website covers the tradeoffs. Don't migrate just because a coding agent makes it seem easy.

Conclusion

Claude Code is a good fit for Shopify theme work when it follows the loop Shopify's tools are built for: pull, branch, edit, preview on a development theme, run theme check, push to an unpublished theme, and let a person publish. Add Shopify's AI Toolkit or Dev MCP so Claude works from current Shopify docs, and keep anything that touches a live store behind a prompt and a review. If you want a team to handle theme builds or ongoing changes this way, see our Claude Code development services. More guides are in our Claude Code Guide.

Frequently asked questions