Odoo 20 – What the New 2026 Release Brings and How DACH SMEs Should Prepare

Odoo 20 – What the New 2026 Release Brings

Odoo SA has confirmed the date for the official unveiling of version 20: Odoo Experience 2026 runs 24–26 September 2026 at Brussels Expo. Fabien Pinckaers will deliver the opening keynote on 24 September at 08:30 under the title "Start your journey on Odoo 20". Until then there is no official release-notes entry, no Odoo 20.0 branch on runbot, and no final feature freeze – but enough concrete signals from Odoo Partner Days on 2 April 2026, the Odoo 19.2 release, and the OXP25 conference in September 2025 to give mid-market companies a sound preparation foundation.

This guide frames what is actually coming in 2026, which expectations are realistic, and which DACH-specific gaps will remain.

Quick verdict: Odoo 20 will land in September 2026 with three major themes: agentic AI (autonomous tasks rather than chat assistance), an Owl 3 frontend rewrite, and the final retirement of the XML-RPC interface. Four new industry modules (Hotel, Construction, Auto Repair Shop, Custom Industrial Equipment) and a fully reworked mobile UI round out the picture. For DACH customers, ELSTER integration remains an open gap – Odoo 20 still does not deliver here. Stable patch release: expected November 2026; production migrations should be planned for Q1 2027.

When does Odoo 20 actually arrive?

Until September 2026, all feature lists remain provisional. The points below are based on official Odoo 19.2 documentation, OXP25 announcements, and the partner-tier roadmap from 2 April 2026 – every claim is sourced in the references at the end.

The three major themes of Odoo 20

1. Agentic AI – not chat any more, execution

Odoo 19 brought an AI assistant into most modules in 2025 – useful for summaries, reply suggestions, and simple search. The partner community consensus: helpful, but not the leap many had hoped for. Odoo 20 responds directly to that. The platform shifts from assistant to agent: tasks are no longer just explained but autonomously executed.

Concretely announced for Odoo 20:

• Autonomous lead distribution in CRM based on past conversion patterns
• Audit Agent in accounting, automatically reviewing quarterly reconciliations and flagging anomalies
• Helpdesk sidekick that summarises tickets and drafts replies based on similar historical cases
• Database-wide natural-language search ("Show me the latest order from supplier X")
• Website Builder with multi-step instructions, applying visual and content changes simultaneously
• Background time tracking from activity signals (PRs, channel activity), privacy-friendly

Companies serious about the AI lever should evaluate these features in production from spring 2027, once the first stable patches and partner experience are available.

2. Owl 3 – the frontend gets rewritten

The entire web frontend has been built since 2022 on Odoo's own reactive framework Owl 2. Odoo 20 brings Owl 3 – per the roadmap, completely rewritten, mobile-first, with significant performance gains. For customers with custom modules or Studio customisations, this means: every frontend change must be reviewed during migration to 20 and possibly reworked.

Migration relevance: Owl major-version transitions are historically the most time-intensive part of an Odoo migration. Companies with their own web components (buttons, widgets, custom views) should budget two to three times the effort compared to a backend-only adjustment.

3. XML-RPC and JSON-RPC retire on self-hosted and Odoo.sh

This was publicly announced at OXP25 in September 2025: the classic XML-RPC and JSON-RPC interfaces will be finally removed in Odoo 20 – not only on Odoo.sh and Odoo Online (already removed there in 19.1), but also in the on-premise variant. The successor is a modern JSON-2 API with OAuth 2.0 authentication.

Who is affected? Practically every customer with third-party interfaces: bank connectors, shipping services, ERP bridges, custom mobile apps, BI tools (Power BI, Tableau, Metabase). These interfaces must be migrated to JSON-2 before the upgrade.

Practical checklist:

1. Inventory every external API access to your Odoo instance
2. Assess the migration effort per interface
3. Plan the API-call switch in the respective third-party tools
4. Test in a sandbox instance before cutover

We recommend starting the API inventory now – Q2/Q3 2026 – regardless of the planned migration timing.

New industry modules

Per the partner roadmap, Odoo 20 brings four new industry-specific modules:

Particularly relevant for DACH customers: hospitality and custom industrial equipment cover sectors that previously needed third-party industry add-ons. Companies in these sectors should evaluate Odoo 20 explicitly.

Mobile rewrite and POS improvements

The mobile UI is being rebuilt from the ground up per the roadmap: stacked fields instead of horizontal scrolling, touch-first, larger tap targets, significant performance improvements. A noticeable upgrade for field service, warehouse, and service technicians.

In POS:

• Drag-and-drop floor-plan editor
• Browser-based hardware detection on the local network (no separate IoT box needed for many devices)
• Kiosk mode for self-service terminals
• Auto-triggered combo deals

Accounting and e-commerce

Accounting in Odoo 20:

