We've already told you about Composable Commerce's smallest and most important kit. If you haven't read that article yet, we recommend a quick look before you continue reading here:
What are modules?
Modules are larger building blocks in the Composable Commerce structure.
A module combines comparable microservices and workflows under one term. Modules can be located in the frontend as well as in the backend.
A practical example - payment modules
The differences, but also the most important points of contact between microservices and modules can best be explained with an example.
In the area of online payments, we find several microservices and modules.
Online stores that follow more of a retail strategy often include an extensive payment structure - customer payments are accepted via credit card, PayPal, Amazon Pay, Klarna, and others at the same time. All of these payment methods need to be customized and enabled in the store. Each payment method is a microservice that interfaces with the store and ERP system.
However, payment microservices can be bundled together in one module because they use the same workflow. A payment module for a B2C store thus contains several payment microservices that adhere to the same rules and serve the same online store area.
On the other hand, we have the example of a classic B2B online store where the only payment method used is payment by invoice. This single microservice can also be called a module - a payment module that contains only one microservice.
However, our B2B online store can use the advantages of Composable Commerce here - if an additional payment method is needed, the microservice can be easily activated and customized via the PIM system, without a big cost or time investment.
It is precisely because of this tremendous flexibility and the low-cost technology that supports it that Composable Commerce is the seminal strategy for online commerce.
Learn about the other benefits of composable commerce and PIM systems in the following articles: