In brief The cost of an ERP project in 2026 is not limited to the licence: it includes scoping, configuration, data migration, internal team time and recurring running costs. The Odoo licence is the only public, readable price; the other four line items are defined by the actual project scope. A structured framework allows you to anticipate the full picture before signing.
A business leader receives a proposal. Three lines, a table, a total. The licence is in bold; the rest is vague. They sign. Six months later, they discover line items they had not seen. This scenario is common. It has nothing to do with anyone acting in bad faith: it comes down to the way an ERP project naturally organises itself around the one price that can be read without effort.
This article gives no integration cost ranges. It gives you a framework. You apply it to your own situation. The cost of an ERP project does not come down to a single line on a quote.
The analogy that holds all the way through
Buying a car means reading a list price. But driving means paying for insurance, maintenance, fuel and servicing. The brochure told you how much the car costs. It did not tell you how much it costs to drive it.
An ERP project works in exactly the same way. The list price is the licence. The insurance, maintenance and fuel are the other four line items. Keep that image in mind through to the conclusion.
Licence, scoping, configuration, internal time, running costs
The licence is the displayed price. It is the publisher's price, not the integrator's. Odoo offers its Custom plan at €35.90 per user per month in the first year, then €44.90 from the second year onwards, covering all applications, multi-company and external APIs (Odoo pricing grid, 2026, Odoo pricing details). This price is clear, public and verifiable. That is precisely why it is the first thing compared. And that is precisely why it is not enough.
A useful note on Odoo 20: the version automatically classifies each user as a Light or Standard profile based on actual usage (verified by ANOR in the source code, internal note dated 5 October 2026). Before counting the licence cost, map out your users' profiles. The total can vary considerably.
Scoping comes before configuration. It includes a review of your management processes: how you purchase, sell, manage stock, invoice and report. Half a day reviewing processes before any proposal is drawn up avoids discovering the project scope mid-way through. Without it, the scope grows after the contract is signed. Organisation consulting is independent of Odoo: it serves businesses looking to clarify their processes, whether or not they have an IT project under way.
Configuration and data migration are measured in days. Workflows, business rules, documents and access rights all need to be set up according to your organisation. Data migration is a line item in its own right: products, customers, suppliers, history, accounting balances. Each piece of data migrated requires mapping, cleansing and checking. Our internal framework groups this work into two families: on one side recurring costs (licences, hosting, maintenance of specific developments and third-party applications); on the other, implementation costs counted in days (project launch, standard implementation, customisation, specific developments, integration, data migration and training).
Internal time is the line item nobody writes down. Your teams take part in the project: they answer the consultant's questions, test scenarios, validate configurations and train their colleagues. This time is real. It appears in no integrator's proposal. User training is part of it. To continue the analogy: internal time is learning to drive. You do not buy it from the dealer, but you pay for it all the same.
Running costs are the everyday fuel. Hosting, support, upgrades and connectors to third-party tools: these costs are recurring. Odoo 20 is the current version. Odoo 17 has not been supported since it was superseded. Staying on an unsupported version is possible on a dedicated server but not on Odoo.sh. Upgrades are part of the running cost, not an exception.
What 2026 shifts in the equation
E-invoicing changes the structure of accounting work. According to the practical guide published on impots.gouv.fr (2026), receiving e-invoices becomes mandatory for all businesses on 1 September 2026. Issuing them becomes mandatory on the same date for large companies and mid-sized businesses, then on 1 September 2027 for SMEs and micro-businesses.
This obligation does not create a new line item in your ERP budget. It shifts time from manual entry to control and verification. Manual input decreases. Vigilance over incoming flows increases. To continue the analogy: 2026 does not change the price of insurance. It changes the route. Fuel is consumed differently.
The question to ask before signing
Before comparing two proposals on the licence line, ask this question: "Which line items are not included in this proposal?"
Thorough scoping answers that question before the contract is signed. It names the scope, maps user profiles, identifies data to be migrated and estimates the internal time required. Without this step, you are comparing list prices. With it, you are comparing projects.
We are ready to go through this framework with you, line item by line item, applied to your real situation. Book 30 minutes with an ANOR consultant: it is the most useful starting point before any decision is made.