Odoo 19 vs. 20: Which Version Better Supports Your Daily Operations?

Every year, Odoo gives its users something new to look forward to. In 2025, Odoo 19 made AI a practical part of everyday ERP work. This year, Odoo Experience 2026 in Brussels introduced Odoo 20, a major version built around agentic AI and autonomous workflows that take over more of the repetitive tasks in your daily workflows.

For companies already on Odoo 19, this is a good problem to have. The current version is stable, capable, and still supported, and the new version promises faster work and smarter decisions across departments. So the choice is mostly about timing and fit: how much your business would gain from Odoo 20’s capabilities right now, and how ready your current setup is to make the move.

To make that decision easier, let’s look at Odoo 19 vs. 20 side by side. Some of the changes in Odoo 20 are easy to notice, like AI agents that can execute tasks instead of only suggesting them. Others are deeper in the system, affecting how users are licensed, how integrations connect, and how certain daily workflows are organized. Both kinds of change matter when you’re considering an upgrade, so we’ll look at each one in terms of what it means for the way your teams work today.

Odoo 19 and Odoo 20: What Each Version Brings to the Table

Before comparing features, it helps to see what each version was designed to do. Both share the same modular foundation, so companies can run sales, accounting, inventory, HR, and their website from a single Odoo instance, with data shared across multiple departments instead of split into data silos across separate ERP systems.

The key difference is the role AI plays. Odoo 19 introduced it as an assistant, and Odoo 20 lets it take action on its own. That change affects how teams automate their work and what an upgrade involves. Below, we’ll look at each version’s strengths, limits, and the businesses it fits best.

A closer look at Odoo 19

Odoo 19 was released in September 2025 and is available on Odoo Online, Odoo.sh, and on-premises, in both Odoo Community and Odoo Enterprise. It made AI capabilities part of everyday work, with AI that responds to manual prompts and helps users draft, summarize, and analyze information.

Its main strengths include:

• Ask AI and AI agents: assistants in Odoo CRM, Odoo Accounting, and Odoo Helpdesk that help sales teams and finance teams work through customer records, invoices, and tickets faster
• AI in automation: prompt-based server actions and support for OpenAI and Google Gemini, with usage billed through AI credits
• Finance tools: OCR-based reconciliation of bank statements and ISO 20022 support for payment files
• Sustainability and industry coverage: an ESG module for tracking Scope 1–3 carbon footprint and preparing CSRD/ESRS reports, plus 50+ industry packages

The main limitation is that AI in Odoo 19 suggests rather than acts, so a person still has to review and complete each step. It also keeps the older integration methods that many third-party integrations rely on. Odoo 19 fits businesses that went live recently and want a stable, well-supported system.

A closer look at Odoo 20

Odoo 20 was released in September 2026 at Odoo Experience 2026, with the same hosting and edition options. Its biggest change is agentic AI. AI agents can create and update records and run multi-step workflows in the background, always within each user’s access rights and with approval steps where needed.

Other key changes include:

• New licensing model: new user access tiers, including a Light User role for people who only need limited access
• Offline mode: the ability to keep working without an internet connection, which is especially useful for teams on site
• Field service in Planning: Field Service is no longer a separate app, and features like route planning, worksheets, and the live technician map are now part of Odoo Planning
• New industry packages: hotels, construction, real estate, and auto repair, in addition to the ESG module and packages carried over from Odoo 19

As a major version, Odoo 20 also includes technical changes. XML-RPC has been removed, and the frontend now uses OWL 3, so custom code and older integrations may need updates. Some workflows in Odoo Payroll and Odoo Planning also work differently. Odoo 20 fits businesses ready to automate complete processes, as well as companies starting a new implementation.

Odoo 19 vs. 20: A Comprehensive Comparison

Odoo 20 updates almost every part of the platform, from how AI handles daily tasks to how users are licensed and how external systems connect. The sections below go through each major change area by area, showing how Odoo 20 compares with Odoo 19 and what it means for the teams that use it every day.

AI and automation: From assistive to agentic

