Most Shopify stores should launch on a free or premium theme, not a custom one. Go custom when your catalog, merchandising or brand keeps forcing apps and code hacks onto a theme that wasn’t built for them, and only when someone will own that code after launch. The right choice depends less on budget than on who maintains the theme.
The three options and what each really costs
The price of the theme is the smallest part of the cost. What adds up is everything around it: apps that fill feature gaps, developer hours for tweaks, and the work of keeping code current as Shopify evolves.
| Free theme | Premium theme | Custom theme | |
|---|---|---|---|
| Upfront cost | $0 | One-time fee, typically a few hundred dollars per store | Typically a few thousand dollars for a customized base, five figures or more for bespoke design and build |
| Time to launch | Days | Days to a few weeks | Several weeks to a few months |
| Built-in features | Core sections, deliberately lean | Broad section library and merchandising features | Exactly what you specify, nothing more |
| Updates | Shopify | The theme developer | Your developer, or nobody |
| Support | Shopify | The theme developer | Whoever built it |
| Hidden cost | Apps bolted on to fill gaps | Code edits that make updates painful | Maintenance and dependence on one developer |
| Best fit | New stores, small catalogs | Most growing stores | Complex catalogs, strong brand needs, a developer on hand |
A store on a free theme with a stack of apps for size charts, badges, sticky carts and product tabs can spend more per year than a premium theme that ships those features, and it usually runs slower, because many of those apps load their own scripts on every page. Count the gap-filling apps before you decide free is cheaper.
When a free theme is enough
Shopify’s free themes, such as Dawn, are built on Online Store 2.0, maintained by Shopify, fast by default and solid on accessibility. A free theme is the right call when:
- Your catalog is small and simple. A focused range with straightforward variants doesn’t need advanced filtering or complex product layouts.
- You’re still validating demand. Money spent on product photography, copy and ads teaches you more at this stage than a theme upgrade.
- Your brand can live in photography, type and color. Most brand expression comes from assets, not unusual layouts.
- Nobody on the team writes Liquid. Free themes have the fewest moving parts to break.
The limit is feature depth. Free themes are lean on purpose, and once you start stacking apps to recreate what premium themes include, it’s time to compare.
Choosing a premium theme: speed, sections and support
Premium themes in the Shopify Theme Store are a one-time purchase per store, include updates from the developer, and have to pass Shopify’s review for performance and accessibility before listing. You can try a paid theme in your own store’s editor before buying, and you should.
Test speed on your own content
Demo stores are tuned: optimized images, few products, no apps. Install the trial, load your real products and your heaviest collection, then test the home, collection and product pages on mobile. Compare two or three shortlisted themes on the same content. If speed is already a problem on your current store, how to speed up a Shopify store ranks the fixes by impact.
Map the sections you need before you browse
Demo aesthetics are mostly photography. Judge themes on structure instead. List every template you use (home, collection, product, landing pages, about) and the blocks each one needs: size guide, ingredients or specs accordion, comparison table, bundle display, video, reviews placement, trust badges. Then check each theme against the list. The theme that covers the most of it without apps or code wins, even if its demo looks less exciting.
Check the support and update record
Read the developer’s changelog and support reviews. You want a theme updated regularly, with documentation you can follow and a support team that answers setup questions. A theme that stops getting updates falls behind new Shopify features, and you inherit the gap.
Customize through settings, not code
When you update a Theme Store theme, settings and content from the theme editor carry over, but direct code edits don’t. Every edit becomes something to reapply on each update. Keep code changes small, document them and track them in version control; Shopify’s GitHub integration makes that straightforward.
Signs you have outgrown your theme
Outgrowing a theme is not the same as being bored with it. Look for constraints that cost you sales or speed:
- Every campaign needs a developer. The section library can’t produce the landing pages and layouts marketing asks for.
- Your app list is doing the theme’s job. Several apps exist only to add display features, and they conflict with each other.
- You’ve stopped updating. Code edits have piled up to the point that updates feel risky, so you’re several versions behind.
- Your product data has outgrown the templates. Specs, compatibility, ingredients or configuration options live in metafields, but the theme can’t display them well.
- The catalog needs different page types. Bundles, kits, subscriptions and single products all get forced into one product template.
- Speed fixes need a rewrite. You’ve compressed images and removed apps, and the remaining weight is the theme’s own code.
- Brand storytelling is flattened. The product needs layouts that no theme’s settings can produce.
If three or more apply, you’re paying for the theme in workarounds.
What custom theme development involves
“Custom” covers three different builds:
- Customized premium theme. A premium base with custom sections added. Cheapest route, but once the code diverges you effectively own a fork and lose easy updates.
- Custom theme on a clean base. Your design and section library, built on Dawn or a similar starter. This is the right choice for most stores that go custom.
- Fully bespoke build. Everything written from scratch. Rarely needed, and the most expensive to maintain.
A sound custom build follows roughly these steps:
- Discovery. Audit the current store, analytics, catalog structure and the apps the new theme should replace.
- Design a component system. Sections and blocks that combine into many pages, not one-off mockups per page.
- Build. Liquid, lean JavaScript, Shopify CLI, version control and theme linting from day one.
- Wire up the data. Metafields and metaobjects feed product-specific content into sections.
- QA. Real devices, speed and accessibility targets agreed before design, and every app that stays.
- Launch and monitor. Changing themes keeps Shopify’s URLs but can alter headings, structured data and internal links. Check those, then watch conversion and speed for a few weeks.
- Maintain. Shopify ships platform changes continuously, and nobody updates a custom theme unless you pay someone to.
That last step is where custom builds go wrong. Before approving one, name the developer or team who will own the code for the next few years. My Shopify development builds include that handover plan. If you’re weighing something more drastic, headless Shopify vs a custom theme covers when going headless is actually worth it.
Online Store 2.0 and the section-based approach
Online Store 2.0 changed what a custom theme should be. Older themes hardcoded most page types in Liquid templates, so changing a product page meant editing code. With 2.0:
- JSON templates put sections on every page type, so merchants can add, remove and reorder sections on product, collection and content pages in the editor.
- App blocks from theme app extensions let apps add features without editing theme code, and they’re removed cleanly when the app is uninstalled.
- Dynamic sources connect section settings to metafields, so content like specs or size guides fills in from product data instead of being typed per page.
- Alternate templates let different product types use different layouts within one store.
For a custom build, that means the deliverable is a library of well-built sections with sensible settings, not a fixed set of pages. The test is simple: can your marketing team build a new landing page from existing sections without a developer? If not, the custom theme will slow you down.
Common mistakes in custom builds:
- Hardcoding copy and images into Liquid
- Giving each section so many settings that the editor becomes confusing
- Rebuilding features Shopify or a well-built app already provides
- Shipping heavy JavaScript frameworks for simple interactions
A decision checklist
Answer these in order. The first strong “yes” usually points to the right option.
| Question | If yes, lean toward |
|---|---|
| Small catalog, simple variants, still validating demand? | Free theme |
| Need richer merchandising, but no layouts unique to your brand? | Premium theme |
| Would a premium theme cover most requirements with a few custom sections? | Premium, lightly customized |
| Complex product data, multiple product types or configurators? | Custom on a clean base |
| Is brand differentiation central, with layouts no theme offers? | Custom on a clean base |
| Already editing theme code monthly and skipping updates? | Custom: you already own the code |
Before you commit to any option:
- Listed every template and the sections each one needs
- Tested shortlisted themes with your own products, on mobile
- Counted the apps that exist only to fill theme gaps
- Named who will maintain the code, and budgeted for it
- Confirmed the build uses JSON templates, app blocks and metafield-driven sections
- Set speed and accessibility targets before design starts
Get it built
If your theme is holding back merchandising, or you’re deciding between a premium theme and a custom build, I’ll scope it and build it. Shopify builds and migrations start from $6,000, and if you’re not sure what the store needs yet, the Growth Audit is $1,500 fixed and credited if we continue. See pricing or get in touch.