Digital Product Identity: What It Is and Why It Matters

A product has had a name (the SKU) and a batch for decades. Neither identifies a single item. Twelve thousand bottles share a GTIN and a lot number. When one of them turns up in the wrong market, the GTIN tells you what it is, not which one it is or where it was supposed to go.

Digital product identity adds the missing level: one identity per physical unit, bound to that unit so it can’t be moved to another, and resolvable to a record that grows over the product’s life. It has three parts, and a programme that’s missing any one of them doesn’t have product identity, only a label.

1. Identifier: A unique serial, structured so any system can parse it (GTIN + serial)
2. Data carrier: Binds the identifier to the item (NFC chip, secured QR, RFID, protected barcode)
3. Record: The item’s data and event history, resolvable from the identifier

The definition matters because the term is used loosely. A QR code that links to a product page is sometimes described as a digital identity. It isn’t, by this definition: it identifies a product type, it can be copied, and the page it points to has no record of the item. A serial number printed on a label is closer, because it’s unique, but it fails the second test: nothing binds it to the physical object, so it can be moved to a fake. Digital product identity requires all three parts working together.

A random string is unique but useless outside the system that generated it. A good product identifier is structured so that a distributor’s WMS, a customs system and a Digital Product Passport registry can all parse it without a bespoke integration. In practice that means GS1 standards: the GTIN identifies the product, a serial identifies the unit, and GS1 Digital Link expresses both as a web address.

The identifier is information. The carrier is what physically binds it to the item, and it’s where the security of the whole programme is set. If the carrier can be copied, the identity can be copied, and the record behind it becomes a liability: a counterfeit carrying a genuine identity is more convincing than one carrying none.

The detail on why cryptographic NFC resists copying is in How Secure NFC Tags Work.

The most common mistake at this layer is choosing the carrier for the experience rather than the threat. A beautiful consumer experience on a copyable carrier creates a record that counterfeiters can borrow. The right sequence is: name the threat (copying, refilling, diversion, nothing), choose the carrier that defeats it, then design the experience on top.

Placement matters as much as technology. A carrier on outer packaging disappears at purchase. For authentication after sale, resale and Digital Product Passport access over the product’s life, the carrier has to be on or in the product itself.

An identity that resolves to a static product page is a marketing link. It becomes infrastructure when the record accumulates events: commissioned at the factory, packed into a case, shipped to a distributor, received in a market, scanned by a consumer, transferred to a second owner. Each event has the same shape, so any system can write to it and any system can read it.

{
  "id": "https://id.brand.com/01/03012345678900/21/A7X9K2M4",
  "product": { "gtin": "03012345678900", "batch": "L2611" },
  "intendedMarket": "JP",
  "events": [
    { "type": "commissioned", "at": "2026-09-02T08:14Z", "site": "FR-bottling-01" },
    { "type": "shipped",      "at": "2026-09-09T16:40Z", "to": "distributor-JP-03" },
    { "type": "consumerScan", "at": "2026-10-21T11:02Z", "country": "SG",
      "result": "authentic", "flag": "outside intended market" }
  ]
}

A useful test of any product identity design is to follow one item through its whole life and ask, at each stage, who reads the identity, why, and what they write back. If a stage has no reader, the record has a gap there. If a reader can’t trust what they read, the gap is worse: the record says something false.

Notice that only the first three stages are under the brand’s direct control. Everything from the distributor onwards depends on someone else choosing to read the identity. The design questions that matter most are therefore about those later readers: can they read it without special equipment, do they get something useful, and can the brand trust what comes back?

Consider an anonymised but typical case: a bottle of aged single malt, produced in Scotland, allocated to a distributor in Japan, with a cryptographic tamper-loop NFC tag in the closure.

