Repairs overview
The repair board, ticket anatomy and how repairs connect to POS and inventory.
Repairs tracks a device from the moment it lands on the counter to the moment it is paid for. Tickets are split into active work and finished work — a ticket counts as finished once it reaches Collected or Paid.
What a ticket holds
- The customer and the device
- The repairs being carried out and what they are priced at
- Parts allocated from stock
- A status history — every change, who made it and any note
- A notification log — every SMS and email sent, and whether it landed
- Any linked special orders
Status history and the notification log are kept per ticket, so "did anyone tell the customer?" is answerable from the ticket itself rather than from memory.
The tabs
| Tab | What it is |
|---|---|
| Active Repairs | Work in progress |
| Finished | Collected and paid tickets |
| Uncollected | Devices nobody came back for, and the notices given about them. See Uncollected goods |
Alongside them, New Repair opens the intake wizard, and the gear beside the module title opens Repair Settings — notification wording and your own intake questions.
Times customers booked online are no longer here: they have their own Bookings module in the sidebar. A booking still turns into a repair ticket in one step — see Turning a booking into a repair.