One identifier.
Many surfaces.
The identifier is issued once and never changes. What changes is the surface it travels on.
Issued by us. Owned by the product.
No external numbering agency, no annual membership, no prefix application.
Each identifier is a random string on a permanent address. Random matters: sequential numbers let anyone walk your catalogue, count your production and find products that have not shipped yet.
Granularity is yours — one identifier per model, per batch, or per individual item. Once a product is on the market, that choice is fixed; changing it means issuing a new identifier that points back at the old one.
Re-personalising a tag never mints a new identity. The physical chip may be rewritten; the product keeps the identifier printed on the box.
Choose by what you are defending.
A passport only needs to be readable. Authenticity is what decides the carrier.
| Carrier | What it proves | Typical use |
|---|---|---|
| Printed code | Carries the identifier. Copyable with a camera. | Passport-only programmes; the EU battery carrier |
| Printed code + activation code | First use claims the item; later scans say so. | Low-cost lines needing a duplication signal |
| Basic NFC | Chip identity and a counter. No secret inside. | Tap convenience, low cloning risk |
| Dynamic-signature NFC | A chip secret signs a fresh answer every tap. | Products worth counterfeiting |
| Dynamic-encryption NFC | Encrypted identity plus signature. | High-value goods, ownership certificates |
| Tamper-evident NFC | Reports irreversibly whether the seal was broken. | Refill fraud: spirits, cosmetics, cartridges |
A code printed wrong scraps the batch.
So we generate the file, not a specification for someone else to interpret.
Every unit ships as vector artwork with the frame, the corner marker, the quiet zone, a module size that survives your substrate, an error-correction level chosen for damage, and the readable identifier set beside the code.
The code contains the identifier and nothing else. No campaign parameters, no tracking tails — extra payload is the most common reason a code fails inspection after the run is printed.
For NFC carriers, personalisation happens on your line and the memory is write-locked afterwards, so a tag cannot be re-pointed at a different product later.
How this runs on a production line →Which carrier fits your product?
It depends on what gets counterfeited, and where. That is a ten-minute conversation.