“Should we buy a theme or build a custom one?” is one of the first questions most brands ask us. The honest answer is that it’s rarely a choice between two options. There are three, and most stores belong in the middle one.
The three real options
- A theme, used as designed. A theme from the Shopify Theme Store, set up through the theme editor with your branding, content and apps. No code changes.
- A theme, customised. The same starting point, plus custom sections, blocks and features built for your store, so it looks and works like your brand rather than a template.
- A fully custom theme. A theme built from scratch around your design and your product logic. You own every line of code, and you also own its maintenance.
What modern themes can already do
Shopify themes are far more flexible than they used to be, and it’s worth knowing what’s possible before paying for custom work.
- Online Store 2.0 brought sections to every page, JSON templates (so you can build different layouts for different products or collections) and app blocks, which let apps sit inside your design rather than being bolted on with code.
- Theme blocks, and Shopify’s Horizon themes launched in the Summer ‘25 Edition, take this further. Blocks can be nested and rearranged, so a lot of layout work that once needed a developer can now be done in the editor.
So if a theme can do 90% of what you want through settings alone, a fully custom build is hard to justify.
When a theme as-is is the right call
- You’re launching or validating a new brand, and speed to market matters more than uniqueness.
- Your catalogue is small and your products are simple (a few variants, no configurators or bundles).
- You don’t yet know which features your customers actually use. Live on a theme for a few months and let the data tell you.
Choose a theme from a developer with a good update record, and test it with your products and your photography before you buy. Demo stores are designed to make every theme look good.
When to customise a theme
This is where most growing brands should be. You keep the solid foundation and the updates of a maintained theme, and add only what makes your store different:
- Custom sections for your brand story, ingredients, size guides or lookbooks.
- Product page features: bundles, personalisation fields, delivery estimates, comparison tables.
- Collection and filtering behaviour that matches how your customers shop.
- Speed fixes and removal of features you don’t use.
The catch is updates. Shopify carries your theme editor settings over when you update a theme, but code edits generally have to be reapplied. You can keep that manageable:
- Put custom work in new files (your own sections, blocks and snippets) instead of editing the theme’s core files.
- Keep a short changelog of every core-file edit, so it can be redone after an update.
- Use version control. Shopify’s GitHub integration and Shopify CLI let your developer work on a copy and track every change, instead of editing the live theme directly.
When a custom theme is worth it
A fully custom theme starts to make sense when a theme is working against you rather than for you:
- Your design is the product. Fashion and lifestyle brands whose visual identity is their main differentiator often end up overriding most of a theme’s styling anyway.
- Complex product logic. Configurators, build-your-own bundles, different catalogues for B2B and retail customers, or products with lots of custom data in metafields.
- Performance is critical. A custom theme ships only the code your store uses. A general-purpose theme ships code for every feature every merchant might want.
- Content-heavy stores. Editorial, recipes, guides and campaigns that need layouts a theme wasn’t designed for.
What you give up: no theme developer is shipping updates for you, so new Shopify features and fixes are your responsibility (or your developer’s). Plan for ongoing support, not just the launch.
A quick way to decide
| If this describes you | Start with |
|---|---|
| New brand, small catalogue, budget is tight | Theme as-is |
| Established brand, theme looks close but “not quite us” | Customised theme |
| You need a handful of specific features | Customised theme |
| You’d override most of the theme’s design | Custom theme |
| Complex products, multiple catalogues or heavy content | Custom theme |
| You change campaigns and layouts every week | Customised theme with flexible sections |
Red flags to avoid
- Buying a premium theme and then rewriting most of it. You pay for the theme and for the rebuild, and you lose the update path.
- Stacking page-builder apps on top of a theme to get layouts the theme can’t do. Each one adds scripts and another place where content lives.
- Editing the live theme directly with no copy, no version history and no record of what changed.
Questions to ask your developer
- Will custom work live in separate files, or will you edit the theme’s core files?
- How will we update the theme in a year’s time?
- Is the code in version control, and do we get access to it?
- Can our team edit everything through the theme editor afterwards, without code?
We do all three kinds of project: theme setup, theme customisation and fully custom themes. If you’re not sure which one you need, send us your store or your brief and we’ll tell you honestly. If your store is slow as well, our speed checklist is a good place to start.