Unbuild, Disassembly & Salvage Orders

ECOSIRE builds a dedicated Unbuild, Disassembly & Salvage layer on top of Odoo's manufacturing core. We extend mrp.unbuild (or introduce a governed ecosire.salvage.order model where a cleaner separation is warranted) with per-BOM-line salvage definitions: for each component you declare an expected recovery yield, a condition/disposition (reuse, rework, scrap, warranty-return), and a destination location. A compute/@api.depends layer derives recoverable quantities and recovered value from the parent unit's inventory cost and your yield rules, so the stock moves that get generated reflect what actually came off the line — not an idealized BOM explosion. Lot and serial numbers are preserved on disassembly: the module writes stock-move lines that link each recovered component's lot/serial back to the parent's serial, so stock.lot traceability (upstream and downstream) stays intact and auditable. When a unit fails quality, the order can spawn a rework loop that feeds the salvaged components straight into a new manufacturing or repair order rather than back to raw stock.

Technically, the module ships as a proper Odoo addon: a versioned __manifest__.py declaring dependencies on mrp, stock, and quality (Enterprise) or a Community-safe fallback; new models.Model classes with fields, compute methods, and constraints; access control via ir.model.access.csv plus record rules for multi-company and warehouse-level isolation; backend list/form/kanban views in XML with OWL components for the salvage-yield editor; a QWeb "Disassembly & Recovery" report showing recovered components, condition, and revalued cost; and optional automated actions (e.g., auto-create a salvage order when a quality.check fails). Everything is reachable over the standard XML-RPC / JSON-RPC API, so WMS, PLM, or reverse-logistics systems can create and read salvage orders programmatically. Recovered-component valuation posts correctly through Odoo's inventory valuation (standard or AVCO), so your stock and COGS reflect reclaimed value.

Because this is build-to-order, nothing is a shrink-wrapped download. We start with a short scoping call, confirm your BOM structure, valuation method (Community vs Enterprise differences matter here), quality workflow, and Odoo version (17.0, 18.0, or 19.0), then write a fixed-scope specification. We build against a copy of your configuration, run UAT on a staging database, and hand over installable source, documentation, and a git repository. Typical delivery is 2–4 weeks from confirmed scope, followed by a post-go-live support window. You own the code.