Odoo 20: New Features and Updates Reshaping ERP, Automation, and AI

Odoo 20 is shaping up to be more than another version upgrade. The latest previewed capabilities point toward an ERP platform that combines traditional business management with deeper automation, AI-assisted workflows, stronger offline capabilities, and a more connected user experience.

From Inventory and Point of Sale to Marketing Automation, Project, Timesheets, Rental, hardware connectivity, and developer tools, Odoo 20 introduces changes across the platform. At the same time, AI is becoming increasingly connected to actual business processes rather than remaining limited to conversational assistance.

With Odoo Experience 2026 putting Odoo 20 at the center of its agenda, businesses and development teams have several changes worth watching closely.

What is New in Odoo 20?

Odoo 20 focuses on improving how users operate, automate and connect their business processes. Some of the most notable areas include:

• AI agents and AI-assisted workflows.
• Model Context Protocol (MCP) integrations.
• Offline functionality.
• Inventory and valuation improvements.
• More flexible Point of Sale workflows.
• Visual Marketing Automation journeys.
• Smarter Timesheet capabilities.
• Rental workflow improvements.
• OBox for hardware connectivity.
• Python framework and developer improvements.
• Security and access-control changes.
• Better navigation and user experience.

1. AI Moves Closer to the Core of ERP Workflows

One of the biggest themes around Odoo 20 is the increasing role of artificial intelligence. Odoo’s 2026 AI program includes dedicated sessions covering AI innovations, conversational AI, AI agents, RAG-based approaches, MCP integrations, and AI-native ERP workflows.

The important distinction is that AI is not being positioned only as a tool for generating text or answering questions. The direction is toward AI interacting with business data and workflows.

AI Agents

AI agents can be used as a layer between users and business operations, with capabilities centered around working with Odoo data and actions. Depending on the configured workflow and available tools, this can involve tasks such as:

• Finding relevant business records.
• Creating or updating records.
• Working with documents.
• Triggering configured actions.
• Assisting users with operational tasks.
• Connecting Odoo with external AI workflows.

This changes the role of AI inside an ERP. Instead of simply asking an assistant for information, users can potentially move from asking → understanding → acting within the same ecosystem.

That also introduces an important implementation consideration: permissions, business rules, validation, and human oversight remain critical when AI is allowed to perform actions on business data.

MCP for Connecting Odoo With AI Systems

Odoo’s MCP implementation provides a standardized way for an external AI agent to interact with an Odoo database. The official documentation describes an architecture where an external AI client can access available tools and use them to read or modify Odoo data.

For businesses, this could make integrations between Odoo and AI applications more flexible. For developers, it also means that future Odoo architectures may increasingly involve:

Rather than treating AI as an isolated add-on, businesses can start considering where AI fits into actual processes.

2. Odoo 20 Introduces a More Practical Offline Experience

Connectivity can become a serious operational problem when ERP users work from warehouses, retail locations, customer sites, or other environments where internet access is inconsistent.

Odoo 20’s Offline Mode addresses this by allowing supported users to continue working with records when connectivity is unavailable. Odoo’s official documentation describes offline browsing, searching, creating, editing, archiving, unarchiving, and deleting records, along with a synchronization queue for reconnecting changes.

This is more substantial than simply improving mobile responsiveness.

For field service, retail, and other distributed operations, this can make ERP access considerably more resilient.

3. Inventory Management Gets More Operationally Focused

Inventory is another major area of change in Odoo 20.

Odoo’s official Odoo Experience program specifically highlights ministock management, new label designs, integrated CMR documents, improved allocation reports, and enhanced intercompany and interbranch flows.

These improvements address different parts of day-to-day warehouse management.

• Ministock Management
  Ministock management provides another way to handle inventory replenishment and minimum-stock requirements, helping businesses maintain better control over stock availability. For organizations managing large product catalogs, multiple locations, or recurring replenishment requirements, inventory controls at this level can reduce the need for manual monitoring.
• Improved Allocation and Intercompany Operations
  Allocation reporting and intercompany/interbranch flows are particularly relevant to organizations operating across multiple warehouses, branches, or legal entities. Instead of treating inventory movements as isolated transactions, these improvements support more connected supply-chain processes.
• A More Transparent Approach to Inventory Valuation
  Another important area is inventory valuation and accounting visibility. The changes discussed around Odoo 20 introduce more specific accounting visibility for situations where goods and invoices do not move through the process at exactly the same time.

For example, businesses may need to identify situations where:

• Goods have been delivered but not invoiced.
• Goods have been invoiced but not delivered.
• Goods have been received but the vendor bill is pending.
• Goods have been billed but have not yet been received.

This type of separation can make stock-related accounting investigations easier, particularly during reconciliation and period-end activities.

