Data Guard

Protect data, not block operations — ORM-level document protection for Odoo 19

The Problem

Odoo lets users freely edit Sales Orders after delivery, modify Purchase Orders after receipt, reset posted invoices to draft, and reset payments to draft even within a locked fiscal period — creating silent data mismatches between your orders, warehouse, and books.

You need protection that guards the data without locking down your workflow.

Two Anchors, One Guard

Data Guard uses two different anchoring strategies tailored to how each business area actually operates:

• Sales & Purchase Orders — anchored on actual delivered / received quantity per line.
• Accounting documents — anchored on the fiscal lock date.

Daily operations stay free and unobstructed, while improper edits to completed data are blocked at the ORM level — not just hidden in the UI.

Settings

One toggle in General Settings. Enable to activate all protections. Disable temporarily for administrator-level corrections, then re-enable. No module reinstall required.

Sales & Purchase Order Protection

Protection is per-line, based on actual stock movement quantity (qty_delivered / qty_received). Only lines with qty > 0 are locked. Cancel, reset to draft, adding new lines, and editing undelivered lines remain fully available. If a warehouse return brings the qty back to zero, protection lifts automatically.

Per-line protection matrix

Stock Picking Source Enforcement

Receipts and deliveries containing storable products must originate from a Purchase Order, Sales Order, or a valid return. Manual pickings without a source document are blocked at validation — preventing rogue stock movements that corrupt your inventory data. Consignment receipts (with an Owner assigned) and internal transfers are exempt.

Journal Entry & Invoice Protection

Posted invoices, bills, and credit notes within the fiscal lock period cannot be reset to draft. Invoice and bill lines linked to a SO or PO are checked for quantity and price mismatches — discrepancies trigger a warning banner and list-view highlighting. Standalone invoices/bills without a source order are not covered by mismatch detection and should be reviewed manually.

Payment Protection (Native Gap Fix)

Odoo 19 decoupled payments from journal entries — native lock dates do not prevent resetting a payment to draft. This module closes that gap: any non-draft, non-canceled payment within the lock period cannot be reset to draft (covers in_process, paid, and rejected states).

Lock Date Protection & Dashboard

All five lock date fields are protected while Data Guard is enabled: fiscalyear_lock_date, tax_lock_date, sale_lock_date, purchase_lock_date, hard_lock_date.

Only users in the dedicated "Data Guard: Lock Date Manager" group can modify these fields. This group is independent — it is NOT inherited by Accounting Administrator and must be assigned explicitly. A Lock Date Dashboard under Accounting > Configuration shows all current lock dates in one place.

Full Protection Summary

Key Features

• ORM-level protection — cannot be bypassed via UI tricks, API calls, or imports
• Per-line granularity — only lines with actual stock moves are locked
• Auto-unlock on return — qty back to zero lifts all protection
• Stock Picking source enforcement for storable products
• Invoice / SO / PO mismatch detection with visual warnings
• Multi-company aware — each company uses its own lock date
• All 5 lock date fields protected with dedicated manager group
• Lock Date Dashboard for at-a-glance status
• Global on / off toggle in Settings
• Zero dependencies beyond native Odoo modules

Why Not Just Hide the Buttons?

Many "protection" modules simply hide UI elements with CSS or view inheritance. Users can still modify data via API calls, imports, automated actions, or developer mode. Data Guard operates at the ORM level — write(), unlink(), and action methods are intercepted before any change reaches the database.

Technical Notes

• No new models — pure _inherit on existing Odoo models.
• No scheduled actions, no background jobs, no performance overhead.
• Protection is synchronous and immediate on every write / unlink / action.
• Dependencies: sale_stock, purchase_stock, account, account_payment, stock (all native Odoo).
• Compatible with Odoo 19.0 Community and Enterprise.
• Emergency bypass: pass suite_force_unlock: True in ORM context.

License & support

Licensed under OPL-1 (Odoo Proprietary License v1). Maintained by SuiteState (ElectroState FZCO). For questions, bug reports, or feature requests, visit suitestate.com or contact hello@suitestate.com.