An overview of Odoo, the open-source ERP

What Odoo is

A widely used open-source suite of business applications.

Odoo (formerly OpenERP) is an open-source suite of business applications developed by the Belgian company Odoo S.A. It is feature-rich and strong on usability, extensibility, and maintainability, and is cost-effective relative to comparable systems. Its coverage extends beyond a traditional ERP's scope into CMS, e-commerce, event management, helpdesk, and more. With multi-currency and multi-language support, it suits use not only in Japan but across overseas locations.

Odoo is made up of a database server (PostgreSQL), an application server (written in Python), and a web client (JavaScript). Users do not need to install any special software on their computers — Odoo is operated from an ordinary web browser. It can be run in the cloud (Odoo's own SaaS, or other providers' cloud services) or on-premise.

Odoo reports more than 28 million users worldwide as of 2026, and service providers that support implementation and operation exist in most regions. Some of these providers take part in open-source activity — community-based bug fixing, feature development, and localization — and the Odoo ecosystem is underpinned by these contributors.

Product philosophy

High modularity and rapid evolution.

Where many ERP products (such as SAP) try to anticipate every business pattern and build by parameter configuration, Odoo meets requirements through extension — by adding modules. Its modularity is high: models and field definitions, business logic, views, and most other data can be extended through customization. The core (standard functionality) is therefore kept simple, and there are many different ways to address a specific need.

Given that character, Odoo S.A. has so far tended to prioritize cross-process integration and usability over data robustness, and speedy evolution over product stabilization. As a result, each annual release brings substantial improvements — but a release can also be more prone to bugs in the period right after it ships. Planning for periodic upgrades is part of owning Odoo, a point this page returns to under the product lifecycle.

What Odoo covers

All of these functions integrate on a single Odoo platform.

Odoo is an integrated business system spanning virtually every operational area — sales, inventory, accounting, project management, HR, e-commerce, and more. Where an organization runs systems adopted piecemeal by division or department, or single-purpose SaaS tools that are not connected — leading to scattered account management and rising costs — Odoo can manage all of it in one place, which can deliver:

• Seamless data flow between business processes
• Simpler account management
• A substantial reduction in running costs

Industries and areas it fits

It serves most industries and operational areas.

Odoo is a business-application suite with the flexibility and extensibility to serve a wide range of industries — manufacturing (assembly, process, food), retail, wholesale, services, information and communications, insurance, transport, and more. A large body of community open-source modules is published, and by developing or customizing as needed, Odoo can meet most business requirements. That said, adoption can be relatively difficult in the following cases:

Odoo in Japan

Long under-served — now improving quickly.

Odoo's global growth was built on an English-first, self-serve, community-localized approach. Japan is a market where that approach needs real adaptation, for reasons that face most overseas business software:

None of these is a total block, but each one demands local depth, and for years much of the gap has been filled by the open-source community rather than by Odoo S.A. The outlook has been improving on three fronts:

Community and Enterprise

There is a Community edition and an Enterprise edition.

Since version 9.0, Odoo has been split into a free Community edition and a paid Enterprise edition. Enterprise consists of the open-source Community edition plus a set of proprietary modules — an open-core model. This structure is worth understanding first, because Odoo's licensing, pricing, and customization options all follow from it.

The Community edition can be obtained from the following:

• Nightly builds: nightly.odoo.com
• The Odoo repository on GitHub: github.com/odoo/odoo

The Enterprise edition is a paid subscription that adds proprietary apps and features and vendor support on top of everything in Community. The cost and feature differences are summarized in the next section.

Software cost

Free (Community) or reasonably priced (Enterprise).

The Odoo Community edition is fully open source (LGPLv3), so anyone can download the source code and use it freely. Odoo's official pricing page covers only the Enterprise edition, so the table below summarizes both together. Enterprise prices are shown per user per month; the discounted figure in parentheses is Odoo's new-customer discount, valid for the first 12 months.

On-premise refers to an Odoo environment you host yourself or through a service provider. Odoo's helpdesk is not available in Japanese, so in practice a partner relays support. List prices as published by Odoo, June 2026; confirm current figures before budgeting.

Open-source licensing

The Community edition is licensed under LGPLv3.

The Odoo Community edition is licensed under LGPLv3. When the editions split into Community and Enterprise at version 9.0, the Community edition that carried on from version 8.0 had its licence changed from AGPLv3 to LGPLv3.

LGPLv3 is compatible with GPLv3 and AGPLv3, and a proprietary program is permitted to depend on an LGPLv3-licensed program. Adopting this licence let Odoo move to an open-core business model and made it possible to sell proprietary modules on the app marketplace. Odoo is sometimes described as "licence-free," which is not accurate: an open-source licence applies, and it must be used correctly in accordance with that licence.

What may build on what

Everything runs on the LGPLv3 core, and any module — open source or proprietary — may build directly on it. One level up, each module's licence decides what may extend it: LGPLv3 community modules accept proprietary extensions, while AGPLv3 community modules do not.

The Odoo Community Association

