// FAQ

Frequently Asked Questions

Use a stable internal asset ID, a controlled record URL, or a pre-filled action-form URL. Do not encode credentials, sensitive employee data, confidential notes, access codes, or the complete inventory record.

They can support a controlled low-risk pilot. Use restricted responder access, a separate append-only event log, reviewed state changes, backups, and cycle counts; a pre-filled value is not proof or authorization.

No. A scan or submission records a claim. The workflow should authenticate the actor where needed, validate allowed transitions, preserve history, and reconcile records through physical checks.

There is no universal size. It depends on payload density, camera, distance, contrast, lighting, damage, and surface. Print the human-readable ID and test representative finished labels on their actual assets.

Consider a maintained platform when you need reliable concurrency, multiple sites, approvals, offline sync, maintenance, integrations, regulatory evidence, large-scale reconciliation, or supported access controls and audit logs.

QR and barcodes need line of sight but cost little, and a phone can read a QR label. RFID reads without line of sight and in bulk, at a higher cost. Many teams use QR for walk-up checks and RFID only for hidden or high-volume items.

No. Keep the ID attached to the historical record and never assign it to a different item. GS1 applies the same rule to its asset identifier, which must stay unique well beyond the life of the asset's records.

Print the human-readable asset ID so staff can key it in if the code is damaged, plus the owning organization and a neutral return or support contact. Leave out internal details, purchase values, and anything sensitive.