If your store runs on a third-party Shopify theme, free or paid, you have probably bumped into a frustrating trade-off. You can customise the theme to fit your brand, or you can keep receiving the theme developer's updates. Try to do both, and sooner or later an update lands and quietly wipes your changes.
So most stores pick one and live with the consequences. That is a shame, because the choice is a false one. With the right approach you can keep your theme, keep its updates, and still make the custom changes your store actually needs. Here is why the problem happens, why the usual fixes fall short, and how we do it differently.
The trade-off nobody warns you about
Whether it is free or paid, a theme from the Shopify Theme Store is actively maintained by its developer. The store lists over 260 themes: roughly two dozen free themes from Shopify, including its flagship, Dawn, plus hundreds of paid themes built by third-party partners. Every one of them ships updates: security patches, performance gains, accessibility fixes and new features, often every month. That ongoing maintenance is part of the deal, and a big part of what makes a Theme Store theme worth running in the first place.
And to be clear, this is not just a "premium theme" problem. Dawn is completely free, and it has exactly the same issue. Any theme you did not build yourself, free or paid, is maintained by someone else and updated on their schedule.
The catch is that a third-party theme is not connected to any version control of your own. It sits in your store, managed by its developer, and the updates arrive on their schedule. The moment someone edits the theme's core files to add a custom feature, the next update becomes a problem. Update the theme, and those edits are gone.
This is different from a custom Shopify build. When we build a theme from scratch, it lives in our own repository and connects to Shopify through the GitHub integration. There is no third party pushing updates, and every change is tracked. The hard problem only exists with third-party themes, free or paid, and it catches a lot of growing stores off guard.
Why updates break customisations
The reason is simple, and it is baked into how theme updates work. An update replaces the theme's files with the developer's new versions. If your custom code was written inside those files, mixed in with the theme's own code, the update does not know which lines are yours. It replaces the whole file.
Your content is usually safe, the text, images and settings you change through the theme editor are stored separately and carry over. It is the code changes that vanish: the custom section a developer hand-edited into a template, the tweaks made directly to the theme's stylesheet, the behaviour bolted onto its core files. All of that lived in the old copy, and the update left it behind.
The problem, then, is not the updates. It is where the customisations were put.
The two bad options most stores settle for
Faced with this, most stores (and a lot of agencies) reach for one of two fixes. Both have a serious downside.
Option one: fork and freeze. Take the theme, copy it into your own setup, and from then on change it as freely as you like. You get total control. You also permanently sever the link to the theme developer, which means no more security patches, no more performance improvements, no more new features. Worse, once you have made a stack of changes, it is extremely difficult to reconnect and catch up later. You have traded your store's future for flexibility today.
Option two: hands off the code. Accept that you will only ever change what the theme editor lets you change. Nothing custom, ever. Your theme stays safely up to date, but you are boxed in by whatever the theme's author decided you are allowed to do. For most ambitious brands, that ceiling gets hit fast.
Neither is a good place to be. One gives up updates to gain flexibility. The other gives up flexibility to keep updates. You should not have to choose.
There is a third way
The better approach flips the problem on its head. Instead of editing the theme and then fighting to protect your changes at every update, you never touch the theme's own files at all.
The theme stays connected to its developer, so updates keep flowing exactly as intended. Everything custom (your bespoke sections, your styling, your added functionality) lives in its own separate, additive files that sit alongside the theme rather than inside it. Because those files belong to you and the theme never owns them, an update simply does not touch them. Your customisations persist while the underlying theme moves forward underneath them.
On top of that, the whole thing is kept under proper version control. There is a full history of every change, so nothing is a mystery six months later, and updates become a short, deliberate, reviewed step rather than a roll of the dice.
Why so few agencies work this way
If it is so much better, why is it rare? Because it is discipline, not a shortcut.
It takes a strict rule that the theme's own files are never edited, by us, by the client or by any tool. It takes a version-controlled source of truth kept carefully in step with the live store. And it takes a defined routine for reviewing and applying each theme update rather than clicking "update" and hoping.
Most agencies default to fork-and-freeze because it is quicker on day one and they do not have to think about updates again. We think that is the wrong trade for a store that intends to be around and growing in three years' time. Keeping a third-party theme customisable and current is more work up front, and it is worth it every single time an update ships. We keep the finer details of our exact workflow in-house, but the principle is the part that matters: additive, isolated, version-controlled, and never fighting the theme.
What this means for your store
Done properly, this gives you the best of both worlds:
- You keep the theme you chose, free or paid, and the updates that come with it
- You add the custom features, layouts and integrations you actually need
- No nasty surprises when an update lands
- A clean, documented codebase that you are never locked out of
It is a genuinely unusual way to run a third-party Shopify theme, and it is exactly the kind of long-term thinking that keeps a store fast, secure and flexible for years rather than months.
If you are on a third-party Shopify theme and feel stuck between customising it and keeping it current, that is precisely the problem we solve, whether you are on a standard plan or scaling on Shopify Plus.
Talk to our Shopify team
