Odoo doesn’t shift direction all at once. Minor software releases make small adjustments to how features work, how the interface reacts, and how the system is built in the background.
These changes can go unnoticed, but over time they show where the product is headed.
They also reduce the gap between versions, making each major release less of a jump and more of a stable continuation so that your system is always sustainably evolving.
Table of contents
The Odoo release model introduces structured minor updates
Odoo release behaviour depends on the hosting environment
Odoo users can try out minor releases before pushing them
Small and ongoing releases make Odoo more sustainable
Minor Odoo releases improve reliability & soft launch features
The Odoo release model includes structured minor updates
Odoo releases one major version each year. Currently the software is at version 18 and Odoo 19 is fast approaching. Between those, minor releases like 18.1 or 18.2 deliver updates to the same core system.
These minor versions don’t introduce groundbreaking changes and they’re safe to apply and keep the system aligned with the latest standards, features, and security updates.
The release model allows Odoo to evolve steadily and safely without needing users to wait for the next full upgrade.
Release notes from the minor Odoo 18.2 version
Odoo release behaviour depends on the hosting environment
These updates can be added to your system based on how you host Odoo.
On Odoo Online, updates are automatic. Users are always on the latest minor release of their version. There’s nothing to install, Odoo handles everything in the background.
On Odoo.sh or on-premises, updates are pulled manually from the source. Most teams apply them during regular development cycles, testing for compatibility with any custom modules. This gives more control over timing and rollout.
Due to software integrations, customisations or other developments, Odoo does not push releases automatically as it can impact the system of their Odoo.sh or on-premise customers.
Either way, the updates are designed to be safe but the method to apply them differs depending on your setup.
Odoo users can try out minor releases before pushing them
Users can explore and test minor releases before rollout. Odoo publishes detailed release notes with each minor release and they become readily available for public testing on Odoo Runbot.
Odoo Runbot is a public R&D testing platform that lets users try out different Odoo versions in live demo environments. It's a practical way to see changes in layout, behaviour, or new options before applying them to a live system.
This is especially relevant for teams on Odoo.sh or on-premise, where updates are applied manually. With documentation and the Odoo Runbot, minor releases can be safely trialed prior to deploying them.
Overview of Odoo Runbot and versions currently available for testing – from the latest Odoo 18.3 minor release to the earliest version with support
Small and ongoing releases make Odoo more sustainable
With each smaller release, bugs are resolved, performance improves, and interface behaviour gets closer to how people use the system.
By the end of its release cycle, a main Odoo version isn’t radically different from launch but it is more stable, faster, and easier to work with. Features respond better, workflows feel smoother, and known issues have been resolved.
As new functionalities are introduced gradually through regular updates, users get used to the changes over time. Nothing feels disruptive, just a steady improvement of something already familiar.
This reduces the pressure on major upgrades. Much of the structural groundwork is already in place. So, the jump to the next version becomes less disruptive especially in systems with custom modules or large user teams.
Minor Odoo releases improve reliability & soft launch features
Minor releases focus on stability. They fix bugs, improve performance, and refine how the interface behaves. These changes are based on real usage across different environments.
But stability is only one part of what they do. Odoo also uses minor releases to quietly introduce new features. These may include configuration options, toggles, or interface elements that prepare users for bigger changes later.
Each release typically includes:
- Fixes in core apps like Sales, Accounting, and Inventory.
- Improved load speeds and smoother data handling.
- Security updates based on internal audits or reports.
- Layout changes that improve clarity.
- Early-stage features that do not disrupt existing workflows.
Minor releases play an active role in shaping how Odoo evolves. They support daily operations and keep the system without major interruptions while gradually introducing the building blocks of future versions.
Minor Odoo releases set the stage for main version updates
Odoo often introduces building blocks in minor releases before launching full features in major ones. These updates aren’t always visible, but they show up in:
- New configuration options or toggles that appear in developer mode.
- Restructured fields or renamed elements in the backend.
- Layout or UI behaviour changes that later expand into full redesigns.
This was the case with Odoo 17 and its full UI overhaul, the biggest visual change since the move to Odoo. Through Odoo Runbot and demo instances, users got early exposure to the new interface before the version was officially launched at the Odoo Experience in Brussels.
Odoo 16 vs Odoo 17, after a major UI revamp between major versions
The shift to smarter automation followed a similar pattern. In Odoo 18.1 and 18.2, background logic appeared to support predictive inputs, field suggestions, and smarter document parsing.
By Odoo 18.3, the direction for Odoo 19 was clear. Prompt-based server actions, editor assistance, and custom AI fields in Studio positioned Odoo as a more native AI system, and pointed directly to the major AI pitch behind Odoo 19.
It’s a pattern Odoo repeats: test the logic quietly, then deliver the full feature when the foundation is in place.
Minor releases still require structured change management
Minor updates do not introduce groundbreaking changes, but they can shift how teams work. A new toggle, renamed field or layout adjustment may change expectations or cause friction.
Organisations hosting Odoo on-premises or on Odoo.sh also manage the technical side and each update must be reviewed in context. Teams test compatibility with custom modules, plan timing, and align rollouts with development cycles.
Both sides of the release require attention. Change management helps ensure that users stay aligned, and that updates support productivity instead of disrupting it. Typical measures include:
- Sharing short update digests for each department.
- Highlighting interface changes in internal communication channels.
- Running brief check-ins with key users after each release.
- Testing custom features early and maintaining a shared change log.
Even a short release log builds confidence. Small updates remain visible, actionable, and safe to adopt.
Looking at your next Odoo release? We’ll help you plan ahead.
If you're considering an upgrade, reviewing your version path, or wondering how recent updates affect your setup, we can help.
Our experts work with Odoo across versions, industries and hosting setups, supporting you from first-time implementations to long-term system planning.