SmartLinks connected product platform
Platform · Concepts

Anatomy of an item.

Not every product needs the same kind of digital identity. A bottle of wine, a battery, a fridge and a limited-edition trainer all belong on SmartLinks — but they don't all live at the same depth. This page maps the levels, and the four kinds of item record we use to represent them.

The hierarchy

Four levels, from the abstract to the physical.

A SmartLinks record isn't one thing — it's a stack. Depending on what you're selling, you might use every level, or just two.

Level 1
Product
The generic thing

Everything true of every unit ever made: name, description, materials, care, compliance, imagery. One record per SKU.

Level 2
Batch & variant
Optional middle layer

Colourway, size, harvest, production run. Everything true of a group of units. Inherits from the product.

Level 3
Item record
This specific one

The identity of a single unit — with its owner, history, attestations and life cycle. Four flavours, coming up next.

Level 4
Tag
The physical carrier

The QR code or NFC chip on the product. A digital twin of the tag itself — so it can be pre-printed, then bound later.

Four kinds of item record

Not every item needs the same depth of identity.

Under the hood, SmartLinks supports four distinct item-record types — chosen per use case, often mixed within the same brand.

Type 01

Serialised item record

The full digital twin
Use it when: Fridges, paintings, luxury handbags, ebikes, high-value tools — anything with a serial number and an owner who cares.
What lives inside
  • Unique serial identity
  • Named owner & transfer history
  • Attestations (repairs, service, provenance)
  • Custom data & lifecycle events

Deep and rich. Exists from the moment it's manufactured.

Type 02

Tag-linked record

Print now, decide later
Use it when: Pre-printed QR runs and pre-encoded NFC tags where the product isn't decided at press time.
What lives inside
  • Tag exists as a digital twin first
  • Bound to a product later
  • Item record lazy-created on claim
  • Encrypted NFC (SUN / 424) supported

Great for printers, packaging vendors, and any workflow where tags ship before products.

Type 03

Virtual / algorithmic ID

Millions of IDs. Zero rows.
Use it when: Batteries, promotional codes, loyalty tokens, mass-produced SKUs with low claim rates.
What lives inside
  • Cryptographically generated
  • Never stored in the database
  • Verifiable for authenticity without a record
  • Instantiated only when someone claims or acts

The cheapest way to give every unit a unique, secure identity at scale.

Type 04

Batch / variant record

One record, many units
Use it when: Food & beverage batches, apparel colourways, harvest runs — where the story is shared across a group.
What lives inside
  • Shared attributes for the whole group
  • No per-unit instance required
  • Can be promoted to per-item later
  • Ideal for FMCG and compliance batching

Lightweight and fast to deploy. Sits between the product and any per-item records.

Which one do I need?

Six real-world examples, matched to a record type.

ScenarioRecord typeWhy
Premium wine, per bottle
SerialisedProvenance, ownership, resale value.
EV or industrial battery
Virtual IDMillions of units, DPP-ready, low claim rate.
Apparel colourway drop
Batch / variantShared story per run, cheap and fast.
Pre-printed QR sticker run
Tag-linkedProduct unknown at print time; bind later.
Limited-edition sneaker
Serialised + NFCAuthentication, ownership, resale royalties.
FMCG beverage SKU
Batch + virtualBatch for compliance, virtual for engagement.
Billing model

Two ways in, two flavours of record, one clean bill.

We only bill for identities coming into the system. Either you prepay by buying tags, or you mint virtual items for a fraction of a penny and then pay a bit more the moment they materialize into a real, tracked item record.

Origin 01

Prepaid via tags

Buy a pack of tags — the record comes with it

When you buy a batch of SmartLinks tags — QR sheets, NFC labels, pre-encoded rolls — the item record is prepaid at print time. One invoice, done. Whether the tag is ever scanned doesn't change the bill.

Billed: Billed once, per tag, at purchase.
Origin 02

Virtual items

Mint your own IDs — pay a fraction to exist

Bulk-minted virtual records — battery IDs, self-printed labels, algorithmic serials. Super cheap to bring into being. The record exists, but the meaningful money moment is when it gets materialized into something real.

Billed: Fractions of a penny per virtual ID minted.
Two materialization modes

When a virtual ID materializes — or a tag is first scanned into life — it becomes one of two kinds of record. The choice sets the price and the data surface.

Registered item record

Internal use

The record exists and has a history — used internally. Asset tags, batch traceability, ops tooling. No consumer identity attached, no CRM footprint. Cheaper because the data surface is smaller.

Claimable / owned item record

Consumer engagement

The record is wired for a real person to attach to it — consumer lifetime, traced ownership, engagement. Comes with the CRM / Customer capability. Priced higher because that identity carries real GDPR weight and real commercial value.

What we don't bill for

Attestations, service records, ownership transfers, app interactions — none of these are metered. Once a record exists, its life on the platform is included. You pay for identities coming into the system, not for the useful things you do with them afterwards.

Not sure which record type your product needs? We'll map it with you.

30-minute walkthrough: bring a product, we'll show which of the four item-record types fits — and what the tag, batch and product layers look like around it.