Record the true production date on every manufacturing order
Odoo locks manufacturing and work order dates to the moment you click. Manufacturing Backdate lets you set the real production date instead — cascaded consistently across work orders and stock moves, with reasons, guardrails, approval, and a complete audit trail.
The problem
Odoo stamps the current date and time on a manufacturing order, its work orders, and its stock moves the instant it is marked done. When shop-floor paperwork lags real production by days or weeks — batched data entry, quality sign-off, or a migration from a legacy system — there is no supported way to record when production actually happened. The result is inventory valuation timing, cost periods, and traceability records that do not match reality.
The solution
Manufacturing Backdate adds a governed way to set the true production date on a manufacturing order and cascade it consistently to its work orders and stock moves. Structured reasons, validation guardrails, an optional approval step, and an immutable audit log turn backdating from a risky override into a documented, auditable correction.
Everything a controller needs to trust a backdate
Every capability below is implemented in the module.
One date, applied everywhere
Set the production date once on the manufacturing order and it cascades to work order start/finish timestamps and the related stock moves, so the record stays internally consistent.
Bulk backdate wizard
Select multiple manufacturing orders from the list view and apply a historical date to all of them in a single pass — built for weekly data-entry backlogs.
Structured backdate reasons
Choose from a reusable, sequence-ordered library of reasons instead of typing free text, so every backdate is documented consistently and stays filterable later.
Mandatory reason enforcement
Optionally require a reason on every backdate at the company level, closing the loophole competitors leave as an unused free-text field.
Date validation guardrails
Block future dates and enforce a configurable maximum lookback window and lock date, so backdating cannot silently corrupt a closed period.
Optional approval workflow
Route a backdate for manager sign-off before it commits, with clear pending, approved, and rejected states shown right on the order.
Immutable audit log
Every backdating action is recorded with the original date, the new date, the user, and the timestamp — a permanent record that cannot be edited after the fact.
Filterable, exportable audit trail
Search and group the audit log by reason or source, and export it for month-end review or a compliance audit.
In-context guidance
A plain-language alert on the Backdate page explains why Odoo locks the date and exactly what backdating does and does not change.
How it works
Enable backdating
Open a completed manufacturing order, or select several from the list, and turn on the Backdate page.
Set date and reason
Pick the true production date and a structured reason; the guardrails block dates that are too far back or in the future.
Approve if required
When approval is enabled, a manager reviews the pending request before the new date is committed.
Review the audit trail
Every change appears in the immutable, filterable Backdate Audit Log with the original date, new date, user, and timestamp.
Frequently asked
No sales fog. If your question isn't here, email us and we'll answer it the same way.
No. The module re-stamps the production-date fields on the order, its work orders, and its stock moves. It does not recompute inventory valuation cost layers or accounting entries.
Buy it on the Odoo App Store
Purchase, download and install directly from the official Odoo Apps Store — you'll always get the latest supported build.
Manufacturing Backdate
Set the real production date on a completed order and cascade it to its work orders and stock moves — behind structured reasons, validation guardrails, optional approval and an immutable audit log.
Buy on Odoo App Store