---
title: "Odoo 20 Offline Mode Adds Record Editing"
description: "Odoo 20 adds offline record creation, editing, archiving, restoration and deletion. See what is confirmed and what organisations should test."
canonical_url: "https://websitefuze.com/blog/odoo-20-offline-mode-record-editing"
last_updated: "2026-10-01T01:03:53.243Z"
keywords: ["Odoo 20", "Odoo offline mode", "offline record editing", "Odoo synchronisation", "Odoo Community Edition", "Odoo 20 release"]
---

# Odoo 20 Expands Offline Mode from Viewing to Record Editing

Published: 2026-10-01

Category: Odoo Updates

Odoo 20 adds offline record creation, editing, archiving, restoration and deletion. See what is confirmed and what organisations should test.

Odoo 20 expands offline mode so users can create, edit, archive, unarchive and delete records without an active connection. Previously executed searches can also be run offline. After connectivity returns, synchronisation queues handle the changes, with an offline interface and management tools for monitoring the process.([Odoo 20 Release Notes](https://www.odoo.com/tr_TR/odoo-20-release-notes);[Odoo Goes Offline](https://www.odoo.com/zh_CN/event/odoo-experience-2026-9099/track/odoo-goes-offline-10140))This shifts offline access from a viewing fallback to a working mode that can change business data. Organisations assessing Odoo 20 should examine how those changes behave when they are synchronised, not only whether records remain accessible during an outage.

Odoo Nightly lists Odoo 20 as a stable, recommended Community Edition release, dated September 2026 and supported until Odoo 23.([nightly.odoo.com](https://nightly.odoo.com/))This listing is relevant to Community Edition planning, but it does not establish identical offline coverage across every platform, Enterprise environment or customised database. Coverage should be checked against the intended deployment.

## What changed from Odoo 19

Odoo 19 offline mode allows users to view records opened before the connection was lost, but not modify them while offline. Odoo 20 adds record creation, editing, archiving, unarchiving and deletion.([Odoo 19.0 Docs: General Offline Mode](https://www.odoo.com/documentation/19.0/applications/general/offline_mode.html);[Odoo 20 Release Notes](https://www.odoo.com/tr_TR/odoo-20-release-notes))This is a functional expansion rather than a new label for the earlier cache. In Odoo 19, users can prepare for disconnection by opening relevant records, but work that changes those records must wait for connectivity. Odoo 20 supports both new records and changes to existing ones while offline.([Odoo 19.0 Docs: General Offline Mode](https://www.odoo.com/documentation/19.0/applications/general/offline_mode.html);[Odoo 20 Release Notes](https://www.odoo.com/tr_TR/odoo-20-release-notes))

Version assessments should distinguish access to cached information from the ability to complete and queue record operations. A workflow that only requires reference data has different requirements from one involving data entry, status changes or deletion.([Odoo 19.0 Docs: General Offline Mode](https://www.odoo.com/documentation/19.0/applications/general/offline_mode.html);[Odoo 20 Release Notes](https://www.odoo.com/tr_TR/odoo-20-release-notes))

## Confirmed offline operations

The confirmed Odoo 20 actions cover five parts of the record lifecycle: creation, editing, archiving, unarchiving and deletion. Previously executed searches are also available while offline.([Odoo 20 Release Notes](https://www.odoo.com/tr_TR/odoo-20-release-notes))Acceptance testing should include at least one scenario for each action and confirm that the expected record state appears after reconnection and synchronisation.

Odoo's Experience session describes a dedicated offline interface, synchronisation queues, and tools for monitoring and managing synchronisation.([Odoo Goes Offline](https://www.odoo.com/zh_CN/event/odoo-experience-2026-9099/track/odoo-goes-offline-10140))These functions should be covered in user training and operating procedures. Users need to know where queued items appear, how to identify an unresolved item and who reviews it. The supplied material confirms that management tools exist, but does not define their complete workflow or administrative permissions.

## Caching and search coverage need verification

The Odoo 19 documentation describes offline access in terms of records opened before connectivity was lost. Odoo 20 separately confirms that previously executed searches can be run offline.([Odoo 19.0 Docs: General Offline Mode](https://www.odoo.com/documentation/19.0/applications/general/offline_mode.html);[Odoo 20 Release Notes](https://www.odoo.com/tr_TR/odoo-20-release-notes))The supplied sources do not specify how much related data is retained, how long it remains available, whether storage limits apply or whether every field associated with a cached record is available. They also do not establish whether repeating a search offline returns the original result set or only data already stored on the device.

Before approving an offline workflow, teams should identify the searches and record types needed by each role. Testing should begin online by running the relevant searches and opening the required records. Testers can then disconnect and repeat the intended tasks, including any use of attachments, linked records and required fields. These are verification points, not confirmed limitations, because the supplied release information does not describe their behaviour.([Odoo 20 Release Notes](https://www.odoo.com/tr_TR/odoo-20-release-notes))

## Conflict handling needs testing

Synchronisation queues and management tools are confirmed, but the supplied sources do not explain how Odoo 20 resolves competing changes to the same record, validation failures after reconnection or dependencies between queued operations.([Odoo Goes Offline](https://www.odoo.com/zh_CN/event/odoo-experience-2026-9099/track/odoo-goes-offline-10140))The presence of a queue does not establish a conflict policy. Its behaviour should be demonstrated in the intended Odoo build and configuration.

A conflict test can have one user alter a record offline while another changes the same record online. After reconnection, the team should inspect the resulting values, queue status and user notification. Separate tests should cover an offline edit to a record archived or deleted elsewhere, and a newly created record that fails a server-side rule. Testing should document whether an update takes precedence, a merge occurs or manual intervention is required.([Odoo Goes Offline](https://www.odoo.com/zh_CN/event/odoo-experience-2026-9099/track/odoo-goes-offline-10140))

## Access controls and destructive actions

Because Odoo 20 includes offline archiving, unarchiving and deletion, evaluation should extend beyond routine data entry.([Odoo 20 Release Notes](https://www.odoo.com/tr_TR/odoo-20-release-notes))Organisations should verify whether access rights, record rules and approval requirements are enforced when the offline action occurs, during synchronisation or at both stages. The release notes confirm the available actions but do not explain how each security control behaves without a connection.

Testing should use representative user roles rather than only an administrator account. Each role should attempt permitted and prohibited actions while connected and disconnected. Testers should then check whether queued changes remain visible, whether rejection messages are clear and whether archived, restored or deleted records reach the intended final state. Processes in which deletion has significant consequences should have a documented offline procedure before deployment.([Odoo 20 Release Notes](https://www.odoo.com/tr_TR/odoo-20-release-notes);[Odoo Goes Offline](https://www.odoo.com/zh_CN/event/odoo-experience-2026-9099/track/odoo-goes-offline-10140))

## Custom modules need targeted testing

The confirmed feature covers Odoo 20's offline record operations and synchronisation facilities, but the supplied sources do not state that every custom module, third-party module, automated action or external integration is compatible with offline work.([Odoo 20 Release Notes](https://www.odoo.com/tr_TR/odoo-20-release-notes);[Odoo Goes Offline](https://www.odoo.com/zh_CN/event/odoo-experience-2026-9099/track/odoo-goes-offline-10140))Customised deployments should therefore assess support module by module rather than assuming that offline mode applies uniformly across the database.

Testing should cover custom fields, onchange behaviour, required values, calculated values and server-side checks used in the organisation's workflows. Integrations that normally react to record creation or editing should also be observed after queued changes synchronise. The purpose is not to assume failure, but to determine whether each element runs offline, waits for reconnection, produces a rejected queue item or requires a different process.([Odoo 20 Release Notes](https://www.odoo.com/tr_TR/odoo-20-release-notes);[Odoo Goes Offline](https://www.odoo.com/zh_CN/event/odoo-experience-2026-9099/track/odoo-goes-offline-10140))

## Questions to settle before rollout

Odoo 20 provides a broader confirmed set of offline capabilities than Odoo 19, supported by a dedicated interface and synchronisation tools for queued work.([Odoo 19.0 Docs: General Offline Mode](https://www.odoo.com/documentation/19.0/applications/general/offline_mode.html);[Odoo 20 Release Notes](https://www.odoo.com/tr_TR/odoo-20-release-notes);[Odoo Goes Offline](https://www.odoo.com/zh_CN/event/odoo-experience-2026-9099/track/odoo-goes-offline-10140))Before relying on those capabilities, an organisation should verify which applications and record types are covered, what users must open or search before disconnection, how conflicts are presented and who monitors failed or delayed synchronisation.

The rollout decision should also record supported devices and deployment environments, storage and retention behaviour, access-control results, custom module outcomes and procedures for deletion or other consequential changes. The supplied release material does not answer these implementation questions, but they determine whether the confirmed functions suit a particular offline workflow.([Odoo 20 Release Notes](https://www.odoo.com/tr_TR/odoo-20-release-notes);[Odoo Goes Offline](https://www.odoo.com/zh_CN/event/odoo-experience-2026-9099/track/odoo-goes-offline-10140))

For Community Edition planning, Odoo Nightly's stable and recommended listing provides the stated version status, with support through Odoo 23.([nightly.odoo.com](https://nightly.odoo.com/))Operational approval should still depend on testing the exact build, modules, permissions and workflows that users will take offline. The confirmed change is that Odoo 20 moves beyond Odoo 19's read-only access to previously opened records by allowing queued offline creation and modification. Testing must establish how that capability behaves in the organisation's configuration.([Odoo 19.0 Docs: General Offline Mode](https://www.odoo.com/documentation/19.0/applications/general/offline_mode.html);[Odoo 20 Release Notes](https://www.odoo.com/tr_TR/odoo-20-release-notes);[Odoo Goes Offline](https://www.odoo.com/zh_CN/event/odoo-experience-2026-9099/track/odoo-goes-offline-10140))