4. Point of Sale Gets More Flexible for Retail and Restaurants

Odoo 20’s Point of Sale improvements focus heavily on reducing friction during actual transactions.

One of the clearest changes is the evolution of POS Presets for scenarios such as dine-in, take-out, and delivery.

Odoo’s official preview explains that these presets can automatically handle changes such as fiscal positions and pricelists, while delivery configuration becomes more detailed to account for logistical requirements.

This matters for businesses where one POS environment serves multiple order types. A restaurant, for example, may need different pricing, tax treatment, delivery rules, and operational flows depending on whether an order is for dine-in, takeaway, or delivery.

Instead of requiring staff to manually configure every order, predefined operating modes can make those transitions simpler.

Other POS improvements being highlighted around Odoo 20 include improvements to checkout performance, combos, self-ordering, hardware configuration, and floor-plan management. Odoo’s official retail session positions these changes around faster in-store operations and stronger control over sales, inventory, and customer experience.

5. Marketing Automation Moves From Linear Sequences to Visual Journeys

Marketing Automation is another area where Odoo 20 introduces a meaningful change in how workflows can be designed.

Traditional automation often follows a simple pattern:

Trigger → Email → Wait → Email → End

The newer approach is more visual and conditional.

Odoo’s official preview describes advanced flows that can combine behavioral triggers such as email opens, link clicks, website visits, and form submissions with conditional branching, lead scoring, AI-generated personalization, and automated promotions.

This allows marketers to build journeys based on what a customer actually does.

For example:

Website Visit → Form Submission → Lead Scoring → Branch Based on Engagement → Personalized Follow-up

The broader benefit is stronger coordination between Website, eCommerce, CRM, Marketing Automation, and customer engagement activities.

Instead of managing these touchpoints as disconnected campaigns, businesses can build more connected customer journeys within Odoo.

6. Project Management Gets More Visibility Into Profitability

Odoo 20 also brings new capabilities to Project management.

The updated Project experience includes a new dashboard, profitability reporting, and custom KPIs using Odoo Spreadsheets. Odoo’s official sessions also highlight improvements across areas such as Gantt, Planning, Roles, Manufacturing integration, CRM integration, and Timesheets.

The profitability improvements are particularly relevant for service businesses. Project profitability often depends on more than the sales order. Actual performance may involve:

• Employee timesheets
• Expenses
• Purchase orders
• Vendor bills
• Materials
• Employee costs

Odoo’s Project profitability session demonstrates how these operational inputs can be connected to project-level financial analysis.

This gives project managers and business leaders a more connected view of project execution and financial performance.

7. Timesheets Get AI-Assisted Activity Suggestions

Timesheet entry is a repetitive task, particularly for consulting, implementation, software development, and other service organizations.

Odoo 20 introduces the Timesheet Assistant, with Odoo describing capabilities around automatic activity tracking and smart suggestions for time entries.

The objective is straightforward: reduce the amount of manual effort involved in remembering and recording activities.

The feature also reflects a larger Odoo 20 pattern. AI is increasingly being used to assist with everyday ERP interactions rather than existing as a separate application.

The important operational principle remains validation. Suggested activities and time entries should still be reviewed by users before becoming part of official records.

8. Rental Gets More Flexible Pricing and Scheduling

Odoo 20 also brings changes to the Rental application, with improvements focused on pricing, scheduling, and integration with other applications.

One highlighted capability is the Advanced Seasonal Pricelist, designed to support more flexible rental pricing based on seasonal requirements.

For rental businesses managing equipment, spaces, or services, more flexible pricing and scheduling can help bring commercial rules closer to the actual rental workflow.

The larger direction is also important: Rental is increasingly connected with other Odoo applications rather than functioning as an isolated process.

9. OBox Reimagines Odoo’s Hardware Connectivity

Odoo’s hardware ecosystem is also evolving with OBox, positioned as the next generation of Odoo’s hardware connectivity experience.

The goal is to connect physical devices, such as printers, scanners, scales, and payment-related hardware, with Odoo business processes through a more centralized architecture.

For businesses operating retail stores, warehouses, manufacturing floors, and other hardware-intensive environments, this is important because hardware setup is often one of the less visible complexities of ERP deployment.

A more centralized approach can simplify how connected devices are discovered, configured, and managed.

This is particularly relevant to POS and warehouse environments where business continuity depends on reliable interaction between software and physical equipment.

10. Security and Access Control Changes Matter to Developers

Odoo 20 is also bringing framework-level changes that developers need to evaluate carefully during custom module development and migration.

Security is one such area.

Developers working on custom Odoo modules should review changes to access-control definitions, model permissions, record rules, and module security structures rather than assuming that an existing Odoo 19 implementation can simply be copied into Odoo 20.

