Skip to content

Business

Headless or hosted commerce: an honest decision guide

Headless is not automatically better. Here is the shortlist of conditions that make it worth the extra cost.

Priya Kaur9 min read

By Priya Kaur

Delivery Director

Keeps twelve concurrent engagements honest about scope, timelines and the difference between the two.

Expertise

Hosted is the correct default

If your catalogue is under a few thousand products, your pricing rules are simple and your team is small, a well-built hosted theme will outperform a rushed headless build on every metric that matters, including speed.

Four conditions that justify headless

We recommend headless when at least two of these are true. One on its own is rarely enough to cover the additional engineering cost.

  • Content and commerce need to interleave on the same page
  • You sell through several channels from one catalogue
  • Your merchandising rules exceed what the platform admin allows
  • Page speed is a measured, material driver of your revenue

Count the running cost, not just the build

Headless moves work from the platform to your team. Someone has to maintain the frontend, the deployment pipeline and the integrations. Budget for that from the start, or the second year will be unpleasant.

About the author

By Priya Kaur

Delivery Director

Keeps twelve concurrent engagements honest about scope, timelines and the difference between the two.

Expertise

Tell us what you are trying to build

A 30-minute call, no deck and no obligation. You will leave with a scope, a rough number and an honest opinion about whether we are the right fit.