> 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/repair-management-overview.md).

# Repair Management Overview

RepairBox manages the complete repair lifecycle: **Customer → Repair Order → Repair Items → Diagnosis → Estimate/Approval when required → Repair → Quality Control → Invoice/Payment → Pickup or Completion → Notifications and History**.

This is an operational guide for repair businesses. It explains the product's record model and how the records move through the process. The precise buttons and screen layout can vary by deployment, so use the labels visible in your installed Admin and Workshop portals rather than assuming a button name that is not present.

## What kinds of businesses does this workflow support?

RepairBox is designed for businesses that receive equipment, assess faults, carry out repair work, communicate progress, and collect payment. The shared workflow can support:

* **Mobile-phone and tablet repair shops:** screen/battery/charging repairs, condition and accessory capture, item-level repair progress.
* **Laptop and computer repair services:** fault diagnosis, custom hardware/model details, approval before chargeable work, testing and QC.
* **Multi-device repair counters:** one customer visit with several independent devices under a single Repair Order.
* **Electronics and game-console workshops:** configurable device types, services, defects, checklists and technician assignment.
* **Multi-outlet repair businesses:** associate the order with the responsible outlet and restrict staff/reporting according to outlet permissions.
* **Business/contract customers:** maintain company customer records, contact persons and billing/tax information where configured.
* **Service desks that need traceability:** status history, technician notes, approvals, invoice/payment records and customer updates.

A business should configure its catalog, statuses, permissions, tax settings and notification policy to match the work it actually performs. RepairBox does not automatically know a shop's unique workflow.

## The core data model

### Customer

The customer is the person or company associated with the repair. Reuse an existing matching record when possible so history, contact preferences and billing are not split across duplicates. RepairBox's customer model can distinguish individual and business customers and hold contact and address information.

### Repair Order

A Repair Order represents the overall customer repair transaction or intake. It has a database ID and a separate human-readable repair reference, for example `REP-2026-000125`. Use the visible repair reference for customer communication; do not treat it as a database primary key or as a secret access token.

Order-level context can include customer, outlet, overall status, priority, timestamps and billing/administrative information according to the enabled workflow.

### Repair Item

A Repair Item is one device/unit under the order. This distinction is essential when a customer leaves more than one device. Items may have their own device details, reported problem, services, defects, diagnosis, technician, status, checklist, notes, attachments, pricing and activity history.

**Example:** a customer leaves an iPhone for a screen replacement and a laptop for battery diagnosis. They can share one Repair Order, but the phone can be in Quality Check while the laptop is Waiting for Approval. Do not assume one item’s status tells the full story for every device.

## End-to-end workflow

1. **Find or create the customer.** Check email/phone and verify the identity before reusing a record. Choose the correct customer type for an individual or business customer.
2. **Create the Repair Order.** Select the responsible outlet and apply the configured order-level defaults such as initial status or priority where offered.
3. **Add one or more Repair Items.** For each device choose the standard catalog flow or custom entry. Capture what the customer reports separately from what a technician diagnoses.
4. **Record intake condition.** Capture existing damage, accessories received, photos and relevant notes when those intake fields are available. Never store device passwords or unlock codes in ordinary notes.
5. **Assign and diagnose.** Allocate the relevant technician and record findings, checks, and internal notes under the correct item.
6. **Prepare an estimate and obtain approval.** Where the business requires authorization before chargeable work, make the quote and approval outcome explicit before proceeding.
7. **Perform the repair.** Use the item’s service information, checklist and status history to document work and blockers.
8. **Quality control.** Test the repaired device against the required checks. A failed check means the item needs further work; it should not be marked ready simply because the repair step is complete.
9. **Invoice and record payment.** Use the configured pricing, tax and discount rules. Payment state must come from the recorded payment workflow, not from a notification being sent.
10. **Ready for pickup, handover and closure.** Verify the item(s), accessories and payment/collection requirements. Complete or cancel records according to the business policy and retain the activity history.
11. **Communicate progress.** Notification events and customer-facing tracking reflect the authoritative repair records, subject to channel configuration and customer contact preferences.

The configured status list may differ by business. Common workflow stages include Received, Awaiting Diagnosis, Waiting for Approval, In Repair, Quality Check, Ready for Pickup, Completed and Cancelled; these are examples, not a hard-coded required sequence.

## Order status versus item status

Use an **order-level state** to summarize the customer transaction, and **item-level state** to tell staff what is happening to a particular device. Where both are present:

* Update the correct item when only one device progresses.
* Use the order status to summarize the overall order; do not mark the order complete while required item work remains.
* Make customer notifications clear about whether the message applies to the entire order or one device.
* Check how totals and invoices aggregate multiple items in the installed billing flow before promising a single combined balance.

## How standard and custom repairs fit in

**Standard/catalog repair:** choose Device Type → Brand → Device/Model → relevant Services and Defects. This is best when the catalog entry actually matches the customer's equipment.

**Custom repair:** manually record Device Type, Brand, Model, Problem, Service and Notes when the catalog cannot describe the device accurately. Custom intake text is historical repair information and must not automatically create shared catalog entries.

For either path, the customer's requested service and reported symptom are not a confirmed diagnosis. The technician records findings after inspection.

## Controls that determine the workflow

* **Permissions:** backend authorization controls who can view, create, assign, change statuses, diagnose, run QC, view billing or export reports. Hiding a button in the frontend is not authorization.
* **Outlets:** orders must be routed to the location responsible for the work. Check outlet access when assigning or transferring a repair.
* **Statuses and priorities:** dynamic configuration should reflect the shop's real process. A status label alone does not implement a technical check or business rule.
* **Checklists and diagnostics:** use applicable checklists to keep intake, troubleshooting and QC repeatable.
* **Estimates and approvals:** establish when customer approval is required and how the outcome is recorded.
* **Notifications:** decide which events should message customers/staff and which contact channels are selected. Provider configuration alone does not guarantee delivery.
* **Billing:** tax, discounts, payments and refunds affect financial records and must follow one authoritative calculation/ledger process.

## Operational checklist

* [ ] Correct customer and outlet are selected.
* [ ] Every device is represented by the correct Repair Item.
* [ ] Standard catalog choices match the real device; otherwise use custom entry.
* [ ] Customer-reported symptoms are distinct from technician diagnosis.
* [ ] Existing damage and received accessories are recorded where relevant.
* [ ] Assignment, approval, status and QC are recorded against the correct order/item.
* [ ] Invoice and payment state match the financial records.
* [ ] Customer messages expose only appropriate information.
* [ ] Completion or cancellation preserves the repair history.

## Related pages

* Creating a Repair Order
* Adding Multiple Devices
* Standard vs. Custom Repairs
* Assigning Technicians
* Diagnosis & Repair Workflow
* Estimates & Customer Approvals
* Quality Control
* Billing & Payments
* Notification Settings
