Odoo 20: AI Features, Module Updates and Upgrade Guide (2026)
Share via
Share via
Marcie Nguyen
Marcie is a skilled writer at Havi Technology focusing on creating content for marketing, eCommerce, point of sales, and ERP solutions. With over 8 years of experience in the retail, eCommerce and ERP technology sectors, Marcie is dedicated to providing insightful answers to business owners of all scales.
TABLE OF CONTENTS
Odoo 20 is the upcoming major version of the Odoo ERP platform, currently associated with the September 2026 release window. This article looks at Odoo 20 through the official Partner Days preview presented by Product Owner Luc Nailis, with a focus on the AI features, module updates, and upgrade questions that matter most for business readers. Because that source is a roadmap rather than a final release note set, the right way to read Odoo 20 at this stage is as a set of visible directions, not a locked list of delivered functionality.
So far, the clearest signals point to AI spreading across everyday workflows, meaningful updates across website, commerce, finance, services, and productivity tools, and a release path that current users should start thinking about now. The practical question is not only what Odoo 20 may include, but how those changes could affect timing, upgrade planning, and whether acting on Odoo 18 or 19 still makes more sense before the new version arrives.
1. AI Across Odoo 20 Workflows
AI in Odoo 20 looks less like a single headline feature and more like a direction spreading across everyday workflows. The roadmap places AI in accounting, helpdesk, record updates, and website work, which suggests Odoo is trying to reduce friction inside tasks people already do instead of pushing them into a separate AI-only layer.
That matters because embedded AI is often more useful than isolated novelty. If Odoo follows through on these themes, the practical value will come from faster handling of information, lighter admin effort, and broader day-to-day assistance across both operational and customer-facing work. At this stage, though, the roadmap shows direction, not a final measure of how autonomous or mature each AI feature will be in production for many business teams.
AI in Accounting, Helpdesk, and Record Updates
The roadmap shows AI in several practical back-office and service workflows, including Accounting for non-CFOs, Create/Update, and Helpdesk. Taken together, those signals point to AI being used for support, summarisation, and easier handling of records and decisions, especially where users need help understanding information quickly or moving work forward with less manual effort. That is a meaningful direction, but it is still best read as an embedded-assistance layer rather than proof of broad end-to-end autonomy.
AI in Website and Content Changes
Website AI is one of the clearest signs that Odoo 20 is pushing AI beyond internal operations and into customer-facing digital work. Here, the value is not just faster content drafting. Website AI matters because it sits closer to editing pages, adjusting content, and making website changes easier to execute inside the same platform. That makes AI in Odoo 20 feel more woven into day-to-day workflows across teams, not limited to one specialist use case.
2. Website, eCommerce, and Marketing in Odoo 20
Website, eCommerce, and marketing form one of the broadest Odoo 20 clusters, covering discoverability, editing, customer journeys, and campaign execution. That matters because many roadmap roundups focus on AI or headline product changes, but Odoo’s own preview gives substantial space to how businesses build pages, structure discoverability, improve customer journeys, and run campaigns inside the same ecosystem.
Performance, SEO, and Editing in Odoo 20
In Odoo 20, website improvements go well beyond cosmetic design changes. The roadmap points to lower loading time and asset loading time, SEO-related work such as microdata or JSON-LD, redirect improvements, and fixes for no-index, sitemap, and canonical URL issues, alongside broader editor, theme, blog, snippet, form, and accessibility improvements. Together, these suggest a push toward websites that are easier to manage and better structured for both users and search systems.
Key roadmap signals here include:
If Odoo follows through on this cluster, the practical gain is not just a nicer editor. It is better discoverability, smoother usability, simpler site maintenance, and cleaner structured output for search engines and AI-driven retrieval.
eCommerce and Marketing Workflows in Odoo 20
Odoo 20 treats eCommerce and marketing less as surface-level add-ons and more as operational parts of the customer journey. Odoo previewed automated cross-sell, standalone catalogue pages, return management, rating requests, and a promotion progress bar on the commerce side, while the marketing side includes new mailing blocks, templates, dynamic mailing lists, heavier file handling, and new automation actions. That makes this cluster important because it touches the full customer journey, from product discovery and conversion support to post-purchase experience and campaign execution.
Key roadmap signals here include:
Taken together, these are the kinds of changes that can support stronger retention, cleaner conversion paths, and more practical campaign delivery rather than just adding isolated marketing features.
3. Accounting and Finance in Odoo 20
Accounting and finance in Odoo 20 look less like a dramatic reinvention and more like a practical move toward flexibility, visibility, and usability. The roadmap points to changes such as Pay from Odoo, prices included or excluded at the product level, multiple IDs for partners, reconciliation on any account, a public accounting website for localisation data, and AI-assisted accounting support for non-CFO users.
Together, these suggest a direction focused on reducing workarounds, widening usability, and making finance operations easier to adapt across real business scenarios.
More Flexible Accounting Workflows in Odoo 20
Odoo 20 points to accounting workflows becoming easier to configure around the way businesses actually transact. Reconciliation on any account suggests more flexible handling of accounting logic, while price included or excluded on products and multiple partner IDs point to cleaner transaction setup and less rigid record handling.
In practice, these kinds of changes matter because finance teams often end up building workarounds when pricing logic, identifiers, or reconciliation behaviour do not fit operational reality. If these roadmap items land well, they could support fewer exceptions, more adaptable transaction handling, and an easier fit for varied accounting processes.
More Accessible Finance Information in Odoo 20
Finance information in Odoo 20 appears to be moving beyond specialist use and becoming easier to surface, explain, and navigate. A public accounting website for localisation data, alongside the “accounting for non-CFOs” direction, points toward accounting information becoming easier to work with across a wider group of users.
That matters because accessibility here is not just about interface polish. It means finance workflows may become more understandable for decision-makers and operational users who need useful financial visibility without working like accountants all day. If Odoo 20 delivers this well, the practical gain could be broader financial usability across the business, not just better tools for finance teams alone.
4. POS, Sales, and Commerce Operations in Odoo 20
POS, sales, and commerce operations are among the most commercially concrete parts of the Odoo 20 roadmap. The changes here are not just about adding more options. They point to easier front-of-house execution, smoother transaction handling, and broader flexibility in how products, pricing, self-ordering, payments, and rental models are configured.
For retailers, hospitality teams, and other businesses running customer-facing operations, that makes this one of the clearest applied-business clusters in the preview. It is also the part of the roadmap that feels easiest to translate into day-to-day operational impact.
POS Setup and Daily Operations in Odoo 20
Odoo 20 suggests a POS setup that is simpler to deploy and less cumbersome to run day to day. “POS: making hardware easy” is reflected in simpler printer setup, no more certificate imports, local network access from Chromium browsers, and a generally more stable environment. The roadmap also adds floor plan editing, combos applied automatically, snoozed product availability, broader kiosk and payment-terminal support, and bookings linked to POS orders.
Key roadmap signals here include:
In practice, these changes matter because they reduce setup friction, support smoother restaurant and retail operations, and remove small but costly points of daily operational drag.
Sales and Commerce Configuration in Odoo 20
In Odoo 20, sales and commerce changes are shaping up as a broader expansion of commercial flexibility rather than one single breakthrough feature. Odoo previewed changes around tag management, variant images, extra fields and specifications, fulfilment without stock, section templates, UOM price rules, promotions, loyalty expiration, pay on invoice, portal improvements, editable price on variants, payment flow improvements, and rental updates such as unified pricelists, dashboards, and seasonalities.
Key roadmap signals here include:
Taken together, these changes could make Odoo 20 a better fit for varied selling models, more configurable pricing strategies, and commerce operations that need more flexibility than a standard one-size-fits-all sales flow.
5. Services, Scheduling, and Productivity in Odoo 20
In the Odoo 20 preview, services, scheduling, and productivity look like a coordinated effort to make day-to-day execution easier to organise and easier to see. The roadmap connects calendar upgrades, appointment management, timesheet assistance, field service planning, and project margin visibility in a way that suggests stronger coordination across internal work, customer-facing scheduling, and operational follow-through.
That matters because for many businesses, the real friction is not a lack of features, but a lack of clean visibility across time, tasks, resources, and outcomes. In that sense, this cluster looks less like a set of isolated productivity tools and more like an attempt to connect scheduling, execution, and reporting more tightly inside Odoo 20.
Calendar and Appointments in Odoo 20
Calendar and appointment changes in Odoo 20 suggest more flexible scheduling control rather than simple interface polish. Odoo previewed personal booking pages, multi-calendar management, multiple calendar synchronisation, synced work locations, activities in calendar, easier linking to records, and availability logic such as slot buffering. Appointments also gain refreshed webpages, recurrence and capacity improvements, and POS floorplan integration in the back end and front end.
In practice, this matters because it can support smoother coordination, clearer availability management, and a more usable scheduling layer for businesses that depend on bookings, service slots, or shared resource planning.
Timesheets, Field Service, and Projects in Odoo 20
Timesheets, field service, and project changes in Odoo 20 bring execution, scheduling, and visibility into closer alignment. Odoo previewed a timesheet timer, a timesheet assistant, field service moving under planning, worksheet properties for field service, and project reporting with actual and projected margin views. Together, these changes create a closer link between the work being done and the way it is tracked, scheduled, and evaluated.
For service and project-heavy businesses, this could make coordination more usable in practice, especially when teams need to connect execution on the ground with planning decisions and reporting outcomes.
6. Payroll, Mobile, Sign, and Phone Updates in Odoo 20
In the Odoo 20 preview, payroll, mobile, sign, and phone updates may look lighter than the bigger commerce or website clusters, but together they reinforce an important theme: everyday usability. These are the kinds of changes that matter when teams interact with Odoo repeatedly through routine admin, approvals, signatures, calls, and mobile access. Rather than feeling like leftover features, they point to a broader effort to reduce friction in the smaller workflows that often shape adoption and daily efficiency.
Payroll and Mobile Simplification in Odoo 20
On the payroll side, the roadmap highlights a new payroll dashboard, no more work entries, and pay runs, while the mobile side points to a new interface. Taken together, these changes suggest a push toward simpler daily handling rather than more complexity.
In practice, that matters because payroll is one of the areas where repetitive admin and process friction are felt quickly, and mobile usability affects how comfortably teams can work outside a desk-bound setup. If Odoo delivers these updates well, the gain could be more straightforward routine usage, lower admin friction, and easier operational handling for teams that need payroll visibility and mobile access without extra process overhead.
Sign and Phone Capabilities in Odoo 20
Sign and phone updates in Odoo 20 strengthen the platform’s ability to support end-to-end workflows inside the same system. Sign includes automated activities and activity plans, automated sign requests, wider country support, touch support and mobile UI for the editor, and broader signed-document handling. Phone adds the ability to buy numbers in 100+ countries, callflow configuration, and an audio, video, and transcript player.
In practical terms, these updates matter because they can make communication, approval, and documentation flows smoother inside the same system, reducing the need to jump between separate tools just to complete routine tasks from start to finish.
Should You Wait for Odoo 20 or Act on Odoo 18/19 Now?
Whether you should wait for Odoo 20 or act on Odoo 18/19 now depends less on roadmap interest and more on business timing. For most teams, the better decision will come down to current operational pain, implementation urgency, and whether today’s mature Odoo versions already solve the real problem well enough. The practical question is not simply whether Odoo 20 looks promising, but whether waiting creates more value than acting now.
When Waiting for Odoo 20 Makes Sense
Waiting for Odoo 20 can make sense when a project is still at an early evaluation stage, when no implementation is yet underway, or when the roadmap themes look especially relevant to the business model being considered. It may also be reasonable for teams that want more final release clarity before committing, especially if their current setup is still workable and the urgency to change is low. In those cases, waiting is less about chasing novelty and more about avoiding premature decisions.
When Acting on Odoo 18/19 Is the Better Decision
Acting on Odoo 18 or 19 is often the better decision when existing inefficiencies are already costly, fragmented workflows are slowing the business down, or a mature version can address the operational problem without waiting for a future cycle. In practice, implementation timing often matters more than version curiosity. For teams weighing today’s proven capability against tomorrow’s roadmap, it can help to review the scope of the Odoo 19 official release and the workflow gains in Odoo 18’s best features. If Odoo 18 or 19 already meets the real business need, delaying a worthwhile project for roadmap-stage possibilities can create more drag than value.
How Should Current Odoo Users Prepare for Odoo 20?
For current Odoo users, interest in Odoo 20 is most useful when it turns into preparation rather than speculation. The roadmap can show where the platform may be heading, but the real value comes from understanding how ready your current setup is for a future upgrade path. The most practical preparation steps are to review customisations, integrations, and business-critical dependencies, then clean up avoidable complexity before the release window gets closer.
What to Review in Your Current Odoo Setup
The first step is to review the parts of your current environment that are most likely to shape future upgrade efforts. In most businesses, the biggest risks do not come from the version number itself, but from the way the current system has evolved over time.
Key areas to review include:
This review matters because upgrade planning is rarely just about comparing features. It is about understanding what in the current setup is tightly coupled, still necessary, or carries more risk than expected.
What to Clean Up Before a Future Odoo Upgrade
Preparation also means removing complexity that no longer adds enough value to justify the effort it creates. A cleaner system is not only easier to upgrade; it also makes it easier to judge whether a future version will genuinely improve the business. For a practical view of how businesses can approach upgrade preparation more deliberately, this Odoo Business Show session offers a useful reference point.
Useful cleanup priorities often include:
Cleaning up does not guarantee an easier upgrade, but it usually reduces avoidable friction and gives teams a clearer view of what genuinely needs to be carried forward.
The roadmap already points to several clear Odoo 20 directions, but the most important questions now are about release timing, final confirmation, and local rollout readiness between now and September 2026.
What to Watch for Odoo 20 Between Now and September 2026
The Odoo 20 preview already outlines several meaningful directions, but the key watchpoints now are release timing, final confirmation, and local rollout readiness. Those are the issues most likely to shape how businesses interpret the roadmap between now and September 2026.
When Will Odoo 20 Be Officially Released?
Odoo 20 is currently expected in the September 2026 release window, with Odoo positioning the launch around Odoo Experience rather than as a fully detailed release-note milestone yet. For practical planning, that means businesses should watch for more formal release communication, then pay attention not just to launch timing but also to how quickly the new version matures after release.
What Still Needs Confirmation Before Release?
What still needs confirmation before release is the final feature scope, rollout depth, and implementation quality behind the broad Odoo 20 themes already visible in the roadmap. A roadmap is not the same thing as final release notes, so visible direction and final delivered detail should not be treated as identical. That is why the broad themes can already be useful for planning, even while detailed behaviour and final delivery may still evolve before release.
Will Odoo 20 Have Community and Enterprise Editions?
Odoo 20 is expected to retain the familiar Community and Enterprise edition structure, although businesses should still watch formal release communication for any edition-specific scope, packaging, or rollout details. For most readers, the practical takeaway is that the edition model is unlikely to be the main uncertainty at this stage, but the final packaging still needs confirmation closer to release.
Will Australian Localisation Be Ready at Release?
Australian localisation may not be fully ready on day one of the Odoo 20 release, so businesses should treat local readiness as something to verify rather than assume. In practice, localisation, payment flows, payroll handling, partner validation, and implementation readiness often matter just as much as the global release itself. That makes local rollout readiness something to monitor carefully between now and September 2026, especially for businesses with market-specific requirements.
Odoo 20 already looks like an important release direction, especially around AI features, practical module updates, and day-to-day usability. But for most businesses, the real value will not come from following the roadmap alone. It will come from judging which changes are relevant, what still needs confirmation, and how your current setup should be reviewed before the release window gets closer. If Odoo 20 is already shaping internal discussions, the next sensible step is to assess whether your business is really waiting for new features or simply ready for a better upgrade plan.
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:
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.