The asset sticker: a code on the part itself

A location sticker says «where»; an asset sticker says «which part». A passenger bridge with three motors is not served by one door sticker.

Create and print

From the asset page → «Asset stickers» card: create a sticker and its code image appears at once, then print. The sticker carries the part's name and its readable code, and scanning opens a public report page.

Three rules that keep the record honest

1. The code forces its asset. The scan page shows no asset picker: the code names the part. A mismatched asset injected into the request is refused — otherwise the sticker becomes a suggestion to be overridden, and the report lands in the wrong part's record.
2. No location is stored on the sticker. Location is derived from the asset at read time, so a part moved from one hall to another takes its sticker with it — no reprint.
3. The location sticker stays. «A leak in the corridor ceiling» is a fault in a place, not in a part — two doors, not one.

Damaged or lost

• Revoke: kills the code, so a scan does nothing.
• Rotate: mints a new code for the same part — for a torn or mis-printed sticker.

Read next

• The site QR profile: a code is an address, not a key
• Fault reports: from a scanned sticker to a work order