AI is where Odoo 19 and Odoo 20 differ the most, and for many businesses it will be the main factor in the decision. In both versions, AI works with the same data your teams already use. The difference is how much of the work it can finish without someone stepping in.

What AI does in Odoo 19

In Odoo 19, AI works alongside your team. It answers questions, drafts content, and makes suggestions, but a person still decides what happens next and starts each action. The main AI features are:

• Ask AI: a built-in assistant that answers questions and runs database queries in plain language
• AI fields: fields that generate their own values from record data, such as summaries or classifications
• AI agents in Odoo CRM, Odoo Accounting, and Odoo Helpdesk: assistants that suggest next steps, draft replies, and help process records
• Prompt-based server actions: automations that call AI through a prompt, using OpenAI or Google Gemini, with usage billed through AI credits

This setup removes a lot of manual work from writing and research. However, most automation still depends on manual triggers or rule-based automation. That works well for predictable steps, but it can’t handle tasks that require judgment partway through.

What changes with agentic AI in Odoo 20

Odoo 20 lets AI carry a task through to completion. Instead of drafting something for a person to finish, AI agents can create and update records and run multi-step workflows in the background, based on instructions written in plain language. The key new features include:

• Action-taking AI agents: agents that create and update records within each user’s access rights, with approval steps where required
• Background workflows: multi-step processes that run with less manual intervention, such as preparing documents, updating related records, and notifying the right people
• AI in automated actions: AI reasoning added to automation rules, so they can handle cases that don’t match a fixed condition
• Autonomous accounting audit: AI review of accounting entries that flags issues for finance teams to check
• Natural-language search and voice interactions: a more user-friendly way to find information across the database and to work with Odoo by voice
• Native MCP server in Odoo Enterprise: support for Model Context Protocol, so external AI tools and third-party apps can connect to Odoo data

Project creation is a good example of the difference. In Odoo 19, a project manager might use AI to draft a task list for a new client, then set up the project and assign the tasks manually. In Odoo 20, an AI agent can take the signed quote, create the project, add tasks from a template, and assign owners, so the manager only needs to review and approve.

Accounting and finance changes

Odoo 19 already gave finance teams a solid base, with AI-assisted bookkeeping and dependable bank reconciliation. Odoo 20 builds on that in three areas: paying bills, handling taxes, and reporting across multiple entities. Each change removes a step that previously required an export, a workaround, or a spreadsheet.

Payments and bank reconciliation

In Odoo 19, accounting teams can use OCR to read bank statements and reconcile them against open entries. ISO 20022 support means payment files follow the format most European banks accept. The usual process is to prepare payments in Odoo, export the file, and then upload it to the bank’s portal.

Odoo 20 removes the export and upload steps by adding direct payments:

• Direct bill payment through PISP: vendor bills can be paid from inside Odoo through a payment initiation service provider, without switching to online banking
• SEPA direct credit: euro transfers can be sent directly from Odoo
• Mass bank reconciliation: large batches of transactions can be reconciled at once instead of line by line
• Bank transaction rules: recurring transactions, such as rent, subscriptions, or bank fees, are matched and categorized automatically

Consider a company that pays around 200 supplier bills a month. With Odoo 19, someone exports a payment batch, logs into the bank, uploads the file, and waits for confirmation. With Odoo 20, the same bills are approved and paid from one system, and the payment status is updated in Odoo right away.

Tax handling

Odoo 20 also adds flexibility for businesses that sell in several local markets or work with mixed pricing models:

• Tax toggle on invoice lines: tax can be switched on or off for individual lines without changing the product’s default settings
• Tax-included or tax-excluded price per product: each product can follow its own pricing logic, which helps businesses that sell both B2C and B2B
• Multiple tax IDs per contact: a single customer or vendor record can store separate VAT numbers for each country where it’s registered

These changes cover functional gaps that previously required add-ons or custom fields. For example, a distributor selling to a customer registered for VAT in both Germany and France can now invoice each entity with the correct tax ID from the same contact record.

Chart of accounts and consolidation

Odoo 20 also changes how the chart of accounts is structured. Parent/child accounts let finance teams group detailed accounts under summary lines, and optional account codes allow companies to use the naming conventions they prefer. Advanced multi-ledger consolidation lets groups combine results from several entities directly in Odoo. This is especially useful for groups with complex reporting requirements.

