Category
11 articles in Composable Commerce
For many years 'no code' and 'low code' have been pitched as the answer to the integration problem. The promise has been simple: no developers, no code, just draw a few arrows between systems and everything is solved. Read on to see why 'much code' is a better option.
Price changes in e-commerce are often planned in advance and scheduled: either a change to the list price or a campaign price that takes effect on a specific date. Getting every system to show the new price at the right moment is a harder challenge than you might think, and in this article we walk through how to solve it with Nexus.
Syncing data between your e-commerce system and your search engine is something every e-commerce operator faces when they want an external search engine like Algolia, Voyado Elevate, Loop 54 or similar. In this article we walk through how to build that sync using Commerce Mind's tool Nexus.
Commerce Mind Nexus is a free framework we have built to help our clients improve their background processes and data flows, but above all to give visibility and control over them to non-technical people.
Interest in composable and headless architecture for e-commerce solutions has grown enormously in recent years. Composable offers many benefits but also comes with costs that are often not talked about. In this article I want to give a balanced view of the pros and cons of the different paths available when you shape your systems landscape.
'Go headless, and the hard part is solved.' A claim I have heard many times in recent years. The freedom to pick isolated systems that fit your specific needs, that can be swapped out, that can scale, where you pay only for what you use. It sounds like a dream. But if it really is that simple, why is not everyone doing it?
For quite a few years it has been a natural aspiration for ambitious e-commerce operators to move towards a best-of-breed architecture, adding more and more SaaS services. But with a weaker economy, post-pandemic conditions and high interest rates, more players are starting to focus on operational efficiency and cost.
As the various systems used in digital commerce become more capable, the complexity of deciding where information and logic should sit only increases. The most common systems in use today for retail and e-commerce were built at a time when things were more isolated. So how should you think about it today?
Keeping accurate stock levels for your items across all systems is a harder problem than it might first appear. How much revenue are you losing because you do not dare trust your own stock levels and always keep a buffer to be on the safe side?
Is your company also chipping away at an RFP or RFI with a hefty Excel list of requirements attached? Then you are far from alone, and this article is for you. After reading and answering a great many procurement documents, I have a good sense of what the process looks like and how little it has changed over time. Today the process is set up so the platform and vendor can build their answers based on your requirement list and wishes, which you have been kind enough to share with a selection of platforms and partners.
The more complex the e-commerce world becomes and the more systems are involved, the more important it is to have control over your data. Above all, that the data is accessible. The more systems you have, the less likely it is that your data is actually accessible. So how do you make it accessible?
