
Buying Odoo
- Author
- Clovis de Bontin
- Published
- 6 November 2026
- Reading time
- 7 min read
Configure Odoo first, build a custom module only if you must
Standard apps are the right default. A custom module is the right answer when a process the business cannot drop is absent from the apps you are buying. The mistake is to custom-build a preference, or to refuse a module the process actually needs.
Custom work is scoped on custom software and apps. The implementation itself is configuration, data and training.
Start with the process, not the code
A custom module is a maintenance obligation with a user interface. Before anyone opens a code editor, ask the person requesting it to name the screen, the data and the decision the module changes. If they can name all three, the request is a requirement. If they cannot, it is a preference wearing a requirement's clothes.
This is not a way to say no. It is a way to separate a process the business depends on from a habit the business has not examined. The first deserves a module. The second usually deserves a configuration change and a week of use.
What configuration can close
Standard apps go further than many buyers expect. Fields, views, approvals, automated actions, print templates, access rules and reports can all be configured without a line of custom code. Odoo Studio can add fields and simple automations inside the database.
Configuration has limits. It is weaker when the change is structural, when a screen must behave differently for one team, when a calculation has to run across a large data set, or when the upgrade path must stay clean. A configuration that bends a standard model too far can be harder to maintain than a small module that extends it properly.
When a module is justified
There are four honest reasons to build. A legal, safety or customer requirement that the standard app does not meet. A two-way integration where a file export would be abandoned within a month. A screen or workflow the standard app simply does not have. A volume or performance need that configuration cannot carry.
Each reason has a test. For a legal requirement, name the rule and who enforces it. For an integration, name the system on the other side and who owns its API. For a missing screen, draw it and name the person who signs it off. For performance, bring the record count and the query that is slow.
The cost that starts after go live
Custom code adds a maintenance obligation. Someone has to own the module, test it on the next Odoo release, and decide what happens when the original author is unavailable. That is true whether the module is ten lines or ten thousand.
Hosting decides part of the answer. Odoo Online does not allow arbitrary custom modules, so a module means odoo.sh or another host. If the business has chosen Odoo Online for its simplicity, a custom module is a hosting decision as well as a development one.
How to decide in discovery
- 01Write the process step in one sentence, in the operator's words.
- 02Show where standard Odoo stops, with a screen or a test, not an opinion.
- 03Name the person who will own the module after go live.
- 04Ask what happens on the next Odoo upgrade if the module is not maintained.
- 05Compare the module against a process change, a configuration, or a small integration.
If the module survives those five questions, build it. If it does not, the scope has saved the business a maintenance cost it did not need to take on.
I sincerely hope this was helpful, and if you have any remark, suggestion or question, you can email me at louis@cdb.solutions or DM me on LinkedIn.
Thank you,
Clovis
Next step
See this in practice
Book a free demo. The technical partner for your country shows the apps that fit, at no charge.
Canonical URL: https://www.cdb.solutions/articles/odoo-standard-or-custom
FAQ
Answers to the questions this article raises
The questions buyers ask most, answered here. If yours is not covered, ask us directly.
01Can custom modules run on Odoo Online?
02Who owns the module?
03Is Odoo Studio a substitute for a module?
Next step
Book a free demo
Tell us the country and the operation. The technical partner for your country shows Odoo against your process, at no charge.
+33 7 69 45 83 27UK with SofthealerEverywhere else with AppNvent
Free demo
Put this against your own operation
Country, industry and company size. The technical partner scopes the work and holds the agreement.
Country chooses the partner. The UK is implemented with Softhealer. Everywhere else, with AppNvent.
The demo is specific. Industry and company size tell the technical partner which apps to show you.
No charge, no obligation. Scoping and any agreement come later, and only if you want them.
