PERSPECTIVE
August 31, 2026
Composable commerce, assembling a retail platform from independent, best-of-breed services instead of a single monolithic platform, has become close to a default recommendation in retail technology conversations. It is the right architecture for a meaningful set of retailers, and actively the wrong one for a larger set that adopts it anyway because it is currently the fashionable answer.
Composable architecture earns its complexity when a retailer has specific, differentiated requirements in particular parts of the stack, a highly custom checkout experience, unusual product configuration logic, or channel requirements a monolithic platform genuinely cannot support well. In those cases, the flexibility to swap and independently scale specific services is worth the added integration overhead.
For a retailer without those specific, differentiated requirements, composable commerce mostly adds integration surface area and operational complexity without a corresponding benefit. Every additional independent service is another vendor relationship, another API to keep in sync, and another point of failure, costs that are easy to underweight when composable is being pitched purely on its flexibility upside.
The retailers who end up regretting a composable migration are usually the ones who adopted it because it was the current best practice, rather than because they had identified a specific requirement a monolithic or lightly-customized platform genuinely could not meet.
Before committing to composable, the honest question is: which specific part of our current platform is actually constraining us, and would a composable architecture solve that constraint in a way a more targeted change would not? If the honest answer is “nothing specific, it just seems like where the industry is headed,” that is a sign the migration is being driven by trend rather than requirement, and it is going to be an expensive way to find that out.
Zero trust gets sold as a technical architecture. In banking specifically, the harder and more important part is the policy and organizational change underneath it.
Composable commerce is the current default recommendation for retail platforms. It is genuinely the right call for some retailers, and a costly overcorrection for many others.
Technical due diligence in private equity deals is often treated as a compliance checkbox late in the process. That sequencing is costing firms real money post-close, and it is fixable.