The useful pattern
A code on a physical thing that opens its record: this machine's maintenance history, this batch's traceability, this room's inspection log, this job's details.
That is genuinely valuable because it removes the step where someone has to work out which record corresponds to the thing in front of them, which is where errors enter.
Applications that pay
- Asset management — scan for history, log a fault, book maintenance
- Batch traceability — scan at each movement, building the chain automatically
- Inspection rounds — the scan proves attendance at the location, which is what auditors want
- Job details on site — scan the meter, the panel, the unit and get its specific record
- Stock movements, which is the classic and still the highest-volume use
For inspection rounds the scan is the evidence. A signed sheet proves someone wrote a signature; a scan at the location proves someone was there at that time.
Own the destination
Codes printed on physical assets last for years. If they point at a third-party shortening service or a domain you might not renew, you have created a large future problem.
Point them at your own domain, with a redirect layer you control, so the destination can change without reprinting anything.
Print them properly
- Big enough for the scanning distance — test at the real distance, not on a desk
- Durable material and adhesive for the environment: heat, moisture, cleaning chemicals
- Human-readable identifier printed alongside, for when the code is damaged
- High contrast, with a clear margin around the code
- Positioned where someone can actually reach and see it
Plan for damage
Codes get scratched, painted over, covered in dust and torn off. The human-readable identifier is the fallback, and a process for reprinting and reapplying is part of the system rather than an afterthought.
Track which assets have unreadable codes, so replacement is planned rather than discovered at the point of need.
Keep the destination fast and mobile
The page a code opens is being viewed on a phone, possibly on poor signal, by someone standing up. It should load quickly, show the relevant information immediately, and offer the two or three actions that are likely.
A code that opens a slow desktop-oriented page is a code that people stop scanning.