Odoo 20: AI takes action. Is your operating model ready?

What changes: from AI that answers to AI that acts

On September 24 in Brussels, Fabien Pinckaers unveiled Odoo 20 at the opening of Odoo Experience, in front of nearly 45,000 attendees. Among Odoo partners, the release was quickly summed up in one line: Odoo 19 had AI features, Odoo 20 has agents.

The distinction matters. An agent no longer just drafts or summarizes: it creates and updates records, such as a customer, a purchase order or a journal entry. It can be triggered by an automated or scheduled action, framed by “skills” that define what it is allowed to do, and connected to external AI tools through the MCP protocol, while respecting access rights.

The change is real, but it shifts the difficulty. An agent doesn’t invent your process: it runs the one you describe. If that process is unclear, or your data contains duplicates, the agent fixes nothing. It reproduces the mess, only faster.

An AI agent doesn’t invent your process. It runs the one you have, flaws included.

Even at Odoo, AI hasn’t replaced organization. According to Fabien Pinckaers, it handles about 40% of support requests, but request volume has nearly tripled and the company keeps hiring.

The updates that matter day to day

AI takes centre stage, but much of Odoo 20’s value lies in quieter improvements.

1. Tighter finance

Odoo now suggests vendor bill lines based on past bills, and flags likely duplicates. Any entry that affects a bank account must now come from a bank transaction: stricter, and worth anticipating if your team posts manual entries. For Canada, Odoo 20 adds batch payments through pre-authorized debits (CPA 005 standard).

2. Smoother operations

In manufacturing, operators record produced quantities from the work order, and the next step can start without waiting for the whole manufacturing order to finish. In the warehouse, a new report shows orders waiting for stock and lets you reserve incoming goods in one click.

3. Mobile teams, even offline

Offline mode lets users create, edit or archive records without a connection, and syncs once they are back online. A real step forward for teams on job sites, on delivery routes or at customer locations.

What the announcements say less about

These points make less noise in launch posts. They still weigh on the decision:

• AI features consume prepaid credits: an agent that runs every day consumes credits every day.
• Prices are going up for the first time since 2022. In Europe, the Custom plan rises from €29 to €35 per user per month; the Standard plan is unchanged.
• Custom modules block the upgrade until they have a compatible version, and both the new interface framework and the access-rights overhaul affect them directly.
• The legacy programming interfaces (XML-RPC and JSON-RPC) are deprecated: your connectors need to move to the new JSON-2 API.
• With Odoo 20 out, Odoo 17 leaves standard support, and Odoo Online offers no extended support.

Should you upgrade now?

Not on release day. The first maintenance releases usually arrive in the weeks after a launch. Our take, depending on where you start:

1. Odoo 16 or earlier: plan now. Aim for the most stable version at project time, often Odoo 19, then Odoo 20 as a second step.
2. Odoo 17: prepare the upgrade. Your standard support is ending. Take stock of your custom modules and integrations.
3. Odoo 18: no rush. Use the coming months to clarify your processes. That is what will make agents useful the day you upgrade.
4. Odoo 19: aim for early 2027, once the first maintenance releases are out.
5. In every case, test on a copy. Ask for an upgraded copy of your database and test your processes end to end before go-live.

In short

Odoo 20 is a real step forward, but the value of agents depends less on the tool than on what you hand over to them. The companies that get the most out of it will be the ones that first put their processes and data in order. That is where every one of our projects starts, before any configuration. See our Odoo migration approach.