An Odoo upgrade is not only a version change. If an implementation includes custom modules, external integrations, automated workflows, or website customizations, developers need to understand how the new version affects the existing environment.
Odoo 20 introduces changes across AI, APIs, inventory, manufacturing, accounting, website, eCommerce, and other areas.
Rather than covering every new feature, this article focuses on the areas that developers and technical teams should review when working with Odoo 20.
## 1. AI Is Moving Closer to Actual ERP Actions
Odoo 20 expands the role of AI in business workflows.
AI agents can work with supported Odoo actions, including reading and modifying data when the relevant tools are exposed. Odoo also provides an MCP server that allows compatible external AI agents to interact with an Odoo database.
For developers, this raises a more practical question than simply asking whether Odoo has AI:
Which actions should an AI system be allowed to perform?
Odoo's MCP documentation shows that tools can be exposed through Server Actions, and tools can also be marked as read-only. This makes permissions and tool exposure an important part of the implementation.
When introducing AI into an Odoo environment, developers should therefore consider:
- Which data the AI can access
- Which operations it can perform
- Which actions require approval
- Whether tools should be read-only
- How AI actions fit into existing business workflows
The technical challenge is not simply connecting an AI model to Odoo. It is controlling what that connection is allowed to do.
## 2. Review Existing External API Integrations
The Odoo 20 API changes deserve particular attention from developers maintaining integrations.
Odoo's documentation states that the XML-RPC and JSON-RPC APIs are deprecated. In Odoo 20, the legacy db service has been removed, while the common and object services remain available for now and are scheduled for removal in Odoo 22. Odoo's External JSON-2 API is the newer API developers should evaluate for future integrations.
This does not mean every existing XML-RPC or JSON-RPC integration stops working with Odoo 20.
Instead, developers should identify exactly which services their integrations use.
A useful inventory can include:
- External applications
- Custom Python scripts
- Middleware
- Scheduled synchronization jobs
- Third-party connectors
- Data migration scripts
- Custom integrations
The JSON-2 API uses a different authentication and request structure from the older object service, so moving an integration should be treated as a technical migration rather than simply changing an endpoint.
## 3. Custom Modules Need Regression Testing
Custom modules are one of the first areas to review during a major Odoo upgrade.
A module may depend on specific models, fields, views, access rules, automated actions, scheduled jobs, or other modules.
Before moving to production, developers should identify the customizations that support critical business processes and test them in the Odoo 20 environment.
Areas worth reviewing include:
- Custom models and fields
- XML views
- Access rights and record rules
- Automated actions
- Scheduled actions
- Custom reports
- Module dependencies
- External API calls
The objective is not simply to confirm that a module installs successfully.
It is to confirm that the business process depending on that module still works as expected.
## 4. Inventory and Manufacturing Changes Can Affect Custom Logic
Odoo 20 includes changes in inventory and manufacturing workflows.
Inventory improvements include suggested reordering rules and an allocation report that helps users work with orders waiting for incoming stock.
Manufacturing also includes capabilities such as continuous production, Bill of Materials comparison, and work-order planning through Kanban and Gantt views.
For developers, these changes are relevant when custom code interacts with:
- Stock availability
- Reordering
- Procurement
- Manufacturing orders
- Bills of Materials
- Work orders
- Product quantities
If a customization relies on a particular workflow or data structure, that dependency should be tested rather than assumed to behave exactly as before.
## 5. Localization Changes Can Affect Customizations
Indian implementations should also review the Odoo 20 localization changes.
The Odoo 20 feature set includes changes involving Bill of Entry, TDS, Composition Taxpayer workflows such as CMP-08 and GSTR-4, Schedule III financial statements, and payroll-related functionality.
For developers maintaining India-specific customizations, this creates an important review point:
Does existing custom code still need to handle a process that Odoo now supports through standard functionality?
A major version upgrade can therefore be an opportunity to review customizations instead of automatically carrying every customization forward.
The right decision depends on the actual implementation and business requirements.
## 6. Website and eCommerce Customizations Should Be Rechecked
Odoo 20 also brings changes to Website and eCommerce.
The AI Website Assistant can help with tasks such as creating pages, rewriting content, translating pages, and suggesting SEO titles and descriptions.
There are also improvements involving structured data, sitemaps, responsive images, product discovery, Click & Collect, cross-selling, customer reviews, and GA4 eCommerce tracking.
For developers working on customized Odoo websites, the useful question is:
Does a custom solution still need to exist when standard Odoo functionality has expanded?
This is particularly relevant during an upgrade because maintaining unnecessary custom code adds testing and maintenance work.
## 7. Test Complete Workflows, Not Just Individual Modules
One of the easiest mistakes during an ERP upgrade is testing applications separately without testing the complete workflow.
Consider a manufacturing business:
Quotation → Sales Order → Inventory → Procurement → Manufacturing → Delivery → Invoice → Payment
A customization may work correctly inside one application while still causing problems somewhere later in the process.
That is why upgrade testing should include complete business workflows.
A practical technical checklist could include:
- Custom modules
- API integrations
- Automated actions
- Scheduled jobs
- Custom reports
- Accounting workflows
- Inventory workflows
- Manufacturing workflows
- Website and eCommerce flows
- Critical user journeys
Testing should happen in a controlled environment before the production upgrade.
## A Practical Odoo 20 Developer Checklist
Before upgrading an Odoo environment, ask:
- Which custom modules are business-critical?
- Which external systems communicate with Odoo?
- Do any integrations depend on the legacy RPC services?
- Which automated and scheduled actions need regression testing?
- Can any existing customization now be replaced with standard functionality?
- Have critical workflows been tested end-to-end?
- Has the deployment and rollback process been reviewed?
The important part of an Odoo upgrade is not simply knowing what changed in Odoo 20.
It is understanding which of those changes affect your particular implementation.
For a broader overview of Odoo 20 features, including AI, accounting, India localization, eCommerce, Field Service, API changes, and upgrade considerations, see the Odoo 20 feature guide.
If you work with custom Odoo modules or integrations, what is the first thing you check before a major Odoo upgrade?
Top comments (0)