# QR codes for asset tagging

> Assets are long-lived where inventory flows, so asset tags optimise for durability over cost: laminated polyester, anodised aluminium or direct engraving, carrying an opaque asset ID that resolves in your register. A tag must outlive repaints, solvents and a decade of handling, and the payload must outlive system migrations.

Source: https://useqr.app/docs/ecommerce/qr-code-asset-tagging · Last reviewed 2026-08-21 · UseQR is free forever, no signup.

---

## Assets are not inventory

The distinction decides every design choice, so it goes first. **Inventory flows**:
stock arrives, sits briefly, leaves; its labels live weeks and die with the carton.
**Assets persist**: the laptop, the forklift, the lab instrument stay for five to
fifteen years, get audited annually, and carry their tag through repaints, relocations
and two changes of asset-management software. [Inventory labelling](/docs/ecommerce/qr-code-inventory-management)
optimises for cost per label; asset tagging optimises for **survival per decade**. A
thermal sticker that is perfect on a shipping carton is the wrong answer on a generator.

## The tag material ladder

Match the material to the asset's environment and life, not to the office label printer:

| Material | Survives | Typical use |
|---|---|---|
| Laminated polyester label | Handling, cleaning sprays, indoor UV, years | IT equipment, furniture, AV kit |
| Subsurface-printed polyester | Abrasion (print is under the laminate) | Anything handled daily |
| Anodised aluminium plate | Solvents, outdoor UV, heat, decades | Plant, vehicles, outdoor kit |
| Direct laser engraving | Everything the substrate survives | Tools, metal housings: see [etched vs printed](/docs/print/qr-codes-etched-vs-printed) |

Two physical notes that catch people: engraved and etched codes rely on shadow contrast,
so they need [more careful lighting and contrast thinking](/docs/print/qr-codes-on-metal)
than printed labels; and any laminate must be **matt**, gloss over a code creates the
glare failure described in
[laminate effects on scanning](/docs/print/laminate-and-varnish-effects-on-scanning).
Size: tags are scanned in-hand or at arm's length, so **1.5–2.5 cm** of code works;
error correction **Q or H**, because scratches are the tag's whole life.

## Payload: an opaque ID, nothing else

The tag will outlive your asset-management system: plan for it. Encode an **opaque
asset ID**, ideally wrapped in a URL on a domain you control:

```
assets.example.com/a/AST-04412
```

- **Not** the asset's name, owner, location or value, all of that changes, and a tag
  is forever; it lives in the register, resolved at scan time.
- **Not** a deep link into this year's SaaS tool, when you migrate systems, a
  vendor-domain URL dies on ten thousand tags. Your own domain redirects wherever the
  register lives this decade, the same
  [permanence logic as packaging](/docs/ecommerce/qr-codes-on-product-packaging).
- A bare ID (no URL) is acceptable where scanning happens only inside a dedicated app,
  but the URL costs nothing and keeps every phone a valid scanner.

Generate tag sets [in bulk](/bulk) against your register export, or
`POST /api/v1/qr/batch` for **up to 1,000 per request**, and
[verify a specimen tag decodes](/validate) after mounting, curved housings and dark
substrates fail in ways flat proofs do not.

## The audit-scan workflow

The annual fixed-asset audit is where tags repay the setup. The register expects the
asset; the auditor walks the floor scanning tags; each scan timestamps
found-here-on-this-date with the scanner's identity, and the exceptions report writes
itself, expected-but-unscanned (missing, moved, disposed) and scanned-but-unexpected
(untracked kit). What took a clipboard week takes a day, and interim spot-checks become
cheap enough to actually happen. The same scan action serves maintenance
(scan → service history → log the job) and staff fault-reporting (scan → "report an
issue with this asset"), which is how tags earn scans between audits.

## FAQ

### What is the difference between asset tagging and inventory labelling?
Lifespan. Inventory labels live weeks on flowing stock and optimise for cost; asset tags live a decade on the same object and optimise for durability: better materials, engraving where needed, and payloads designed to survive system migrations.

### What should an asset tag QR code contain?
An opaque asset ID, ideally in a URL on your own domain that redirects into your current asset register. Never encode names, locations or vendor-tool deep links. Those change, and the tag cannot.

### What material should asset tags be made of?
Laminated polyester for indoor equipment, subsurface-printed polyester for daily handling, anodised aluminium or direct engraving for plant and outdoor assets. Always matt-finish over the code to avoid glare.

### How do QR tags speed up asset audits?
Auditors scan tags as they walk; each scan records the asset as found, timestamped and located. The register then reports what was expected but not scanned and what was scanned but untracked, replacing clipboard reconciliation entirely.

## Try it

- https://useqr.app/url
- https://useqr.app/bulk
- https://useqr.app/validate