The SI’s Guide to Composable Commerce: Deliver High-Value Upgrades Without the Rip-and-Replace Risk

Let me tell you about my friend, Maya.

On Friday night over dinner, Maya was still fuming about work. She runs purchasing for a mid-size contractor, and she'd spent all week fighting one routine task: reordering the same parts her crews buy every month.

She'd logged into her supplier's B2B portal to reorder from her order history. But the pricing looked off, so she couldn't tell if she was getting her company's negotiated rate. She pushed the order through anyway, and the site said the quantity wasn't available, even though it had looked in stock a minute before. She tried again the next day, and an approval rule kicked the whole order back.

Then she gave up, emailed her sales rep, and waited for someone to place the order by hand, which delayed the parts, delayed a job site, and became her problem to explain.

“Isn't this the type of stuff you fix, Mishel?” she asked. 

Yes, my friend, I know how to fix this. The supplier didn't lose that order because of a bad price or a missing part. They lost it because the different parts of their commerce experience weren't telling the same story. Pricing lived in one place, inventory in another, approvals in a third, and none of them agreed.

And that's the part of composable commerce that doesn't get enough attention, especially for those of us who deliver these platforms for our clients.

Composable Commerce Is a Great Idea. But There’s a Catch.

Instead of one giant system, composable commerce uses smaller building blocks. One handles search, another the cart, others pricing and checkout. In B2B there are more of them, and they're more demanding: contract-specific pricing, customer catalogs and entitlements, account hierarchies, approval workflows, and quoting.

Each block does its job, and in theory you can change one without changing everything. I've always liked that idea. It gives your clients more freedom to adapt.

But breaking one big system into many smaller pieces doesn't make complexity disappear. It moves the complexity between the pieces.

Search might say a part is available while inventory says it isn't. The contract-pricing block might show one rate while checkout charges another. An approval workflow might reject an order the catalog said the buyer could place. Two parts of the same order end up telling different stories.

Each individual block can be working perfectly, while the overall buyer experience is still broken.

That's what happened to Maya.

The Answer Isn’t Fewer Pieces. It’s Making the Pieces Work Together.

This is where HCL Commerce+ takes a different approach.

You shouldn't have to put a client on an old, rigid platform, or hand them a pile of disconnected tools your delivery teams have to constantly wire together and keep alive.

HCL Commerce+ is built around the idea of Integrated Composable Commerce: giving businesses the flexibility to evolve individual parts of their commerce experience while keeping those parts connected as part of a broader enterprise commerce platform.

HCL Commerce+ uses independent business services, storefront, search, transactions, that evolve without forcing changes across the whole platform, while reducing the maintenance burden of managing microservices one by one.

So What Makes Hcl Commerce+ Different From Every Other Platform That Calls Itself "Composable"?

Fair question. These days almost every platform you'd put in front of a client offers building blocks. So if composable is table stakes, what actually makes HCL Commerce+ different, and easier for you to deliver?

For me, the biggest difference is simple. You don't have to tear down what your client already has.

A lot of composable platforms mean a full rip-and-replace: pull out the client's existing commerce stack and rebuild it from scratch. That's a huge, high-risk program for your delivery team to run, and the client's business still has to keep trading the entire way through.

HCL Commerce+ lets you modernize instead. You keep what's working today and upgrade groups of capabilities, on a timeline the client can live with. Think of it like renovating a house room by room, instead of knocking it down and moving the family into a construction zone for a year.

That's a big deal for a systems integrator. You can lead a client into composable without betting their business, or your delivery reputation, on a single “replace everything” program. Smaller, lower-risk phases are easier to scope, easier to deliver, and easier for the client to say yes to.

This Matters to the People Delivering Commerce, Too

If you're a systems integrator, you've seen the other side of the composable story. More components can create more opportunities to add value. But they can also create more integrations to build, test, monitor, troubleshoot, and maintain.

That's not always bad, integration is often where an SI creates real value. The problem is unnecessary integration. Every connection that exists just because two products weren't designed to work together is another dependency to build, test, monitor, and eventually explain when it fails.

This is where the HCL Commerce+ architecture earns its keep. Because the core capabilities are built and integrated as one platform, the connections between them aren't yours to wire up, test, or babysit. The pieces are designed to agree out of the box, search with inventory, contract pricing with checkout, approvals with the catalog, and that connective tissue stays tested every time the platform is updated.

That's the real difference from a stitched-together best-of-breed stack. With HCL Commerce+, most of that “make unrelated products agree” work goes away, so your testing and monitoring focus on integrations that actually add value (like your client's ERP, CRM or tax engine).

Integrated Doesn’t Mean Closed

A composable platform still has to fit the client's wider tech landscape. HCL Commerce+ is API-first, with OpenAPI-based services, GraphQL, and webhooks for integration and extension.

That matters, because integrated shouldn't mean closed. You want a platform that removes unnecessary integration work, not one that blocks the integration work that actually creates value for the client.

What Does That Mean in Practice?

• Performance matters. Traffic doesn't arrive at a predictable rate; for retailers, a flash sale during the holidays or an unexpected event can spike demand in seconds. HCL Commerce+ is built on a backbone designed for performance and significant peaks in buying activity.
• Security matters. The more separate solutions you bolt together, the more connections you have to protect. HCL Commerce+ is an integrated platform, not a kit an organization has to assemble and secure itself.
• Agility matters. Businesses enter new markets, launch products, and add brands. HCL Commerce+ supports B2B, B2C, B2B2C, and D2C, across multiple geographies and brands on a single instance.

For your client, that means more freedom to change. For you, it means a more manageable foundation to deliver that change on.

Managing AI Makes This Even More Important

Shopping is changing. As AI shopping assistants get more capable, they'll search, compare, check prices, and complete purchases, which means the systems behind a commerce experience have to agree even more tightly.

Picture Maya's bad reorder, but an AI assistant is placing the order instead of Maya. It checks availability, looks up the contract price, and tries to submit.

If those systems disagree, the assistant is stuck too, and it may improvise in ways you really don't want. The more shopping gets automated, the more a consistent, connected platform matters.

Partners who help clients build commerce foundations that are flexible, connected, and ready for AI-powered experiences will play a far bigger role than partners who just implement another platform. They'll be helping clients build what comes next.

That's the story I think HCL Commerce+ tells well. As an integrated composable platform, it gives businesses room to evolve while staying connected, scalable, and secure, and it gives systems integrators a modern foundation to add value on, without burning their time solving integration problems that shouldn't exist.

Because customers don't experience your architecture. They experience whether the products are available. Whether the price is what was agreed. Whether the order goes through.

And that's exactly the point.

I'd love to hear from other systems integrators and digital transformation leaders: has going composable made your client projects easier to deliver, or just harder to keep in sync? Reach out to me over email or fill out the contact us form.