Headless commerce agencies

When headless is worth it

• The front end has to do something the theme layer cannot. A configurator with real complexity, an editorial site with commerce embedded, an experience spanning several brands or several back ends.
• Content is the product. When a serious CMS drives most of the site and commerce is one part of it, driving the whole thing from the store’s theme is the tail wagging the dog.
• You have a front-end team. This is the decisive one. Headless moves responsibility for performance, accessibility, SEO rendering and the build pipeline from the platform to you, permanently.

When it is not

If your storefront is a catalogue, collection pages, a product page and a checkout, a well-built theme will be faster to deliver, cheaper to run, easier to hire for, and — this surprises people — frequently faster in the browser, because the platform’s own rendering has had far more optimisation attention than a typical custom front end receives.

Headless also removes the platform’s app ecosystem. Extensions that install in one click on a themed store may need rebuilding, and the ones that inject storefront UI usually will.

The costs that are not in the quote

Hosting and a CDN. A build pipeline and the person who maintains it. Preview environments so merchandisers can see changes. Framework upgrades on someone else’s schedule. Re-implementing analytics and consent handling that the theme gave you. None of these is large alone; together they are a standing cost the business case rarely includes.

Questions worth asking

• What does the merchandising team lose? Usually the visual editor. Ask what replaces it and who has to be involved to change a banner.
• How is search rendering handled? Server rendering is not optional for a storefront, and getting it wrong is silent.
• What is the checkout? Most headless builds keep the platform’s checkout, which is the right answer and worth confirming.
• Who runs it in year two?

What it costs

Headless storefront builds commonly start around $60,000 and routinely reach several hundred thousand for multi-market implementations. Running costs — hosting, CDN, monitoring, plus a front-end capability you must retain — are typically $2,000–$10,000 a month before any feature work.