There are three broad options, and choosing the wrong one is expensive in opposite directions: over-engineering a store that a theme would have served, or repeatedly patching a theme that was never going to do the job.
Option 1: a theme, configured
A commercial theme with your branding, content and settings. No code changes beyond what the theme editor offers.
Right when: you sell a reasonably conventional catalog, your differentiator is the product rather than the buying experience, and speed to launch matters more than fit. This is the correct answer far more often than agencies admit.
Option 2: theme customization
A theme as the foundation, with code changes for the parts that do not fit — a modified product page, a custom section, a different cart behaviour, integrated third-party functionality.
Right when: a theme gets you 80% there and the remaining 20% genuinely matters commercially. This covers the majority of real Shopify projects.
Watch for: accumulation. Each customization is small; twenty of them produce a theme that cannot be updated safely and that nobody fully understands. There is a point where continued customization costs more than a custom build would have.
Option 3: custom development
A theme built from the ground up, or substantial custom application work — private apps, API integrations, bespoke buying experiences.
Right when: your buying experience is genuinely unusual, you have complex catalog or pricing logic, you need deep integration with other systems, or your store operates at a scale where marginal conversion improvements justify the investment.
Also right when: you are building B2B or wholesale, where the buying experience diverges sharply from anything a retail theme anticipates.
Honest signals you need custom
- You have paid for the same kind of theme patch three times
- Your theme cannot be updated because of accumulated modifications
- You are running five apps to achieve one coherent behaviour, and they conflict
- Your product configuration or pricing logic cannot be expressed in a theme
- Page speed is poor because of app and script accumulation rather than images
- You are selling wholesale and retail from one store with materially different journeys
Signals you do not
- You want a specific visual effect you saw elsewhere
- The theme is "limiting" in ways you cannot articulate commercially
- Someone told you custom is more professional
- You have not yet tested whether the standard experience converts
The performance argument
Custom builds are often justified on speed, and they can be dramatically faster — but only because they omit what a commercial theme carries to serve every possible merchant. A well-chosen theme with disciplined app usage frequently outperforms a custom build that accumulated the same bloat by a different route. Speed comes from restraint, not from custom code as such.