Custom Shopify Theme vs Premium Theme vs Headless: How to Decide

There are three ways to build a Shopify storefront, and the pricing gap between them is roughly thirty to one. A customised premium theme runs $2,500-$5,000. A custom theme runs $8,000-$50,000. A headless build runs $30,000-$250,000 or more.

Most stores should choose the cheapest option. Most stores are sold one of the other two, because both are more profitable to build and because "custom" sounds better in a pitch than "we'll configure an existing theme well."

This guide compares the three honestly on cost, maintenance, speed, flexibility, and risk, and gives you a decision framework that starts from what you actually need rather than from what sounds impressive.

The three options at a glance

Option 1: Premium theme with customization

Start from a modern Online Store 2.0 theme (Dawn, Sense, Refresh, or a premium option like Impulse or Prestige) and customise it: brand styling, custom sections where needed, PDP and collection page structure tuned to your merchandising.

What you get

• Theme updates. The developer maintains it against Shopify's changes. When conventions shift or an API version deprecates, they ship an update.
• Editability. Sections and blocks mean you can restructure pages yourself without a developer.
• Tested code. A theme with thousands of installs has had its edge cases found by other people.
• Speed baseline. Modern themes ship with lazy loading, responsive images, and sensible script handling already in place.
• Portability. Any Shopify developer can work on it. You are not locked to whoever built it.

Where it genuinely limits you

• Unusual merchandising models: complex configurators, non-standard product relationships, subscription flows that need bespoke UX
• Design ambitions that fight the theme's structure rather than working within it
• Feature bloat: premium themes ship options you never use, and that code still loads

Option 2: Custom theme

A theme built from scratch in Liquid for your store specifically. Nothing you do not use, structured exactly around your merchandising.

When it is genuinely justified

• Your merchandising model does not fit any existing theme. Product configurators, made-to-order flows, complex variant relationships, unusual bundling logic.
• Brand differentiation is a material competitive advantage. If your entire category uses the same three themes and design is how you win, custom is defensible.
• You have maintenance capacity. In-house developer or a retained agency, because nobody else is going to update it.
• Performance is a genuine constraint and you have already exhausted app cleanup and theme optimisation on your current setup.

What it actually costs beyond the build

• No theme updates. This is the real cost and it is chronic rather than one-off. Shopify changes conventions, deprecates API versions, and ships new capabilities. Every one of those is now your development ticket.
• 10-20% of build cost annually in maintenance as a working budget.
• Developer dependency for structural changes. If sections are built as reusable blocks you can edit, this is manageable. If they are hardcoded, every layout change is a ticket.
• Handover risk. An undocumented custom theme is a liability. Insist on documentation as a deliverable.

The question that decides it

Can you name a specific thing you need that no existing theme can do? Not "we want it to look unique" but a functional requirement. If you can name it, custom may be right. If you cannot, you are paying 5x for aesthetic control you could get for less within a premium theme.

Option 3: Headless

A separate frontend application (Hydrogen, Next.js, Nuxt, Remix) talking to Shopify through the Storefront API. Shopify handles commerce and checkout; you own everything the shopper sees before checkout.

What it genuinely gives you

• Unlimited design and interaction freedom. No Liquid constraints.
• Performance ceiling. A well-built headless storefront can achieve sub-second navigation that Liquid cannot match.
• Multi-channel content reuse. One CMS feeding a storefront, an app, in-store screens, and marketing surfaces.
• Advanced personalisation that would be awkward or impossible in a theme.

What it actually costs

Hosting is the least of it: Oxygen is included on every paid Shopify plan except Starter. The budget goes elsewhere.

Representative year-one headless budget:

Build (agency, standard scope)          $60,000
Headless CMS licence (annual)           $12,000
Ongoing engineering (0.5 FTE)           $40,000
Migration and content work               $8,000
Monitoring, error tracking, misc         $2,000
                                        --------
Year one total                         ~$122,000

Published examples land in a similar range: a representative Hydrogen budget of around $115,000 in year one is a realistic figure for a standard agency build with CMS and engineering included.

The costs most headless quotes omit

• Headless CMS licence. Contentful, Sanity, or Storyblok. $300-$3,000+ monthly depending on tier and seats. Almost never in the build quote.
• Ongoing engineering. You maintain two systems now. Shopify API version deprecations, framework upgrades, dependency security patches. This is not optional and it does not stop.
• Specialised hiring. Liquid developers are plentiful and reasonably priced. React or Hydrogen developers who understand commerce are neither, and they cost accordingly.
• Marketing team velocity. This is the underrated cost. On a theme, your marketer can build a landing page in an afternoon. On headless, they file a ticket. Whether that trade is worth it depends entirely on how often you ship pages.
• Apps. Many Shopify apps rely on theme app extensions and simply do not work headless, or need custom integration. Audit your app stack before committing.

When headless is genuinely right

• Revenue meaningfully above $2M, with the engineering capacity to maintain two systems
• A specific, named requirement Liquid cannot meet, not a general desire for speed or freedom
• Multi-channel content reuse as a real operational need, not a hypothetical
• Performance as a measured business constraint where you have already exhausted app cleanup and theme optimisation
• An existing engineering team who will own it, or budget for one