Inventory, purchasing, and manufacturing

For operations teams, Odoo 20 focuses less on new screens and more on the decisions behind them: how much to stock, what to reorder, which vendor to choose, and what to produce first. Many of these decisions used to rely on someone’s experience or a spreadsheet next to Odoo. In Odoo 20, more of them come from the data already in the system.

Inventory and replenishment

In Odoo 19, replenishment is based on reordering rules that someone sets up and maintains manually. That works when demand is steady, but the min/max values get outdated quickly when sales change with the season or a product suddenly sells faster.

Odoo 20 improves inventory tracking in several ways:

• Smarter stock-level calculations: more accurate forecasts of available stock that include incoming and outgoing moves
• Smart replenishment: min/max rules generated from demand history, so reorder points adjust as sales patterns change
• Automated COGS updates: cost of goods sold updates automatically when actual costs differ from expected ones, which reduces manual cost corrections at month-end
• Shipment handling improvements: clearer, more efficient processing of incoming and outgoing deliveries

For example, a garden supply retailer typically raises its stock levels before spring and lowers them in autumn. With Odoo 19, someone has to update hundreds of reordering rules twice a year. With Odoo 20, the rules adjust based on previous seasons, which helps the business stay ahead of demand instead of reacting after shelves are empty.

Purchasing and vendor management

Purchasing in Odoo 20 relies more on data. Instead of reordering from the usual supplier by default, buyers get support in choosing who to buy from and checking that bills are correct:

• Purchase recommendations: suggested quantities and timing based on stock levels and demand
• Vendor analysis and vendor ratings: a score for each supplier based on delivery times, accuracy, and pricing
• Automated bill matching: vendor bills matched to purchase orders and receipts automatically, with only exceptions sent to a person for review

Consider a purchasing team working with 40 suppliers. Vendor ratings show which ones regularly deliver late or send partial shipments, so buyers can move volume to more reliable suppliers. Automated bill matching also means the accounts payable team only reviews bills that don’t match, instead of checking every bill line by line.

Manufacturing

Odoo 20 also improves how production is planned and tracked on the shop floor:

• Improved work-order flows: fewer clicks for operators to start, pause, and complete work orders
• BOM comparison: two versions of a bill of materials can be compared side by side
• Gantt scheduling: a timeline view of work orders across work centers for capacity planning
• Kanban-based production priorities: production orders can be reordered by dragging cards, so the shop floor sees changes in real time

BOM comparison is especially useful for manufacturers that update products often. For example, a furniture maker switching to a new hinge supplier can compare the current BOM with the revised one before the next production run. This shows which components, quantities, and costs have changed, so purchasing and production can confirm the update before it reaches the shop floor, avoiding operational disruption caused by a mismatched part.

Website, eCommerce, Point of Sale, and marketing

For businesses that sell online, in store, or both, Odoo 20 focuses on the work around each sale: creating pages, getting found in search, making checkout easier, and following up with customers afterward. Many of these tasks used to require a separate tool, an add-on, or a developer. In Odoo 20, more of them are part of the platform.

Website and SEO

Odoo’s website builder has always been easy to use, but filling it with content took time. Odoo 20 adds AI-assisted page creation and content generation, so teams can create a full page layout from a short description and generate first drafts of landing pages, blog posts, and product descriptions.

Technical SEO is also more complete:

• Native JSON-LD: structured data that helps search engines understand products, prices, and reviews
• Redirects: built-in redirect management when pages move or URLs change
• Canonicals: canonical tags that help prevent duplicate-content issues across similar pages
• Sitemap: an automatically maintained sitemap for search engine crawlers

For example, a manufacturer launching 30 new products can use AI to draft product descriptions from item specifications, then have the marketing team edit them instead of writing each one from scratch. Structured data is added automatically, so the products are ready to appear in rich search results.

eCommerce and checkout

Odoo 20’s eCommerce updates focus on the steps between browsing a product and receiving it:

