Odoo 18 · Gains by team · Stay or migrate
Odoo 18 new features: what each team gains
A version is judged by what your teams do in less time, not by its feature list.
We sorted the Odoo 18 new features by workstation: the accountant, the salesperson, the warehouse operator, the shop floor lead, the cashier and the person who looks after access.
You leave with a simple verdict for your database: stay on this version or prepare the next one.
Is Odoo 18 still worth it?
Yes, and the reason fits in one sentence: Odoo 18 is still inside the vendor's support window. Your users work on a version that still receives its fixes.
This version mostly polished daily work. Screens answer under a /odoo address that you can read and edit by hand. An error shows its details, and the user passes them to support in one click.
Dashboards can be shared from one team to another. Installable mobile apps cover barcode, point of sale, attendance, the self-service kiosk and the shop floor. Industry packs (bakery, cleaning, dropshipping, weddings) give a head start to anyone starting from scratch.
Who saves time with Odoo 18?
Six workstations, six gestures that change.
Your accountant reviews instead of retyping
Bank statements in PDF are read by text recognition. Duplicate vendor bills are spotted more reliably. Peppol sending, loans with repayment schedules and analytic budgets join the toolbox.
Your salesperson builds tailored offers
They offer combo products and track commission plans without a spreadsheet. Price lists export as PDF, CSV or XLSX. Expected revenue updates as soon as the quote is validated.
Your warehouse operator picks in waves
Picking waves start automatically. Delivery rounds and returns are handled from a single screen. The barcode scanner understands RFID and collects the signature on delivery.
Your shop floor lead sees the whole year
The master production schedule shows a yearly view and replenishes by itself. Operators run operations in the order reality dictates, not the one set by the routing.
Your cashier checks out faster
The point of sale is completely redesigned. Customers pay by QR code and follow their order on a remote screen. On the shop side, in-store pickup and mega menus widen the buying journey.
Your access owner removes passwords
Passkeys allow a password-free login that stands up to phishing. Each employee manages them from their own profile.
Should you stay on Odoo 18 or migrate?
Here are our decision guidelines. Each one can be checked in a single meeting, on your own database.
- You stay if your database is stable, if your teams expect nothing from later versions and if your module inventory fits on one page.
- You prepare what comes next if you combine custom or third-party modules, in-house connectors or public web pages under the /odoo path.
- You migrate now if your Odoo.sh hosting demands a supported version or if a feature of version 19 or 20 solves a real business problem.
The vendor's calendar weighs as much as the features. Three major versions are followed at once: 20, 19 and 18. When the next one is released, yours will leave that trio, just as 17 did when Odoo 20 arrived.
Hosted on Odoo.sh, you cannot stay on an unsupported version: the migration goes into your calendar. On your own server, nothing stops, but no more security fixes arrive. It is up to you to weigh what your database exposes and what it contains.
Reaching Odoo 20 takes two consecutive jumps: Odoo 19 first, then Odoo 20. We test them one after the other on a copy, even if your users never see the intermediate version.
How do we set the right calendar with you?
1
We count
In-house developments, third-party extensions, printed reports, connectors, web pages published under /odoo: the list sizes the project.
2
We choose the target
Odoo 19 or Odoo 20, compared against your module list. We flag the foreseeable breaking points: packaging, employee contract, access rights.
3
We rehearse
Each step is played on a clone first. Your key users redo their Monday morning tasks there. We adjust, then rerun until the green light.
4
We switch over
Go-live lands in a quiet period. Your teams are trained on the new version's screens before they work in it.
What about the other versions?
One page per version, to compare before you decide.
Odoo 16: Knowledge and dashboards
Go back to the early days of document apps and faster screens.
Odoo 17: a redesigned interface
New ergonomics, assisted writing and the Shop Floor app.
Odoo 19: AI inside the screens
Built-in AI, guided accounting close and ESG tracking.
Odoo 20: the most recent
Simpler access rights, a reworked print engine and the longest support coverage.
Your questions about Odoo 18
The answers we are asked for most.
Yes. With 19 and 20, it makes up the trio the vendor maintains.
Readable /odoo addresses, passkeys, combo products, commission plans, bank statement reading, Peppol sending and the redesigned point of sale.
On Odoo.sh, a version outside support is not tolerated. Put the migration in the calendar well before the deadline so you can work without stress.
Your database still starts. Only the vendor's security fixes disappear. The more open the instance is to the Internet and the more sensitive its data, the more waiting costs.
Two successive steps, 19 then 20. We validate each one on a clone of your database before moving on to the next.
The product form drops the Storable and Consumable types in favour of Goods, complemented by a tracking field. Your import templates and custom developments need a review.
Yes, if public pages sit on that path: they clash with the backend. We move or redirect them during the migration.
Not if your database is stable. Still, it is better to choose the date than to have it imposed. Start the inventory early when you have many custom modules.
Pick your date before it picks you
The free audit lists your modules, assesses the effort of each jump and hands you a migration calendar.