Why does a successful ERP implementation start with understanding processes rather than software?
An ERP project does not start with configuring software, or at least, it shouldn’t.
Looking back at our recent Odoo implementations, one pattern keeps emerging: the more challenging questions often have less to do with the software itself and more to do with understanding how the company actually operates.
In a manufacturing company, this can mean asking very specific questions. What is the final product made of? Which semi-finished products are produced along the way? What production stages are involved? Where is the material located at each stage? How does production-related data move through the company, and how is the actual cost of the final product ultimately calculated?
When a company’s day-to-day operations need to be analysed and described step by step, things that may previously have gone unnoticed often start to become visible. Quite often, this gives the company something very valuable even before the new system goes live: a better understanding of its own business and processes.
In one recent implementation, we worked with the client to map out multi-level recipes, finished and semi-finished products, and the entire flow of production operations. Once the process had been clearly defined, it could be built using standard Odoo functionality, with virtually no custom development required.
In another project, the situation was completely different. The company’s project-based manufacturing did not use traditional BOMs, and the standard manufacturing logic did not reflect the way the company actually operated. The solution therefore had to be built differently, connecting projects, material movements, and a custom solution developed specifically for the company.
At a third manufacturing company, a single finished product can involve as many as ten semi-finished products before completion, moving between different production locations. Here, too, the challenge was not simply implementing a manufacturing module, but understanding the entire production logic and bringing it into the system as a coherent whole.
Three different companies, processes, and solutions.
But the common denominator is the same. Before deciding how something should be handled in Odoo, you first need to understand how the company actually operates. And quite often, this process leads the company to another question: is the way we work today really the most sensible way to do it?
This, in turn, creates an opportunity to make future workflows more efficient.
ERP implementation should not mean transferring existing ways of working into a new system one-to-one. A well-executed implementation provides an opportunity to look at business processes with fresh eyes, understand them better, and only then decide what should be retained, what can be simplified, and what should be done differently.
A successful ERP implementation does not start with configuring software. It starts with understanding the business.