Headless Shopify is the most over-recommended architecture in ecommerce right now. Every agency proposal lists it. Every YouTuber demos it. Most stores that pay for it don't need it — and most stores that doneed it can't tell why.
Here's the honest decision framework I use when a merchant asks “should we go headless?”
What headless actually means
In a normal Shopify store, the same server renders both your shopfront and handles your cart/checkout. Liquid runs on Shopify's infrastructure. Your theme, your data, and your checkout all live in one place.
In a headless setup, you split that in two:
- Frontend — your own Next.js / Hydrogen / Astro app, hosted wherever you want (Vercel, Netlify, Cloudflare).
- Backend — Shopify still owns product data, cart, and checkout, accessed via the
Storefront API.
You build the storefront in whatever framework you want. The checkout still hands off to Shopify-native to keep PCI compliance and conversion.
The 4 reasons headless is worth it
1. Editorial control you can't fake in Liquid
Liquid was designed for ecommerce sections, not editorial storytelling. If your brand depends on magazine-quality content— long-form artisan stories, technique deep-dives, custom layouts per product — you'll hit Liquid's ceiling fast.
Forge & Fire (one of Faber's case studies) is the textbook example. Hand-forged Japanese-style knives, multi-step heat treatment processes, single-craftsman runs. That story needs custom video lazy-loading, scroll-driven product pages, editorial-style content management. Liquid would have meant fighting the theme every day. Headless was the right call.
2. Performance ceilings Liquid can't cross
A well-optimized Liquid theme can hit 0.9–1.5 seconds LCP. Excellent. But the floor in Next.js with React Server Components + ISR is 0.5–0.8 seconds on the same hardware. That last 300ms is meaningful for premium brands where every fractional second of friction costs conversion.
You also gain partial prerendering, streaming SSR, fine-grained cache control — things you simply can't do inside a Shopify-hosted theme.
3. Component reuse across surfaces
If you're shipping a web app + a mobile app + a kiosk experience that all share the same product data, headless lets you reuse the same Storefront API across React Native, native iOS, and your website. One source of truth, multiple frontends.
This is rare in DTC but common in B2B and omnichannel retail.
4. Future-proofing for non-Shopify systems
If you're probably going to integrate Sanity for content, Algolia for search, Klaviyo for marketing, custom ERP, etc., the decoupled architecture pays for itself in flexibility. You're no longer constrained by Shopify's app ecosystem.
The 4 reasons it's NOT worth it
1. You don't have a content team
Headless requires you to manage two systems — Shopify for commerce + a CMS (Sanity, Contentful, or your own database) for content. If you don't have someone owning the content pipeline, you've added complexity without value.
2. You're under $1M GMV
Headless adds 3–5x complexity to ongoing maintenance. Every merchant feature (gift cards, B2B, subscriptions, loyalty) needs custom integration work that's “free” in a regular theme. If revenue can't justify a dedicated developer (or retainer), Liquid is the right call.
3. You're bottlenecked by features, not design
If the reason your store is “slow to ship” is features(subscriptions, B2B portal, inventory workflows), headless doesn't help. Those problems are solved by apps and theme integrations, not a frontend rewrite.
Headless solves presentation problems, not functionality problems.
4. Your team can't hire React engineers
Shopify devs (Liquid + Theme + Apps) are a different talent pool from React/Next.js engineers. If your team is wired around Shopify Partners and Liquid contractors, going headless means rebuilding the team.
The decision matrix
Go headless if you check 3 or more of these boxes:
- Annual GMV over $2M
- Brand depends on editorial / long-form content
- Need sub-1s LCP for SEO + premium positioning
- Shipping to multiple surfaces (web + mobile + kiosk)
- Have or can hire React/Next.js engineers
- Integrating with Sanity, Algolia, or custom backends
- Can support a dev retainer ($1.5k+/mo)
Stay on Liquid otherwise. A well-built Dawn-based theme will serve a single-channel DTC brand under $1M GMV better than headless every time.
The hybrid option most miss
You don't have to choose between “all in” and “all out.” Some merchants run a hybrid setup: most pages stay in Liquid, special pages (landing pages, editorial features, campaign microsites) get built in Next.js and embedded via subdomain or custom routing.
This is often the right answer for brands that want premium content surfaces without rebuilding their entire commerce flow.
Wrap
Headless is a tool. Tools should answer a specific problem. If you can't name the problem headless solves for your store in one sentence, you don't need it yet.
And if you can — and the answer is editorial freedom, sub-1s performance, or multi-channel — you should go headless yesterday. Just go in with eyes open about the maintenance cost.