Shopify Theme or Custom Build: How to Decide

The question gets framed as a binary and it is not. There are four distinct commitments, and most stores comparing the extremes should be looking at the middle two.

Framing it properly changes the answer for a lot of merchants, usually toward spending less.

The four options

A stock theme, configured. A premium or free theme, set up entirely through the editor with no code changes at all. Fastest, cheapest, receives updates from its author. Constrained to what the theme supports.

A theme with custom sections. The theme handles standard patterns; bespoke sections and blocks are built for the parts that are genuinely specific. Still updateable, with care. This is where most stores belong.

A heavily customised theme. The theme is the starting point and substantial parts have been rewritten. Updates become difficult, because merging author changes into modified files is where the cost appears.

A custom build. Written from the ground up. Total control, total ownership, and no updates arriving from anywhere but you.

The third column is where decisions go wrong. Build cost is discussed and compared; annual cost is often not mentioned at all, and it is what determines the total over three years.

Themes cover more than merchants expect

The assumption behind most custom-build decisions is that themes cannot express a distinctive design. That has become steadily less true.

Modern themes support extensive layout configuration, custom sections, metafield-driven content, and app blocks. Horizon's block-based system, with nesting up to eight levels, widened this considerably — composition that previously required development is now editor work.

The practical consequence is that "we want it to look bespoke" is no longer a reason to go custom. Themes handle bespoke. What themes struggle with is structurally unusual interaction — configurators, non-standard browsing models, interfaces that do not resemble a commerce page.

Before commissioning a custom build, it is worth having a designer produce what you actually want and asking an experienced Shopify developer whether a theme can build it. The answer is usually yes with some custom sections, and finding that out costs a conversation rather than a budget.

Where custom genuinely wins

Four situations where a theme is the wrong tool.

Interaction a theme cannot structurally express. A product configurator, a booking flow, a browsing model unlike a catalogue.

Extreme performance requirements where you need control over every byte, and where you have the discipline to maintain that control. This is rarer than it is claimed, because most stores lose their performance advantage to app scripts within a year regardless of architecture.

Deep integration with other systems that needs to be present throughout the front end rather than at a few points.

A design system spanning several properties, where the storefront is one surface among many and consistency across them matters more than commerce conventions.

Notice what is absent: wanting a distinctive look, wanting to be faster, and disliking the theme's admin. The first is achievable with a theme, the second is achievable with discipline, and the third is usually a configuration problem.

The maintenance cost nobody quotes

The most under-discussed part of this decision, and the one that determines total cost.

A premium theme receives updates. When Shopify changes something, when a browser changes something, when an accessibility standard tightens, the theme author responds and you take the update.

A custom build receives what you pay for. Every platform change, every deprecated API, every new checkout requirement is your project. This is not occasional — Shopify ships continuously, and a storefront that is not maintained drifts steadily toward broken.

Budget for it explicitly. A custom build with no maintenance allocation is a store that will look neglected in three years and will be expensive to rescue.

That last question is worth asking aloud. A custom theme with no documentation, built by an agency you no longer work with, is one of the more expensive positions a store can be in.

The middle option, in practice

For most stores the answer is a good premium theme plus custom sections, and it is worth being concrete about what that looks like.

The theme provides the product page, collection page, cart and the standard patterns — all maintained by its author. Custom sections cover the parts specific to you: a particular merchandising module, a comparison table your category needs, an unusual homepage arrangement.

Those sections are additive. They live alongside the theme rather than rewriting it, which means theme updates remain applicable. The discipline that keeps this working is resisting the urge to modify the theme's own files when a new section would do.

This gets you most of the distinctiveness of custom, most of the maintainability of a theme, and a build cost between the two.

It also degrades gracefully, which is an underrated property. If the relationship with your developer ends, a theme with custom sections is something any competent Shopify agency can pick up, because the majority of it is a documented commercial theme they already know. A ground-up custom build with no documentation is a considerably harder handover, and the cost of that shows up precisely when you are least able to absorb it.

Choosing a premium theme well

If the answer is a theme, which theme matters more than merchants treat it. The differences between them are mostly invisible in a demo and expensive afterwards.

Check what it weighs before it has anything on it. Themes vary substantially in baseline page weight, and a feature-heavy theme starts you in a hole you then add apps to. Run the theme demo through PageSpeed rather than judging by how it looks.

Look at how it handles your catalogue shape. A theme designed for a twelve-product boutique behaves differently with eight hundred products and heavy filtering. Ask the author, or find a live store using it at your scale.

Check the section inventory against your actual needs. Every section you need that the theme lacks is custom work, and every section it has that you do not need is weight. The fit matters more than the count.

Look at the author's update history. A theme last updated eighteen months ago is a theme whose maintenance you have quietly inherited. This information is public and almost nobody checks it.

Test the admin experience. Your team will spend more time in the theme editor than looking at the storefront. A theme with confusing settings costs you every week, forever.

A way to decide

1. Design what you actually want, without reference to what is technically easy.
2. Ask a Shopify developer whether a theme can build it, and what the custom sections would be.
3. If yes — which it usually is — take the theme plus sections route.
4. If no, be specific about what cannot be done. "It would look different" is not a reason; "the browsing model is not a catalogue" is.
5. Compare three-year costs including maintenance, not build costs.
6. Confirm who maintains it before committing to anything custom.

Step four is where most of the value is. Forcing the reason to be specific either confirms the custom build is necessary or reveals that it is not, and both outcomes are worth the hour it takes.

One caution about who you ask. An agency that only builds custom will tend to find that you need a custom build, and an agency that only sells theme setups will find the opposite. Neither is dishonest; both are answering from what they do. If you can, ask someone who builds across the range, and ask them to argue the case against their own recommendation before you accept it.

For what Horizon changed about theme capability, see storefront and design. The headless question, which is a different decision again, is covered in Shopify development.

One last framing that helps more than any feature comparison: a theme is a constraint you accept in exchange for speed and cost, and a custom build is a constraint you remove in exchange for time and money. Neither is the better answer in the abstract. The question is only whether the constraint you are accepting is currently costing you anything measurable, and for most stores at launch the honest answer is that it is not yet.