Feature: Backend scaffolding for Repair Orders (#12064)

docs/docs/manufacturing/index.md

@@ -29,3 +29,9 @@ Read more about stock allocation in the [Stock Allocation documentation](./alloc
 The reverse process is also supported - an assembled stock item can be broken back down into its component parts, based on its BOM. This is useful for reworking or scrapping an assembly, or for splitting a bundled "kit" product purchased from a supplier into its individual components.
 
 Read more about this process in the [Stock Disassembly documentation](../stock/disassemble.md).
+
+### Repair Orders
+
+InvenTree supports the creation of Repair Orders, which are used to manage the process of repairing or reworking existing stock items. Repair Orders track the parts consumed during a repair and can optionally be linked to a customer.
+
+Read more about repair orders in the [Repair Order documentation](./repair.md).

docs/docs/manufacturing/repair.md

@@ -0,0 +1,156 @@
+---
+title: Repair Orders
+---
+
+## Repair Orders
+
+A *Repair Order* is used to manage the process of repairing or reworking existing stock items. Where a [Build Order](./build.md) creates *new* stock by assembling components, a Repair Order tracks the restoration of *existing* stock items to working condition, consuming replacement parts from inventory as needed.
+
+Repair Orders are particularly useful for organizations that offer after-sales service, warranty repairs, or internal rework processes. Each Repair Order can optionally be linked to a [customer](../concepts/company.md), allowing you to track which customer's item is being repaired.
+
+!!! tip "Repair vs. Build"
+    Use a *Build Order* when you are manufacturing a new item from components. Use a *Repair Order* when you are fixing, refurbishing, or reworking an existing stock item.
+
+### Key Concepts
+
+A Repair Order consists of three core components:
+
+| Component | Description |
+| --- | --- |
+| **Repair Order** | The top-level record that tracks the overall repair, including the customer, description of the issue, and current status |
+| **Line Items** | Individual entries specifying which parts are required to perform the repair, and in what quantity |
+| **Allocations** | Links between line items and specific stock items in inventory, reserving real stock for the repair |
+
+```mermaid
+graph LR
+    A[Repair Order] --> B[Line Item 1]
+    A --> C[Line Item 2]
+    B --> D[Stock Allocation]
+    B --> E[Stock Allocation]
+    C --> F[Stock Allocation]
+```
+
+## Repair Order Details
+
+### Repair Order Reference
+
+Each Repair Order is uniquely identified by its *Reference* field. Read more about [reference fields](../settings/reference.md).
+
+### Repair Order Parameters
+
+The following parameters are available for each Repair Order, and can be edited by the user:
+
+| Parameter | Description |
+| --- | --- |
+| Reference | Unique repair order reference e.g. 'RO-0001' |
+| Description | Description of the repair order |
+| Customer | Link to the *Company* who owns the item being repaired (optional) |
+| Symptoms | Detailed description of the reported symptoms or issues |
+| Status | Current status of the repair order |
+
+### Repair Order Status
+
+Each *Repair Order* has an associated *Status* flag, which indicates the current state of the repair:
+
+| Status | Description |
+| --- | --- |
+| `Pending` | Repair order has been created, but work has not yet started |
+| `In Progress` | Repair work is actively underway |
+| `On Hold` | Repair order has been paused, but is still considered active |
+| `Complete` | Repair has been successfully completed |
+| `Cancelled` | Repair order has been cancelled |
+
+**Source Code**
+
+Refer to the source code for the Repair Order status codes:
+
+::: build.status_codes.RepairOrderStatus
+    options:
+        show_bases: False
+        show_root_heading: False
+        show_root_toc_entry: False
+        show_source: True
+        members: []
+
+Repair Order Status supports [custom states](../concepts/custom_states.md).
+
+### Status Lifecycle
+
+The typical lifecycle of a Repair Order follows this progression:
+
+```mermaid
+graph LR
+    A["Pending"] --> B["In Progress"]
+    B --> C["Complete"]
+    A --> D["Cancelled"]
+    B --> E["On Hold"]
+    E --> B
+    B --> D
+```
+
+!!! info "Active Orders"
+    Orders with a status of *Pending*, *In Progress*, or *On Hold* are considered **active** (open) orders.
+
+## Line Items
+
+Each Repair Order can contain one or more *Line Items*, which specify the parts required to perform the repair. A line item references a specific [Part](../part/index.md) and a required quantity.
+
+| Field | Description |
+| --- | --- |
+| Repair Order | The parent repair order |
+| Part | The part to be consumed for this repair |
+| Quantity | The quantity of the part required |
+
+!!! info "Example - Repair Line Items"
+    A laptop is returned for repair. After diagnosis, you determine that the screen and the battery need to be replaced. You would create two line items: one for the replacement screen, and one for the replacement battery, each with a quantity of 1.
+
+## Stock Allocations
+
+*Stock Allocations* link a repair order line item to a specific [Stock Item](../stock/index.md) in inventory. Allocating stock to a repair order signals an *intent* to consume that stock during the repair process.
+
+| Field | Description |
+| --- | --- |
+| Line Item | The repair order line item this allocation is for |
+| Stock Item | The specific stock item being allocated |
+| Quantity | The quantity being allocated from this stock item |
+
+!!! warning "Stock Reservation"
+    Allocating stock to a repair order does not immediately subtract the stock from inventory. It reserves the stock, indicating that it is earmarked for this particular repair. The stock is consumed when the repair order is completed.
+
+!!! info "Multiple Allocations"
+    Multiple stock items can be allocated against a single line item, if a single stock item does not have sufficient quantity for the repair.
+
+## Repair Order Features
+
+Repair Orders inherit a number of standard InvenTree features:
+
+### Barcode Support
+
+Each Repair Order can be assigned a unique [barcode](../barcodes/index.md), allowing for quick scanning and lookup.
+
+### Attachments
+
+File [attachments](../concepts/attachments.md) can be uploaded against a Repair Order, for example photographs of the damaged item, diagnostic reports, or customer correspondence.
+
+### Notes
+
+Repair Order [notes](../concepts/attachments.md) support markdown formatting, and can be used to record detailed information about the repair process.
+
+### Tags
+
+[Tags](../concepts/tags.md) can be assigned to Repair Orders for flexible categorization and filtering.
+
+### Reporting
+
+Custom [reports](../report/index.md) can be generated against each Repair Order.
+
+## Repair Order Permissions
+
+Access to Repair Orders is controlled by the `repair_order` [permission](../settings/permissions.md) ruleset. Users must be assigned to a group with the appropriate Repair Order permissions to create, view, edit, or delete repair orders and their associated line items and allocations.
+
+| Permission | Description |
+| --- | --- |
+| View | View repair orders and their details |
+| Add | Create new repair orders, line items, and allocations |
+| Change | Edit existing repair orders, line items, and allocations |
+| Delete | Delete repair orders, line items, and allocations |

docs/mkdocs.yml

@@ -164,6 +164,7 @@ nav:
     - Required Quantity: manufacturing/required.md
     - Allocating Stock: manufacturing/allocate.md
     - External Manufacturing: manufacturing/external.md
+    - Repair Orders: manufacturing/repair.md
     - Example Build Order: manufacturing/example.md
   - Purchasing:
     - Purchasing: purchasing/index.md

src/backend/InvenTree/InvenTree/api_version.py

@@ -1,11 +1,14 @@
 """InvenTree API version information."""
 
 # InvenTree API version
-INVENTREE_API_VERSION = 533
+INVENTREE_API_VERSION = 534
 """Increment this API version number whenever there is a significant change to the API that any clients need to know about."""
 
 INVENTREE_API_TEXT = """
 
+v534 -> 2026-07-27 : https://github.com/inventree/InvenTree/pull/12072
+    - Adds API endpoints for RepairOrder, RepairOrderLineItem, and RepairOrderAllocation models
+
 v533 -> 2026-08-18 : https://github.com/inventree/InvenTree/pull/12317
     - Refactors the PurchaseOrder, PurchaseOrderLineItem and PurchaseOrderExtraLine API endpoints to use DRF viewsets
 

src/backend/InvenTree/build/admin.py

@@ -2,7 +2,14 @@
 
 from django.contrib import admin
 
-from build.models import Build, BuildItem, BuildLine
+from build.models import (
+    Build,
+    BuildItem,
+    BuildLine,
+    RepairOrder,
+    RepairOrderAllocation,
+    RepairOrderLineItem,
+)
 
 
 @admin.register(Build)
@@ -52,3 +59,34 @@ class BuildLineAdmin(admin.ModelAdmin):
     search_fields = ['build__title', 'build__reference', 'bom_item__sub_part__name']
 
     autocomplete_fields = ['bom_item', 'build']
+
+
+@admin.register(RepairOrder)
+class RepairOrderAdmin(admin.ModelAdmin):
+    """Admin class for the RepairOrder model."""
+
+    list_display = ['reference', 'customer', 'status', 'description']
+
+    search_fields = ['reference', 'customer__name', 'description']
+
+    autocomplete_fields = ['customer']
+
+
+@admin.register(RepairOrderLineItem)
+class RepairOrderLineItemAdmin(admin.ModelAdmin):
+    """Admin class for RepairOrderLineItem model."""
+
+    list_display = ['order', 'part', 'quantity']
+
+    search_fields = ['order__reference', 'part__name', 'part__IPN']
+
+    autocomplete_fields = ['order', 'part']
+
+
+@admin.register(RepairOrderAllocation)
+class RepairOrderAllocationAdmin(admin.ModelAdmin):
+    """Admin class for RepairOrderAllocation model."""
+
+    list_display = ['line', 'item', 'quantity']
+
+    autocomplete_fields = ['line', 'item']

src/backend/InvenTree/build/api.py

@@ -23,7 +23,14 @@
 import part.models as part_models
 import stock.models as stock_models
 import stock.serializers
-from build.models import Build, BuildItem, BuildLine
+from build.models import (
+    Build,
+    BuildItem,
+    BuildLine,
+    RepairOrder,
+    RepairOrderAllocation,
+    RepairOrderLineItem,
+)
 from build.status_codes import BuildStatus, BuildStatusGroups
 from data_exporter.mixins import DataExportViewMixin
 from generic.states.api import StatusView
@@ -1204,6 +1211,48 @@ def get_queryset(self):
     ]
 
 
+class RepairOrderList(ListCreateAPI):
+    """API endpoint for accessing a list of RepairOrder objects."""
+
+    queryset = RepairOrder.objects.all()
+    serializer_class = build.serializers.RepairOrderSerializer
+
+
+class RepairOrderDetail(RetrieveUpdateDestroyAPI):
+    """API endpoint for detail view of a single RepairOrder object."""
+
+    queryset = RepairOrder.objects.all()
+    serializer_class = build.serializers.RepairOrderSerializer
+
+
+class RepairOrderLineItemList(ListCreateAPI):
+    """API endpoint for accessing a list of RepairOrderLineItem objects."""
+
+    queryset = RepairOrderLineItem.objects.all()
+    serializer_class = build.serializers.RepairOrderLineItemSerializer
+
+
+class RepairOrderLineItemDetail(RetrieveUpdateDestroyAPI):
+    """API endpoint for detail view of a single RepairOrderLineItem object."""
+
+    queryset = RepairOrderLineItem.objects.all()
+    serializer_class = build.serializers.RepairOrderLineItemSerializer
+
+
+class RepairOrderAllocationList(ListCreateAPI):
+    """API endpoint for accessing a list of RepairOrderAllocation objects."""
+
+    queryset = RepairOrderAllocation.objects.all()
+    serializer_class = build.serializers.RepairOrderAllocationSerializer
+
+
+class RepairOrderAllocationDetail(RetrieveUpdateDestroyAPI):
+    """API endpoint for detail view of a single RepairOrderAllocation object."""
+
+    queryset = RepairOrderAllocation.objects.all()
+    serializer_class = build.serializers.RepairOrderAllocationSerializer
+
+
 build_api_urls = [
     # Build lines
     path(
@@ -1276,4 +1325,59 @@ def get_queryset(self):
     ),
     # Build List
     path('', BuildList.as_view(), name='api-build-list'),
+    # Repair Order endpoints
+    path(
+        'repair/',
+        include([
+            path(
+                '<int:pk>/',
+                include([
+                    path(
+                        '', RepairOrderDetail.as_view(), name='api-repair-order-detail'
+                    )
+                ]),
+            ),
+            path('', RepairOrderList.as_view(), name='api-repair-order-list'),
+        ]),
+    ),
+    # Repair Order line item endpoints
+    path(
+        'repair-line/',
+        include([
+            path(
+                '<int:pk>/',
+                include([
+                    path(
+                        '',
+                        RepairOrderLineItemDetail.as_view(),
+                        name='api-repair-order-line-detail',
+                    )
+                ]),
+            ),
+            path(
+                '', RepairOrderLineItemList.as_view(), name='api-repair-order-line-list'
+            ),
+        ]),
+    ),
+    # Repair Order allocation endpoints
+    path(
+        'repair-allocation/',
+        include([
+            path(
+                '<int:pk>/',
+                include([
+                    path(
+                        '',
+                        RepairOrderAllocationDetail.as_view(),
+                        name='api-repair-order-allocation-detail',
+                    )
+                ]),
+            ),
+            path(
+                '',
+                RepairOrderAllocationList.as_view(),
+                name='api-repair-order-allocation-list',
+            ),
+        ]),
+    ),
 ]

src/backend/InvenTree/build/events.py

@@ -18,3 +18,12 @@ class BuildEvents(BaseEventEnum):
     # Build output events
     OUTPUT_CREATED = 'buildoutput.created'
     OUTPUT_COMPLETED = 'buildoutput.completed'
+
+
+class RepairOrderEvents(BaseEventEnum):
+    """Event enumeration for the RepairOrder model."""
+
+    ISSUED = 'repairorder.issued'
+    HOLD = 'repairorder.hold'
+    COMPLETED = 'repairorder.completed'
+    CANCELLED = 'repairorder.cancelled'