In standard Odoo, a landed cost (stock.landed.cost) is intentionally hard to undo once validated. The moment you post it, Odoo allocates the freight, duty, insurance, and handling amounts across the target stock moves, writes the adjustment onto the stock.valuation.layer records, and — for real-time (perpetual) valuation categories — posts a journal entry that debits inventory and credits the landed-cost expense/clearing account. There is no native "cancel" button and no supported reset-to-draft path. When a warehouse or finance user picks the wrong receipt, keys a duty amount off by a decimal, applies a cost to the wrong product category, or simply validates a duplicate, the only sanctioned fix Odoo offers is to book a second, opposite landed cost to net it out. That leaves a permanent trail of offsetting records, inflated valuation layers, and reconciliation noise that auditors and month-end close teams have to explain every period.

This is where a typical off-the-shelf apps.odoo.com module and Odoo core both run out of road: core gives you no cancel action at all, and generic marketplace add-ons frequently just flip a state flag without truly reversing the downstream valuation layers and journal items, which silently corrupts your inventory valuation. ECOSIRE builds a made-to-order module that adds a first-class, auditable cancellation lifecycle to stock.landed.cost. We introduce a controlled cancel state and a guarded reset-to-draft path on the model, and — critically — we generate proper accounting reversals rather than deletions: the module creates a reversing account.move (using Odoo's native reversal mechanics) so the general ledger stays balanced and traceable, unwinds or neutralizes the stock.valuation.layer rows the cost created, and restores the affected stock moves' additional landed-cost amounts to their pre-application values. Deletion of a landed cost is permitted only from a safe state and only when no irreversible downstream dependency exists.

Technically, the work centers on subclassing stock.landed.cost (and its stock.valuation.adjustment.lines) with new state transitions guarded by @api.depends/@api.constrains logic, a set of button-triggered methods (action_cancel, action_reset_to_draft, action_unlink_guard) wired into inheriting XML/OWL form views, and reversal routines that call into account.move._reverse_moves() and the valuation-layer APIs so we never bypass Odoo's own accounting engine. Access is locked down through ir.model.access.csv plus record rules and a dedicated security group, so only authorized inventory/finance roles can cancel a posted cost — with an optional approval step via an automated action or activity. Every cancellation is logged to the chatter and (optionally) a mail.activity, giving you a complete audit trail. We respect Community vs Enterprise differences (Anglo-Saxon vs Continental accounting, real-time vs manual/periodic valuation, and multi-currency landed costs) and expose the cancel/reset actions over the XML-RPC/JSON-RPC API so your integrations and automated flows can call them programmatically. The module ships tagged for Odoo 17.0, 18.0, and 19.0 with the appropriate __manifest__.py version and dependency pins for the version you run.

Because this is build-to-order, nothing is sold as an instant download. After a short scoping call we confirm your exact requirements — Odoo version, edition, valuation method, approval workflow, and any localization or multi-company nuances — then build, test on a staging copy of your database, and deploy behind a UAT sign-off with a rollback plan. Typical delivery is one working week from confirmed scope. Pricing starts from $999 (indicative, single-company base scope); multi-company deployments, additional approval/automation logic, deep localization requirements, or reconciliation of large volumes of historical landed-cost data increase the quoted scope. You receive a fixed quote after the scoping call — never a surprise on the invoice.