For most stores under $2M revenue, headless is significantly over-engineered. That is not a dig at headless; it is the same reason you would not run Kubernetes for a five-page brochure site.

The decision framework

Work through these in order. Stop at the first honest yes.

Question 1: Can you name a functional requirement no existing theme meets?

Not aesthetics. Function. A configurator, an unusual purchase flow, a merchandising relationship no theme models.

No → premium theme with customization. You are done. Spend the difference on conversion work, content, or acquisition.

Yes → continue.

Question 2: Can that requirement be met with a custom section, an app, or a Shopify Function?

This is the money-saving question and it gets skipped constantly. Many "we need a custom theme" requirements are actually a custom section (hours of work) or an existing app ($29 a month).

Yes → premium theme plus that specific piece of custom work.

No → continue.

Question 3: Do you have maintenance capacity for a codebase nobody else updates?

No → reconsider. A custom theme without maintenance capacity degrades over 18-24 months as Shopify moves and nothing keeps pace.

Yes → custom theme is defensible. Continue only if you are also considering headless.

Question 4: Does the headless payback case hold in gross profit, with evidence?

No → custom theme. You get most of the flexibility at a fraction of the total cost of ownership.

Yes → headless, with eyes open about the ongoing engineering commitment.

The sequence most brands should follow

Rather than choosing once, choose in stages:

The point of this sequence is that each stage produces the evidence you need for the next decision. Starting at custom or headless means designing for assumptions, and you will rebuild anyway once you learn what actually works.

On speed specifically

Speed is the most common argument for going custom or headless, and it is usually the weakest one, because most Shopify speed problems are not caused by the theme.

The actual causes, in order:

1. App scripts. Each app adds roughly 150-300ms to LCP. A store with fifteen apps has a speed problem that no theme choice fixes.
2. Theme drift. Every "small" customization adds a CSS file or a script. Nobody removes anything. Two years later the codebase is strangling LCP.
3. Unoptimised hero media. An uncompressed hero image is worth more LCP than any framework choice.
4. Render-blocking resources in the head.
5. The base theme. Last, and by a distance.

A store that gets LCP under 2.5 seconds on mobile typically sees conversion rate rebound 0.4-0.7 points within four weeks. That result comes from app auditing and theme cleanup, not from replatforming. If speed is your driver, do the cheap work first and see where you land.

Common mistakes

• Choosing custom for aesthetic control you could get within a premium theme for a fifth of the cost.
• Choosing headless for speed without first auditing apps and theme bloat.
• Choosing headless below $2M revenue. Over-engineered, and the ongoing engineering cost is the part that hurts.
• Not budgeting the headless CMS licence. Almost never in the build quote, and it is a recurring five-figure annual cost at most tiers.
• Ignoring marketing team velocity. On a theme your marketer ships a landing page in an afternoon. On headless they file a ticket. Cost that.
• Building a custom theme with hardcoded sections. If you cannot restructure pages without a developer, you have bought a brochure, not a storefront.
• No documentation on a custom build. An undocumented custom theme is a liability the day the agency relationship ends.
• Rebuilding when a targeted fix would do. A mobile PDP problem is an $8,000 project, not a $40,000 rebuild, and the rebuild resets your conversion baseline too.

How we advise on this

We recommend a premium theme for most projects, and we say so before quoting, because the alternative is selling you a more expensive build than your situation needs.

Custom themes when there is a functional requirement no theme meets and you have maintenance capacity. Headless only when the payback case holds in gross profit and there is engineering capacity to own it, which for most brands means later than they expect.

See how we approach Shopify development and design: scope by template count, premium theme unless custom is genuinely justified, and a stated speed target at launch.

Frequently Asked Questions

Do I need a custom Shopify theme or is a premium theme enough?

A premium theme is enough for most stores. A modern Online Store 2.0 theme with thoughtful customization delivers roughly 90% of a custom theme's value at a fraction of the cost, and it keeps receiving updates. Custom themes are justified when your merchandising model genuinely does not fit any existing theme, or when brand differentiation is a material competitive advantage in your category.

Is headless Shopify worth it?

For most stores under $2M revenue, no. Headless is significantly over-engineered at that scale, and a well-built Liquid theme delivers around 90% of the value at 10% of the cost. Headless earns its keep at meaningful scale with specific needs: performance-critical commerce, multi-channel content reuse, advanced personalisation, or design requirements Liquid genuinely cannot meet.

Are custom Shopify themes faster than premium themes?

Not automatically. A well-built custom theme can be faster because it carries only the code your store uses, while premium themes ship features you may never enable. But most speed problems on Shopify come from app scripts and accumulated theme customizations rather than the base theme, so a custom theme with fifteen apps installed is not faster than a premium theme with five.

What is the real cost of maintaining a custom Shopify theme?

Budget 10-20% of the build cost annually. The bigger issue is that a custom theme receives no theme updates, so when Shopify changes conventions or deprecates an API version, that work falls to you or your agency. A premium theme's developer handles that and ships an update.

Can I switch from a premium theme to custom later?

Yes, and it is often the right sequence. Launch on a customised premium theme, learn what your shoppers actually respond to through real conversion data, then invest in a custom build once you know what to build. Starting with custom means designing for assumptions rather than evidence.