How much does Odoo cost? It is the first question every Geneva business considering this management software asks, and it is also the question no serious page can answer with a single figure. Odoo prices change according to first-year promotions, the billing method, the currency and the plans available; a fixed amount stated on a web page becomes wrong without anyone noticing, until the day a client relies on it. This page therefore gives no price. It explains the cost structure: what makes up an Odoo bill, what makes it vary, and how to build a budget that holds up. This is the question you need to know how to ask before requesting a quote, as part of our Odoo ERP support.
The three cost blocks that get systematically confused
The most common confusion is comparing the price of an Odoo licence to the price of another management software, forgetting that the licence is only one of three spending items. There are three, of very different natures:
- The vendor licence: what you pay Odoo S.A. to use the software, potentially nil if you stay on Community.
- The set-up project: the scoping, configuration, data take-on and training work needed for the software to match your business. This is a one-off cost, generally the most significant of the three for an SME.
- Annual running costs: recurring licence, hosting, support, version upgrades, future developments.
A well-built Odoo budget accounts for all three. Looking only at the first, as almost every quick software comparison does, gives a false picture of the real cost.
The Odoo licence: Community or Enterprise
Two editions, two logics
Odoo exists in two distinct editions. Community is free and open source: the code is public, installation costs nothing in licence fees, and it covers a broad functional core. Enterprise is paid, billed per user per month, and adds modules and services that Community does not have, including certain advanced Swiss payroll functions. Odoo 19 is the current stable version of both editions.
The Standard and Custom plans
The Enterprise edition itself comes in several plans, including Standard and Custom, which differ in functional scope and the terms of access to customisation. The choice of plan depends on your needs: number of applications used, need for bespoke development, level of support desired.
What makes the licence bill vary
For the same plan, the bill varies according to the number of users, the billing method chosen (annual or monthly), and the first-year promotions Odoo sometimes offers. These parameters change regularly. The only up-to-date source is the official odoo.com/pricing page: that is where, and only where, you should check the price at the time you are budgeting, not in an article written months earlier.
Hosting: Odoo Online, Odoo.sh or your own servers
Three hosting options coexist, with different implications for cost and technical constraints.
- Odoo Online: hosting managed by Odoo, with no technical administration on your side. The simplest choice for an organisation without a dedicated IT team.
- Odoo.sh: a more technical hosting platform, designed for projects with bespoke development, several test environments and a structured deployment cycle.
- Installation on your own servers: full control of the infrastructure, but technical responsibility and maintenance entirely on you or on a dedicated provider.
The choice is made according to your compliance constraints, your internal technical appetite and the nature of your project, not a default preference. This is generally decided during scoping, in connection with our implementation offering.
The set-up project: what it really covers
This is the item most often underestimated, even though it generally represents the bulk of the total budget for an SME. An Odoo set-up project covers:
- The scoping: identifying the processes to cover, the priorities, the scope of the first phase.
- The configuration of the modules chosen according to your organisation.
- Swiss localisation: Odoo automatically installs the l10n_ch module as soon as the company is configured in Switzerland, but its fine-tuned configuration for your sector remains project work.
- Take-on of existing data: customers, suppliers, items, accounting history.
- Any bespoke development, where the standard does not cover a particular business need — see our Odoo development offering.
- Integrations with other software already in place (e-commerce, bank, till, business tools).
- Testing before going into production.
- Team training, covered in detail on our Odoo training page.
- Start-up support, in the weeks following go-live.
Each of these items can be reduced or extended depending on the scope chosen; this explains most of the budget gap between two apparently comparable Odoo projects.
What really makes a project's budget vary
Beyond the licence, it is the project's characteristics that determine the scale of the work, and therefore the cost:
- The number of modules deployed at the same time.
- The complexity of the business processes to reproduce or develop.
- The volume and cleanliness of the data to take on: clean data is taken on quickly; scattered or inconsistent data requires preliminary clean-up work that is often underestimated.
- The number of entities and currencies to manage, for multi-company structures or those with international activity.
- The presence of stock or production, whose management logic is more demanding than a pure service activity.
- Payroll, where it is part of the scope — Odoo is listed on the Swissdec register at the swissdec certified basic level (certificate no. 1203.25, ELM 5.3 standard), but advanced Swiss payroll functions fall under the Enterprise edition.
- Bespoke development, which adds design, testing and future maintenance time.
- The number of interfaces with third-party software, each requiring its own design and testing.
Two businesses of the same size can have very different project budgets depending on the combination of these factors. This is why a serious quote always starts with scoping, never with a remote estimate.
Annual running costs
Once the project is delivered, Odoo generates recurring costs to include in the operating budget:
- The Enterprise licence, if chosen, billed periodically according to the number of users.
- Hosting, according to the option chosen among Odoo Online, Odoo.sh or your own servers.
- Support, for day-to-day assistance and incident resolution — detailed on our Odoo support page.
- Version upgrades, needed to stay on a version maintained by the vendor, covered by our migration offering.
- Further developments: new modules, process adjustments, new business needs arising after go-live.
This block is often absent from early discussions, even though it weighs on the total cost over time far more than the initial project.
How to reduce a project's cost, honestly
There are real levers for controlling an Odoo budget without degrading the quality of the result:
- Reduce the scope of the first phase to the genuinely priority processes, and postpone the rest to later phases once the foundation is stable.
- Prepare your data in advance rather than discovering its condition during the project: a customer file cleaned up before the start saves considerable time.
- Appoint an internal point of contact who centralises decisions and avoids scattered back-and-forth between several people.
- Avoid premature customisation: requesting bespoke development before testing whether the standard is enough often leads to paying for a feature that already existed.
- Use the standard Odoo wherever possible: every departure from the standard adds design, testing and maintenance time at every future version upgrade.
These choices are not shortcuts that sacrifice quality: they protect it, by concentrating effort where it matters.
Miscalculations to avoid
Certain reasoning errors come up repeatedly when a business budgets an Odoo project:
- Comparing licence to licence, forgetting the set-up project. The entry price of a piece of software says almost nothing about the total cost of a functional deployment.
- Underestimating data take-on. Incomplete data scattered across several files requires preparation work that can weigh more heavily than the configuration itself.
- Forgetting the cost of internal time. The time your teams spend on testing, validating processes and training has a real cost, even if it appears on no external invoice.
How AX-Fiduciaire builds an estimate
As a Geneva-based fiduciary and official Odoo partner, we build an estimate from concrete elements, not a market average. For a quote to make sense, we need to know: your business and its current organisation, the number of users involved, the processes you want to cover as a priority, the state of your existing data, the software Odoo will need to communicate with, and any regulatory or sector-specific constraints. On this basis, we define a realistic first-phase scope, consistent with your budget and operational priorities. Our support in Geneva is detailed on the Odoo in Geneva page.
The concrete first step is simple: a request for a quote, in which you describe your situation. That is when a coherent estimate becomes possible — never before.