Offline Mode in Odoo 20: Work Anywhere, Sync Later

Every ERP demo assumes perfect Wi-Fi. Real workplaces do not cooperate: warehouse aisles block signals, construction sites may have no fixed connection at all, and field technicians spend their days in basements, rural areas, and buildings where coverage comes and goes. Until now, losing the connection to Odoo usually meant switching to paper, a notes app, or a spreadsheet — and re-typing everything later. Odoo 20, released in September 2026, adds a platform-wide offline mode designed to close exactly that gap: keep working in the same screens, and let the system catch up when the connection returns.

Diagram showing Odoo 20 offline mode creating and editing records without connection, then syncing changes when coverage returns

What offline mode actually does

Odoo's release notes describe the new mode in deliberately plain terms. While offline, you can:

Create records
Edit records
Archive and unarchive records
Delete records
Execute searches you have previously run

That list matters because it is a working mode, not a read-only cache. Earlier “offline” behaviour in web applications typically meant you could look at whatever happened to be loaded, but not change anything safely. In Odoo 20, the record lifecycle — create, edit, archive, unarchive, delete — is available without a connection, and the changes you make are synchronized back to the database once you are online again.

The search capability deserves a closer look, because it defines the practical boundary of the feature. Offline, you can re-run searches you have already executed while connected. In other words, the data you have worked with and the views you have opened are the data you can keep working with on site. A brand-new query against records you have never loaded is not something to count on in a dead zone — which has a direct consequence for how teams should prepare, covered below.

Sync: work now, reconcile later

The second half of the feature is what happens on reconnect: changes made offline are synchronized when the connection returns. For the user, the intended experience is simple — the work you did in the field becomes part of the central database without a manual export, import, or copy-paste session back at the office.

That simplicity is the real productivity story. The cost of offline work in most businesses was never the outage itself; it was the double handling afterwards. A technician writes job notes on paper, an office worker re-keys them, a supervisor reconciles the two versions, and somewhere in that chain a detail gets lost or a quantity gets mistyped. If the record is created once, in Odoo, at the point of work — and simply syncs when the van reaches coverage again — the whole re-entry chain disappears.

It also changes what “the system of record” means during the day. Instead of Odoo being accurate only at the start and end of a shift, it stays the working tool throughout the shift; the connection becomes a synchronization detail rather than a precondition for using the software.

One practical consequence is worth planning for: when several people work away from the office at once, each of them is building up changes that will land in the same database later. That is far better than the paper alternative, but teams should still agree on simple ownership habits — who updates which record on a shared job, for example — so two people do not unknowingly rewrite the same information in parallel while both are out of coverage.

Who this is built for

Odoo positions offline mode at three classic dead-zone environments, and each one maps to a familiar failure of connected-only software:

Warehouse floors. Large racking, metal shelving, and deep building footprints create pockets where Wi-Fi is weak or absent. Staff who can keep creating and editing records while moving through those pockets no longer need to batch their updates at a desk.
Construction sites. Sites change weekly, temporary structures go up before network infrastructure does, and much of the work happens outdoors or underground. Offline mode lets site staff capture progress, issues, and changes where the work happens.
Field technicians. Service work is mobile by definition. A technician finishing a job at a customer site can close out the record on the spot — even in a plant room with no signal — and let it sync on the drive to the next call.

The common thread is that these users are the ones furthest from the IT comforts of head office, yet they produce some of the most time-sensitive data in the business: what was done, what was used, and what happens next.

A natural partner for the redesigned mobile app

Offline mode arrives in the same release as a redesigned mobile experience, and the two clearly belong together. Odoo 20's mobile interface adds a swipe-down command palette on the main dashboard, date pickers presented as bottom sheets, touch-friendly forms with visible field labels, and the ability to share files from the phone straight into Odoo — to digitize bills and expenses, or to create tasks, leads, to-dos, and time-off requests.

For a field user, that combination is the point: capture on the phone (including photos and files from the job), keep editing when the signal drops, and sync when it returns. The phone stops being a viewer for data other people entered and becomes the primary input device for the people doing the work.

Not the same thing as POS offline

Long-time Odoo users may shrug at this point: hasn't the Point of Sale worked offline for years? Yes — and it is important not to confuse the two. The POS offline behaviour is a separate, older mechanism specific to the point of sale application, built so a till can keep taking orders through an internet outage. It solves a retail problem: don't stop selling.

Odoo 20's offline mode is broader and different in kind. It applies to records across the platform — the general create, edit, archive, and delete workflow your team uses in everyday apps — and to re-running searches, rather than being a special mode inside one application. If your mental model is “the shop till keeps working,” extend it: in 20, the same resilience philosophy reaches the warehouse terminal, the site manager's laptop, and the technician's phone.

Working well offline: a short field guide

Because offline search covers searches you have already run, a little preparation before leaving coverage goes a long way:

Load before you go. While still connected, open the lists, records, and searches you expect to need on site, so they are part of your previously run searches.
Do the work in Odoo, not alongside it. Create and edit the real records offline rather than keeping side notes to transcribe later — transcription is exactly what the feature eliminates.
Reconnect deliberately. When you are back in coverage, give the device a moment on a stable connection so the offline changes can synchronize before you log out or hand the device over.
Check the synced result. After a long offline stretch, spot-check a couple of the records you changed to confirm they landed as expected, especially the first times your team uses the workflow.
Make it a procedure, not a hope. Add “open your day's work before leaving the yard” to the standard routine for field and warehouse staff, the same way you would charge the device.

The bottom line

Offline mode is not the flashiest line in the Odoo 20 release — the AI agents take that prize — but for operations-heavy businesses it may be the most immediately useful one. It takes the record-keeping work that used to stop at the edge of Wi-Fi coverage and lets it continue, with changes syncing when the connection returns. If your team works on warehouse floors, construction sites, or customer premises, this is one of the strongest practical reasons to look seriously at the upgrade.