Odoo 20 was unveiled by Fabien Pinckaers at Odoo Experience in Brussels on 24 September 2026, and Odoo has published the official Odoo 20 release notes. The headline changes are AI agents that create and update records, an offline mode, a simpler access rights model, a long list of accounting work and a new, lower cost Light User licence. The release notes also state that all AI features now need credits bought through In-App Purchase (IAP).

The changes that matter most for businesses, in summary:

• AI agents that act: agents create and update records, run on a schedule and connect to other systems through MCP.
• AI credits: every AI feature now consumes credits bought through IAP, which no plan includes.
• Offline mode: records can be created, edited and searched without a connection.
• Simplified access rights: record rules are removed, which affects custom modules.
• Accounting: bank consistency, bill line prediction, invoice reminders, simpler assets and bill payment from Odoo.
• Apps: wide changes across CRM, eCommerce, Inventory, Point of Sale, Marketing Automation, Project, Timesheets, Rental and HR, plus OBox for hardware connectivity.
• Light User licence: a lower cost user type for employees with limited access.
• Localisation: country updates for tax, payroll and statutory reporting, including the US, Canada, UK, Singapore and India.

AI agents in Odoo 20: from answering to acting

In Odoo 20, AI agents move from answering questions to doing the work: they create and update records, run on a schedule and connect to other systems through MCP. But every AI feature now consumes paid credits.

The items that matter most for business users:

• Agents create and update records. An agent can generate records, including from instructions in an uploaded PDF, and modify existing ones. A client specification can become a project with its tasks.
• Agents run on a schedule. Automated and scheduled actions can call an agent, so a routine check runs without anyone requesting it.
• Agents ask before going too far. Responses can include buttons for questions, permissions and suggestions. When an agent reaches its limit of tool calls, it asks the user before continuing.
• Files and voice. Users can question a file while previewing it, send documents into an agent chat and dictate requests.
• MCP. The release notes describe connecting Odoo to other systems through MCP (Model Context Protocol), the standard by which AI tools communicate with other software.
• Housekeeping. Odoo selects the AI model for each task automatically. Conversations are retained for 30 days after the last message, and “topics” are renamed “skills”.

How MCP connects Odoo with external AI

Odoo’s MCP implementation gives external AI agents a standard way to work with an Odoo database. Odoo’s documentation describes an architecture in which an external AI client can access the tools a database exposes and use them to read or modify Odoo data. For businesses, this makes integrations between Odoo and AI applications more flexible; for development teams, it means AI becomes part of the integration architecture rather than an isolated add-on.

Governance still matters

Once AI can act on business data, permissions, business rules, validation and human oversight become implementation requirements. Each organisation should decide where an agent may act on its own and where a person must approve the outcome.

Budget for AI credits

Several keynote recaps state that AI is included in the subscription. The release notes say otherwise: all AI features now need credits, which can be bought through IAP. The pricing page lists “Odoo Studio / Agentic AI” under the Custom plan and states that In-App Purchase credits are not included in any plan.

For finance teams, the practical step is the same: treat AI credits as a separate, usage based budget line until Odoo confirms otherwise for your contract.

Everyday changes every Odoo user will notice

The general section of the release notes is long; the changes below are the ones users in every country will notice first, led by offline mode and a simplified access rights model.

Offline mode: what implementation teams should plan for

Odoo’s documentation describes offline browsing, searching, creating, editing, archiving, unarchiving and deleting of records, with a synchronisation queue that applies changes once the connection returns. Because offline changes must be reconciled later, record dependencies, conflicting updates and offline compatible customisations need attention during implementation. For field service, retail and other distributed operations, the result is ERP access that keeps working when connectivity does not.

Simplified access rights: the change most likely to need developer time

Odoo 20 removes record rules and moves the domain onto the access right itself. For a standard database this is simpler to manage. For companies with custom modules that define their own record rules, it is the change most likely to require development effort during the upgrade, wherever the database is hosted.

Accounting changes in Odoo 20 for every country

Accounting has one of the longest sections in the release notes, and most of its changes apply regardless of country. The improvements finance teams will notice first:

• Bank consistency. Everything that touches a bank account must originate from a bank transaction, keeping the books and the bank in step.
• Parent accounts replace account groups in the chart of accounts.
• Bill line prediction uses history and labels to fill vendor bills.
• Customer invoice reminders, both manual and automatic.
• Reconciliation against several accounts at once, and analytic distribution on write-offs.
• Simpler asset models built around depreciation logic, with depreciation by rate.
• Paying bills from Odoo through a payment initiation (PISP) interface, where the bank and country support it.
• Multi-ledger consolidation improvements for groups reporting across companies.

The last two points deserve attention from multinational groups. Payment initiation depends on local bank and country support, so availability may differ between the US, UK, Canada, Singapore and India. Consolidation improvements matter most to groups with entities in several of these countries, and should be tested against your actual intercompany structure.

Business app changes in Odoo 20

Beyond AI and accounting, Odoo 20 changes most of the everyday business apps, from CRM and eCommerce to Inventory, Point of Sale, Marketing Automation, Project, Rental and hardware connectivity.

CRM and eCommerce

