Odoo 20 is attracting attention from businesses planning their next ERP upgrade. New versions can introduce useful improvements across business applications, performance, usability and technical architecture—but an upgrade should be based on verified requirements, not release rumours.
As of 28 August 2026, Odoo has publicly promoted upcoming demonstrations of Odoo 20 features, but a complete final feature list and production release notes are not yet publicly available. That distinction matters. Screenshots, development branches and community discussions may show work in progress that can change before the final release.
This guide explains what is confirmed, which business areas should be evaluated when official details arrive, and how to prepare an existing Odoo environment safely.
What is officially confirmed about Odoo 20?
Odoo has confirmed that Odoo 20 is the next major version and that new-feature demonstrations are planned at official Odoo events. Until Odoo publishes final release notes and production documentation, individual feature claims should be treated as provisional.
For decision-makers, the practical lesson is simple:
- Do not approve a migration based only on social-media previews.
- Do not assume a development-branch feature will ship unchanged.
- Do not promise users functionality until it is documented and tested.
- Evaluate the final version against your actual workflows, integrations and local requirements.
SmartDesk will update this article as Odoo publishes authoritative Odoo 20 documentation.
Business areas to evaluate when Odoo 20 details are released
The following are evaluation areas—not claims that a particular unannounced feature is guaranteed.
1. User experience and daily productivity
Review whether common actions require fewer clicks, whether search and reporting are clearer, and whether mobile workflows work for your field and warehouse teams. A visual change has business value only when it reduces errors or saves measurable time.
2. Accounting and Saudi localization
Saudi businesses should test taxes, invoice formats, credit notes, journals, payment reconciliation and ZATCA Phase 2 workflows. Never assume a version upgrade automatically preserves localization behaviour, especially where custom accounting logic or third-party modules are involved.
3. Sales, CRM and subscriptions
Evaluate lead handling, quotations, approvals, pricing, recurring revenue and customer communications against your current process. Confirm that custom automation still triggers correctly.
4. Inventory, purchasing and multi-warehouse operations
Test receipts, deliveries, internal transfers, replenishment, landed costs, lots, serial numbers, valuation and multi-company routes. Retailers and distributors should reproduce real high-volume scenarios rather than testing only a simple sales order.
5. Point of Sale
For multi-branch retail and hospitality, test session opening and closing, offline behaviour, payments, returns, discounts, loyalty, stock updates, accounting entries and peripheral devices. POS issues can interrupt revenue, so staged testing is essential.
6. Manufacturing and maintenance
Manufacturers should validate bills of materials, work orders, costing, subcontracting, quality, maintenance and traceability. Any custom production logic needs a separate migration assessment.
7. Website, eCommerce and integrations
Check themes, checkout, payment providers, shipping, product feeds, tracking and integrations with platforms such as Shopify, Amazon, Salla, WhatsApp or custom APIs. An ERP upgrade can affect both backend methods and frontend assets.
8. Automation, reporting and AI-assisted workflows
Evaluate new automation or AI-assisted capabilities against security, access rights, data quality and measurable outcomes. A feature should not be enabled merely because it is new; it should solve a defined business problem with appropriate review controls.
Should you upgrade to Odoo 20 immediately?
Not every business should upgrade on release day.
An early upgrade may make sense when:
- A confirmed Odoo 20 capability solves an important limitation.
- Your current version is approaching the end of your internal support policy.
- You have a clean database with limited customization.
- Your team can test a staging environment thoroughly.
- Your integrations and third-party applications support Odoo 20.
Waiting may be safer when:
- Critical third-party modules are not ready.
- Your system contains undocumented customizations.
- POS, accounting or ZATCA workflows cannot tolerate instability.
- You are in a financial close, peak retail period or major operational rollout.
- No clear business benefit justifies the migration cost.
Odoo 20 upgrade-readiness checklist
Step 1: Inventory the current environment
Record the Odoo version and edition, database size, user count, installed applications, custom modules, Studio changes, scheduled actions, reports and external integrations.
Step 2: Classify customizations
For every customization, decide whether it is still needed, replaced by standard functionality, must be migrated, or should be retired. Unnecessary customization increases cost and upgrade risk.
Step 3: Review data quality
Check duplicate contacts and products, invalid taxes, inconsistent units of measure, archived records, reconciliation issues and incomplete master data. Migration is an opportunity to correct controlled data issues—not carry them into a new version.
Step 4: Confirm application compatibility
Verify that every third-party application supports Odoo 20. A module being listed for an older version does not mean it is safe to install on the new version.
Step 5: Build a staging migration
Never test a major upgrade first on the production database. Use a recent copy in an isolated staging environment and prevent it from sending real emails, payments or external API transactions.
Step 6: Test complete business scenarios
Create test scripts for lead-to-cash, purchase-to-pay, inventory, accounting close, POS, manufacturing, ZATCA, integrations and reporting. Test both normal and exception cases.
Step 7: Reconcile the results
Compare opening balances, receivables, payables, inventory valuation, taxes, journal entries, document counts and key reports between the old and migrated systems.
Step 8: Plan rollback and go-live
Define the migration window, data freeze, backups, responsible people, acceptance criteria, user communication and rollback decision. A successful technical migration is not enough; operations must be able to continue.
Common Odoo upgrade mistakes
- Migrating every customization without challenging its value
- Testing only screens instead of complete workflows
- Ignoring accounting and inventory reconciliation
- Forgetting scheduled jobs and external webhooks
- Allowing staging to email real customers
- Upgrading during a business-critical period
- Assuming a successful database conversion means the project is complete
How SmartDesk helps
SmartDesk supports Odoo version assessments, custom-module audits, staging migrations, compatibility fixes, testing, reconciliation and production go-live planning. Our approach focuses on protecting operational continuity while removing unnecessary complexity.
If you are considering Odoo 20, start with an upgrade-readiness review before committing to a timeline.
Book a free Odoo health check or explore our integration and migration services.
Frequently asked questions
Has Odoo published the complete Odoo 20 feature list?
Not at the time this article was prepared. Odoo has promoted official demonstrations, but businesses should wait for final production documentation before treating individual feature claims as confirmed.
Can we migrate directly from Odoo 17, 18 or 19 to Odoo 20?
The appropriate path depends on Odoo's official upgrade service, edition, hosting model, database condition, custom modules and third-party applications. Assess the actual database before selecting a path.
Will custom modules work automatically?
No. Custom modules must be reviewed and commonly require manifest, Python, XML, JavaScript, asset, security or ORM changes plus functional testing.
How long does an Odoo upgrade take?
It depends on database size, customizations, integrations and testing scope. A clean standard database may be straightforward; a heavily customized production environment can require a structured multi-week project.