Custom theme versus headless: cost, speed, flexibility

The short answer

Both options give you a store that looks like your brand. The difference is where the pages shoppers see are made. With a custom theme, Shopify renders them, inside its theme system, with your design applied. With headless, a separate storefront that you own renders them, on Astro in our case, and asks Shopify for products, prices and the cart through its APIs. Checkout stays on Shopify either way.

For an ordinary store a clean custom theme is the right answer. Headless is the right answer for a specific kind of store, and it pays to know which kind you are before you spend.

Side by side

	Custom theme	Headless with Astro
Who renders the pages	Shopify’s theme engine	Your storefront, built and hosted separately
Speed on phones	Good, if apps and images are disciplined	Fast by construction; finished pages from the edge
Speed ceiling	Limited by the theme system and any app scripts	Limited only by what you build
Design freedom	High, within theme conventions	Total
Content pages, blog, guides	Workable, not the platform’s strength	Native: same fast site, same design
Storefront apps	Work as designed	Do not apply; functions rebuilt where they earn their place
Editing	Shopify theme editor	Content system or code, via your partner
Checkout, admin, orders, inventory	Shopify	Shopify, unchanged
Build effort	Days to weeks	A development project
Ownership	Theme code lives in your Shopify store	Storefront code in a repository you own
Right for	An ordinary store	Stores with volume where speed, design or content is a measured limit

When a custom theme is the better investment

• The store sells in a standard way and the team likes the theme editor.
• Traffic and revenue do not yet justify a development project.
• Speed problems are apps and images, which a clean-up fixes without a rebuild.
• Storefront apps you rely on are doing real work.

When headless pays

The middle path

Many stores take a step in between: a fast Astro site for content, guides and landing pages on the same domain, with the theme still serving products. Shoppers get fast content and one design; the store keeps its theme and apps for now. When the product pages become the measured limit, they move over too, onto a storefront that already exists.

What this means for you

Clean up the theme first, whatever you plan later. Then look at three numbers: your volume, your mobile Core Web Vitals on product pages after the clean-up, and how often the theme stops you doing what the brand needs. If all three point the same way, headless is the next step and the clean store is the right starting point. If they do not, the money is better spent elsewhere, and we will tell you so.