01 · Section
What "going headless" actually buys you
A headless storefront separates the front end (Next.js, Astro, Hydrogen) from the commerce engine (Shopify, BigCommerce, custom). You get full control over performance, layout, and locale logic — and you can ship a sub-second LCP that a Liquid theme cannot match.
You also get an escape from the platform's frontend ceiling — A/B testing, custom checkout flows, and integrations with your own services become engineering problems, not theme-hack problems.
02 · Section
When the math works
Catalogue over ~1,500 SKUs with complex filtering — headless wins on performance and merchandising flexibility.
Multi-region or multi-currency pricing with locale-specific rules — far easier in a custom storefront than a multi-store Shopify setup.
You are losing measurable revenue to Core Web Vitals — every 100ms of LCP improvement is typically worth 1–2% in conversion.
You have a frontend engineering team that can own the storefront long term.
03 · Section
When a stock theme is the right call
Under $1M GMV. The build and ongoing maintenance cost rarely pays back at that scale.
A small marketing team that needs to ship landing pages without an engineer in the loop.
A product line that is changing weekly and benefits from the speed of Shopify's native editor.
No bias either way is healthy. We have shipped both for clients in the same quarter.
Key takeaways
- Headless unlocks performance and merchandising flexibility — at the cost of build and maintenance complexity.
- The math typically works above ~1,500 SKUs or with multi-region pricing.
- Under $1M GMV, a well-tuned Shopify theme usually beats a custom storefront.
- Decide on revenue impact, not technology fashion.
Tags
Written by
Bilal Ahmed
6 min read · Posted in E-Commerce