Every year Odoo publishes a long page of new features, renamed buttons, and removed settings. Reading Odoo 20 Release Note in full takes hours, and most items will never touch your business. This guide condenses the recent notes into the changes that affect daily work by department, flags the ones that raise upgrade effort, and shows where to read the official source when you need detail.
Key Takeaways
- The latest release centres on AI agents that act, offline mode, simpler access rights, and a restructured chart of accounts.
- Some changes are renames, not features. Renamed payment labels and removed menus can quietly break reports, filters, and staff habits.
- Developer changes such as the removal of record rules decide how much an upgrade costs, so read them first if you run custom modules.
- Release notes tell you what changed. Only a tested copy of your own database tells you whether the change suits you.
Table of Contents
- What Odoo 20 Release Note Cover
- Why a Plain Summary Helps
- Recent Versions at a Glance
- Accounting and Invoicing Changes
- Inventory and Manufacturing Changes
- Sales, Point of Sale and eCommerce Changes
- Usability and Mobile Updates
- Developer Changes in Odoo 20 Release Note
- Where to Read the Official Odoo 20 Release Note
- How to Turn Odoo 20 Release Note Into an Upgrade Plan
- Frequently Asked Questions
What Odoo 20 Release Note Cover
Odoo 20 Release Note are the official record of what is new, changed, or removed in each major version.
- One page per major version. Odoo publishes a single page for each annual release, grouped by app.
- An annual rhythm. Major versions arrive each autumn alongside the Odoo Experience event.
- Both editions share one number. Community and Enterprise carry the same version number, but many listed features are Enterprise only.
- Localisation fills much of the page. Country updates for tax, electronic invoicing, and payroll take up a large share.
If you are still choosing between Community and Enterprise, settle that first, because it decides which half of the page actually applies to you.
Why a Plain Summary Helps
What makes the official page hard to use
- Volume. The latest page covers dozens of apps and hundreds of items.
- Feature wording instead of impact. Items read like product announcements. They rarely explain what happens to existing reports.
- Buried behaviour changes. A renamed status or a removed menu sits beside headline features with equal weight.
- Mixed audiences. End user features, admin settings, and framework changes appear side by side.
Read by role, not from top to bottom. Finance reads Accounting and the country section, operations reads Inventory and Manufacturing, and whoever owns custom code reads the technical items first.
Recent Versions at a Glance
Four recent releases and their headline themes, newest first.
| Release | Year | Headline Themes | Support Status |
|---|---|---|---|
| Latest release | 2026 | AI agents that create and update records, a connection over the Model Context Protocol, offline mode, simpler access rights, parent accounts | Newest version |
| Previous release | 2025 | First AI agents, AI fields, natural language search, live voice transcription, receipts merged with invoices and bills | Supported |
| Two releases back | 2024 | Interface refresh, faster Point of Sale, broad usability work | Supported |
| Three releases back | 2023 | Redesigned interface and command palette | Leaving standard support |
For a deeper walk through every new capability, read our odoo 20 feature guide.
The oldest supported release now has a deadline. Each version receives three years of standard support, so the release from three years back drops out now that the newest one has shipped.
Accounting and Invoicing Changes
Structural changes in the latest notes
- Parent accounts replace account groups. The chart of accounts is now structured through parent accounts, and account codes become optional. Review reports built on the old groups.
- Depreciation models replace asset models. Asset configuration moves onto the asset accounts themselves.
- Payment labels are renamed. What used to read In Process now reads Paid, and what used to read Paid now reads Reconciled. Saved filters need updating.
- Expenses flow into bills. The standalone Employee Expenses menu is removed, and approved expenses now create draft bills in the default expense journal.
Day to day improvements
- Stronger duplicate detection. Invoices and bills now show two levels of warning when a likely duplicate is found.
- Bank flexibility. One bank transaction can be split across several accounts during reconciliation, and a new reconciliation summary report is available.
- Tax included or excluded. Sales orders, purchase orders, and invoices can switch between tax included and tax excluded prices.
- Cleaner exchange entries. Exchange gains and losses are consolidated into one line per invoice that expands to show the calculation.
Indian businesses should read the India localisation entry separately. GST, electronic invoicing, and TDS updates appear in the country section rather than in the main Accounting list.
Inventory and Manufacturing Changes
Inventory
- Suggested reorder levels. Minimum and maximum quantities on reordering rules are now suggested from demand history, days of coverage, and order frequency.
- Stock aging report. It shows how long stock has been sitting.
- Intercompany supply. One company can resupply another through routes.
- Simpler returns. The return wizard is gone and the returns process is streamlined.
Manufacturing and purchase
- Continuous production. When enabled on a bill of materials, later operations start as soon as some quantity is ready.
- Split ongoing orders. A manufacturing order in progress can be split so the remaining quantity is produced later.
- One produce button. The separate Produce and Produce All buttons become a single Produce button in Manufacturing, Shop Floor, and Barcode.
- Vendor discipline. Purchase adds a default Incoterm per vendor and a vendor quality rate based on quality checks.
Sales, Point of Sale and eCommerce Changes
- Editable margins. Changing the margin on a sales order line now recomputes the sales price automatically.
- Timed pricelist rules. Pricelist rules, including surcharges, can apply to specific periods or days of the week.
- Commission on payment. Sales commissions can be calculated on the amount actually paid.
- eCommerce recovery. Abandoned carts can be followed up over WhatsApp, and customers can pick a preferred delivery date.
- Point of Sale. Multiple currencies at checkout, multiple printers per shop, and a simplified stock mode that runs without the Inventory app.
Usability and Mobile Updates
- Offline mode. Users can create, edit, archive, and delete records without a connection, then sync later. Field teams benefit most.
- Mobile redesign. Forms suit touchscreens better, and files can be shared from a phone straight into Odoo to digitise bills and expenses.
- AI that acts. Agents can now create and update records, including from an uploaded file of instructions such as a PDF.
- Friendlier data entry. A dot or a comma both work as the decimal separator, and several records can be dragged at once in list and Kanban views.
- Safer deletion. When a record cannot be deleted, Odoo offers to archive it instead.
AI is not free. The latest notes state that all AI features now consume credits bought through in app purchase. Estimate usage per team first.
Developer Changes in Odoo 20 Release Note
These items rarely make headlines, yet they decide how long an upgrade takes for any database with custom code.
Read these before planning an upgrade
- Record rules are gone. Access rights now carry a domain directly. Custom modules that ship record rules need their security rewritten.
- Tracking values are removed. Tracking messages are generated on the fly, so any code that reads stored tracking values must change.
- Icon library replaced. Font Awesome icons give way to Material Symbols.
- Model Context Protocol support. External AI assistants can connect to the database. Treat it as an access decision.
- Push notifications move in house. Odoo's own push service replaces Firebase.
Our guide to custom module compatibility during an upgrade explains how to find what breaks before it reaches production.
Third party apps carry the same risk. Apps that relied on record rules or tracking values must be ported by their authors, and the quality problems in the Odoo App Store mean some never are.
Where to Read the Official Odoo 20 Release Note
- The official release notes page. Odoo hosts one page per version, starting with the official release notes for the newest version.
- The developer changelog. The technical section of the Odoo documentation lists framework and API changes that the main page leaves out.
- The upgrade documentation. It explains support duration and how to request a test upgrade.
- Your country section. Scroll to your localisation entry for tax and statutory changes specific to your market.
How to Turn Odoo 20 Release Note Into an Upgrade Plan
Match the release to your situation
- Starting a new implementation. Begin on the newest version unless a key module lacks a build for it.
- On the previous version with light customisation. Run an upgraded test copy now and let users try the renamed labels and new flows.
- On a version leaving support. Plan the move this year. Any of the three supported versions is a valid target.
- Heavily customised. Code porting is the critical path.
- Running third party apps. Confirm each app has a build for the target version before committing to a date.
Before you fix a date, read our upgrade cost and timeline guide to size the effort realistically.
Turn the notes into a checklist. Write one test for each item that touches your workflows and run them on an upgraded copy. If you would rather hand that over, our Odoo migration and upgrade services cover the full process.
Odoo Upgrades
Not Sure Which Changes Affect Your Database?
Tatvamasi Labs reviews your setup against the latest Odoo 20 Release Note, flags code and apps that need porting, and plans a tested upgrade.
Get a Release Impact Review →Frequently Asked Questions
Odoo publishes one release notes page for every major version on odoo.com, grouped by app.
A new major version arrives once a year, normally in the autumn around the Odoo Experience event, and its release notes go live with it.
Community and Enterprise share the same version number, but many items in Odoo 20 Release Note are Enterprise only, including Studio and several accounting and AI features.
The latest notes focus on AI agents that can create and update records, a database connection over the Model Context Protocol, an offline mode, access rights that replace record rules with a domain, and parent accounts that replace account groups.
Yes. The latest notes state that every AI feature now consumes credits bought through in app purchase. Estimate usage for each team before switching agents on across the company.
Odoo supports each major version for three years. In practice the three most recent versions are supported, so the oldest one leaves standard support whenever a new version ships.
Not automatically. Upgrade once every custom and third party module you rely on exists for the new version and an upgraded test copy of your database has passed your own checks.
Prefer a quick chat? Ask our Odoo team what the latest release means for you. CHAT ON WHATSAPP
