Odoo 20 · Teams · Decision
What's new in Odoo 20: what each team gains
A new version is only worth the days it frees up. See what Odoo 20 changes for your salespeople, buyers, warehouse staff, accountants, shop floor and HR.
Each team finds its everyday tasks first, technical details after. The points that call for a decision from you are flagged plainly.
Does Odoo 20 deserve a project at your company?
Turn the question around: which team loses time today on a task that version 20 simplifies? If the answer is clear, the project has its reason to exist. If it stays vague, you gain by preparing rather than rushing.
Three changes reach all your staff, whatever their job:
- Access rights you read at a glance: record rules fade away and a single screen gathers what used to allow viewing, editing or deleting.
- The "Light" role: an occasional user gets restricted access, without opening the whole application to them.
- Offline mode: your teams create, edit and archive records without a network, then get back the searches already run.
What does each team gain in the first week?
Six teams, six tasks that change their day.
Sales: the quote goes out sooner
A dashboard sits above the quotes. Margin is corrected right on the line and any order becomes a quote template. Commissions are computed on collected amounts.
Buyers: month-end closes without a spreadsheet
An assistant compares, line after line, what is received but not invoiced and what is invoiced but not received. A promised delivery date finally makes each supplier's punctuality readable.
Warehouse: less manual entry
Odoo suggests replenishment minimums and maximums from your history. A goods return starts in one click, with a CMR document already filled in.
Accountants: bank lines match almost on their own
Automatic reconciliation handles a good share of transactions. Duplicate payments are spotted and overdue reminders are managed from a single screen.
Shop floor: a schedule you read effortlessly
Continuous production, a Kanban by planned week, Gantt views of work orders. The actual cost of each order appears on closing.
HR: each departure follows its thread
From notice to effective date, an employee leaving becomes a tracked process. Salary simulation and clock-ins validated by a manager complete the picture.
Which tasks can you hand to an AI agent?
After a discreet first appearance with Odoo 19, AI gains ground: 52 AI modules in the Enterprise 20 edition, against 15 in Odoo 19.
Create and fix on your behalf
An agent creates or edits records on request, even from a PDF of instructions. If it hesitates, it asks you and you answer with a click on a button.
Work without being asked
An automated or scheduled action wakes the agent. Its exchanges stay viewable for thirty days, and it asks for your approval when it reaches its tool call limit.
Keep control of the AI provider
You pick the provider and Odoo chooses the model that fits each task. Voice, images for the website and mailings, and questions asked about a file in preview all benefit.
Plug in your other tools
The MCP connection links your database to your external tools. Agents exist for sales, purchasing, stock, projects, support, email marketing and calendar.
Migrate now or prepare: which signals guide you?
Auguria benchmark: Odoo 20 is the latest major version and the publisher supports the last three, that is 20, 19 and 18. Your starting version sets your pace.
Migrate now if
- Your database is on Odoo 17: the publisher stopped covering it as soon as Odoo 20 arrived.
- You are on Odoo.sh: the host requires a supported version, so the switch is a must.
- Your Odoo 17 lives on a dedicated server: it keeps running, but without any new fix, and the exposure of the instance becomes a risk.
Prepare calmly if
- You are on Odoo 19, the previous and most deployed version.
- You are on Odoo 18, still supported: you have time to build the project.
- None of the new features above answers a pressing need of your teams.
In every case, choose your date rather than have it forced on you.
Which topics need your green light before the switch?
A version is also judged by what it removes. Five topics call for a decision:
- Work at your customers' sites: the Field Service application is discontinued. Planning takes over with a real-time technician map and travel expenses. Review the organisation and train your teams.
- HR team: goodbye to work entries and to the link between Planning and Payroll. Remote work and the org chart move into the Employees application.
- French payroll: we check with you the availability of the French payroll modules in the Odoo 20 Enterprise sources analysed, before any commitment.
- Printed documents: two print engines now coexist. The watermark or background image under your reports has no successor in this version. Try your templates on a copy of the database.
- Custom developments: access rights, print engine and icons change. Each module is reviewed and ported.
How to decide in four meetings?
1
The inventory
We list your modules, reports, access rights and field service work.
2
Sorting the priorities
We set the new features against your priorities. A feature that matters justifies the jump, otherwise staying on 19 is a sound choice.
3
The dress rehearsal
We replay the migration on a copy of your database. Your key users run their real flows on it.
4
D-day
We set the switch away from your peak periods and train your teams on the screens that evolve.
What if you compare with the other versions?
One page per version to measure the gap before choosing.
What teams ask us about Odoo 20
It depends on your version and your hosting. From Odoo 17, the switch is urgent on Odoo.sh. From Odoo 18 or 19, you prepare at your own pace.
We migrate for a feature that is useful to your business: that is what gives the project its value.
No. Each AI feature consumes credits bought through IAP. We assess the useful usage before activating them.
Not without work. They must be ported, because access rights, the print engine, icons and the API evolve. We audit each module before the migration.
They remain usable but need checking. The new print engine coexists with the old one and the watermark disappears with no replacement. We test your documents on a copy.
The Field Service application stops and Planning replaces it. You get the technician map, travel expenses and customer satisfaction. Team organisation is prepared before the switch.
We check these modules in the Odoo 20 Enterprise sources with you, before any decision.
Odoo 20 for your teams: yes, no or not yet?
A free audit sets your database against Odoo 20 and hands you a clear recommendation: migrate, wait or prepare.