Repairs

The repair board, ticket anatomy and how repairs connect to POS and inventory.

Capturing customer, device, stated fault and accessories at the counter.

Recording condition with photos and notes so pickup disputes do not happen.

The seven built-in statuses, which moves between them are allowed, and how that is enforced.

Putting a ticket in a technician's name from its detail view, the email they get, and how that differs from who booked the device in.

A month grid where every repair is drawn from its take-in day to its due day, coloured by status.

Open, overdue and due-this-week counts for each technician, plus the jobs nobody owns yet.

Recording the parts used on a ticket, and what that does and does not do to stock.

Send a priced quote from the ticket, and let the customer approve or decline it from a link on their phone.

Taking money up front on an open repair, and how the balance is worked out at collection.

Automatic SMS and email at status changes, and customising the message text.

Maintaining a repair price list by device and fault, including bulk import.

Sign at drop-off, at pickup or both — on a Wacom Intuos pen tablet, a touch screen or a mouse — and what handover records.

Recording warranty terms and raising a rework ticket linked to the original.

Devices nobody came back for — the written notice, the earliest date you may dispose of one, and the record of what happened to it.

There is no separate work-order document — a repair ticket already handles multi-line jobs.

Flagging a ticket as mail-in, the shipping panel, the Device arrived stamp and Awaiting device, and the {tracking} template variable.

How a completed repair is collected and paid for at the till.