eCommerce

Shopify themes built like software: Git, tests and fewer monthly fees

Jamie · 29 July 2026 · 8 min read

Most Shopify stores I'm asked to look at are paying rent on their own shopfront. A premium theme with an annual licence, then five or six apps at twenty or thirty dollars a month each, several of which exist only to do something the theme should have done in the first place. None of it is unreasonable on its own. Together it quietly becomes one of the larger line items in a small retailer's year.

There's another way to build a Shopify store, and it isn't exotic: treat the theme as software you own, keep it in version control, test it before it goes live, and only reach for an app when an app is genuinely the right answer.

Why a custom theme usually costs less to run

The saving isn't in the build. A custom theme costs more up front than buying one — that's the honest trade. The saving is in what you stop paying every month afterwards.

A large share of the apps on a typical store are patching gaps: a size chart, a bundle display, a trust badge row, a custom product tab, a slightly different collection filter. Each one adds a subscription, a bit of JavaScript, another third party with access to your storefront, and another thing that can break when Shopify changes something. Built into the theme instead, those become part of the thing you already own, with no recurring licence and nothing extra to load.

The apps worth keeping are the ones doing real work — reviews, subscriptions, a proper ERP or accounting link, anything touching payments. Those earn their fee. The rest are usually there because the theme couldn't be changed.

This is the same logic behind pricing a care plan: the cheap option is rarely the one with the smallest monthly number attached.

Built in GitHub, not in the admin

Shopify will connect a theme directly to a GitHub repository, and once that's in place the whole way you work changes.

Every change has a history. Who changed the product template, when, and why. Not a folder of theme-copy-FINAL-v3 duplicates in the theme library.
Work happens on a branch. A new section or a campaign layout is built on its own branch, published to a preview theme, and looked at properly before it goes near the live store.
Rollback is a real thing. If something ships badly, you revert a commit. You are not reconstructing last week's template from memory at nine on a Friday night.
Two people can work at once without overwriting each other, which the theme editor alone does not handle well.

Checks that run before it ships

Because the theme is in a repository, GitHub can run checks on every change automatically:

Theme Check — Shopify's own linter for Liquid. It catches deprecated filters, undefined objects, missing translation keys and the performance patterns Shopify warns about, before a customer ever sees them.
Lighthouse on the key templates, so a change that quietly adds two seconds to the product page gets flagged while it's still cheap to fix. Speed is a conversion issue as much as a technical one — see why your site is slow.
Build and link checks, so a broken asset path or a dead internal link doesn't get merged.

None of this is exotic tooling. It's the ordinary discipline of software development applied to a shopfront, and it's the difference between "we think that's fine" and "the checks passed".

Where AI actually helps — and where it doesn't

I use AI tools daily in this work, and I'd rather be specific about how than vague and impressive.

Design exploration. Tools like Lovable and Claude are genuinely good for getting from a brief to several honest options quickly — laying out a product page three different ways, or seeing what a collection grid looks like at different densities, before anyone commits to building it. That used to be a week of static mockups. It's now a conversation, and the client sees real options instead of one.

Writing the boring parts. Liquid loops, schema blocks for theme sections, the tedious ARIA and structured-data plumbing. Fast to draft, and every line still gets read before it's committed.

Content at volume. A catalogue of four hundred products with descriptions copied from a supplier PDF is a genuine problem, and one a person will never be given the budget to fix by hand. More on that below.

Where it doesn't help: judgement. What the brand sounds like, which product deserves the top of the page, whether a claim is actually true. AI drafts, a person decides — particularly on anything a customer will read as a promise.

Moving a store off WooCommerce

Replatforming is where most of the anxiety sits, and most of it is misplaced — provided the data is treated as the serious part of the job. If you're still deciding between the two platforms, that's a separate question worth answering first.

The product data

Matrixify does the heavy lifting: bulk import and export of products, variants, images, collections, customers and orders through spreadsheets, which means the data can be examined and corrected before it lands in the store rather than after. For anything Matrixify doesn't cover, or where a mapping needs to be conditional, the Admin API fills the gap.

