Assets are rarely one thing. When something fails in the field, "the gate is broken" isn't actionable — "the coin acceptor in Gate 3, serial SPK-100042, installed 14 months ago" is. Every component gets its own record, its own history, and its own QR label.
Competing tools track parts as a free-text note at best. Here, components are structured records with their own identity — and the QR label makes that identity physical, on the part, not just in the database.
Every component gets a detail page: status, custom fields from its definition (serial number, firmware, part number), assigned assets, and a full audit trail. Not a free-text note on the parent.
Same claim flow as assets: print pool labels in batches ahead of time, stick one on the part, claim it in seconds. Unattached spares work too — label it on the shelf, attach it to an asset when it's installed.
Serial, install date, swap history — one scan, no app. Works with any phone camera, and the technician lands inside the parent asset's context, not on a bare record.
Detach the spare from the service van's kit, attach it to the machine — one action in the field. Van to machine, shelf to anywhere, asset to asset: no re-labelling, no lost history.
Pull a failed component and reassign it to your workshop — or let a workflow do it: mark it faulty and it's assigned for repair automatically, with the right people notified. Once repaired, it transfers back out like any spare.
Pick a definition, set a serial pattern, and create the whole batch with sequential serials — then print every label as one sheet. Rolling out soon.
A ticket gate is a gate motor, a card reader, a display panel, and a safety sensor. Component-level knowledge usually lives in one senior technician's head — which display panel is in which kiosk, which parts were swapped last quarter, which spares are on the shelf. None of it written down, all of it lost when that person is on holiday.
Asset labels open the machine; component labels open the part. Pair this with free vinyl QR asset tags on an annual plan and the whole fleet — machines and parts — is one scan away.
Unassigned pool codes can be printed in batches ahead of time — claiming one to a component takes seconds in the field.
Generate a sheet of unassigned QR codes and print them in one batch — before you know what they'll go on.
On the installed component, or on the spare sitting on the shelf — the label doesn't care yet.
First scan claims the code to that component. Same flow you already use for assets.
Opens the component page — parent asset context, serial, custom fields, and full history.
From the blog
How QR code asset tagging works in practice — QR vs barcode vs RFID, label materials that survive a worksho…
The foundation of effective maintenance management isn't your work orders or schedules — it's how you defin…
Poor asset management drains money through downtime, ghost assets, and compliance risks. Learn the hidden c…
Set up your first component definitions, claim a QR label, and scan it with your own phone — all inside a free trial workspace. No call required.
No credit card required · Cancel any time
We use cookies to analyse site traffic and improve your experience. Read our cookie policy