• Enhanced product experiences: richer product pages that show more information to help customers decide
• Automatic cross-sell: related products suggested automatically, without setting up each pairing by hand
• Delivery-date selection: customers choose when their order arrives during checkout
• Checkout improvements: a simpler checkout flow that works with the local payment gateways customers already use
• Returns management: return requests handled inside Odoo instead of by email

These changes are designed to improve conversion rates and repeat purchases. For instance, a furniture retailer can let customers pick a delivery date at checkout, which reduces failed deliveries and the follow-up calls they usually cause.

Point of Sale

Odoo 20 makes Point of Sale setup quicker and easier to run day to day:

• Browser-based hardware connection: printers, scanners, and payment terminals connect through the browser, without managing certificates
• Automatic combos: meal deals and product bundles applied automatically when the right items are in the order
• Visual floor-plan editor: restaurant and café layouts updated by dragging tables into place

For example, a café opening a terrace for the summer can add the outdoor tables to its floor plan in a few minutes. Staff can start taking orders right away, and combo pricing is applied without anyone having to remember the discount.

Marketing automation

Odoo 20 brings omnichannel automation together, so campaigns can run across email, SMS, and WhatsApp in a single flow, with AI helping draft messages and personalize content. This gives marketing teams a clear view of how each customer interacts across channels, rather than separate results in separate tools.

For example, an online store can send an email reminder about an abandoned cart, follow up on WhatsApp if the email isn’t opened, and send a personalized offer by SMS. The whole sequence runs in Odoo, so the team can focus on high-value opportunities like loyal customers and larger accounts instead of setting up each message manually.

Field service, planning, communication, and HR

Most Odoo 20 updates add to existing features, but this area is different. Here, some workflows have been reorganized. For existing users, that means learning new screens and processes, but the result is fewer separate apps to manage and fewer steps between planning work and getting paid for it.

Field Service merged into Planning

Field Service is no longer a separate app in Odoo 20. Its features are now part of Odoo Planning, so technician schedules and the rest of the team’s shifts are managed in the same place. Planning now includes:

• Live technician map and route planning: dispatchers see where technicians are and plan efficient routes between jobs
• Worksheets, travel fees, and vehicle inventory: job reports, travel charges, and van stock are handled in Planning
• Offline field service: technicians can keep working in areas with weak or no signal
• Integrated scheduling: field jobs and in-house shifts share one calendar

For Odoo 19 Field Service users, the main adjustment is location. Dispatchers will assign jobs in Planning instead of a separate app, and technicians will open their tasks and worksheets from a new starting point. A short retraining session before go-live usually makes this a smooth transition.

Communication and calling

Odoo 20 expands communication tools with improved calling and call transcription. Calls can be transcribed and saved to the related record, so a support agent or salesperson can review what was agreed without relying on handwritten notes.

HR and Payroll changes

Odoo Payroll changes the most. Work Entries, the layer that turned attendance and time off into payable hours, has been removed. In its place, Odoo 20 offers:

• Pay Runs view: a single screen for preparing and processing payslips in batches
• Pre-payment alerts dashboard: missing data or unusual amounts are flagged before payslips are confirmed
• Time off and scheduling inside payslips: absences and shifts appear directly on each payslip

For example, a payroll team used to check work entries for conflicts before generating payslips. With Odoo 20, the team opens the Pay Runs view, fixes anything on the alerts dashboard, and confirms the batch. Before upgrading, it’s worth checking how historical data from previous pay periods carries over.

New user tiers and the Light User role

Odoo 20 changes more than features. It also changes how users are counted and billed, which can affect your total cost of ownership even if you never use a single new feature. That makes this section important in any ERP comparison between versions.

New user tiers and the Light User role

Odoo 20 introduces a lower-priced user type and updates its plans:

• Light User: a new license at €7.90 a month, available when there is at least one full user, for employees who only use Odoo for their own HR and operational tasks
• Standard plan: unchanged at €19.90 per user per month
• Custom plan: about 20% more expensive, Odoo’s first price increase in four years, and now the plan for companies that customize Odoo through Odoo Studio, agentic AI, custom developments, or the API
• Employee counting: any active employee record in the HR app that isn’t linked to an active non-portal user account counts as a Light User, even if that person never logs in

