What is the core difference between headless and traditional commerce?

The core difference is the decoupling of the front-end (presentation layer) from the back-end (commerce logic) in headless. Traditional commerce platforms, like Adobe Commerce out-of-the-box, have these layers tightly integrated, meaning the platform handles both data and its display.

Does headless commerce automatically improve website performance?

No, not automatically. Headless allows for the *potential* of improved performance by enabling custom, highly optimised front-ends (e.g., PWAs). However, a poorly implemented headless front-end can perform worse than a well-optimised traditional site. Performance gains depend entirely on the quality and optimisation efforts put into the custom front-end development.

Is headless commerce suitable for every B2B business?

Headless commerce is not suitable for every B2B business. It offers benefits for those with complex omnichannel needs, highly customised user experiences, or stringent performance demands. For businesses with standard requirements, a well-configured traditional Adobe Commerce instance, potentially with PWA Studio, often provides sufficient functionality without the increased technical complexity and cost.

What are the main drawbacks of implementing headless commerce?

The primary drawbacks include increased complexity, higher development and maintenance costs due to managing separate front-end and back-end systems, and the need for specialised development skills. It also introduces potential challenges in API management and ensuring consistent performance across decoupled layers.

Can I go headless with my existing Adobe Commerce instance?

Yes, an existing Adobe Commerce instance can be made headless. Adobe Commerce exposes robust APIs that allow a custom front-end to interact with its back-end functionalities. However, adapting an existing site to a headless architecture is a significant undertaking requiring planning, development, and testing that often equate to a substantial replatforming effort for the front-end.

Talk to an expert

Issue 030BriefingAdobe CommerceRef 114

Why "headless" is not a strategy

Headless architecture is a technical implementation option, not an inherent business strategy. Its suitability depends on specific organisational needs, existing technical debt, and long-term commerce objectives, particularly within B2B and complex retail environments.

Andrew Pemberton· Development Director

29 Dec 20245 min readReviewed December 2024

"Headless architecture is a technical choice, not an inherent business strategy."

Written by

Andrew Pemberton

Development Director

19 years at iWeb

LinkedIn →Speak with Andrew about your brief →

Andrew leads the development practice at iWeb and owns the delivery runbooks behind large commerce migrations. He writes about release governance, deployment sequencing, parallel-run strategy, and the engineering decisions that reduce operational risk during complex transformation programmes. Focused on stable delivery, observable systems, and migration approaches that avoid unnecessary disruption to trading.

Next step

Take this conversation private.

If this note matches the brief on your desk, the version we'd write for your platform, sector and trade-account model is the work itself. Send a short brief and a senior lead replies inside 48 hours.

Talk to an expert Back to The Record →

Operational notes worth reading next.

When to keep Magento 2 past end-of-life: a defensible position, not a default one

How to know when Adobe Commerce still makes sense

Magento 2 end-of-life: the migration paths that survive contact with reality

A regular round-up of new notes.No content marketing.

Take this conversation private.

A regular round-up of new notes.
No content marketing.