Headless commerce decouples the store frontend from the backend, providing full control over UX and performance. When is it worth it, and when is it better to stick with classic Shopify or WooCommerce?
Headless commerce is an architecture where the presentation layer (frontend) is decoupled from the business logic layer (backend) and communicates with it via APIs. In practice: the backend (Shopify, BigCommerce, commercetools) manages products, cart, and payments, while the frontend (Next.js, Astro, custom) handles the UI.
When headless commerce pays off
Stores with high performance requirements (Core Web Vitals are critical)
Custom purchase journeys (configurators, dynamic pricing)
Multiple sales channels (web, mobile app, kiosk, marketplace)
High scale (>100k page views/day)
Need for complete control over UX and branding
When NOT to choose headless
A small store with up to 1,000 products, a standard sales model, no dedicated development team, and a limited budget - in this case, classic Shopify or WooCommerce is cheaper, faster to deploy, and fully sufficient. Headless is a significantly larger investment.
Technology stack
The most popular combinations: Shopify Hydrogen + React/Remix, Next.js + commercetools, Astro + Saleor. The choice depends on scale, team expertise, and SEO requirements. All of them allow ISR/SSG, which results in excellent Core Web Vitals.
Implementation costs
Headless Shopify (basic Next.js frontend): individual quote
Headless with a dedicated configurator: higher budget, individual quote
Enterprise headless with multiple channels: usually starting from approx. 150 000 zł net and up.
We design headless stores from MVP to enterprise implementations. A quick discovery call - quote within 24h.
Top comments (6)
This is one of the most balanced breakdowns of headless commerce I've read in a while. The comparison on when not to choose it is especially valuable - saving businesses from over-engineering too early is huge. Out of curiosity, which framework combo (Hydrogen vs. Next.js) are you seeing clients lean toward most lately?
Thank you, I really appreciate that!
To answer your question: Next.js is still the undisputed king when a client has a highly fragmented backend (e.g., pulling data from a separate PIM, a legacy ERP, and a custom CRM alongside the commerce engine) simply because of its massive ecosystem and flexibility.
However, if a client is 100% committed to Shopify Plus and just wants a faster, more dynamic storefront without reinventing the wheel, I'm seeing a massive shift toward Hydrogen. Shopify has made the developer experience with Remix so smooth that it often guarantees a faster time-to-market for Shopify-native brands.
Great, well-balanced breakdown of the topic. Too often, "headless" gets treated as a buzzword rather than a tool for specific use cases—for smaller stores, classic Shopify or WooCommerce genuinely win on time-to-market and maintenance overhead.
One thing worth keeping in mind is the ongoing operational cost: in a headless setup, adding a new feature or third-party integration usually requires developer time rather than a quick app install. Glad to see that distinction clearly laid out!
Couldn't agree more! If a marketing team has to wait for a developer every time they want to test a new feature or integration, headless might actually slow the business down instead of scaling it. You trade convenience for absolute control. Great addition to the discussion!
A very detailed overview. You often hear people in the industry talk about “headless” as a magic cure-all, but there’s a lack of honest discussion about the costs and responsibilities involved.
Thanks! That was exactly my goal. The tech industry loves the "new shiny thing", but at the end of the day, moving to headless is a business decision, not just a technical one. If the ROI doesn't justify the ongoing maintenance and responsibility, sticking to a solid monolith is simply the smarter move.