Your Platform Readiness Score

Insights

Why Headless Commerce Architecture Alone Isn't Enough for a Unified Commerce Strategy

At Retail Jam 26 at Knebworth, we hosted a roundtable titled “Creating Unified Commerce Experiences with Headless Architecture.” The title was deliberate. Headless was the entry point into the conversation. But within minutes, the room had moved somewhere more interesting and more honest.

Because here is what became clear across two cohorts of senior retail leaders: headless commerce architecture is a solved problem compared to what comes after it. The real challenge is not how you decouple your front end from your back end. It is what you do with the freedom once you have it, and whether that freedom supports a genuine, unified commerce strategy.

The definition problem

Ask a room of CIOs, CTOs and CEOs what unified commerce means, and you will not get one answer. You will get ten. Some describe it as an architecture. Some as a customer experience ambition. A few, if the conversation feels safe enough, admit they are still working it out.

That is not a failure of understanding. It is an accurate reflection of where most businesses genuinely are. Headless commerce gives you architectural freedom. It does not give you a unified commerce strategy. Confusing headless commerce with unified commerce is where organisations lose significant time and money.

What headless commerce architecture exposes

Moving to a headless architecture is genuinely liberating. You remove the monolithic constraint. You gain the ability to move faster, compose your stack intentionally, and deploy change without the blast radius of a tightly coupled system.

But headless also exposes what was hidden underneath. The data fragmentation that the monolith was papering over. The ownership questions nobody had formally answered. The organisational seams between channels, between functions, between the teams responsible for governing data and the teams that need to use it.

This pattern surfaced consistently across both cohorts at Retail Jam. Businesses that had done significant platform work, integrated, headless, architecturally sound, arrived at a new and harder question. They had the infrastructure. They did not yet have the operating model required to deliver unified commerce.

Heart surgery on a live patient

There is an analogy that captures the transformation challenge better than any technology framework. Imagine performing heart surgery while simultaneously replacing the lungs. The patient cannot be put under. The business keeps trading. You are operating on a live system, with revenue flowing and every change carrying real commercial risk.

That is not hyperbole. For most mid-market and enterprise retailers navigating a unified commerce strategy, that is the reality. The constraint is not ambition. It is the fact that you cannot stop the business to fix the business.

The organisations that navigate this well do not try to solve everything at once. They make a deliberate set of strategic choices about what to protect and what to change, sequenced against a clear north star. Not a technology roadmap. A commercial story the whole organisation can orient around, visible at board level, stable enough to make hard trade-offs against.

The data ownership question nobody wants to answer

Beneath every unified commerce conversation, and this held true across both Retail Jam cohorts, is a data ownership question that rarely gets resolved cleanly.

Who owns the customer record? Who owns product data? Who is responsible for maintaining a single customer view across the business? And who has the authority to govern it, cleanse it and share it downstream to the teams and systems that need it? In businesses operating across multiple channels, marketplaces and geographies, this question becomes genuinely complex, particularly in omnichannel retail environments.

The organisations making progress have done something straightforward but organisationally difficult. They have separated the question of who owns the data from the question of who uses it. Technical ownership, cleansing, data governance and downstream distribution sits in the right function with the right authority. Business ownership, what the data means, what decisions it enables, what customer outcomes it drives, sits at leadership level. That distinction, once made, accelerates everything else.

Where AI fits

AI featured in both cohorts. The dynamic was consistent. Executive appetite is high. Platform and data readiness, in most cases, is not yet where it needs to be to support serious AI investment.

The leaders who spoke most credibly about AI were not the ones with the biggest ambitions. They were the ones who led with foundations. Clean data, clear ownership, and the ability to observe what is happening across the business in real time. AI amplifies whatever is underneath it. If the foundations are fragmented, AI makes the fragmentation faster and more expensive.

The opportunity is real. Reducing operational overhead, accelerating insight, building intelligent capability on top of a unified platform — these are happening. But they are happening in businesses that invested in the foundational work first.

The question worth asking now

Unified commerce is not a platform decision. It is a continuous operating discipline designed to deliver connected customer experiences. Headless commerce architecture gives you the technical foundation. What you build on top of that, the data governance, the organisational clarity, the board-level story that makes every investment decision purposeful, is the harder and more important work.

The question worth asking in your business right now is not whether you have the right architecture. It is whether you have the foundations that make unified commerce genuinely possible.

If this resonates with where your business is, I am always open to a conversation.