Shopify work has a particular rhythm. A merchant wants a new product-page section by Friday, an app needs a webhook handler that reconciles orders, and the theme carries three years of accumulated Liquid that nobody wants to touch. Claude Code, the command-line coding agent from Anthropic, sits inside that codebase and does the reading, drafting and refactoring alongside the developer rather than in a separate chat window.
For Australian agencies and freelance developers, the appeal is speed without losing control. Claude Code runs in your terminal, sees the real files, and proposes changes you approve before anything is written. This piece walks through the two jobs it handles best on Shopify: theme sections and embedded apps.
Where Claude Code fits in a Shopify build
A Shopify project is rarely greenfield. Most of the value is in understanding what already exists: which snippets a section depends on, where a metafield is rendered, how the cart transform was wired. Claude Code reads the whole repository, so a request like "find every place we render the compare-at price and list the templates involved" returns an accurate map in seconds rather than a grep session across a dozen files.
From there the work is incremental. You describe the change in plain English, Claude Code drafts the Liquid, JavaScript or Ruby, and you review the diff. Because it works against your actual branch, it respects your naming, your existing helpers and your theme structure instead of producing generic boilerplate that you then have to rewrite by hand.
Theme sections and Online Store 2.0
Online Store 2.0 made sections the unit of theme work. A good section needs a schema block with sensible settings, presets so merchants can add it from the editor, and Liquid that degrades gracefully when a setting is left empty. This is repetitive, detail-heavy code, which is exactly where an agent earns its keep.
Ask for a section and Claude Code will scaffold the schema, the settings and the markup together, then wire in the block-level settings a merchant expects. A typical request looks like this:
Generate a testimonials section with a configurable heading, star rating, and up to six quote blocks, each with author and role fields.
Add responsive settings for columns on mobile and desktop, defaulting to one and three.
Include a preset so it appears in the theme editor with placeholder content.
Match the spacing and typography tokens already defined in the theme's base CSS.
The developer still owns the outcome. You check that the schema validates in the editor, that settings have sane defaults, and that the section renders on a real product and collection page. What changes is that the first draft arrives complete, so your review is about correctness rather than typing.
Building embedded apps
Shopify apps are a bigger surface: an embedded admin built with Remix and Polaris, OAuth, webhook subscriptions, GraphQL Admin API calls, and billing. Claude Code is comfortable across that stack. It can scaffold a Remix route, add a Polaris data table bound to a GraphQL query, and write the webhook handler that keeps a local database in step with orders.
The parts developers dislike most tend to be where it helps most. API version bumps, for instance, often break queries in small ways. Pointing Claude Code at the migration notes and asking it to update every affected query, then explain each change, turns an afternoon of careful reading into a reviewable set of diffs. The same applies to webhook verification and rate-limit handling, which are easy to get subtly wrong by hand.
What this does to project economics
The commercial case is straightforward. A custom Shopify theme build in Australia commonly runs between $18,000 and $45,000, and a large share of that is the repetitive section and template work that Claude Code accelerates. On our own client projects, first-draft time for a new section falls by roughly half, which lets a small Sydney or Melbourne studio take on more builds without hiring ahead of revenue. For an agency billing $1.2M a year, recovering even a day a week of senior developer time is worth more than most tooling budgets.
The saving is real, but it is not automatic. It shows up only when the review discipline is in place, because a fast wrong answer costs more than a slow correct one.
Guardrails that keep merchant stores safe
Merchant stores hold customer and order data, so the same care you apply to any change applies here. A few habits keep things safe:
Run Claude Code against a development theme or a staging store, never a merchant's live theme.
Keep API credentials in environment variables and out of the repository, so nothing sensitive lands in context.
Treat customer data under the Australian Privacy Act as you would anywhere else: minimise what you pull into logs and prompts.
Review every diff before it is committed, and keep app changes behind version control and a proper release.
Used this way, Claude Code turns Shopify development from a typing exercise into a review-and-direct one, which is where experienced developers add the most value. If you run a Shopify studio or build stores in-house and want to work out where an agent fits your process, book a short session with us.
