“Headless” Commerce vs. Traditional Commerce
Headless ecommerce allows you to decouple the business logic of the sales process from the implementation of the user interface (UI). But it's important for business people to decide if headless architecture is needed for their new ecommerce project.
Yes, for a new business idea, you can create an application from existing software. Headless architecture helps in the case of a new project to take existing components, in this case applications from the market, and use them to create a unique new product.
Take Lego as a reference and integrate ERP, PMI, front-end, and other applications into the ecommerce system so that customers can get acquainted with your product and buy it. Create a flexible UX (or user experience) by extending your business idea with different applications so that they work together to get the customer to click the “buy” button. Headless architecture allows for experimentation.
Otherwise, you need to duplicate all business logic for all types of front ends used or, in other words, touchpoints (e.g., website, mobile app, messenger). This is expensive to develop and can lead to chaos when the business rules are implemented separately at different touchpoints.
Imagine the chaos of your sales team if, for example, the website has changed and updated these rules, but not at other touchpoints, so customers get confused about different catalog versions and prices.
Headless seems to have been created precisely to support the principle of omnichannel sales. It is better to stick with no head; otherwise, the omnichannel may be broken when the synchronicity of the catalog of goods, prices, and stocks is disrupted, and different channels may not coincide with or may even contradict each other.