Contact Us

Odoo 20: New Features, AI Agents, and Upgrade Guide for Australian Businesses

Odoo 20 is the September 2026 major release of the open-source Odoo platform, unveiled at Odoo Experience in Brussels from 24 to 26 September 2026. For Australian businesses with growing or complex operations already running Odoo, the practical question is whether it is worth upgrading now.

The headline changes are autonomous AI Agents, native Model Context Protocol (MCP) support, full offline mode, and the merger of Field Service into Planning. Australian localisation continues its progressive journey: Odoo 19 delivered Single Touch Payroll Phase 2 and Peppol readiness, and Odoo 20 adds Basiq open banking for bank synchronisation.

This guide covers the shipped features, practical AI considerations, and the upgrade decision most Australian teams are weighing.


What Is Odoo 20 and When Was It Released?

Odoo officially launched version 20 at Odoo Experience 2026 in Brussels from 24 to 26 September 2026, marking the platform’s 20th major release since its origins as TinyERP. It follows Odoo 19 (September 2025) and shipped with autonomous AI Agents, native MCP (Model Context Protocol) support, a merger of Field Service into Planning, and full offline mode.

The release was presented by Odoo founder and CEO Fabien Pinckaers. Odoo 20 is available on Odoo Online, Odoo.sh, and on-premises, with Community and Enterprise editions both continuing.

offer odoo upgrage impact scan

What’s New in Odoo 20: The Key Changes

Beyond AI Agents (covered in the next section), Odoo 20 ships five headline changes: full offline mode, a refreshed interface, the discontinuation of Field Service, accounting on autopilot, and updates across eCommerce, Point of Sale, Sales, and Website.

Full Offline Mode

Odoo 20 works entirely offline: records can be created, read, updated, or deleted without a connection. Changes sync automatically when connectivity returns.

Odoo 20 offline mode Havi Technology

Odoo 20 offline mode: records sync automatically when connectivity returns. Source: Odoo Experience 2026.

Interface Refresh and Material Symbols

The interface keeps the layout of version 19 but refreshes icons to Google’s Material Symbols, places content on white backgrounds against lighter chrome, and adds subtle interaction animations.


Odoo 19 (top) vs Odoo 20 (bottom): Material Symbols icons and lighter chrome. Source: Odoo Experience 2026.

Field Service Merges into Planning

The Field Service app is discontinued in Odoo 20. Its features (live map, route planning, worksheets, travel fees, customer equipment tracking, and website booking forms) now live inside Planning. Existing Field Service users will find their workflows preserved but re-homed after the upgrade​.


Field Service scheduling now inside the Planning app in Odoo 20. Source: Odoo YouTube.

Accounting on Autopilot: PISP, AI Assistant, and Payroll Simplification

Accounting in Odoo 20 ships with embedded payment initiation through Payment Initiation Service Providers, removing the need to export payment batches or scan QR codes. An AI assistant answers questions about your company’s finances from the accounting data in your database. Payroll changes in 20: work entries and the Planning–Payroll link are removed, and work-entry types merge with time-off types. For Australian payroll, that means cutting over at a pay-period boundary, never mid-period.


Embedded payment initiation in Odoo 20: bills paid directly from the system. Source: Odoo Experience 2026.

"Does that mean I don’t need an accountant anymore? No, of course not. But if your accountant is running your accounting on Odoo, at least you will be sure to pay him for valuable advice instead of low added value tasks." - Wynand Tastenhoye, Odoo Business Development Manager, Odoo Experience 2026

Other Notable Updates

Module

Key Changes in Odoo 20

eCommerce

Pay on Invoice, portal-driven returns, WhatsApp abandoned cart follow-up.

Point of Sale

Order lines convert to combos automatically, products can be snoozed from the menu, an order-specific QR code lets diners order and pay from the table, and multiple currencies work at one till.

Sales

Description-only lines, editable margins, tax include-or-exclude toggle

Website

AI assistant that builds pages from prompts, native llms.txt support for AI-engine readability


5 minutes to know if you’re ready for Odoo 20.

Check your modules, integrations, and localisation gaps. Free.

Take the self-assessment →


AI Agents in Odoo 20: What They Can Do, What They Cost, and What to Consider

Odoo 20 introduces autonomous AI Agents that create records, update records, respond to files, and trigger automated actions. All capabilities require Odoo In-App Purchase (IAP) credits, shifting AI from a free experiment to an ongoing cost. For Australian businesses, three considerations matter more than the feature list: data readiness, human oversight, and privacy compliance.

What AI Agents Can Do in Practice

In practice, AI Agents in Odoo 20 can:

  • Create records from a text or voice prompt (a sales order from an email, a lead from a scanned business card, a project from a brief)
  • Update existing records when triggered by scheduled events or field changes
  • Respond to questions about files in Odoo Documents
  • Generate images for marketing or product listings
  • Request specific permissions before acting outside their default access rights


AI Agent in Odoo 20 creating project tasks from a PDF and requesting user permission. Source: Odoo Experience 2026.

How MCP Opens Odoo to External AI Tools

