> For the complete documentation index, see [llms.txt](https://codehas.gitbook.io/the-repairbox/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://codehas.gitbook.io/the-repairbox/adding-multiple-devices.md).

# Adding Multiple Devices

A RepairBox Repair Order can contain several **Repair Items**. This is useful when one customer hands in more than one device at the same visit, but each item needs its own diagnosis, service work, technician, notes, status and quality checks.

## When to use one order and multiple items

Use a single order when the devices belong to the same customer visit or repair transaction and the business wants one shared reference. Examples:

* Phone and tablet from one customer.
* Laptop plus charger/accessories received with it.
* Several company devices collected under one service request, when the business process treats them as one order.

Use separate orders when the devices belong to different customers, different business transactions, unrelated outlet workflows or require separate financial/customer processes under your policy. Do not combine records just because the contact person is the same.

## Order/item distinction

| Data                                   | Usually shared at order level                            | Captured for each Repair Item                                            |
| -------------------------------------- | -------------------------------------------------------- | ------------------------------------------------------------------------ |
| Customer and overall reference         | Yes                                                      | Linked through the order                                                 |
| Responsible outlet                     | Order's operational scope, subject to app workflow       | Confirm item routing if the installation supports different item routing |
| Device type, brand, model              | No                                                       | Yes                                                                      |
| Standard or custom description         | No                                                       | Yes                                                                      |
| Reported problem, services and defects | No                                                       | Yes                                                                      |
| Condition and accessories              | No                                                       | Yes                                                                      |
| Technician, diagnosis and checklist    | No                                                       | Yes                                                                      |
| Status and activity history            | Overall summary may exist                                | Item's own progress                                                      |
| Price lines and final billing          | May roll up into order/invoice depending on billing flow | Item-specific pricing where supported                                    |

Actual invoice grouping and totals depend on the configured billing workflow. Confirm the generated estimate/invoice before quoting a combined total.

## Add devices carefully

1. Open or create the correct Repair Order and verify the customer.
2. Use the app's supported add-device/add-item action.
3. Complete the first item's details before moving on: standard or custom, device identity, service/defect, condition, accessories, notes and photos as applicable.
4. Add the next item and repeat the process independently.
5. Confirm each device is represented by a separate Repair Item.
6. Assign technicians to the appropriate item where the workflow allows independent assignment.
7. Review overall order status and each item's status.
8. Save and reopen the order to verify all data persisted under the correct item.

The exact name and location of the add action should be taken from the installed UI, not inferred from this guide.

## Example: two devices in one order

A customer hands in an iPhone with a cracked screen and a laptop that loses battery charge.

**Repair Order:** one customer and one human-readable reference.

**Item 1 — iPhone**

* Type: Mobile.
* Standard catalog selection if the exact model exists; otherwise custom entry.
* Reported issue: cracked screen.
* Requested service: screen replacement, if selected and available.
* Condition/accessories: record only what was received.
* Status: may progress through diagnosis, repair and QC independently.

**Item 2 — Laptop**

* Type: Laptop.
* Standard or custom description, depending on catalog availability.
* Reported issue: battery drains quickly.
* Diagnosis: technician records findings after testing.
* Status: can remain awaiting diagnosis or parts even when the phone is ready.

A customer notification must not claim the entire order is ready if only Item 1 is ready. Check whether the message trigger is order-level or item-level before enabling status-change notifications.

## Common data integrity problems

* **Second item overwrites first:** verify that item details are saved to separate records and that the staff member used add-item rather than editing the first item.
* **Wrong technician sees the item:** verify the current outlet, assignment and permissions.
* **Customer sees incomplete status:** distinguish overall order state from item state and use the correct tracking/display rules.
* **Invoice total does not match item estimates:** verify which line items and adjustments are included in the invoice and whether tax/discounts are order-level or line-level.
* **Only one device appears in a notification:** confirm the notification is designed for the item or the overall order and inspect the actual template variables.

## Checklist

* [ ] Every physical device is represented by its own item.
* [ ] Each item has the correct standard/custom details.
* [ ] Services, defects, condition, accessories and notes are item-specific.
* [ ] Technician assignments and status changes affect the intended item.
* [ ] Overall order state does not hide unfinished item work.
* [ ] Customer messages accurately describe the item/order scope.
* [ ] Estimate/invoice aggregation is verified.

## Related pages

* Creating a Repair Order
* Standard vs. Custom Repairs
* Assigning Technicians
* Status Updates
* Quality Control
* Notification Settings
