Odoo 20: What's New and What Actually Matters
Odoo 20 explained without the hype: AI agents, accounting and inventory changes, Field Service moving into Planning, and the changes that affect upgrades.
Platform comparison
Context
Odoo 20 was released in September 2026. It brings AI agents, accounting and inventory improvements, and several changes under the hood that matter more for upgrades than any new feature.
Odoo 19 remains supported, so there is no need to rush. The question is whether the new features are worth the upgrade effort for your database now, or after the modules you rely on are ported.
Licensing, editions and features change frequently. Treat this as a structural comparison and confirm current pricing and capabilities with each vendor before deciding.
01At a glance
| Criterion | Odoo 20 | Odoo 19 |
|---|---|---|
| AI | AI agents that create and update records and run in automations; MCP connection; AI uses paid credits | Earlier AI features, without agents running inside automations |
| Accounting | Bill line prediction, matching rules, duplicate warnings, parent accounts replace account groups | Account groups; manual bill coding |
| Inventory | Stock aging, inventory at a past date, suggested reorder levels, simplified returns | Classic return wizard; no built-in stock aging report |
| Manufacturing | Continuous production, MO Kanban, MO splitting, single Produce button | Previous MO flow |
| Field Service | Merged into Planning | Separate Field Service app |
| Security model | Record rules removed; access rights carry their own domain (ir.access) | Access rights plus record rules |
| External API | JSON-2 API; XML-RPC and JSON-RPC deprecated | XML-RPC and JSON-RPC |
| Support | Supported for three years from release | Still supported, ending earlier |
02
Every custom module with security files needs updating for ir.access. Integrations using XML-RPC or JSON-RPC should move to the JSON-2 API. Custom views and themes using Font Awesome icons need Material Symbols. Field Service users need their workflows mapped into Planning, and payroll users lose work entries.
03
New implementations should start on Odoo 20. Lightly customised databases on Odoo 19 can plan an upgrade once their third-party apps are available for 20. Heavily customised databases and Field Service users should run a test upgrade first and budget for the changes above.
Decision guide
Verdict
Odoo 20 is the right target for new projects and for anyone already outside the support window. For stable Odoo 19 databases, plan the move rather than rushing it, and start with a test upgrade.
FAQ
Yes. It is a single version step. Custom modules still need porting and testing.
Yes. AI features use paid IAP credits on top of the subscription.
Odoo supports its three latest major versions, so Odoo 19 stays supported until two more versions have been released.
Insights
Odoo 20 explained without the hype: AI agents, accounting and inventory changes, Field Service moving into Planning, and the changes that affect upgrades.
An Odoo 20 upgrade checklist covering breaking changes: record rules, tracking values, account groups, Field Service, payroll work entries, icons and the RPC API.
How to upgrade Odoo to a new major version: assessing custom modules, upgrade service vs OpenUpgrade, test cycles and a cutover plan that holds.
Other comparisons
Next step
We will review your requirements, volumes and integration needs and tell you plainly which platform fits — including when it is not one we implement.