Back

Digital Product Identity

Connected Product Technology Explained

Eugenia Vitali


01 Jun 2026

integration

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.

What Makes a Product "Connected" and Why It Matters

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.

How Connected Product Technology Works: The Four Layers

A connected product system is not a single technology — it is four layers working together. Understanding each layer separately clarifies which decisions are infrastructure choices and which are feature choices.

  • The physical carrier: NFC chip, RFID tag, or serialised QR code
    The access technology embedded in or applied to the product. This is how the product’s digital identity is made physically accessible — via a smartphone tap (NFC), a reader gate (UHF RFID), or a camera scan (QR). The carrier is not the identity itself: it is the interface through which the identity is reached. Multiple carriers can point to the same identity, and the carrier choice can evolve over time without rebuilding the identity infrastructure beneath it.
  • The product identity: the unique item-level digital record
    The cloud record that exists exactly once for each physical unit. Created at the point of production, it stores the product’s manufacturing origin, expression or variant, batch reference, allocated distribution territory, and every event in the product’s lifecycle that has since been recorded. This is the product’s permanent identity not a session, not a campaign, but a persistent record that accumulates value across years of interactions. The most consequential architectural decision in any connected product programme is whether this identity is unified across all functions or fragmented by system.
  • The validation backend: authentication and intelligence engine
    The cloud infrastructure that validates each interaction against the product identity record, detects anomalies, logs scan events, and generates intelligence from patterns in the data. This is where grey market diversion is detected, a scan in an unexpected territory triggers an alert. Where counterfeit attempts surface, a chip generating an invalid cryptographic response is flagged immediately. And where first-party behavioral data accumulates consumer tap locations, frequencies, and ownership patterns that no distributor sell-in report can provide.
  • The interaction experience: what the consumer or partner sees
    The branded page, verification result, or data output delivered to the person interacting with the product. For a consumer tapping a luxury handbag, this is an authentication confirmation, a provenance story, and a warranty activation. For a customs inspector scanning a palette of spirits, this is a shipment verification and territory confirmation. For an auction house assessing a fine wine, this is a complete ownership and storage history. The experience is a surface built on the identity  and it can change without the identity changing beneath it.

NFC, UHF RFID, and Secure QR: Which Technology for Which Purpose

The three main physical carrier technologies used in connected product deployments are not interchangeable,  each has distinct physical properties, security characteristics, and deployment economics that make it the right choice for specific stages of the product lifecycle and specific threat profiles.
  1. Near Field Communication — 13.56 MHz HF band
    NFC is the dominant technology for consumer-facing connected product authentication. Its defining advantage is native smartphone compatibility: every modern iPhone and Android device has a built-in NFC reader, meaning consumers can tap and verify any NFC-enabled product with no app download and no additional hardware. The chip is embedded invisibly inside the product in a closure, capsule, lining, or sole making it tamper-resistant and removing any surface marking that a counterfeiter could photograph or replicate.

    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

  2. Ultra-High Frequency RFID — 860–960 MHz
    UHF RFID is the standard technology for automated supply chain tracking. Its long read range up to 10 metres with a fixed reader gate and ability to read hundreds of tags simultaneously make it operationally transformative for warehouse management, retail inventory counting, and logistics checkpoint verification. A pallet of tagged products passing through a distribution gate is accounted for in under a second, without anyone handling a single item.

    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

  3. Serialised, server-validated QR codes
    A secure serialised QR code is not the same as a standard batch QR code. Where a standard QR code encodes the same URL for every unit in a production run, a secure serialised QR assigns a unique code to each individual unit — dynamically generated at production, server-validated on every scan, with duplication detection that flags a cloned code on its second scan.

    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.

What Connected Product Technology Delivers Across the Product Lifecycle

The commercial case for connected products is not a single use case it is the accumulation of value across every stage of the product’s life, each delivered through the same per-unit infrastructure investment.

  • At manufacture: Each unit receives a unique serialised identity linked to production origin, batch, and allocated territory. The root of every downstream capability.
  • In distribution: Checkpoint scans track product movement. Geographic anomalies flag diversion routes before pricing distortion reaches reported sales.
  • At authentication: Consumer or trade tap verifies the product is genuine in under 3 seconds. Counterfeit chips generate invalid responses, detected immediately.
  • Post-purchase: Direct brand relationship opened via the product itself. Ownership registration, loyalty, personalised content, after-sales access no retailer as intermediary.
  • Service & repair: Service history logged to the product record. Warranty entitlement verified by tap, not documentation. After-sales routed based on verified product history.
  • Resale & circular economy: Ownership transfer recorded on the product identity. New owner accesses complete provenance history. Resale platforms verify authenticity at scale.

Connected Products and the EU Digital Product Passport

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.

  • DPP Requirement: Item-level product identity, unique per unit
    Serialised at production via NFC chip or secure QR

  • DPP Requirement: Manufacturing origin and material composition data
    Stored in product identity cloud record at creation

  • DPP Requirement: Consumer-accessible product information via digital interface
    Delivered via NFC tap or QR scan, no app required

  • DPP Requirement: Lifecycle event tracking distribution, sale, service, repair
    Each interaction appends a timestamped event to the record

  • DPP Requirement: End-of-life routing and recyclability information
    Stored in product record, accessible at any lifecycle stage

  • DPP Requirement: Persistent identity beyond first sale, resale and secondary market
    Lifecycle identity persists through ownership transfer

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 Architecture Decision That Determines Everything Else

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.

Fragmented Identity Model

  • Separate identifier per function — compliance, logistics, engagement each create their own
  • Consumer scan data cannot be correlated with supply chain scan data
  • Grey market intelligence is partial because data lives in disconnected systems
  • Each new use case requires rebuilding from the same product data
  • DPP compliance requires a new data collection effort, not a reporting layer
  • Switching platform requires renegotiating data access with multiple vendors

Unified Identity Model

  • One item-level identity per unit, defined at production, used across all functions
  • Consumer scans and supply chain scans feed the same intelligence platform
  • Grey market route mapping works because all data is correlated by item identity
  • New use cases — resale, loyalty, DPP — extend the same record, not rebuild it
  • DPP compliance is a reporting layer on existing lifecycle data
  • Brand owns all data and can export it fully at any point

From Pilot to Full Deployment: A Realistic Implementation Path

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.

Weeks 1–4: Define the identity model before selecting the technology

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.

Weeks 5–10: Select carriers and integration points for the pilot product line

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.

Weeks 11–16: Deploy the pilot and start accumulating data

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.

Month 6: Review pilot data and scale the decision on evidence

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.

Month 7+: Scale across the full product range

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.

Build the Connected Product Infrastructure That Scales

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

Discover more articles

All our articles