For example, a company with 50 office staff and 150 warehouse employees can move the warehouse team to Light Users and lower its licensing costs considerably.

Offline mode and mobile

Odoo 20 makes it easier to work away from a desk:

• Offline mode: employees keep working without a connection, and changes sync when they reconnect
• Mobile web workflows: full Odoo processes run in the mobile browser
• Native app: better for quick, frequent tasks on the go

Odoo Online, Odoo.sh, or on-premises

How you upgrade depends on your hosting and edition:

• Odoo Online: Odoo runs the upgrade, and your team tests the workflows
• Odoo.sh and on-premises: you use the Odoo Upgrade service, test custom modules in staging, and follow a migration plan
• Odoo Community vs. Odoo Enterprise: several key features, including the native MCP server, are Enterprise-only

Technical changes, performance, and integrations

Most Odoo 20 updates are visible to users, but this section is about the parts IT teams work with. These changes rarely show up in demos, yet they usually decide how long an upgrade takes.

Framework and API changes

Odoo 20 updates the technical foundation in three main ways:

• OWL 3 frontend framework: the interface runs on a new version of Odoo’s web framework, so custom screens and widgets may need updates
• JSON-2 API as the standard: the JSON-2 API was introduced in Odoo 19 and is now the main way external systems connect to Odoo, using API keys instead of login and password
• XML-RPC removed: the XML-RPC and JSON-RPC endpoints were scheduled for removal in Odoo 20, so integrations that still use them need to be updated first

Performance and scalability

For companies with large datasets, Odoo 20 also improves infrastructure:

• Read replicas: heavy reporting can run on a separate database copy, which keeps day-to-day work fast while reports are being generated
• Python requirement: the minimum version moves from Python 3.10 to Python 3.12
• PostgreSQL requirement: the minimum version moves from PostgreSQL 13 to PostgreSQL 16

What this means for custom modules

Not every customization needs the same amount of work:

• Usually adapts with minor updates: custom fields, business logic, reports, and automation rules
• Often needs rework: custom interface components built on the older frontend framework and changes that override core screens
• Needs to be rebuilt: third-party integrations that connect through XML-RPC

For example, a distributor connects its legacy warehouse management system to Odoo through an XML-RPC connector. The connector stops working in Odoo 20, so before the upgrade the team rewrites it to use the JSON-2 API with an API key and tests it in staging. Once that’s done, the rest of the upgrade can go ahead as planned.

When to Stay on Odoo 19 and When to Move to Odoo 20

Both versions are strong options, so the right choice depends on your current situation more than on the feature list. Use the table below to find the scenario closest to yours.

Most businesses will match more than one scenario. If some rows point to upgrading and others point to waiting, the scenarios about technical setup, like integrations and customizations, usually determine the timing. The scenarios about features show what you’ll gain once you’ve upgraded.

Get Your Odoo System Ready for Odoo 20 with Glorium Technologies

Odoo 20 adds a lot, but how much your business gets out of it depends on how well the move fits your current system. The right timing, a clear view of your customizations, and careful testing make the difference between an upgrade that pays off and one that disrupts daily work.

As an official Odoo partner, Glorium Technologies helps companies plan and deliver that move. Our technical discovery phase takes 2–4 weeks and gives you a review of your custom modules and integrations, a risk assessment, and a realistic estimate. From there, our Odoo developers handle upgrade compatibility planning, rework custom modules for Odoo 20, and rebuild integrations, for example by replacing XML-RPC connectors with the JSON-2 API. Every project includes documentation and knowledge transfer, so your team stays in control after go-live.

We’ve taken the same approach on recent projects. For a B2B eCommerce company, we connected Odoo with QuickBooks Online and Avalara AvaTax so sales tax across state, county, and city jurisdictions is calculated automatically. For a contract manufacturer moving off JobBOSS, we tested Odoo alongside the old system and switched over one module at a time, so production never stopped and job turnaround became 31% faster.

Ready to see what Odoo 20 would take for your business? Book a 15-minute intro call with our Odoo experts.

FAQ