A connected product is a physical item that carries its own unique digital identity able to authenticate itself, report where it is, accumulate a verifiable history, and communicate directly with consumers. Understanding how the technology works, what it delivers, and why the infrastructure decision matters is the starting point for any brand building product identity at scale.
Definition: A connected product is a physical item embedded with a unique digital identity, via NFC, RFID, or a secure serialised identifier, linked to a cloud record that stores and accumulates data across the product’s entire lifecycle: from manufacture through distribution, first sale, service, resale, and end of life. The product can speak for itself. Every interaction generates intelligence. The identity travels with the product, not with the packaging it left in.
Most products today are identified at the SKU or batch level. A barcode or a standard QR code on a bottle of premium gin tells a logistics system: this is product X, from brand Y. It does not say: this is unit number 847,293 of product X, which left the bottling hall in Cognac on 14 March, was allocated to the UK market, was scanned by a consumer in a bar in Edinburgh on 22 April, and has never been opened.
That second level of specificity, item-level, individual, persistent, is what “connected” means. A connected product has a digital identity as individual and permanent as a serial number, but richer: it is linked to a cloud record that updates every time the product is interacted with, and accessible to any authorised party with a compatible reader, across the entire product lifecycle.
The commercial significance of this shift is not incremental. Brands that know where individual products are in their distribution network can detect diversion before it damages pricing. Brands whose products communicate directly with consumers can build relationships that indirect distribution makes impossible. And brands deploying product-level identity infrastructure today are simultaneously building the foundation for EU Digital Product Passport compliance, without a separate regulatory investment.
The strategic question is not whether to connect products it is who governs the identity. Product identity is becoming infrastructure across retail, supply chain, authentication, and regulation. Brands that define and govern their own product identity control the data and the relationship. Those that defer to platform intermediaries or technology vendors to define it may find they have delegated a strategically critical asset.
Secure NFC chips use AES-128-based cryptographic authentication (specifically, CMAC-based Secure Unique NFC message generation) that produces a unique output on every tap — impossible to reproduce without the chip’s secret key. Each tap is also a data event: timestamped, linked to the chip’s identity, and available to the brand’s intelligence platform for grey market monitoring and consumer analytics.
Details:
– Frequency: 13.56 MHz (HF)
– Read range: ~4 cm
– Consumer reader: All modern smartphones
– Security: AES-CMAC cryptographic
– Best for: consumer authentication, grey market detection, luxury, fine wine, premium spirits, post-purchase engagement
Standard UHF tags (EPC Gen2 / ISO 18000-6C) broadcast a fixed electronic product code and lack the cryptographic capability of secure NFC. This makes them suitable for supply chain tracking where the threat model is inventory discrepancy rather than sophisticated counterfeiting, but not appropriate as the primary authentication mechanism against motivated counterfeiters. In connected product programmes, UHF RFID is typically deployed on outer packaging or logistics labels, working alongside NFC chips embedded in the product itself.
Details:
– Frequency: 860–960 MHz (UHF)
– Read range: Up to ~10 m
– Consumer reader: Dedicated hardware required
– Security: Basic (EPC Gen2, no crypto)
– Best for: supply chain tracking, warehouse inventory, logistics gate scanning, retail stock management
Serialised QR codes offer meaningful protection for high-volume lines where per-unit NFC cost is a constraint. They provide the same geographic scan intelligence as NFC — each scan is a timestamped, located data event — and the same grey market detection capability. Their limitation relative to NFC is physical: the code is visible on the label surface, and a sufficiently motivated counterfeiter can photograph and attempt to replicate it. Duplication detection catches the attempt on the second scan, but the first scan of a cloned code may not raise an alert. For high-value products where label fraud is a primary threat, NFC’s invisible integration is the stronger choice.
Details
– Format: Printed label surface
– Reader: Any smartphone camera
– Security: Duplication detection
– Best for: high-volume lines, mass-premium products, markets where NFC integration cost is disproportionate to per-unit margin
The unified identity principle: NFC, UHF RFID, and serialised QR can all be deployed simultaneously across a product range but they must point to the same underlying item-level identity record. When each technology creates its own data structure and product reference, scan events from different technologies cannot be correlated, grey market intelligence becomes fragmented, and each new use case requires rebuilding from scratch. The technology is an access layer. The identity underneath it is the infrastructure that matters.
The EU Digital Product Passport is the regulatory dimension of a shift that commercially driven brands are already making. The DPP requires brands to maintain a persistent, accessible, item-level record of each product’s material composition, manufacturing origin, distribution history, and end-of-life routing across the product’s entire lifecycle, accessible to consumers, supply chain partners, and regulators through a standardised digital interface.
Connected product infrastructure delivers every element the DPP requires. Brands that deploy NFC authentication for commercial reasons: authentication, grey market detection, consumer engagement, are simultaneously building the data infrastructure that satisfies DPP obligations, not as a parallel investment but as a by-product of the same per-unit deployment.
The compliance argument for acting now: DPP requirements are expanding, new product categories, richer data fields, stricter verification standards, on a regulatory timeline that has already started. Brands deploying connected product infrastructure today generate compliance data as a by-product of their commercial programme. Those who wait build the same infrastructure under regulatory deadline pressure, without the commercial returns that justify the investment.
The single most consequential decision in any connected product programme is not which access technology to use it is how the product identity is structured. Brands that define one unified item-level identity, governed centrally and applied across compliance, supply chain, authentication, resale, and consumer engagement, can build every capability on the same foundation. Brands that allow identity to fragment different identifiers for different functions, introduced separately by compliance, logistics, marketing, or technology teams embed technical debt that becomes expensive and sometimes impossible to reverse.
Connected product programmes that scale successfully share a consistent implementation pattern: they start with an identity architecture decision, not a consumer experience decision. The consumer-facing tap experience is a surface built on the identity infrastructure — it can be refined, personalised, and extended indefinitely. The identity architecture, once deployed at scale, is costly to change.
Decide: one unified item-level identity across all functions, or separate identifiers per programme. Map which systems will need to access the product record supply chain, compliance, CRM, e-commerce and design the identity model to serve all of them from day one. This decision is harder to reverse than any technology choice.
Choose the physical carrier (NFC, UHF, QR, or a combination) based on the product’s threat profile, manufacturing constraints, and consumer interaction requirements. Brief existing packaging and manufacturing suppliers on integration specifications. The pilot should use the same identity architecture as the eventual full-scale deployment — not a temporary structure that will need to be replaced.
First serialised units enter distribution. Scan events begin generating supply chain and consumer intelligence. The pilot’s primary objective is to validate that the identity architecture connects to core systems — not to demonstrate scan volume or engagement metrics. Real grey market signals and consumer behavioral data emerge within weeks of product reaching market.
Six months of real scan data provides the evidence base for a full deployment decision — with actual grey market intelligence, actual consumer engagement patterns, and a validated picture of integration performance. The decision to scale is made on evidence, not projection.
Roll out the same identity architecture across remaining product lines and territories, adding use cases — resale authentication, loyalty, DPP compliance data collection — as extensions of the existing record rather than separate programmes. Each new use case adds value to the same infrastructure investment, not cost to a new one.
Selinko’s platform delivers unified product identity across NFC, RFID, and serialised QR — deployed across luxury, spirits, wine, cosmetics, and premium goods brands globally, with full brand data ownership and real-time grey market intelligence built in.
Get in Touch
Blog
Digital Product Identity
Digital Product Identity
Digital Product Identity