This module extends the repair management functionality in Odoo, providing additional options for handling the repair process in a more customizable and efficient way. It allows the configuration of repair steps based on specific business requirements and adds new picking types for managing component addition and removal in repair orders.
The main features are:
- Customize repair steps: Choose between a 1-step, 2-step, or 3-step repair process.
- Add and recycle components during the repair process using separate picking types.
- Associate repair orders with pickings for improved traceability.
- Automatic creation of pickings and procurement routes based on the selected repair steps.
- Manage repair locations and routes more efficiently with warehouse settings.
auto_awesome What this module does
AI-generated from the code · Odoo 17.0Configure how repairs are handled in each warehouse: one step, two steps (pick components then repair) or three steps (also store removed components), with automatic internal transfers for adding and recycling components.
This module adds repair configuration to each warehouse. On the warehouse form you choose a repair process: "Repair" (1 step), "Pick component, repair" (2 steps) or "Pick component, repair, store removed component" (3 steps). You also set a Repair Location and the module automatically creates the matching internal operation types ("Add Component to Repair" and "Recycle component from Repair") and a repair route with its rules.
When a repair order is confirmed, the system launches procurement for the repair lines according to the warehouse setting: components to add are picked in 2- and 3-step mode, and components to recycle are picked only in 3-step mode. A procurement group is created and linked to the repair order for traceability. The related transfers are created and linked to the repair moves, and their status is kept in sync.
If the repair is cancelled, any open transfers linked to it are cancelled too. Changing the repair location on a repair order updates the source or destination of its lines automatically. The module touches repair.order, stock.warehouse, stock.move and procurement.group.
Depends on
Models and fields (4)
- stock.move · extends an existing model
- repair.order · extends an existing modelprocurement_group_id
- stock.warehouse · extends an existing modelrepair_steps, add_c_type_id (Add Component to Repair), repair_route_id (Repair Route), recycle_c_type_id (Recycle component from Repair), repair_location_id (Repair Location)
- procurement.group · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 17.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 14.0
Confirmed on 2026-11-03 in branch 14.0 of OCA/manufacture.
terminal Installation and usage
OCA documentation · Odoo 17.0Configuration
Source · Odoo 17.0- Navigate to Inventory \> Configuration \> Warehouses, and select a warehouse.
- In the "Repair Steps" field, choose between "Repair", "Pick component, repair", or "Pick component, repair, store removed component" to define the repair process.
- Define the "Repair Location", "Add Component to Repair" picking type, "Recycle component from Repair" picking type, and "Repair Route" as needed.
Usage
Source · Odoo 17.0- Navigate to Repair \> Repair Orders and create a new repair order.
- In the Operations tab, add components to be added or removed during the repair process.
- Confirm the repair order. This will automatically generate the necessary pickings based on the configured repair steps.
- Process the pickings as required during the repair process.
- If the repair order needs to be canceled, all associated pickings that are not in "cancel" or "done" state will also be canceled automatically.
No verified information in OCA: Installation.
Installation 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.