MRP Repair Refurbish & Repair Stock Move
Glue module. This makes repair_refurbish to work together with repair_stock_move
auto_awesome What this module does
AI-generated from the code · Odoo 15.0This glue module makes the refurbish and repair stock move features work together, so repair orders that produce a refurbished product also create and manage the related stock moves.
This module connects two existing repair features: refurbishing a product and tracking repair stock moves. It is installed automatically when both are present, so users do not need to enable it separately.
On a repair order (repair.order), when the order is marked to refurbish a product, the system creates a stock move for the refurbished item and links it to the repair order. When the repair is finished, that refurbished stock move is completed automatically.
If the user changes the refurbish flag or the refurbished product while the repair is in progress, the existing stock moves are cancelled and recreated so they match the new choice. If a refurbish lot is set, the corresponding move lines are updated with that lot.
When stock moves are created and confirmed during a repair, they are automatically reserved (assigned) if the repair is under repair. The button that opens stock moves from the repair order is adjusted to also show the refurbished stock move.
All of this happens on the repair order screen; no new menus are added. The module touches the repair.order model and the stock move records linked to it.
Depends on
Models and fields (1)
- repair.order · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 15.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 2 confirmed, 7 with no information of 9 versions.
Sources · Odoo 15.0
Confirmed on 2026-11-03 in branch 15.0 of OCA/repair.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.