CRM gains lead distribution rules (always, limited rotation or out of rotation), a pipeline switcher per team, and upsells or renewals created directly from a lead’s existing subscriptions. Lead generation now uses the Dun & Bradstreet database in place of Clearbit.

eCommerce adds AI assisted product editing, customer returns through the portal, preferred delivery dates, minimum order quantities, automatic unpublishing when stock runs out, WhatsApp abandoned cart messages, and selling without installing the Inventory app.

Inventory and Barcode

Odoo’s Odoo Experience programme highlights ministock management, new label designs, integrated CMR documents, improved allocation reports, and enhanced intercompany and interbranch flows. Ministock management offers another way to handle replenishment and minimum stock requirements, while the allocation and intercompany changes matter most to organisations running several warehouses, branches or legal entities.

Inventory valuation also gains clearer accounting visibility for cases where goods and invoices do not move at the same time:

• Goods delivered but not yet invoiced.
• Goods invoiced but not yet delivered.
• Goods received with the vendor bill pending.
• Goods billed but not yet received.

Separating these cases should make stock related accounting investigations easier during reconciliation and period end close.

The Barcode app gains bulk lot and serial number generation, manual lot entry, batch receipts from one vendor, product creation by scanning, and the option to count a total instead of scanning each unit. Light Users can be limited to the Barcode app, which pairs with the new licence described below.

HR, Attendance and Discuss

Attendance adds a photo at check-in, automatic check-out times, overtime rulesets with public holiday rates and an overtime analysis report. Appraisals gain bulk actions and 360 feedback from external contacts. Discuss adds polls, channel categories and favourites, and the Phone app shows who is on a call and can record calls with a transcript and summary.

Point of Sale

POS Presets now cover scenarios such as dine-in, take-out and delivery. According to Odoo’s preview, presets can apply the correct fiscal position and pricelist automatically, and delivery configuration becomes more detailed. For a restaurant serving several order types from one POS, this removes manual configuration from each order.

Other POS improvements include checkout performance, combos, self-ordering, hardware configuration and floor plan management. Much of the POS section of the release notes covers country e-invoicing, so retailers and restaurants should also test the reservations and WhatsApp receipts Odoo trailed before release.

Marketing Automation: from linear sequences to visual journeys

Marketing Automation moves from simple trigger, email and wait sequences to visual, conditional journeys. Odoo’s preview describes flows that combine behavioural triggers (email opens, link clicks, website visits, form submissions) with conditional branching, lead scoring, AI generated personalisation and automated promotions. A journey can now run from a website visit to a form submission, a lead score and a personalised follow up chosen by engagement, connecting Website, eCommerce, CRM and Marketing Automation.

Project profitability and the Timesheet Assistant

Project gains a new dashboard, profitability reporting and custom KPIs built with Odoo Spreadsheets, with further work across Gantt, Planning, Roles and the Manufacturing, CRM and Timesheets integrations. For service businesses, profitability can draw on timesheets, expenses, purchase orders, vendor bills, materials and employee costs.

The new Timesheet Assistant offers automatic activity tracking and smart suggestions for time entries, reducing the effort of recalling and recording work. Suggested entries should still be reviewed before they become official records.

Rental

Rental improvements focus on pricing, scheduling and integration with other apps. The highlighted addition is the Advanced Seasonal Pricelist, which supports rental pricing that varies by season.

OBox for hardware connectivity

OBox is positioned as the next generation of Odoo’s hardware connectivity, linking printers, scanners, scales and payment hardware to business processes through a more centralised architecture. For stores, warehouses and manufacturing floors, this should simplify how connected devices are discovered, configured and managed.

Odoo 20 localisation highlights

Localisations make up a large part of the Odoo 20 release notes. The table summarises the changes for five major markets; companies in any country should test their own localisation against real transactions before go-live.

Odoo 20 pricing and the new Light User licence

The pricing change that affects most companies is a new user type, the Light User, which Odoo’s pricing page describes as an employee without application access or a user with limited access. Odoo’s published prices differ by country:

Odoo sells Light User licences through an Odoo Advisor with a customised quote, so treat these as list prices and confirm the figure for your own region and user mix.

Light Users can also be limited to the Barcode app. For companies with many shop floor, retail or warehouse staff who only record their own time, leave or scans, the Light User licence can reduce the licence bill noticeably.

Several recaps state that Light Users require Odoo 20, and report changes to other plan prices. We could not confirm either on odoo.com, so request a quote for your own user mix and region from Odoo or your partner.

The lowest cost Odoo 20 upgrade is often not a new feature but moving the right people onto Light User licences.

What we left out, and why

We have excluded claims that do not appear in the official release notes. Some Odoo 20 feature lists circulating online mention an “OWL 3.0” web client, native GraphQL endpoints and Bluetooth thermal printing for offline POS. None of these appear in the release notes we reviewed, and at least one such list was published weeks before the keynote. They may appear later in the code or the developer documentation; until then, we do not treat them as announced.

The same discipline applies to the country sections. Where a partner recap reported a country change we could not find in the release notes, such as Canadian CPA 005 batch debits, we have flagged it as unverified rather than presenting it as fact.

