What are the main hidden costs associated with composable commerce?

Key hidden costs include significant ongoing integration development and maintenance, the administrative burden of managing multiple vendor contracts, the need for specialised and expensive technical staff, and the accumulation of technical debt from bespoke connectors that are hard to update or replace.

How does composable commerce affect technical debt?

Each integration between composable components, particularly custom ones, creates technical debt. This debt accumulates over time, making system updates, feature development, and issue resolution more complex and time-consuming, ultimately slowing down innovation and increasing operational costs.

Is vendor lock-in still an issue with composable commerce?

While composable commerce aims to prevent lock-in to a single monolithic vendor, it can create a different form of lock-in to a *set* of vendors. Replacing a critical component often requires rebuilding extensive integrations, which can incur costs comparable to a full platform replatforming.

What kind of technical expertise is needed for a composable setup?

Teams require deep expertise in multiple APIs, various programming languages, and different technology stacks across the component ecosystem. DevOps capabilities to manage complex deployment and monitoring environments are also essential, demanding a highly skilled and potentially larger team.

When might a monolithic or hybrid approach be preferable to entirely composable?

A monolithic or hybrid approach, such as a strong platform like Adobe Commerce with targeted integrations for specific needs, is often preferable when integration capacity is limited, TCO predictability is critical, or the overhead of managing numerous disparate systems outweighs the agility benefits. This is common for mid-market and enterprise businesses with established processes looking for a manageable growth path.

Talk to an expert

Issue 038PositionAdobe CommerceRef 128

Why composable commerce can become expensive chaos

Composable commerce promises flexibility but often introduces system complexity and cost. Mismanagement of integrations, vendor relationships, and long-term maintenance can quickly erode initial benefits, leading to an expensive, fragmented system.

Andrew Pemberton· Development Director

11 Aug 20255 min readReviewed August 2025

"While composable commerce promises flexibility, it frequently introduces unmanageable integration debt and hidden costs, turning agility into administrative burden."

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.