• "Pay from Odoo" – direct payment of incoming invoices via SEPA with single-signature batches
• Multiple partner IDs per business partner (VAT, commercial register, LEI)
• Universal account reconciliation
• Dynamic tax-inclusive/exclusive logic per product

E-commerce in Odoo 20:

• Native connectors for TikTok Shop, Lazada, and extended Amazon marketplace support
• Extensions to the storefront redesign introduced in 2025

The DACH gap in 2026

Honesty here: Odoo 20 contains no confirmed improvements in DACH localisation beyond what already shipped in Odoo 19. Specifically:

• ELSTER integration (direct submission to the German tax authority): remains open. On the wishlist of several DACH partners, but not on the official roadmap. Companies that need ELSTER in production continue to combine Odoo with DATEV or specialised tax tools.
• GoBD and DATEV: no new features in the master documentation. The existing localisation remains productive and compliant – but no new features are landing.
• XRechnung / ZUGFeRD e-invoicing for B2B (Wachstumschancengesetz): as of April 2026 no specific Odoo 20 announcements. Possibly in the OXP26 keynote – worth watching.
• Itsme identity verification in the Sign module: extended to 30+ countries, but Itsme is Benelux, not DACH-relevant.

What does this mean in practice? Odoo 20 is a clear upgrade for German mid-market companies in performance, AI, and new industries – but not a breakthrough in German compliance. The localisation add-ons (ODION, manaTec, much. Consulting) remain important.

Migration: when and how

If you run Odoo 19

Recommended approach:

1. Wait for the first stable patch release (expected 20.0.1 late October/November 2026)
2. Set up a migration sandbox once the patch is available
3. Audit custom modules for Owl 3 compatibility
4. Migrate API consumers to JSON-2
5. Production migration: Q1 2027

Effort: 4–8 weeks for lightly customised setups, 8–12 weeks for setups with substantial customisation.

If you run Odoo 18

Recommended two-step migration: first to Odoo 19 (in Q4 2026), then to Odoo 20 (Q2/Q3 2027). Two smaller migrations are historically less risky than a single jump across two versions.

If you run Odoo 17 or older

Path: 17 → 18 → 19 → 20, or a paid version-skip migration via upgrade.odoo.com. Begin planning now – the right path is project-dependent.

Confirmed breaking changes (already in 19.2)

Three changes have already landed in Odoo 19.2 and must be considered before any jump to 20:

1. Field Service module discontinued, functionality integrated into Planning
2. Work Entries removed from Payroll – leave and attendance data flow directly into payslips
3. Flexible material consumption is the new default in manufacturing orders

Customers using these modules in production must navigate the migration path within 19.x.

What the community sees critically

Expectations of Odoo 20 are high; the risks are openly discussed in the partner community:

• Owl 3 + RPC retirement at the same time: more breakage than the 18→19 jump. Expect higher effort on custom modules and third-party apps.
• OCA modules (Odoo Community Association) historically lag two to three months behind the major release. Companies dependent on OCA extensions plan accordingly.
• App Store quality: a persistent community concern. Before any third-party module: check maintenance history, issue tracker, last update.
• Mid-cycle module retirements (like Field Service in 19.2) have raised concerns in the partner community. It is unclear whether the pattern will repeat.

What we recommend for DACH mid-market companies

1. Inventory now: list every external API access to your Odoo instance – this is the single biggest migration single-point-of-failure.
2. Custom-module audit Q3 2026: which adjustments can be replaced by Odoo 20 standard? Which need reimplementation?
3. Watch OXP26: the 24 September 2026 keynote will provide final clarity. We will publish an update to this guide after OXP26.
4. Plan migration for Q1 2027: after the first stable patch, before fiscal year-end. By then OCA modules will have caught up, larger bug fixes will be in, and the move is economically plannable.
5. Continue maintaining DACH localisation: ELSTER, DATEV document transfer, XRechnung – these remain in partner hands. We continue to maintain the corresponding configurations.

Final take

Odoo 20 is a step forward, not a platform change. The three big themes – agentic AI, Owl 3 frontend, JSON-2 API – affect every customer, in different intensities. Companies that plan cleanly and start early will be on a materially more productive platform 12 to 15 months after release than they are today on Odoo 19. Companies that wait risk that third-party interfaces delay the migration and the competitive advantage from the AI features is lost.

We accompany DACH mid-market companies through the preparation and migration to Odoo 20 – from the API inventory to post-cutover hypercare.

Schedule a preparation workshop for Odoo 20 →

This guide is based on public sources as of April 2026: the Odoo Experience 2026 event page, Odoo 19.2 Release Notes, OXP25 conference recordings, Odoo Partner Days from 2 April 2026, and publications from various Odoo partners. We will update this article after OXP26 (24–26 September 2026) with the officially confirmed feature scope.