What does an Odoo implementation cost?
The honest answer is: it depends. The dishonest one would be a number. What can be said cleanly is what the cost is made of and what drives it up or down — so you can judge the order of magnitude to plan with before talking to anyone.
The five items
Two of them are monthly, three are one-off. Looking only at the licence is the most reliable way to get it wrong.
1. Licence
recurring, per user per monthOdoo Community is free — the edition is licensed under the LGPLv3 and free to use. Odoo Enterprise is billed per user per month, with a surcharge for individual apps. What drives the bill is the number of users, not the number of modules: twelve modules for eight people cost less than three modules for thirty.
2. Hosting & operations
recurring, monthlyServers, updates, backups, monitoring. Three routes: the Odoo cloud, your own servers, or a partner. We run Odoo on German infrastructure. This is the smallest recurring item and the one where saving money most reliably backfires — a backup nobody ever tested is not a backup.
3. Implementation
one-off, largest itemProcess mapping, concept, configuration, testing, go-live. In almost every project the largest block — and the only one you control yourself. It grows with the number of modules, with the number of departments involved, and above all with every deviation from the standard.
4. Data migration
one-offMaster data, products, stock, open items. The effort depends on the state of the legacy data, not its volume. 20,000 clean products move faster than 800 spread across three spreadsheets with three different spellings.
5. Training
one-off at launch, then as neededThe item most often cut. And the one that takes revenge fastest: a system nobody can operate properly gets worked around — and then the old spreadsheets keep running, only now on top of the ERP licence.
What drives the price up
- Every deviation from the standard. It costs twice: once to build, and again at every version upgrade.
- Unclear processes. Whatever is undecided internally gets decided during the project — at project rates.
- Many departments with a veto and nobody who decides.
- Legacy data nobody wants to clean up but everybody wants to keep.
What brings it down
- Stay in the standard wherever possible. Odoo does more than most companies initially use.
- Roll out in stages instead of all at once. Two modules that work beat eight that are half-configured.
- One person in-house who carries the project and is allowed to decide.
- Clean up before migrating. An ERP rollout is the cheapest moment for that you will ever get.
Three orders of magnitude
Not as a price tag, but as a way to locate yourself: which of these three situations are you in?
Lean start
One company, one or two areas — sales and invoicing, say. Few users, standard without exceptions, manageable master data. The rollout stays a matter of weeks, not months.
The mid-market norm
Sales, purchasing, inventory and accounting interlock, plus a legacy system to migrate from. Several departments are involved, some workflows need adapting. Here the groundwork decides the cost.
Manufacturing & multi-site
As soon as manufacturing, bills of materials, multiple warehouses or sites come into play, the rollout becomes a genuine phased project. Not different software — a different order of magnitude.
Common questions about cost
Why is there no price list here?
Because an Odoo implementation is not a product off the shelf. The licence can be looked up, but the implementation — the largest item — depends on your modules, your processes and the state of your data. A number named without that context would be revised in the first call, which helps nobody. What we can do is make the items transparent, which is what this page is for.
What is the cheapest way to run Odoo?
Community, self-hosted, in the standard, with someone in-house who knows it. That genuinely works and costs nothing in licences. The bill arrives elsewhere: you carry updates, backups and upgrades yourself, and you have no support to call. For many small operations that trade is worth it; for most it is not.
What does a version upgrade cost?
In Enterprise the upgrade is part of the licence. The work is not in the standard but in your customisations: the more exceptions carved into the standard, the more expensive every upgrade gets. That is the real price of a special request, and it comes due years later.
Can we start small and grow?
Yes, and it is usually the cheaper route. Modules are activated individually, users are added as needed, and Community and Enterprise convert in both directions without losing data. Starting with two modules that actually work beats eight that are half-configured.
What is commonly forgotten in the calculation?
Three things: the time your own team spends on the project, the training, and the cleanup of legacy data. None of them appear on a vendor quote, and all three decide whether the rollout works.
The order of magnitude for your case
In the first call we walk through the five items for your business. You leave knowing what to budget for — even if you decide against us.