Some community discussions have pointed to changes such as access-rights file naming and the organization of security definitions. These should be validated against the final Odoo 20 framework before being adopted as development standards.

The broader takeaway is more important than any single filename:

Odoo 19 security implementations should be reviewed, not blindly carried forward, when migrating custom modules to Odoo 20.

Security changes can affect module installation, permissions, record visibility, and application behavior, making them part of the migration checklist rather than an afterthought.

11. Developer and ORM Changes Require Migration Attention

Odoo 20 is not only a functional release. It also introduces changes in the technical framework.

Odoo’s official Odoo Experience program includes a dedicated session on the Python framework for Odoo 20, highlighting the importance of framework-level changes for developers.

Developers should therefore review:

• Python models and business logic.
• XML views.
• OWL and JavaScript customizations.
• Controllers.
• RPC calls.
• ORM usage.
• Security definitions.
• Third-party modules.
• External integrations.
• Automated tests.
• Custom reporting.

Even apparently small framework changes can have a wider impact when a business has a heavily customized Odoo environment. A structured migration process should therefore look like:

Assessment → Custom Module Review → Refactoring → Testing → Staging → Production

This becomes especially important when moving from Odoo 19 to Odoo 20 rather than starting a new implementation.

12. User Experience Improvements Go Beyond Visual Changes

Odoo 20 is also refining how users navigate and interact with the platform.

One example is the improved navigation experience for long-form content, where an automatically generated “On this page” navigation can help users move between sections without manually searching through a long page.

While small compared with AI or offline functionality, these usability improvements matter because ERP productivity is affected by hundreds of small interactions throughout the workday.

The same principle appears across other Odoo 20 updates: fewer unnecessary steps, clearer workflows, and more contextual actions.

Odoo 20: What These Changes Mean for Businesses

Taken individually, many Odoo 20 updates solve specific operational problems. Taken together, they point toward a broader shift in how an ERP can function.

The traditional ERP model is largely:

Record → Process → Report

Odoo 20 increasingly moves toward:

Data → Context → Automation → Assistance → Action

AI agents can work with business data. MCP can connect Odoo with external AI workflows. Offline functionality can keep operations moving without continuous connectivity. Marketing automation can respond to customer behavior. Project and inventory improvements can provide more operational context.

This does not mean every organization should immediately automate every process with AI.

Instead, businesses should identify where automation and intelligence can genuinely improve an existing workflow, and where human approval and conventional business rules should remain in control.

Should You Upgrade to Odoo 20?

The answer depends on the way your current Odoo environment is built and used. For organizations running mostly standard Odoo applications, new functionality may provide clear reasons to evaluate the upgrade. For highly customized environments, the decision requires more technical analysis.

Before upgrading from Odoo 19 to Odoo 20, businesses should assess:

• Custom Modules
  Review every custom module for framework, ORM, view, security, and JavaScript compatibility.
• Integrations
  Check APIs, payment gateways, eCommerce connectors, third-party applications, and external services.
• Data and Accounting
  Validate accounting configurations, inventory valuation, historical data, reports, and reconciliation processes.
• Security
  Review access rights, record rules, user groups, and custom security logic.
• Operational Workflows
  Test business-critical processes end-to-end instead of validating individual screens in isolation.
• Performance and Offline Requirements
  If your organization will use offline capabilities, warehouses, field operations, or hardware-connected workflows, test those scenarios specifically. A controlled staging environment should be used before production migration.

What Developers Should Prepare for Odoo 20

Odoo 20 expands the technical landscape that developers need to work with.

The traditional Odoo development stack of Python, XML, PostgreSQL, and JavaScript is increasingly complemented by APIs, automation, AI services, and agent-based workflows. That means development teams should think beyond module compatibility.

They should also consider:

• How AI interacts with business records.
• How permissions apply to AI-driven actions.
• How external systems communicate with Odoo.
• How offline synchronization affects custom modules.
• How new framework conventions affect existing code.
• How customizations will behave across future upgrades.

The result is a more interconnected Odoo architecture, but also a greater need for disciplined development and testing.

Final Words

Odoo 20 represents a broader evolution of the platform rather than a collection of isolated feature updates. From AI-assisted operations and MCP connectivity to offline workflows, inventory, POS, marketing automation, services, and developer tooling, the release is expanding what businesses can do within a connected ERP environment.

For businesses already using Odoo, the next step is not simply to ask what is new. It is to understand which changes fit existing processes, which customizations need attention, and where new capabilities can create measurable operational value. A well-planned Odoo 20 upgrade can therefore be approached as both a technical migration and an opportunity to rethink how ERP, automation, integrations, and AI work together.