The parts that actually take the time:

Variant structure. WooCommerce attributes and Shopify options are not the same shape. Stores with more than three variant dimensions need a real decision, not an automated guess.
URLs. Product and category URLs change between platforms. Every old URL needs a redirect to the right new one, or you hand back rankings you spent years earning.
Customers and history. Accounts and past orders can come across; passwords cannot, and customers need to be told that plainly rather than discovering it at checkout.

Content refresh on the way through

A migration is the one moment when touching every product description is already on the schedule. That makes it the sensible time to fix them: expand the thin ones, strip the supplier boilerplate that's duplicated across a dozen other retailers, give them a consistent voice, and make sure each one answers the questions customers actually ask.

AI makes that possible at catalogue scale. The workflow that works is draft-then-review: generate from the real product attributes, then have someone who knows the products read them before they go live. Anything involving a measurement, an ingredient, a compliance claim or a compatibility promise gets checked against the source, not trusted.

Metafields: the part most stores never switch on

Shopify metafields let you add structured fields to products — materials, dimensions, burn time, care instructions, origin, compatibility, whatever your category actually needs — and then display them properly in the theme.

This is one of the highest-value things you can do to a product page, for three reasons:

It answers the question that stops the sale. Most abandoned product pages are someone failing to find one specific fact. A structured spec block puts it where they're looking.
It's consistent. Every product in a collection presents the same fields in the same order, instead of whatever happened to be typed into the description that day.
It feeds structured data. Metafields map cleanly into product schema, which is what search engines and shopping surfaces read.

Because the fields are defined once and rendered by the theme, staff add products by filling in boxes. No HTML in a description field, and nothing to reformat later.

Built for organic search from the start

Retrofitting SEO onto a theme is expensive. Building it in is mostly free, because it's decisions rather than work: one h1 per page that says what the page is, headings in an order that reflects the content, product and breadcrumb structured data generated from real fields, image dimensions set so the layout doesn't jump, and templates that render fast on a phone on regional mobile data.

The other half is not painting yourself into a corner: clean URL structure, collection pages that can carry real copy, and a blog that isn't an afterthought. Plenty of stores can't publish a decent category page because the theme has nowhere to put one.

The owner keeps the theme editor

This is the part people are most nervous about, and it's worth being clear: a custom theme is not a locked box. It's built with Shopify's section and block system, which means the owner still gets the standard theme editor — reorder sections, swap imagery, change colours and fonts, run a campaign banner, build a new landing page out of existing blocks. All the day-to-day work stays self-service, exactly as it would on a bought theme.

What's different is that the underlying template is yours, so the things a bought theme won't let you change are now things that can simply be changed.

Which makes updates cheaper

Because the theme is small, documented and in version control, a change is a change — not an archaeology exercise across a 40,000-line premium theme built for every store on the platform at once. Less code means less to read, less to break and less to bill for. It's the same reason a well-kept site is cheaper to look after than a neglected one, and it compounds over the years you own the store.

Carrying the brand across

The last thing, and for a lot of businesses the reason they call in the first place: a bought theme flattens a brand. It looks like a Shopify store first and your business second, because it was designed to look acceptable for everyone.

If there's an existing site, existing print, a livery on a van, a packaging system — the store should be visibly the same business. Type, spacing, photography treatment and tone carried across, not approximated. That continuity is what makes a store feel like somewhere you've heard of, and it's most of the trust a new customer has to work with. You can see how that plays out on the work we've done, including The Essential Candle Co., which we moved onto Shopify with its brand intact rather than rebuilt around a template.

If you're weighing it up

A custom theme is not automatically the right answer. If you're launching, testing an idea, or running a straightforward catalogue on a tight budget, a good bought theme is a sensible start and you should take it. The case for building changes when you're paying for apps to work around your theme, when the store doesn't look like the rest of your business, or when every small change costs more than it should.

If that sounds like your store, it's worth a conversation before you renew anything.

We build custom Shopify themes, and move stores across from WooCommerce.

Shopify development → Talk it through