1. Bottled and commissioned: The tag is encoded on the line and the bottle commissioned against its batch. From this moment it can verify as genuine.
2. Packed and shipped: The bottle is aggregated into a case and pallet. The pallet ships to the Japanese distributor; the bottle inherits ‘JP’ as its intended market.
3. Diverted: Weeks later, the distributor sells part of the allocation to a trader. The case surfaces in a retail shop in Singapore.
4. Scanned by a consumer: A buyer taps the closure. The result is authentic and sealed. The platform records the scan in Singapore and flags it as outside the intended market.
5. Opened and registered: The buyer opens the bottle at home. The tamper loop now reports opened. The buyer registers the bottle and receives tasting content.
6. Empty bottle resurfaces: Months later, the bottle is scanned in a bar, presented as new. The tag reports opened. The scan is flagged as a possible refill.

Three different teams learn something from this one bottle. Supply chain sees diversion from a specific shipment. Marketing gains a registered owner in a market it doesn’t serve directly. Brand protection gets evidence of a refill attempt at a named venue. None of those findings needed an investigator, and all of them came from the same identity.

Sector shapes the first use case, but the identity layer underneath is the same. A spirits brand that starts with refill detection and a fashion brand that starts with DPP end up needing the same three parts.

For sector depth, see NFC Product Authentication for Luxury Brands and NFC Authentication for Wine & Spirits: How It Works and Why It Matters.

The EU’s Ecodesign for Sustainable Products Regulation requires products in scope to carry a Digital Product Passport linked to a unique identifier through a data carrier. In 2026 the EU formally recognised NFC as a compliant data carrier (Implementing Decision (EU) 2026/1736, referencing EN 18220). A brand with product identity in place already has the identifier, the carrier and the record. The passport is a defined subset of that record with access rules.

The reverse is not true. A passport built without an identity layer can meet a compliance date and still be useless for authentication or traceability. Digital Product Identity vs Digital Product Passport: What’s the Difference? sets out exactly where the two overlap and where they don’t.

There’s a practical consequence for project planning. Brands that already run authentication or traceability on item-level identity can treat the passport as a content and access-rights project. Brands without it face an identity project and a content project at the same time, often on a regulatory deadline. The second group tends to make identity decisions quickly, based on what’s cheapest for compliance, and pays for it later. Why DPP Projects Fail When Product Identity Is an Afterthought covers the failure patterns.

Getting started

Most brands don’t start from nothing. They have an existing QR code on packaging, NFC tags from a past campaign, or serialisation in one factory. The starting point is to take stock and decide what can be reused.

1. Audit what’s on your products today: Carriers, identifiers, domains and where the data lives. Note which are secure, standard and brand-owned.
2. Choose the product line with the most overlap: Where counterfeiting, diversion, resale or passport obligations apply together.
3. Fix the foundations: GS1 identifiers, a brand-owned resolver domain, a standard event model, a carrier chosen for the threat.
4. Instrument production and shipment: Commission on the line; capture intended market at shipment.
5. Give the field a reason to scan: Consumer content, retailer verification, resale authentication.
6. Expand by product line: Reuse the same foundations. Each new line costs less than the last.

The first line takes the longest, because the foundations are set there. Brands that get them right find the second and third lines are mostly operational work: new form factors, new production sites, new content.

• ‘We have a QR code, so we have digital identity.’ A model-level QR identifies the product type. It can’t distinguish one unit from another or prove anything.
• ‘Blockchain makes it secure.’ A ledger can make the record tamper-evident. It does nothing to stop the physical carrier being copied. Security starts at the carrier.
• ‘Consumers won’t scan.’ They won’t scan for authentication alone. They do scan when the product gives them something: provenance, care, registration, offers, resale value.
• ‘It’s a marketing project.’ The marketing experience is the visible part. The value is in the record, which serves operations, compliance and brand protection.
• ‘We’ll do it when the DPP requires it.’ Then the identity will be designed for the minimum regulatory requirement, and every other use case will be retrofitted.

• Digital product identity has three parts: a unique, standard identifier; a carrier that binds it to the item; and a record of the item’s data and events.
• Without all three, you have a link or a label, not identity. Security is decided at the carrier.
• Regulation, resale and channel complexity now require item-level identity on the same products.
• One identity can serve authentication, diversion detection, ownership and the Digital Product Passport.
• Use GS1 standards and a brand-owned domain so the identity outlives any vendor.