"Headless" has been the loudest word in e-commerce circles for the past three years. Every conference, every vendor pitch, every consultant deck. But for most stores, switching to headless is a bad financial decision — and for a small group, it's transformative.
Here's how we actually decide for our clients.
What "headless" actually means
A traditional e-commerce platform (Shopify, WooCommerce out of the box) bundles two things: the frontend (what shoppers see) and the backend (cart, inventory, payments, orders). They ship together; you customize within the limits the platform allows.
"Headless" means decoupling the two. The backend keeps doing its job — but the frontend is a separate codebase, usually built with a modern framework like Next.js or Astro, talking to the backend via an API.
The trade-off is straightforward:
- Pro: total design and performance freedom on the frontend
- Con: you now own and maintain a custom frontend (with all the cost that implies)
When headless is the right call
From the projects we've shipped, headless makes sense when at least two of these are true:
1. Your design ambitions exceed what themes allow
If you're a luxury brand, an editorial commerce site, or a design-forward DTC brand, the standard Shopify themes will hold you back. We've seen brands lose ~20% conversion to "this looks like every other store" perception. (Our client Tsaloys is a good example — multilingual luxury fashion needed editorial care that no theme could deliver.)
2. Performance is a real revenue lever
For high-volume stores, every 100 ms of load time correlates with measurable conversion changes. Headless setups routinely hit Lighthouse scores of 95+ where templated stores struggle to break 70.
3. You sell across multiple channels
Web store, mobile app, in-store kiosks, marketplace integrations. If you need the same product catalog and order system feeding multiple "heads", a decoupled backend pays for itself.
4. You have engineering capacity (or can hire it)
This is the unsexy one. A custom frontend needs ongoing developer attention — security updates, dependency upgrades, browser compatibility. Plan for at least 8–15 hours of dev maintenance per month.
When headless is the wrong call
If you're nodding along to any of these, stay templated:
- You sell < 200 SKUs and < $500K/year
- Your team has no developer (in-house or on retainer)
- Your bottleneck is marketing or product, not the website
- You're using 6+ Shopify apps and rely on their integrations
- You launched less than a year ago
The realistic numbers
For a typical mid-market store moving from templated Shopify to a Next.js + Shopify Storefront API setup, here's what we usually quote:
- Initial build: $15,000–$45,000 depending on scope
- Time to ship: 6–12 weeks for the first version
- Ongoing dev cost: $1,200–$3,000/month for maintenance + improvements
- Hosting: $0–$200/month (Vercel free tier covers a lot)
Compare that to staying on a templated Shopify with a $200/month plan + $50/month in apps. The math only works if the new frontend drives meaningful, measurable revenue gains.
Half-measures worth knowing
Two middle-ground options exist that we recommend more often than full headless:
Hybrid customization
Stay on Shopify, but build a heavily customized theme (Liquid + custom JS). You get most of the design freedom without owning a separate codebase. Cost is roughly 30–50% of a full headless build.
Headless for one section only
Some clients keep their core store on the platform, but build a custom Next.js page for a specific high-stakes flow (a holiday landing page, a configurator, a specific product line). You get the performance win where it matters most, without the full migration.
"The best e-commerce platform is the one that disappears from your daily problem list. Sometimes that's headless. More often it's a well-tuned templated store with the marketing budget you would have spent on engineering."
The decision framework
If you're considering the move, sit down with these four questions:
- What specific revenue lift would justify the build cost? (Calculate it.)
- Who maintains the frontend after launch? (Name the person or company.)
- What's the rollback plan if performance doesn't improve as expected?
- What's the lowest-cost test we could run to validate the assumption first?
If you can't answer all four with specifics, you're not ready yet — and that's fine. The platforms aren't going anywhere.
Bottom line
Headless commerce is a powerful tool for the right store. For the wrong store, it's an expensive way to discover that your problem wasn't your platform.
If you're weighing this decision and want an outside read, we offer a free 30-minute commerce architecture review. We'll tell you honestly whether you're ready — and if not, what to fix first.
