Our hopes and dreams for Odoo 20

Closing the "last mile" in Accounting

Odoo 19 has introduced significant improvements to closing processes and reporting. Still, it’s one step away from becoming a truly end-to-end, locally compliant accounting engine. 

To get there, we’re hoping that Odoo 20 will introduce:

Government reporting interfaces

The most critical missing piece is the native integration of specific interfaces for mandatory government reporting, such as ELSTER in Germany. 

Currently, this often requires third-party bridges. A direct export feature would be far more convenient, and would also signal that Odoo is ready to handle compliance processes fully.

Financial forecasting

Odoo 18 introduced budgeting, and Odoo 19 brought in advanced closing features. 

We wish for Odoo 20 to introduce native financial forecasting by leveraging the existing Budget views. 

This would allow users to project future performance based on current numbers rather than just comparing actuals against a static plan.

Reconciliation

For Odoo 20, we want to see a reconciliation view that works seamlessly for companies of all sizes and finally closes functional gaps created by previous versions.

Breaking the 10,000 user ceiling

For Odoo to arrive fully in the Enterprise segment, its technical foundation needs to mature.

Odoo 19 already pointed in the right direction with significant architectural updates; we hope Odoo 20 will continue this evolution by advancing features such as: 

Full offline mode

Odoo 19 introduced offline mode; however, it’s still limited and unreliable for day-to-day use.

In Odoo 20, we want to see refined front-end caching to make daily use smooth. 

This would be a great improvement, especially to use Odoo on a mobile network or low-bandwidth connections. 

Read replica (R/R) databases

Odoo 19 added framework-level support for read replicas, allowing one database to handle reads while another handles writes. 

Our hope for Odoo 20 is a full implementation to boost performance further. 

For one, this would enable Odoo to support over 10,000 simultaneous users - a notable increase, given that the maximum capacity pitched in recent years was 5,000 users.

With this technical bottleneck out of the way, Odoo would also be free to invest more in corporate-level features.

Increasing the use of agentic AI 

The native AI app in Odoo 19 is a great start, but it currently functions primarily as a chatbot.

Our wish for Odoo 20 is a shift toward agentic automation.

Instead of chat interfaces that wait for prompts, agentic AI works directly within the process to execute tasks.

This advancement would align Odoo with industry trends toward fully autonomous AI-enhanced processes, where the system actively drives the process, and humans intervene only to approve.

Automating price visibility for bundles & upsells

Odoo 19 introduced a great new feature that allows grouping sale lines to hide section prices, but this automation relies on Sale Order Templates.

If you start from a blank quote or add optional products on the fly, the grouping logic fails to trigger, forcing users to adjust lines manually.

We hope Odoo 20 moves this logic to the Product form. We need settings to designate specific items — whether they are bundles, upsells, or special offers — to never display a standalone price. This would ensure correct formatting even when building a quote from scratch.

Native frame agreements for subscriptions

Managing multiple subscriptions per customer has been a challenge since the frame agreement feature was discontinued after v16.

Currently, if a customer purchases subscriptions at different times or under different terms, syncing and merging them is complicated, often requiring customisations or third-party apps.

Almost every company that sells subscriptions has customers with more than one, so this limitation affects nearly all Odoo Subscription users today. Making it a standard feature would therefore be very valuable.

We’d love to see Odoo 20 introduce an automatic way to merge multiple subscriptions, handle upsells and add-ons, and ensure all calculations remain accurate.

Proactive replenishment of inventory

Odoo 19 introduced automated replenishment based on forecast, but currently, it exists only in a basic form.

We hope Odoo 20 expands on this feature to make inventory management truly proactive. 

The system should reliably anticipate needs and trigger supply chain actions with minimal manual oversight.

Improved handling of mixed pallets & complex UoM packaging

Odoo 19 merged unit-of-measure and packaging features, creating some issues in practice. 

Specifically, the system currently assumes products in a package are identical, which rarely matches the reality of mixed logistics.

We need Odoo 20 to refine the packaging logic to handle common use cases such as mixed pallets - containing multiple products of different sizes or weights - independently. 

This would be especially valuable for manufacturing companies to use the standard feature without workarounds.

Independent translations on the website

The website builder is getting stronger with each version, but translations are still a pain.

Currently, edits in one language can break pages in another, and managing blocks is cumbersome. 

Our big wish for Odoo 20 would be fully independent language pages, where users won’t have to rely on in-text translations.

This would give much more control over multilingual sites and prevent double work or broken pages when translating content.