The Model Context Protocol (MCP) lets external AI tools (Gemini, OpenAI, Claude, and others) read from and write to an Odoo database with the user’s access rights preserved. Nothing needs to be built on the Odoo side beyond a URL and credentials. For businesses already using external AI, MCP removes the integration layer that previously required a developer.

IAP Credits: How AI Features Are Priced

Every AI Agent capability draws on Odoo IAP credits, purchased in-app from EUR 1.00 per credit. Every new database receives 20 free credits to start. Credit usage varies by feature, task complexity, and request size. Packs range from 10 credits (EUR 10) to 1,000 credits (EUR 1,000), with no expiry.

To illustrate: an AI Agent extracting invoice data and creating the vendor bill might consume two credits per document. At 200 invoices per month, that is roughly 400 credits. Actual rates vary by task. The 20 free credits in every new database are enough to test real consumption before buying a pack. For Australian businesses, confirming local credit pricing with your Odoo implementation partner is a practical next step.

Practical Considerations Before Adopting Odoo 20 AI Agents

Fabien Pinckaers framed Odoo’s AI positioning at Odoo Experience 2026:

odoo 20 features Havi Technology Pty Ltd

Fabien Pinckaers on Odoo’s open-source AI advantage at Odoo Experience 2026.

"Odoo has an unfair advantage in AI. 2% of the open-source lines of code in Python in the world is Odoo, and all the AI LLMs are trained on open-source data." - Fabien Pinckaers, Odoo founder and CEO, Odoo Experience 2026

Beyond positioning, four considerations shape responsible adoption.

  • Data readiness first. If your data is inconsistent across systems, AI will scale the confusion, not fix it.
  • Not every workflow should be automated. Keep humans in the chain for decisions involving customer trust, financial sign-off, or team judgement.
  • Native, MCP, or custom build. Decide upfront whether native Odoo AI, an MCP-connected external tool, or a custom build fits your workflow. This prevents paying for capability you do not need.
  • Australian Privacy Act applies. AI workflows touching personal data should be documented with human oversight aligned to Privacy Act requirements.

While Odoo 20’s native AI Agents are new, Havi has deployed AI automation into Odoo for Australian clients. Our AI-powered OCR automation for a leading Australia and New Zealand B2B agency delivers 99% extraction accuracy with invoice turnaround under 30 seconds. The same practitioner considerations apply to Odoo 20’s AI Agents.

Should You Upgrade to Odoo 20 or Stay on Your Current Version?

For most Australian mid-market Odoo users, Odoo 20 is worth planning for but rarely worth rushing to on day one. The challenge is knowing what the upgrade involves for your specific database, customisations and integrations before committing to a date.

Odoo’s support policy covers the three most recent major versions. With Odoo 20 released, the supported window is now versions 18, 19 and 20. Businesses still on Odoo 16 or 17 are outside this window and face an additional 25% annual fee on their subscription if they do not upgrade.


Upgrade decision framework for Australian Odoo users considering Odoo 20.

When Upgrading to Odoo 20 Makes Sense

Upgrading makes sense if your team has workflows suited to agentic AI and your data is clean enough to feed agents reliably.

It also makes sense if Field Service is a critical workflow, because the consolidation into Planning is a change you want to control early. If you are on Odoo 18 or earlier, Odoo 20 brings enough new capability (agentic AI, accounting automation, payroll simplification) to justify skipping a version and planning one considered upgrade project.

Odoo 20 is available for all new databases. Odoo will announce when existing databases can be upgraded; we will update this page when the date is confirmed.

When Staying on Odoo 18 or 19 Is the Better Call

Staying is the better call if your setup is mature and the upgrade effort may not pay back within 12 months. If custom workflows require significant re-testing against Odoo 20, the validation cost may exceed the feature benefits. If Australian localisation requirements extend beyond Basiq into payroll, e-invoicing, or tax reporting not yet verified for Odoo 20, staying until confirmation is the lower-risk path.

Before any upgrade, understanding which Odoo 20 changes affect your existing database (removed modules, changed workflows, renamed fields) prevents surprises. Havi’s Upgrade Impact Scan identifies these for your specific setup.

Odoo 20 Pricing: What Changed and the New Light User Tier

Odoo 20 introduces a Light User tier alongside three plans: One App Free (AUD 0), Standard (AUD 34.40/user/month), and Custom (AUD 64.00/user/month). Standard AUD 34.40 and Custom AUD 64.00 are yearly-billing prices shown on Odoo’s pricing page in October 2026. Monthly billing is higher. Light User pricing and eligibility for Australia are confirmed with Odoo per client.


Odoo 20 pricing for Australian businesses, including the new Light User tier. Source: odoo.com/pricing.

Light Users can manage their own time off, expenses, attendance, and appraisals, operate inventory barcodes, and access Planning and Shop Floor workflows. Odoo is also adjusting POS access so that employees whose only system activity is Point of Sale may not require a Light User licence. Check current eligibility with your Odoo partner as conditions are being finalised.

Licence tiers, implementation costs, and ongoing support fees each contribute to the total cost of running Odoo for an Australian mid-market business, and Havi's Odoo pricing breakdown covers per-user costs, hosting options, and real implementation benchmarks across different business sizes.

