Every platform vendor now has a headless story, and every agency deck has a slide about "composable commerce." Strip away the marketing and the actual question is narrow: do you need a custom frontend badly enough to take on the engineering that comes with decoupling it from the platform that runs your checkout?
What "headless" actually means
In a traditional setup, the platform - Shopify, WooCommerce, whatever you run - owns both the backend (products, inventory, checkout) and the frontend (the theme customers see). Headless splits those apart: the backend stays, but the frontend is a custom-built application - often React or Next.js - that talks to the platform purely through its API. You keep the commerce engine and replace everything customers actually look at.
Where headless earns its complexity
- Content-led brands where product pages, editorial and campaign landing pages need to share one design system, not live in separate theme and CMS silos
- Multi-channel selling - the same product data powering a website, an app and in-store kiosks from one backend
- Performance-critical storefronts at real scale, where shaving seconds off load time has a measurable revenue impact
- Teams with genuine frontend engineering capacity to own a custom build long after launch, not just at handover
Where it just adds cost
- Smaller catalogues where a well-built theme already covers what the brand needs
- Teams without in-house or retained frontend engineering to maintain a custom layer
- Stores where the checkout and product experience are not the bottleneck - marketing and merchandising are
- Anyone chasing "headless" because it sounds modern rather than because a specific limitation is costing them sales
What we actually recommend
Most stores we work with are better served by a well-built theme on Shopify Plus or WooCommerce than by going headless. We only recommend the decoupled route when a client can point to a specific frontend limitation - a content experience the theme genuinely cannot support, or a second channel that needs the same product data - that headless actually solves. If the answer is "it would be nice," that is not reason enough to take on a second codebase.
“Headless is not an upgrade tier. It's a trade: more control over the frontend, in exchange for owning more of the engineering yourself.”
Weighing it up for your store? Tell us what the theme is actually stopping you from doing and we will give you a straight answer on whether headless is worth it.
