This module introduces a sequence to the repair type that will be influence the numbering in the repair orders.
auto_awesome What this module does
AI-generated from the code · Odoo 16.0Lets you give each repair type its own numbering sequence, so repair orders are automatically numbered with the prefix and next number you define for that type.
This module adds numbering control to repair types. On the repair type form you now see a prefix, a next number and an entry sequence field. When you type a prefix and save, Odoo automatically creates a numbering sequence for that repair type, using that prefix, four digits and no gaps. Once a sequence exists, the prefix and next number fields become read-only, and the next number shown is the one that will be used for the following repair order of that type.
When a repair order is created with a repair type that has a sequence, its reference is set automatically from that sequence instead of the standard numbering. The same happens if you later change the repair type on an existing repair order: the reference is taken from the new type's sequence. Saving a repair type also fills in references for its existing repair orders that still have no number.
Everything is configured on the repair type screen; no new menu is added. The module touches repair.type and repair.order.
Depends on
Models and fields (2)
- repair.type · extends an existing modelsequence_id (Entry Sequence), sequence_prefix, sequence_number_next (Next Number)
- repair.order · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 16.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 16.0
Confirmed on 2026-11-03 in branch 16.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.