# QR codes for repair shops

> Repair shops need a status-tracking code on the job ticket with the ticket number in the URL, a review code at collection, and a warranty-of-repair record the customer can keep. Do not rely on the thermal receipt — direct thermal print fades in months, so put a durable label on the device too.

Source: https://useqr.app/qr-codes-for/repair-shops · Last reviewed 2026-08-21 · UseQR is free forever, MIT licensed, no signup.

---

## The job ticket is the product page

Every repair generates the same three customer questions: is it ready, what did you do,
and is it guaranteed. Three codes answer them:

| Code | Where | Why |
|---|---|---|
| Status tracking | Job ticket and collection slip | "Is it ready?" answered without a phone call |
| Warranty of repair | Collection receipt | Proof of what was done, findable months later |
| [Review](/google-review-qr-code) | Counter card at collection | The moment of a working device is the review moment |
| [Feedback](/feedback-qr-code) | Same card, labelled separately | A private lane for the unhappy case |

## Ticket number in the URL

The pattern that makes this work: each ticket's code encodes its reference —
`example.com/s?t=8412` — so scanning opens that job's status, not a lookup form asking
the customer to retype the number printed 2 cm away. Tickets are sequential, which makes
this a natural [bulk generation](/docs/how-to/how-to-make-qr-codes-in-bulk) job: generate
codes for the next thousand ticket numbers in one run via the [bulk tool](/bulk) and
print them onto the ticket stationery. Keep the URL token meaningless to outsiders — a
ticket reference, never the customer's name or phone number, since a job ticket taped to
a shop shelf is public.

## The thermal-fade trap

Most repair-shop receipts come off a [thermal printer](/docs/print/thermal-printer-qr-codes),
and [direct thermal print fades](/docs/print/direct-thermal-vs-thermal-transfer-for-qr) —
heat, sunlight and months in a wallet turn it grey. A warranty-of-repair code on a
receipt that is illegible when the fault recurs at month five has failed at its only
job. Two fixes: print the warranty code on a durable adhesive label applied to the
device or its charger (thermal-transfer or laser, not direct thermal), or make the
status page itself the permanent record and say so at collection. Codes at **2–2.5 cm**
suffice — receipts and labels are read in-hand at 20–30 cm.

## Collection is the review moment

The customer standing at the counter holding a working device is the highest-intent
review moment the trade offers. A counter card — review code on one side, private
feedback code clearly labelled on the other — catches both outcomes. Asking in person
beats the follow-up text, and the pairing keeps complaints out of the public rating.

## What goes wrong

- A status code opening a login page — the customer has a ticket, not an account.
- Warranty codes on direct-thermal receipts, blank by the time they are needed.
- Customer phone numbers used as URL tokens on tickets pinned to a public board.

## FAQ

### How does a QR status-tracking code work for repairs?

The ticket's code carries its reference number in the URL, so a scan opens that job's
live status directly. Codes for upcoming ticket numbers are generated in bulk and
printed on the ticket stock in advance — no per-job work at the counter.

### Why should the warranty QR code not be on the receipt?

Because most receipts are direct thermal and fade to illegibility within months —
usually before the warranty period ends. Put the code on a durable label on the device,
or treat the online status page as the permanent record.

### When should a repair shop ask for a review?

At collection, in person, while the customer holds the working device. A counter card
with the review code, plus a clearly labelled private feedback route beside it, converts
the moment without pushing unhappy customers into the public rating.

## Try it

- https://useqr.app/url
- https://useqr.app/google-review
- https://useqr.app/feedback