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.

Repairs — active tickets
Apple iPhone 13 — Screen replacement
Dana Whitfield · 0412 555 118
Diagnosing
Samsung Galaxy S22 — Battery, Charge port
Peter Nguyen · 0433 555 902
Waiting Parts
Google Pixel 7 — Rear glass
Ruth Cadogan · 0401 555 447
ReadyCollect & Pay →
🛡️ WARRANTYApple iPad Air — Screen replacement
Marcus Bell · 0455 555 210
In Progress
Ticket rows as the repairs list renders them. The device line is brand, model, generation, then the repairs selected; the line under it is the customer and their phone. A rework carries an amber WARRANTY chip and stays linked to the ticket it re-does. The Collect & Pay → button appears on a ticket at Ready and on no other status — it hands the job to the till. Source: RepairModule.tsx and repairs.module.css.

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.

Open in the app
Still stuck? We answer every message.Contact support