Customization in Odoo can be a good solution if it truly adds value to your business. Sometimes it is even necessary. But customization also brings costs for maintenance and future upgrades. Therefore, our advice is: first investigate whether you can achieve the same result with standard Odoo and a different setup of your processes.
In 2012, I founded Odoo Experts. Since then, together with my team, I have developed hundreds of Odoo custom apps. When we created those modules, the client and I were convinced that the adjustments were indispensable. They were all 'must-haves'. Many clients are happy with Odoo, but now view part of that customization differently. Was creating it always such a good idea?
Nobody wants custom development, right?
At by far the most companies we visit, we hear the remark: “We are going to use the software completely standard. We do not want customization.”
That desire often stems from costs. And saving costs with the help of ERP software, that is exactly our job. So if it can be standard, without incurring customization costs, then we are all for it.
But can a company operate without customization? To what extent has research been conducted into the processes and the software required for them? Can the processes be accommodated in the standard software? And is the software flexible enough to adapt to the needs and wishes of the end users?
Many companies cannot yet answer these questions. A thorough preliminary study is needed before the actual ERP implementation begins. Part of this is a GAP analysis, which describes the differences between the business processes and the software. For each difference, you then determine which solution fits best.
Customization can be a good solution for such a difference. But sometimes there are also other possibilities that allow you to avoid customization. Make sure to get well-informed about this and weigh the options.
What is custom development?
Customization is software developed for a specific purpose or a specific client. In the case of Odoo, for example, it involves an app that expands standard functionality or adjusts its operation.
That does not mean that the source code of Odoo itself must be overwritten directly. Developers can also create a separate module that connects to the standard software and adds functionality to it.
Many modern ERP systems also have tools that allow you to customize and extend software. Odoo has, for example, Odoo Studio. Because you use features that Odoo itself provides, it is not always referred to as customization. Nevertheless, you also make adjustments that need to be maintained and can have implications for future upgrades.
What are the advantages and disadvantages of custom development?
Customization has, like everything, advantages and disadvantages. Advantages can include:
The software aligns better with business operations.
You can create a solution for a process that distinguishes you in the market.
You can link systems and thus reduce manual work.
You can support users with functionality that is missing in standard Odoo.
You do not always have to wait for a new version from the supplier for a desired extension.
Customization also has disadvantages:
The costs of development and maintenance are yours.
Specific customization does not automatically evolve.
Knowledge of the customization is often present in a small group of people.
During an upgrade of Odoo, the customization must also be assessed and possibly adjusted.
Customization can make an upgrade more complicated if functional or technical limitations arise.
Therefore, the most important thing is not how much customization you make, but which problem you solve with it and what that yields.
What possibilities are there for customization in Odoo?
Odoo is open-source software and suitable for customization and extension. Developers around the world create apps for Odoo. Customization is somewhat in the DNA of Odoo, but the question remains: is that really such a good idea?
There are various ways to customize or extend Odoo. Each of those possibilities has its own advantages and disadvantages.
Customization via Odoo Studio
Odoo Studio is a tool that allows you to customize and extend Odoo without conventional programming. In conventional customization, code is written as an Odoo app, which then needs to be installed on the Odoo server. That is not necessary with a customization via Odoo Studio.
So can anyone create custom development with Odoo Studio? No, that is not a good idea. Even through Odoo Studio, you come into contact with technical aspects of software. It requires (technical) knowledge of Odoo to use Odoo Studio properly. If someone does not really know what they are doing, they can truly break Odoo.
Odoo Studio can be a tool for small adjustments and extensions. But think ahead when using it and do not combine Odoo Studio with conventional customizations. This leads to unforeseen problems.
Customization via development
Customization in Odoo often means developing Odoo apps. With these apps, or modules, you can extend Odoo or adjust its functionality. A developer is needed for development, and for conventional custom modules, you rely on Odoo.sh or your own hosting.
With customization, you can for example extend business logic, create connections with other systems, or add new functionality. An Odoo app is integrated into the environment, so the end user does not always see whether a feature is standard or specially developed.
The technical possibilities are vast. That does not mean that every desired adjustment is also wise. Every module must be maintained and continue to work with future changes in Odoo.
Customization outside Odoo via the API
It is also possible to keep customization outside of Odoo. The extra functionality then reads data from Odoo via the Odoo API and can, if necessary, also write data back. Examples include connections with carriers or e-commerce platforms.
One advantage is that the solution can be developed and managed outside of Odoo. However, there remains a dependency on the API and on the data and functions that the connection uses.
With a new Odoo version, you must therefore check whether the connection still works properly. Sometimes adjustments are necessary, for example because the API or the used functionality has changed. How much work that is depends on the connection and the transition you make.
More information can be found in the documentation about the Odoo API. That link refers to the development version of the documentation. Always use the documentation that corresponds to your Odoo version for technical choices.
What is the impact of AI on custom development?
AI makes developing custom solutions easier. A developer can use AI, for example, to analyze existing code, create an initial draft for a module, or assist in writing tests. This can save time and make it easier to explore different solutions.
But writing code is only part of custom development. First, it must be clear what problem you want to solve, how the business process works, and what the implications of a modification are for other parts of Odoo. Someone must also assess whether the solution is safe, maintainable, and suitable for future upgrades.
AI can assist in creating custom solutions, but it does not independently determine which customizations are wise.
Functional knowledge, practical experience, and human oversight remain necessary for that. A solution may work technically but still not fit the way your business operates. Or it may solve a problem that could have been avoided with standard Odoo.
AI does not reduce the need to critically examine custom solutions. It makes the question why you want to make a change at least as important as the question how you build it.
Can you use an app from the Odoo App Store?
Odoo has a large App Store. Developers can offer both free and paid apps there. If you are looking for functionality that is missing in standard Odoo, an existing app may seem like a solution.
However, there is a major downside: there is no quality control on the apps in the Odoo App Store. Therefore, you must carefully assess what you install. For example, look at the quality of the code, the support from the creator, the availability for new Odoo versions, and the compatibility with other apps.
Why did we stop using apps from the Odoo App Store?
Odoo apps are not always compatible with each other. Individual apps may work fine, while they cause problems together. This can happen, for example, when two apps modify the same screen and make different assumptions about the available fields.
An app from the App Store can be cheap and quickly available. But the same applies to that app: you are dependent on maintenance, support, and future upgrades. So keep in mind: an app from the Odoo App Store is also a form of customization.
When is customization a good idea?
Customization is not always a choice. Sometimes an adjustment is necessary to properly support an important business process. But if customization is a choice, our advice is to avoid it when standard Odoo offers a workable solution.
Our experience is that customization is often used for a temporary problem. This is often because the operation of the new software is not yet well known and is compared to functionality from the previous software package.
Suppose a user misses a button that was present in the old system. Then it is wise to first investigate whether the same result can be achieved in another way in Odoo. Perhaps the button turns out to be unnecessary after some experience with the new process.
It is different when an essential step in the business process cannot be executed or when a necessary link is missing. In that case, customization may indeed be necessary from the start. The consideration revolves around the consequences for the company, not whether a desire resembles the old way of working.
We also regularly encounter a form of 'over-automation'. An end user actually wants the button that does everything and tries to increase efficiency at a micro level. Customization is rarely a good solution for that.
How do you make a good choice?
Based on our experience, we give you the following tips:
Carry out a GAP analysis to determine where the gaps between the company and the software are.
Only opt for customization if it demonstrably adds value for the company.
Let employees gain experience with the software first where possible and reassess the desire afterwards. Three months can be a useful guideline, but necessary customization does not always have to wait that long.
Look at the business interest and not just at the interest of each individual employee.
Set aside a budget for maintenance and future migrations.
Be critical of third-party apps if quality, support, and compatibility are unclear.
Ensure that knowledge and support for the customization are also secured in the long term.
Customization can be a good investment. But only if you know what problem you are solving with it, what it yields, and what is needed to continue using the solution.