What developers should prepare for in Odoo 20

Odoo 20 is a technical release as well as a functional one, and Odoo 19 customisations should be reviewed rather than carried forward unchanged. Odoo’s Odoo Experience programme includes a dedicated session on the Python framework for Odoo 20, and the security model changes with the removal of record rules.

Before migrating custom work, development teams should review:

• Python models and business logic, and ORM usage.
• XML views, OWL and JavaScript customisations.
• Controllers and RPC calls.
• Security definitions, model permissions and user groups.
• Third party modules and external integrations.
• Automated tests and custom reports.

Some community discussions point to further changes, such as how security definition files are named and organised. These should be validated against the final Odoo 20 framework before being adopted as development standards.

The development stack is also widening beyond Python, XML, PostgreSQL and JavaScript to include APIs, AI services and agent based workflows. Teams should therefore consider how permissions apply to AI driven actions, how external systems communicate with Odoo through MCP, and how offline synchronisation affects custom modules.

Should you upgrade to Odoo 20 now?

For most live databases, not in the first weeks after release. A structured test upgrade comes first:

1. Request a test upgrade of a copy of your database and check that your custom modules install on 20.0.
2. Review custom modules and security for framework, ORM, view, JavaScript and access rights compatibility, since record rules are removed.
3. Check integrations: APIs, payment gateways, eCommerce connectors and other third party services.
4. Validate data and accounting: accounting configuration, inventory valuation, historical data, reports, reconciliation and your country localisation.
5. Test end to end workflows rather than individual screens, including offline, warehouse and hardware connected scenarios where you will use them.
6. Price AI credits and Light Users for your user mix before you rely on either.
7. Choose a go-live date away from month end and your tax filing dates.

For customised databases, a structured path works best: assessment, custom module review, refactoring, testing, staging and then production.

Frequently asked questions about Odoo 20

1. When was Odoo 20 released?

Odoo 20 was unveiled by Fabien Pinckaers in the opening keynote of Odoo Experience in Brussels on 24 September 2026. Odoo has since published the official Odoo 20 release notes on odoo.com.

2. What are the biggest new features in Odoo 20?

The biggest changes are AI agents that create and update records, an offline mode, a simplified access rights model that removes record rules, extensive accounting improvements and a new Light User licence for employees with limited access.

3. Is AI included in the Odoo 20 subscription?

No, according to the release notes. All AI features now need credits bought through In-App Purchase (IAP), and the pricing page states that IAP credits are not included in any plan.

4. What can AI agents do in Odoo 20?

AI agents in Odoo 20 can create and update records, including from instructions in an uploaded PDF, run from scheduled and automated actions, ask the user before exceeding their tool call limit, and connect Odoo to other systems through MCP (Model Context Protocol).

5. Does Odoo 20 work offline?

Yes. Odoo 20 introduces an offline mode in which users can create, edit, archive, delete and search records without a connection, which is most useful for field staff and warehouses with unreliable connectivity.

6. How does Odoo 20 change access rights?

Odoo 20 removes record rules and places the domain directly on the access right. Standard databases become simpler to manage, but custom modules that define their own record rules need their security reviewed and retested before upgrade.

7. What localisation changes does Odoo 20 include?

Odoo 20 updates many country localisations. Examples include a redesigned US Sales Tax Report, an “Avalara Included” AvaTax option for the US and Canada, multi-company HMRC VAT submission in the UK, IRAS and SFRS aligned reports in Singapore, and TDS, Composition Scheme and Schedule III support in India.

8. What is an Odoo Light User?

A Light User is an employee without application access or a user with limited access. Light Users can manage their own HR items, view Planning, use POS as an employee, read Knowledge and scan barcodes, but cannot use Sales, Purchase, Projects or Accounting. Odoo lists it at US$8.90 per month in the US, £7.00 in the UK and Rs 195 in India.

9. Should we upgrade to Odoo 20 immediately?

For most live databases, no. Run a test upgrade on a copy of your database, review custom record rules, test your country localisation against real transactions and schedule go-live away from month end and tax filing dates.

10. What should developers check before migrating from Odoo 19 to Odoo 20?

Developers should review Python models, ORM usage, XML views, OWL and JavaScript customisations, controllers, RPC calls, security definitions, third party modules, integrations, automated tests and custom reports, then follow a staged path from assessment and refactoring through testing and staging to production.

11. What is new in Odoo 20 Marketing Automation?

Odoo 20 replaces linear email sequences with visual, conditional journeys that combine behavioural triggers such as email opens, link clicks, website visits and form submissions with branching, lead scoring, AI generated personalisation and automated promotions.

How Aarav Solutions can help with Odoo 20

Odoo 20 is best approached as both a technical migration and an opportunity to rethink how ERP, automation, integrations and AI work together. The value lies in knowing which changes fit your existing processes, which customisations need attention and where new capabilities create measurable operational benefit.

Aarav Solutions supports businesses with Odoo ERP from offices in the US, UK, Canada, Singapore and India. To plan your Odoo 20 assessment or upgrade, talk to our Odoo team.

Sources

• Odoo 20 release notes
• Odoo pricing