Odoo 20 was released on 24th September 2026 during Odoo Experience, Brussels. Many companies are left asking if they should upgrade or wait until Odoo 19. This guide explains the key changes in simple terms. All information is provided from Odoo's documentation and release notes.
1. Apps added or restructured in Odoo 20
According to Odoo's release notes, Odoo 20 is an ‘Automate Everything’ release. This means you can automate processes easily, create beautiful websites with just a prompt, and have access to an accounting expert when you need it. There are also some smaller improvements to everyday features, like searches saved as favourites in list views will now show the correct columns, better dialogues, new KPI's added to your digest emails, and attachments can be downloaded in bulk.
AI agents
Odoo 20 gives more advanced functionality to AI agents. As well as answering questions, AI agents can now create and update records (including using instructions provided in a PDF that has been uploaded). Other features include asking questions about a file whilst previewing it, generating images, and smart buttons for websites and mailings. They also give real-time feedback whilst they are running rather than just saying ‘AI is thinking’. Finally, they can ask you to authorise an action by clicking a button. The agents can also be run via automated and scheduled actions. You can now connect to external AI tools using the MCP (Model Context Protocol). Once you have selected your AI provider, Odoo will automatically select the right model for each task.
What this means for your budget and setup:
- AI is not free. All AI features now require credits. These can be purchased via IAP (In-App Purchases). You should plan your budget accordingly.
- Conversations are kept for a limited time. Conversations with your agents will be kept for 30 days from the last message.
- Self-hosted servers may need an extra database extension. If you're using the Enterprise AI features to search your documents, then you will also need to install the pgvector extension.
- Review access rights before connecting MCP. External AI tools will have access to your Odoo data with the same level of access as the user. You should make sure you understand what records they can access.
- The AI Website Assistant is stronger. You can create new web pages, modify forms and menus. It can also be used to assist with modifying product names, descriptions, and prices within your eCommerce site.
Databases
The new ‘My Subscription’ menu item can be found in the User menu. This gives users a central place to find details of their Subscription Plan, IAP Services, and Database Management. The db service has also been removed from the external API for developers in Odoo 20. A better source could be added if there is one for a new Databases app. However, this is simply an administrative change.
Field Service on Planning
Field Service has also been removed as a new app. It has been discontinued, and the features can now be found in the Planning app. Partner blog posts detailing what has changed mention ‘Live map of technicians’, ‘Route planning’, ‘Travel costs’ and ‘Worksheets’. Travel times can also be seen in the Gantt view.
What this means in practice:
- Planning is used as the primary application.
- Menus, filters, training resources, and Studio modifications that are based on Field Service will need to be documented and recreated.
- Customised worksheets will need to be recreated.
- The integration with Payroll has been removed along with the entry of work.
TikTok, Shopee and Lazada connectors
The Odoo documentation provides information about sales connectors for marketplaces. Within the Odoo 20.0 Sales documentation, we can find information about Amazon, Shopee, and Lazada connectors. However, there is also information about TikTok Shop and Gelato.
- The TikTok Shop connector allows you to import orders, products, and stock between TikTok Shop and Odoo. This includes platform fees and order splitting.
- Orders will be imported from TikTok Shop every 60 minutes. They will cover the last 15 days since your last sync. Only orders requiring shipping (Awaiting Shipment or Awaiting Collection) will be imported.
- When an order is cancelled within TikTok Shop, it will show as cancelled within Odoo. However, if cancelled within Odoo, it will not update TikTok Shop.
- Disputes, refunds, and monthly fees reports will still need to be done within the TikTok Shop Partner Center.
The Shopee connector will allow you to import orders from Shopee (confirmed), send stock levels to Shopee, and manage multiple seller accounts and multiple shops. Income reports, disputes, and refunds can be managed in Shopee Seller Central.
The Lazada connector is also available in Odoo 20.0. Create an app on the Lazada Open Platform (App Category: Seller In-house APP) and then connect your Lazada Seller account from the Apps list.
- Click on the Sync Catalog button to import active products from Lazada. Map the Lazada SKU to the Odoo Internal Reference.
- Orders are imported every 60 minutes. If you have FBM orders, then a picking, sales order, and customer will be created.
- If an order is cancelled in Lazada, it will show in Odoo, but if cancelled in Odoo it will not reflect in Lazada.
Obox
Obox is a new app for linking hardware such as printers, scales, and cameras. Once the connect button has been clicked, the box can be linked to Obox. If automatic detection does not work, the box can be manually linked using the IP address and serial number. The devices section will show devices grouped by box, and if you go to Obox > Logs, there is a clear queue of commands sent from Odoo. During testing, we noticed that this does not replace your IoT Box but installs alongside it. You can use the Odoo Android app as an Obox for Point of Sale, self-order, and Quality. The documentation for Odoo 20.0 IoT still refers to the IoT Box and Windows Virtual IoT, so make sure you know what you need. We could not find a specific page in Odoo documentation relating to Obox, so make sure you are clear on what you need by looking at a test database.
2. Changes from SaaS 19.1 to 19.5 that roll into Odoo 20
Odoo also provides a series of SaaS versions (19.1, 19.2, etc.) between each stable version. These are incremental, and if you keep your stable version as 19.0, you will have all of these changes when you upgrade to 20.
Upgrade scripts: two different things
It helps to separate two types of scripts:
- Database upgrade scripts. These follow a specific tree structure. They have a naming convention to determine when they run. These can be written using SQL and ORM. They will upgrade your data.
- Code upgrade scripts (odoo/upgrade_code). These will modify your source code. The Odoo odev tool says that upgrade_code is "Odoo's own upgrade tool, which is available from Odoo 18.0." This will automatically upgrade source code using internal upgrade scripts. You can use an optional dry run to see what will change, a glob to select files, and run individual upgrade scripts (e.g., rename tree to list)."
Odoo 20 includes some upgrade scripts which will upgrade module source code. To use them, run odoo-bin upgrade_code within Odoo 20. You will need to run this on a copy of your custom add-ons and tell it what version your code was written in. For example: ./odoo-bin upgrade_code --addons-path=/path/to/custom_addons --from 19.1 --dry-run.
Other 19.x changes that surface in Odoo 20
- Access control has been consolidated. There is a new model for access control called ir.access. This merges the access control lists and record rules. In Odoo 20, record rules have been removed, and the access rights have a domain assigned.
- Tracking values for chatter are no longer stored. Tracking messages are created dynamically. This means that any custom reports that display previous tracking history will need to be reviewed. Odoo notes that if you still need these, you can install a specific module.
- The external API is changing. The db service has been removed in Odoo 20, and common and object services are due to be removed in Odoo 22. JSON-2 has been introduced and is already documented for use in Odoo 19. JSON-2 can only be accessed using Custom Odoo pricing plans
already documented for use in Odoo 19. JSON-2 can only be accessed using Custom Odoo pricing plans
Custom modules come first
Odoo has clearly stated that if there is a custom module in your database, you must upgrade the source code of the module before upgrading your database.
3. OWL 3 frontend and what it means for custom modules
OWL is a JavaScript framework used to build Odoo's screens. Custom buttons, widgets, dashboards, and form components are typically built using OWL.
Odoo 20 has moved to OWL 3 for the web client. The bundled OWL library has been upgraded from 2.8 in Odoo 19 to a pre-release version of 3.0. This means that there is an upgrade to the frontend in Odoo 20. Odoo 20 also has tools to help with the code. A rewrite tool to upgrade OWL 2 components to OWL 3 has been included. This does not fully cover the upgrade. The migration script has been named owl3-migration.py and has specific rules.
What this means in simple terms:
- Modules with pure Python models and Views will require minimal front-end development.
- Modules with custom JavaScript, OWL components, or XML templates will require more attention.
- Scripts will only translate the syntax; it will still require a developer to review the functionality and test
4. Stricter platform requirements
| Component | Odoo 19 | Odoo 20 |
| Python | 3.10 or later | 3.12 to 3.14 |
| PostgreSQL | 13 or later | 16 or later |
Odoo 20 provides some real improvements, especially around automation and AI. However, you will need to do some preparation for the upgrade (new servers, code review for custom modules, and third-party apps). As long as you have a clean inventory and perform a test upgrade, it should go smoothly. If you would like help determining if you’re ready, we’d be happy to help!
Other self-hosted details to check:
- Python has a maximum version; the Odoo 20 release file states that the minimum is 3.12 and the maximum is 3.14. Any lower than 3.12 will cause Odoo not to start. Any higher than 3.14 will start but will show a warning that the version is not officially supported (from the source code).
- Older PostgreSQL versions will just show a warning. Any lower than 16 will show a warning that it is below the minimum. But you shouldn't rely on this for production.
- PDF engine: Partner guides show that they require a patched version of wkhtmltopdf or paper-muncher v0.6+.
- pgvector is only required if you are using the Enterprise AI features to search your documents.
What to do:
- If you are self-hosting, then you should check your Python and PostgreSQL versions. If they are below the new minimum versions, then you should plan to upgrade your server.
- If you have custom code, then you should test your code on Python 3.12.
5. Impact on existing customizations and third-party apps
The areas that deserve a review before you move:
| Area | What to check |
| Custom Python modules | Run upgrade_code with a dry run and review all changes. |
| Custom JavaScript and OWL components | Rewrite OWL 2 to OWL 3 using upgrade_code, and review all custom components with developers. |
| Security files and record rules | Record rules have been removed, and a domain has been added to the access rights. Convert profile by profile, including multi-company and test |
| Field Service and Planning customizations | Field Service has been moved into Planning. Rebuild worksheets, views, filters, and Studio customisations. |
| Marketplace connectors | Compare your current connector to the ones provided by Odoo. |
| Third-party apps | Ask vendors for an Odoo 20 version. |
| Integrations and custom reports | Test on a copy of your database. |
| External API integrations | The db service has been removed, and common objects have been moved to Odoo 22. Plan to migrate to JSON-2. |
| Reports that read chatter history | Tracking values are no longer stored. Review custom reports and audits. |
| Payroll and accounting customizations | Payroll work entries have been removed. Account groups have been made parent accounts. Asset models have been made into depreciation models. |
| AI agents and MCP | Budget for IAP credits and review access rights before connecting external tools. |
6. Decision table: stay on 19 or move to 20?
This table is editorial guidance, based on the verified facts above. It is not an official Odoo recommendation.
| Your situation | Suggested choice | Reason |
| Stable version with few customisations and no urgent need for new features. | Stay on 19. | Less risk. You can plan to upgrade later. |
| You want to use the new AI and automation features. | Upgrade to 20. | These are the main areas of focus for Odoo 20. |
| Self-hosted on Python <3.12 or PostgreSQL <16. | Upgrade the servers. | These are hard minimum requirements. |
| Many custom modules using JavaScript. | Stay on 19 and test. | Most testing is required on the frontend. |
| Lots of third-party apps. | Wait for confirmation from the vendor. | Apps will need to be compatible with 20. |
| Using Field Service heavily. | Test on a copy. | App architecture has changed. |
| Selling on TikTok Shop, Shopee, or Lazada. | Check the documented connectors. | These may replace any custom or paid integrations. |
| Running a significantly older version. | Plan an upgrade soon. | Older versions will no longer be supported. |
| Want to use AI but uncertain about running costs. | Pilot with one team. | All AI features require IAP credits. |
| Reliant on record rules or multi-company security. | Test on a copy. | Record rules have been replaced with domain filters on access rights. |
| Custom integrations using the old external API. | Plan an upgrade to JSON-2. | The 'db' service has been removed, and 'common' and 'object' are in Odoo 22. |
7. Other changes worth knowing
The following changes have been noted in the release notes:
- Offline mode. This is a new feature added to Odoo 20 and allows field staff to work offline. Data will be synced when reconnected.
- A new mobile experience. This includes a secure login screen, command palette (accessible from swiping down on the dashboard), date picker (bottom sheet), improved touchscreen forms, and the ability to share files from your phone (e.g., to scan bills or create tasks and leads).
- Simpler payroll. No work entries. Work entry types have been merged with time off types.
- Accounting changes. Account groups have been replaced with parent accounts. Asset models have been replaced with depreciation models. Bills can be paid one at a time or in bulk using PISP. Improved duplicate detection.
- Website & e-commerce. In addition to the AI assistant, partner write-ups have included automated upsell suggestions, minimum order quantity, customer-selected delivery dates, return orders via the portal, and automatic unpublishing based on stock
- Localisations. A big part of the release notes includes changes to specific countries. For example, India now includes support for the GST composition scheme (CMP-08, GSTR-4) and Bill of Entry for imports. Please check your country.
- Licensing. A new light access user plan has been reported. Please check the pricing page on Odoo for current plans.
- Support. Odoo provides around 3 years of standard support for each major version. Odoo 17 has now reached the end of standard support. Please check the supported versions page for accurate dates.
Odoo 20 provides some real improvements, especially around automation and AI. However, you will need to do some preparation for the upgrade (new servers, code review for custom modules, and third-party apps). As long as you have a clean inventory and perform a test upgrade, it should go smoothly. If you would like help to determine if you’re ready, we’d be happy to help!.
To read more about Odoo 20 Release Date, Support Timeline, and Version Policy, refer to our blog, Odoo 20 Release Date, Support Timeline, and Version Policy.