Custom Shopify theme vs a bought theme: how to choose
The answer is not \"custom is always better\". It depends entirely on how much of it you are going to change.
7 min read · Themes & storefront ·
A bought theme for a few hundred, or a custom theme for ten times that? The answer isn't "custom is always better." It depends on how much of it you're going to change.
The bought theme
What you get
A finished look, tested across thousands of stores, with documentation and support from its author. Deployment is a matter of days. For a store with a standard catalogue that mainly needs to look good and work properly, it's the right choice and there's no point over-engineering it.
Where it stops working
The problem isn't the theme — it's what people do to it. The typical progression: buy a theme, edit the header, add a section the theme doesn't have, install three apps for things the theme can't do — and a year later you have a theme that's a third rewritten, can't be updated, and nobody knows why it's slow.
This is the most expensive scenario of all. You paid for the theme, for three monthly app subscriptions and for the modifications, and the result is worse than if the theme had been built properly from the start.
Speed
Commercial themes are built to sell as many licences as possible, so they contain features you'll never use — and those load anyway. They can be trimmed, but it's work, and it comes back after every update. App accumulation usually finishes the job.
The custom theme
What you get
Exactly what's in the design and nothing else. No code for features you don't use. Sections built the way you actually use them, with settings that make sense to the person managing the store.
And above all: speed can be written into the brief. With a bought theme you inherit whatever the performance audit turns up. With a bought theme you inherit performance; with a custom theme you design it.
Online Store 2.0 is non-negotiable
A custom theme doesn't mean the client can't change anything. The opposite — with a well-built theme the client gets sections and blocks in the editor that they recombine without a developer. If someone builds you a "custom theme" where you can't reorder the sections on the homepage, they didn't build you a theme. They built you a static page. How that's done properly is worth reading before you commission one.
The downsides, stated plainly
- It takes longer — weeks, not days.
- It costs several times more.
- You depend on whoever built it until someone else takes it over. That's why you insist on clean, commented code, and on the code being yours.
The third path I recommend most often
A solid base theme with a proper layer on top. Take a well-written theme as the foundation and build custom sections and modifications on it — cleanly, with a plan, knowing what's happening. You get 80% of the benefit of a custom theme for a fraction of the cost.
The condition is that it's done systematically, not with patches. Custom sections in their own files, custom CSS separated from the theme, no edits to the core where they aren't necessary. Do that and the theme is still updatable a year later.
How to decide
| Situation | Recommendation |
|---|---|
| First store, standard catalogue | Bought theme |
| Brand with its own visual identity | Custom, or a strong layer on a base theme |
| Complex catalogue, filtering, configuration | Custom |
| Already paying for 5+ apps just for appearance | Custom pays for itself |
| Speed is a commercial priority | Custom |
| Budget in the low thousands | Bought, with targeted modifications |
A bought theme is cheap as long as you leave it alone. The moment you start rebuilding it, it stops being cheap — you just don't know that yet.
Is this the problem you’re looking at?
Send me the link to your store and a line about what is going wrong. You get a straight answer within one business day — no pitch, no obligation.
mario@clicksandcarts.coOr see what I do around Shopify: services, work beyond the theme, selected work.