Australian Localisation: A Progressive Journey Across Versions

Australian localisation in Odoo has matured version by version. Odoo 19 delivered Single Touch Payroll Phase 2, SuperStream, Peppol PINT-A-NZ e-invoicing, and Australian Taxation Office integrations. These remain in Odoo 20.Odoo 20's Australia-specific additions are a Basiq open banking integration for bank synchronisation and native integrations with ShipStation and carriers including Australia Post and New Zealand carriers (Ray Carnes, Odoo Senior Project Director, 2026).

A ShipStation connector is new in 20 (Enterprise). For Australian and New Zealand carriers, the connector is Starshipit, which covers Australia Post, StarTrack and others through one integration (Ray Carnes, Odoo Senior Project Director, 2026). Basiq open banking integration adds bank synchronisation for Australian businesses.

For teams with specific compliance needs, confirm localisation status for your modules with your Odoo implementation partner before scheduling the upgrade. Australian Privacy Act considerations also apply when AI Agents will access business data.

How to Prepare for Your Odoo 20 Upgrade

Preparation is less about the version number and more about your current setup. Two steps carry the most weight: reviewing dependencies before the upgrade window, then cleaning up avoidable complexity.

What to Review in Your Current Odoo Setup

Three things need reviewing: custom modules, integrations, and business-critical dependencies. Note which custom modules are partner-maintained, in-house, or built by unavailable vendors. Map every external connection (accounting, banking, eCommerce, logistics, email). List specialised units of measure, custom warranty processes, tailored batch transfers, and custom reporting that shape your operations.

What to Clean Up Before Any Odoo Upgrade

Four areas of cleanup pay off: workarounds, inconsistent data, unused customisations, and compliance touchpoints. Workarounds for current-version limitations often break during upgrades. Inconsistent data (duplicate records, mismatched codes) carries into Odoo 20 unchanged. Unused customisations add complexity the business no longer needs.

For Australian teams, add a compliance checklist: Single Touch Payroll Phase 2 continuity, SuperStream, Peppol PINT-A-NZ, Australian Taxation Office integrations, and Australian Privacy Act alignment if AI Agents will access personal data. Verify each with your Odoo partner before the upgrade window.

Lessons from Real Odoo Upgrade Projects

At the Odoo Business Show, TR Savage & Son’s Director Joel and Havi’s CTO Ryan shared their upgrade approach: upgrade every second or third year, review which customisations the new version replaces natively, eliminate what you can, then pass the rest to your partner for compatibility testing.

A separate project, an Australian timber manufacturer’s upgrade from Odoo 11 to Odoo 16, reinforced the same lessons at a larger version jump. The upgrade scoped four critical modules (Manufacturing, Purchase, Inventory, Sales), preserved load-bearing custom workflows (specialised UoM handling, warranty tracking, batch transfers for overseas shipments), and treated staff training as a first-class deliverable.

The lesson from both projects: upgrade success is about discipline, not version. These upgrade principles are part of Havi’s ISO 9001:2015 certified delivery process, applied consistently across every Odoo project.

Frequently Asked Questions About Odoo 20


Making a Confident Decision About Your Odoo 20 Upgrade

The right upgrade decision is the one grounded in your setup, not in the roadmap.

If you want to see AI Agents and offline mode in action, Havi runs personalised Odoo 20 demos tailored to your industry and modules. If your team is ready to plan the move, an Upgrade Impact Scan shows exactly what changes in your database, what it costs to address, and when to schedule the cutover. Havi has worked through Odoo upgrades with Australian businesses across manufacturing, timber, wholesale, distribution, eCommerce, and more.

Your setup, your team, your decision.

Article Sources

Havi Technology requires writers to use primary sources to support their work. These include white papers, government data, original reporting, and interviews with industry experts. We also reference original research from other reputable publishers where appropriate. You can learn more about the standards we follow in producing accurate, unbiased content in our AI Content Policy:

  1. Odoo (2026). Odoo 20 release notes. Odoo.
  2. Odoo (2026). Meet Odoo 20's best features. YouTube.
  3. Odoo. Odoo Enterprise Subscription Agreement.
  4. Pinckaers, F. (2026). Opening keynote: Odoo 20 and industries. Odoo Experience 2026.
  5. Pinckaers, F. (2026). Opening keynote: Unveiling Odoo 20. Odoo Experience 2026.
  6. Tastenhoye, W. (2026). ‘Accounting and fiscal compliance’ in Opening keynote: Unveiling Odoo 20. Odoo Experience 2026.
  7. Ray Carnes (2026). Things to look forward to in #Odoo 20. LinkedIn.


Disclaimer

All content on Havi's blog is provided for informational and educational purposes only. It does not constitute legal or financial. While Havi Technology strives to ensure accuracy by referencing reputable sources and industry expertise, information may not be complete, current, or applicable to every business context. Readers should seek independent professional advice before making business or operational decisions. References to third-party products or services do not imply endorsement unless explicitly stated.

Want to see how Havi can help with your ERP software implementation?

Let our dedicated team support you every step of the way.