Headless commerce is an operating model, not a badge

Architecture should follow the organisation

A composable commerce stack can create speed, flexibility, and a distinctive experience. It can also create more systems to maintain, more decisions to coordinate, and a higher cost for every change. The useful question is not whether headless is better. It is whether the operating model fits the business.

Understand what is genuinely constrained

If the current platform limits performance, international content, complex merchandising, or experience design, a more flexible architecture may be justified. If the main constraint is unclear product messaging or slow internal approval, changing the stack will not solve it.

• List the experiences the current platform cannot support.
• Estimate how often those limitations affect revenue or team velocity.
• Identify who will own integration quality after launch.
• Compare the total change cost, not only the initial build.

Protect the editor experience

A fast storefront that makes publishing difficult is not a fast system. Content teams need clear preview, reusable sections, safe controls, and a workflow that matches how campaigns are actually launched.

The best architecture is the simplest one that supports the experience and pace the business truly needs.

Choose for the next few years

Consider market expansion, catalogue complexity, localisation, experimentation, and internal capability. A traditional platform with disciplined implementation may outperform a sophisticated stack that the team cannot operate confidently.