A cellar, a basement, a building site in the middle of the countryside: the network drops, the Odoo screen freezes, and the technician jots everything down on a scrap of paper to "key in when he gets back". With Odoo 20, the web client keeps working offline and syncs when the network returns. Here is how it works, what to prepare, and what this mode does not do.
1. The problem: information gets lost between the field and the office
For the field-service companies we work with (heating engineers, chimney sweeps, removal firms, installers), the number-one objection to online software is always the same: "What happens when there is no network?". Up to Odoo 19, the answer was uncomfortable: without a connection, nothing could be saved. The result: paper notes, forgotten details, and double entry in the evening.
💡 Key takeaway
The cost of an outage is not the outage itself: it is the information re-entered later, or never.
2. What Odoo 20 does when the network drops
There is nothing to install: offline mode is part of the standard Odoo 20 web client, Community and Enterprise alike. When the connection disappears, a yellow "Working offline" badge appears in the top bar. The user can then create, edit, archive, unarchive and delete records, just as usual.
Each change is queued and listed in a dropdown under the badge, with its status: "Created", "Edited", "Archived", "Unarchived" or "Deleted". A tooltip details the modified fields, old and new value. If a mistake was made, a bin lets you "Discard offline change".
When the network returns, the badge switches to "Syncing" and the changes are sent to the server. Clicking the badge forces a check ("Click to check connection and Sync"). If a change is rejected, the badge shows "Sync issues" and the change stays listed, in red, with its error message.
💡 Key takeaway
The technician enters data as he works; the office sees everything as soon as the phone finds the network again.
3. Preparing your teams: the rule to know
The point that is not in the announcements, and that we found in the code: offline, Odoo only serves what the device has already seen online. Lists, kanban views and records are kept in the browser as they are consulted. A record never opened on that phone will not be available at the bottom of the cellar.
In practice, three habits:
- Open your day before leaving: the list of your tasks and the records of the day's customers, on the phone that will go into the field.
- Keep the same device and the same browser: the cached data and the pending changes live in that browser.
- Let the synchronisation finish before clearing the browser data or changing phone.
💡 Key takeaway
Offline mode has to be prepared: what was consulted in the morning is available in the afternoon, the rest is not.
⚔️ The Match: Odoo 19 vs Odoo 20 without a network
| Criterion | Odoo 19 | Odoo 20 |
|---|---|---|
| Edit a record without a network | Impossible | Yes, queued |
| Create, archive, delete | Impossible | Yes |
| Tracking of pending changes | — | List with status, can be discarded |
| Records available offline | — | Those already opened online on the device |
| Module to install | — | None, standard |
Behaviour observed in the Odoo 20 source code (web module) and the official release notes, October 2026.
4. Prerequisites, limits and who it is for
HTTPS required. Offline mode relies on features that browsers reserve for secure
sites: on an http:// address, Odoo refuses it. This is the default on Odoo.sh and on the instances
we host; on a server installed in-house, it needs to be checked.
This is not a full Odoo in your pocket. You work on records: no new search on data that was never loaded. And until synchronisation has taken place, the office does not see the changes: a schedule decided on the spot still depends on the network.
Who is it for? Every team that enters data on site: technicians, fitters, delivery drivers, stocktakes in a warehouse or cellar, sales reps on country roads.
💡 Key takeaway
HTTPS, a dedicated device and a morning routine: with these three conditions, an outage becomes a non-event.
The Verdict: the field no longer stops, provided you prepare for it
Odoo 20's offline mode removes the most common objection from field-based businesses. It does require a little
discipline: open your day before leaving, keep your device, let it sync. This is what we put
in place during an
Odoo training
for your teams, after identifying, during an
audit of your Odoo processes,
the moments where information is lost today.
And at your company, where does the network drop most often?
A cellar, a basement, a building site in the middle of the countryside: the network drops, the Odoo screen freezes, and the technician jots everything down on a scrap of paper to "key in when he gets back". With Odoo 20, the web client keeps working offline and syncs when the network returns. Here is how it works, what to prepare, and what this mode does not do.
1. The problem: information gets lost between the field and the office
For the field-service companies we work with (heating engineers, chimney sweeps, removal firms, installers), the number-one objection to online software is always the same: "What happens when there is no network?". Up to Odoo 19, the answer was uncomfortable: without a connection, nothing could be saved. The result: paper notes, forgotten details, and double entry in the evening.
💡 Key takeaway
The cost of an outage is not the outage itself: it is the information re-entered later, or never.
2. What Odoo 20 does when the network drops
There is nothing to install: offline mode is part of the standard Odoo 20 web client, Community and Enterprise alike. When the connection disappears, a yellow "Working offline" badge appears in the top bar. The user can then create, edit, archive, unarchive and delete records, just as usual.
Each change is queued and listed in a dropdown under the badge, with its status: "Created", "Edited", "Archived", "Unarchived" or "Deleted". A tooltip details the modified fields, old and new value. If a mistake was made, a bin lets you "Discard offline change".
When the network returns, the badge switches to "Syncing" and the changes are sent to the server. Clicking the badge forces a check ("Click to check connection and Sync"). If a change is rejected, the badge shows "Sync issues" and the change stays listed, in red, with its error message.
💡 Key takeaway
The technician enters data as he works; the office sees everything as soon as the phone finds the network again.
3. Preparing your teams: the rule to know
The point that is not in the announcements, and that we found in the code: offline, Odoo only serves what the device has already seen online. Lists, kanban views and records are kept in the browser as they are consulted. A record never opened on that phone will not be available at the bottom of the cellar.
In practice, three habits:
- Open your day before leaving: the list of your tasks and the records of the day's customers, on the phone that will go into the field.
- Keep the same device and the same browser: the cached data and the pending changes live in that browser.
- Let the synchronisation finish before clearing the browser data or changing phone.
💡 Key takeaway
Offline mode has to be prepared: what was consulted in the morning is available in the afternoon, the rest is not.
⚔️ The Match: Odoo 19 vs Odoo 20 without a network
| Criterion | Odoo 19 | Odoo 20 |
|---|---|---|
| Edit a record without a network | Impossible | Yes, queued |
| Create, archive, delete | Impossible | Yes |
| Tracking of pending changes | — | List with status, can be discarded |
| Records available offline | — | Those already opened online on the device |
| Module to install | — | None, standard |
Behaviour observed in the Odoo 20 source code (web module) and the official release notes, October 2026.
4. Prerequisites, limits and who it is for
HTTPS required. Offline mode relies on features that browsers reserve for secure
sites: on an http:// address, Odoo refuses it. This is the default on Odoo.sh and on the instances
we host; on a server installed in-house, it needs to be checked.
This is not a full Odoo in your pocket. You work on records: no new search on data that was never loaded. And until synchronisation has taken place, the office does not see the changes: a schedule decided on the spot still depends on the network.
Who is it for? Every team that enters data on site: technicians, fitters, delivery drivers, stocktakes in a warehouse or cellar, sales reps on country roads.
💡 Key takeaway
HTTPS, a dedicated device and a morning routine: with these three conditions, an outage becomes a non-event.
The Verdict: the field no longer stops, provided you prepare for it
Odoo 20's offline mode removes the most common objection from field-based businesses. It does require a little
discipline: open your day before leaving, keep your device, let it sync. This is what we put
in place during an
Odoo training
for your teams, after identifying, during an
audit of your Odoo processes,
the moments where information is lost today.
And at your company, where does the network drop most often?