The largest open-source ERP community in the world.

The Odoo Community Association (OCA) is a nonprofit organization that promotes collaboration among community developers worldwide in building and maintaining features that complement Odoo. Odoo S.A. drives the development of the core product, while the OCA sustains complementary modules that reflect the needs of the countries and industries its members work in — together they underpin the Odoo ecosystem.

Programs managed by the OCA carry one of the open-source licences recognized by the Open Source Initiative; most modules are released under AGPLv3 or LGPLv3. The OCA's workflow builds in strict code-style checks and review steps, so modules maintained under the OCA are generally consistent in quality. As of October 2024, more than 2,200 OCA modules were available for v16.

Leaning on standard and OCA modules where possible keeps a deployment closer to the upstream codebase, which makes upgrades and long-term maintenance easier than carrying large amounts of private custom code. Choosing an implementer who coordinates with the OCA rather than working only in private repositories is one practical way to keep that advantage.

Product lifecycle

Periodic version upgrades are expected.

In recent years Odoo's major versions have been released once a year, timed to the "Odoo Experience" event held each autumn. The current release is Odoo 19, released in October 2025.

Under the July 2025 Enterprise terms revision, Odoo S.A. now supports all versions (previously only the latest three); at the same time, using a version older than the latest three incurs an additional charge of 25%. In practice the latest three major versions — at present Odoo 17, 18, and 19 — receive standard support, while older versions are supported at extra cost.

When you want to upgrade your Odoo to a newer major version, Enterprise users can use Odoo S.A.'s database conversion service. Community users will, in practice, want to consider upgrading with the community-supported OpenUpgrade.

Version history

Choosing an edition

If in doubt, try the Community edition (CE).

The decision comes down to two questions: "are the features I need present?" and "do I need Odoo S.A.'s support?" If you cannot decide, it is reasonable to try Community first and consider switching to Enterprise if it falls short — switching later is possible.

Are the features you need present?

Check whether features exist for the business scope you want to cover. If the scope includes areas such as Accounting, Marketing Automation, or IoT, Enterprise is worth considering. If the scope is areas like Sales, Purchase, and Inventory, Community is often sufficient on functionality alone.

Do you need Odoo S.A.'s support?

Choosing a version

Decide by understanding the trade-offs of each.

Odoo gets faster and more usable with each version, so on that score the latest version has the edge. On lifecycle grounds the newer version is also preferable, since it is supported for longer. On the other hand, older versions tend to have fewer core bugs and a fuller set of OCA modules available.

If you prioritize the richness of standard features and are willing to spend some time and cost building what is missing (bringing community modules up to the latest version), go with the latest version. If, when a need arises that standard features cannot meet, you would rather use existing community modules for a lower-cost, faster build, an older version (one release back) is the better choice.

The partner system

Evaluated mainly on licence-sales results.

Odoo S.A.'s partner programme exists to spread Odoo across the world's markets by working with providers who know Odoo and local conditions. Because implementing and operating Odoo takes specialist expertise, a user company adopting Odoo entirely on its own is often impractical; relying on a service provider experienced with Odoo is the realistic path.

Odoo partners are split into Official Partners and Learning Partners. To use Odoo Enterprise outside of Odoo Online (Odoo's SaaS), you need an Odoo partner to provide the code. Official Partners must meet certain KPIs (new Enterprise users acquired, customer retention), which Learning Partners do not. Official Partners have "Ready," "Silver," and "Gold" levels, and receive support from Odoo S.A. according to their grade.

Note, however, that the KPIs behind the Official Partner levels currently weigh short-term (one-year) contribution to Odoo S.A.'s revenue heavily, and do not necessarily reflect a partner's service quality from a user's point of view. A provider with low service quality can become a Gold partner if it lands one large Enterprise deal, while a provider with high service quality can be downgraded to Learning Partner without new Enterprise sales. For providers whose style is to deliver value through open-source activity, the KPIs are a poor fit.

Some providers become Official Partners despite limited Odoo expertise, while others who know Odoo deeply have no need of Odoo S.A.'s support and deliberately remain Learning Partners (which is cheaper), or choose not to become partners at all. Some partners take the stance of supporting Enterprise only. Odoo's own partner page also uses the term "reseller," which may describe the reality better than "partner."

Challenges and room for improvement

There is no challenge that cannot be improved.

Odoo is a strong product in many respects, but implementation and operation come with some challenges.

Odoo, AI, and open source

AI weakens the old reasons for open source — and strengthens the deeper ones.

An obvious question today: if AI can generate custom code on demand, does an open-source ERP and its community matter less? Two of the traditional arguments have indeed weakened — code has become cheap to write, and AI assistants now answer many questions that once required forums and documentation. Yet three things have become more valuable, not less:

Writing code is cheaper than ever; reviewing and maintaining it is not. The health of the ecosystem therefore depends more than ever on users and vendors who feed improvements back rather than only consuming them.

Sources

Figures and policies on this page are drawn from the following authoritative sources, last checked in June 2026: