# QR codes for field service

> Field-service teams use QR codes as the machine's filing cabinet — a durable tag on each asset linking its full service history — plus job-sheet codes with the ticket number in the URL, and payment codes on invoices so the job is paid before the van leaves. A sign-off or feedback code closes the visit.

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

---

## The codes that earn their place

| Code | Where | Why |
|---|---|---|
| Service-history tag | On the boiler, AHU, compressor | Every engineer reads the machine's past at the machine |
| Job-sheet code | Printed ticket, works order | Scan opens this job — notes, parts, customer sign-off |
| Payment code | Invoice left on completion | Paid at the door beats a 30-day chase |
| [Feedback](/feedback-qr-code) | Completion note | The unhappy customer tells you, not the review sites |

## The machine is the filing cabinet

The recurring failure in field service is context: an engineer stands at a unit another
firm installed, with no history, phoning an office that is searching a shared drive. The
fix is the [asset-tag pattern](/docs/ecommerce/qr-code-asset-tagging) — a tag on the
machine whose URL carries the asset ID:

```
https://service.example/assets/AHU-0231
```

Behind it: install date, model and serial, every visit, every part fitted. The tag makes
the machine self-describing to whoever stands in front of it next, including your own
engineer three years on. Plant rooms are hot, damp and occasionally pressure-washed, so
use [weatherproof labels](/docs/print/weatherproof-qr-code-stickers) — or
[etched tags](/docs/print/qr-codes-etched-vs-printed) on kit that outlives any sticker —
and generate the run per asset register with [bulk](/bulk).

## Job sheets with the ticket in the URL

Printed works orders still rule field service, and a code per sheet — ticket number in
the URL — bridges paper and system: the engineer scans to open this job's live record,
attach photos and capture the customer's sign-off on their own phone. No app install,
no laptop in the van.

## Get paid before the van leaves

An [invoice payment code](/docs/payments/qr-code-for-invoices) on the completion
paperwork converts "we'll pay the invoice" into payment on the spot, using whichever
rail the region trusts — an [EPC code](/epc-qr-code) prefilled with amount and reference
in much of Europe, [UPI](/upi-qr-code) in India. The reference field is the part that
saves the bookkeeper: it reconciles the payment to the job automatically.

## What goes wrong

- Histories filed by customer address rather than asset — buildings have many machines,
  and machines move.
- Paper labels in plant rooms; a year of heat and drips later the tag is gone.
- A payment code pointing at a generic "pay us" page with no amount or reference — the
  customer abandons, and payment reverts to the 30-day chase.

## FAQ

### How do field-service companies use QR codes on equipment?

A durable tag on each asset encodes its ID in a URL linking the full service history —
install date, visits, parts. Any engineer at the machine gets complete context in one
scan, which is worth more than any office phone call.

### What should a job-sheet QR code contain?

A URL with the ticket number, opening that job's live record for notes, photos and
customer sign-off. Never encode job details themselves in the payload — the sheet gets
left behind, and paper payloads cannot be corrected.

### Can a QR code take payment at the end of a service visit?

Yes — print a payment code on the completion invoice with amount and reference
prefilled, using the regional rail (EPC in the SEPA area, UPI in India). On-the-spot
settlement measurably beats invoicing for small-ticket domestic work.

## Try it

- https://useqr.app/url
- https://useqr.app/epc
- https://useqr.app/upi
- https://useqr.app/feedback