Skip to content
Tutorials Center
My learning

Topics

Lesson 3 of 39 ยท Getting Started

Community, Enterprise and Odoo Versions

Compare Odoo Community and Enterprise, the three hosting options (Online, Odoo.sh, on-premise), and learn how Odoo's yearly version numbers work for modules.

When you start with Odoo you meet three words very quickly: Community, Enterprise and a version number such as 18.0. They decide which features you have, where the software runs and which of your modules will work. Picking the wrong one early is an annoying surprise later, so this lesson sorts them out.

The details of pricing and feature lists change, so treat this lesson as the concepts and check the official site for the current numbers.

Two editions

Community is the open-source edition. Its source code is public, it is free to download and you can run it anywhere. It contains the core framework and the most important apps: Contacts, CRM, Sales, Purchase, Inventory, basic Invoicing, Website, Project and more.

Enterprise is the paid edition. It is built on top of Community: the Enterprise modules are installed in addition to the Community ones, and some of them replace or extend Community screens. Enterprise adds, for example, a more complete accounting suite, a mobile-friendly web client layer, Studio (a no-code customiser), and extra apps such as full-featured Helpdesk or Planning. The Enterprise modules are not open source and need a subscription.

flowchart BT
    C["Community<br/>(open source: framework + core apps)"] --> E["Enterprise<br/>(extra proprietary modules on top)"]
    C --> M["Your custom modules"]
    E --> M

Your own modules can depend on both layers, but a module that depends on an Enterprise-only module will not install on Community.

A practical rule for developers: if you build modules to sell or share widely, depend only on Community modules so that every user can install them.

Three ways to host

Option What it is Custom Python modules
Odoo Online Hosted by Odoo as a SaaS product Not allowed (you can use Studio)
Odoo.sh Platform-as-a-service with Git, staging and production branches Allowed
On-premise You install and run it on your own server or cloud machine Allowed

This course focuses on on-premise and Odoo.sh style development, because they are the options where you can write Python modules. Chapter 8 covers deployment in detail.

Version numbers

Odoo publishes a new major version about once a year, numbered like 17.0, 18.0, 19.0. The part before the dot is the series. Each series gets bug fixes and security fixes for a limited time, and older series eventually stop being supported, so always check the support policy on the official site.

Why this matters for you:

  • Modules are tied to a series. A module written for 16.0 will usually need changes for 17.0, because the framework changes: views, JavaScript and sometimes ORM details differ.
  • A module declares its version in the manifest, with the series first: "version": "18.0.1.0.0" means series 18.0, module version 1.0.0.
  • Branches in Git typically follow the series: 16.0, 17.0, 18.0. Third-party module repositories use this convention too.
  • Upgrades are a project. Moving a database from one series to another changes tables and views, so test on a copy first.

This course uses the current mainstream syntax. Where an idea changed between series (for example, how attribute conditions in views are written), the lesson says so. Always match the tutorial to your installed series by opening Settings and reading the version, or running the server with --version.

A stand-in: reading a manifest version

The manifest version string packs the series and the module version. The next stand-in splits such a string and checks if a module fits an installed Odoo. It is plain Python, not Odoo code.

Python Stand-in: does this module fit my Odoo series?

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Real Odoo behaves similarly: if the manifest version does not start with a series, it prepends the series of the running server. A mismatched prefix is only a hint; Odoo will not stop you, but the module may fail at import or when views load.

Choosing for a project

  1. Need a closed-source, hosted, no-code solution? Odoo Online with Studio.
  2. Need custom Python and Git-based deployment without managing servers? Odoo.sh.
  3. Need full control, offline or special infrastructure? On-premise with Community or Enterprise.
  4. Not sure? Start on Community on a laptop; you can still move the same database to Enterprise later by installing the Enterprise addons (check the official migration notes first).

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does the Enterprise edition add to Community?

    Enterprise modules sit on top of Community and need a subscription.
  2. 2. On which hosting option are custom Python modules NOT allowed?

    Odoo Online is a shared SaaS platform. You can configure it and use Studio, but you cannot upload your own Python code.
  3. 3. What does the manifest version "17.0.1.2.0" tell you?

    The first two numbers are the Odoo series; the remaining three are the module's own version.
  4. 4. Why should a module you plan to share widely avoid depending on Enterprise modules?

    A dependency that is missing on Community makes the module impossible to install there.

Summary

  • Community is open source and free; Enterprise adds proprietary modules and needs a subscription.
  • Odoo Online does not allow custom code; Odoo.sh and on-premise do.
  • Odoo releases a major series roughly yearly (17.0, 18.0, ...), and modules are tied to a series.
  • The manifest version starts with the series, followed by the module's own version.
  • Check the support policy and upgrade on a copy of your data first.

Next: Exploring the Odoo Interface