10 stumbling blocks when moving to composable commerce

As avowed fans of the composable commerce framework, we know its many strengths very well. But we also know just as well where the transformation of your e-commerce platform can start to stumble.

1. Not all that glitters composable is gold.

The very first stumbling block is a hefty piece of consulting work: the fact that systems are "composable" does not mean they convince across the board, that they really combine with every other building block and, above all, that they truly meet your individual requirements. So here is an important tip right away: first define your own target picture (where do you want to go?), look at your flexibility requirements and only then decide on a system that really fits.

2. Composable commerce begins in your head.

Assume that your team's mindset has to change. Working in several systems at once calls for a different approach and demands the willingness to engage with new possibilities and to keep learning.

3. More monitoring, please.

In a MACH architecture, several systems always have to be monitored at the same time. So you should define in a binding way, up front, which systems are observed where and by whom. On top of that, it needs to be clear when notifications should be escalated.

4. Optimal cost control. Or should we say "optimized"?

Costs usually depend on usage, meaning actual traffic, computing power and the storage space you need. That sounds good at first, and it is, provided that traffic, computing power and storage are optimized as far as possible. Otherwise you may face a nasty, or rather an expensive, wake-up call.

5. Goodbye, dependency!

Composable commerce is designed, among other things, so that you can build your system landscape with maximum freedom and without any dependencies. For that reason, think carefully about whether you want to opt for accelerators, for example, which restrict your independence all over again.

Composable commerce delivers flexible solutions through the
seamless combination of specialized services

6. Possibilities want to be used.

A switch to a composable landscape can open up a lot of potential. But only if you also know how to use the technologies you deploy and actually work with them. A modular IT landscape alone changes nothing, not even when it is assembled from the best specialist systems in the world.

7. Know-how matters: the integration.

Yes, yes, composable can be very simple. But that does not mean the detailed requirements of your enterprise business can be met just like that, in a flash, by plug and play. Data, processes and the APIs of the systems are usually far too complex for that. Not everything glitters that should glitter (see point 1).

8. We need to talk. About your data.

Composable commerce does not make your data better per se. Without the diligent work of modelling and otherwise processing it, your great modular tools will bring you little to nothing.

9. Yes, you are a stumbling block!

In the worst case, you yourself do not yet know exactly what you are getting into, and on top of that your service provider does not advise you really well. When these two possibilities meet, your dream of domain-oriented microservices and the like can turn into a nightmare of endless workarounds and never-ending patchwork pretty quickly.

10. Wrong requirements stay wrong requirements.

Whatever originally made your monolith or your all-in-one digital wonder stumble, the same mishap can threaten you again with a modular architecture. For example through nonsensical requirements, poor prioritization, missing checks via KPIs or a lack of sparring with a trusted service provider. These are all killer stumbling blocks that can keep driving you crazy. And none of us want to go there, right?