What is a Unique Product Identifier in ESPR

See artikkel ei ole veel teie keeles saadaval, seetõttu kuvatakse see inglise keeles.

The Role of Unique Product Identifiers in ESPR

The Ecodesign for Sustainable Products Regulation (ESPR) introduces a requirement that will fundamentally change how products are identified and tracked: every product subject to a Digital Product Passport must carry a unique product identifier that links the physical item to its digital passport data. This identifier is the bridge between the tangible product in a consumer's hands and the comprehensive sustainability, compliance, and provenance information stored in the Digital Product Passport.

Unique product identification is not a new concept in commerce, barcodes and serial numbers have been used for decades. However, the ESPR elevates identification requirements to a new level of specificity and standardisation. The regulation requires identifiers that are globally unique, machine-readable, and capable of resolving to the product's DPP data through standardised protocols.

For manufacturers, understanding the ESPR's identifier requirements is a prerequisite for DPP compliance. The identifier system you choose will affect your production processes, labelling procedures, data infrastructure, and supply chain interactions. Getting this right from the start avoids costly rework as compliance deadlines approach.

What Makes an Identifier "Unique" Under ESPR

The ESPR requires identifiers that are unique at the individual product level, not merely at the product model or batch level. This is a critical distinction. While a traditional barcode might identify that a product is a "Model X Widget," the ESPR's unique identifier must distinguish each individual Model X Widget from every other Model X Widget ever manufactured.

This individual-level identification is known as product serialisation, and it is essential for several reasons:

• Traceability: Individual identifiers enable tracking of specific product instances through the supply chain, from manufacture to point of sale and beyond.
• DPP linkage: Each product instance has its own DPP containing instance-specific data such as date of manufacture, factory of origin, and batch-specific material composition.
• Lifecycle events: Repairs, ownership transfers, and end-of-life processing can be recorded against specific product instances, building a complete lifecycle history.
• Market surveillance: Regulators can trace non-compliant products back to specific production runs and manufacturing facilities.
• Recall management: In the event of a product recall, affected individual units can be precisely identified rather than recalling entire model ranges.

The requirement for instance-level uniqueness means that manufacturers must implement serialisation systems in their production lines, assigning, encoding, and recording a unique identifier for every individual product they manufacture.

Identifier Standards and the GS1 System

The ESPR does not mandate a single identifier standard but establishes criteria that compliant identifiers must meet: global uniqueness, interoperability, machine-readability, and the ability to resolve to DPP data via standardised protocols.

The GS1 system is widely expected to be the primary identifier framework used for ESPR compliance. GS1 manages the global standards for product identification, including GTINs (Global Trade Item Numbers), GLNs (Global Location Numbers), and SSCCs (Serial Shipping Container Codes).

For DPP purposes, the most relevant GS1 identifiers are:

• GTIN + Serial Number: The combination of a product's GTIN (which identifies the product model) and a unique serial number (which identifies the individual instance) creates a globally unique product identifier. This is encoded using GS1 Application Identifiers AI(01) for the GTIN and AI(21) for the serial number.
• GS1 Digital Link URI: A web-addressable URI that encodes the GTIN and serial number in a URL format, enabling resolution to DPP data via web browsers and applications. For example: https://id.gs1.org/01/09506000134352/21/ABC123.
• SGTIN (Serialised GTIN): Used in RFID implementations, combining the GTIN and serial number in a format optimised for radio-frequency data carriers.

The GS1 Digital Link standard is particularly relevant because it combines identification with resolution, the same identifier that uniquely identifies the product also provides a mechanism for accessing the DPP data. This dual function makes it an efficient choice for ESPR compliance.

Data Carriers: Physical Encoding of Identifiers

The unique product identifier must be physically present on the product or its packaging in a machine-readable format known as a data carrier. The ESPR references several types of data carrier that may be used, depending on the product category and specific delegated act requirements.

QR codes are expected to be the most widely used data carrier for consumer-facing products. They can encode GS1 Digital Link URIs, are easy and inexpensive to produce, and can be read by any smartphone camera. QR codes can be printed on product labels, packaging, or even directly onto the product itself.

Other data carrier options include:

• Data Matrix codes: Smaller than QR codes, suitable for products with limited labelling space such as electronic components or medical devices.
• NFC (Near Field Communication) tags: Embedded chips that can be read by smartphones at close range. Useful for products where printed codes might be damaged or undesirable for aesthetic reasons.
• RFID (Radio Frequency Identification) tags: Enable reading at greater distances and through packaging, useful for logistics and supply chain tracking.
• Digital watermarks: Invisible markings embedded in product packaging that can be detected by camera-equipped devices. Emerging technology with potential for products where visible codes are unacceptable.

The specific data carrier requirements for each product category will be defined in the relevant ESPR delegated acts. Manufacturers should monitor these developments to ensure they implement the correct data carrier technology.

Identifier Resolution: Connecting Products to Data

A unique identifier is only useful if it can be resolved, that is, if scanning or reading the identifier leads to the associated DPP data. The ESPR requires that identifiers resolve to DPP information through a standardised, interoperable mechanism.

The GS1 Digital Link resolution framework provides this capability. When a GS1 Digital Link URI is scanned, a resolver service interprets the identifier and directs the request to the appropriate DPP data source. The resolver can serve different content based on the requester, a consumer might see a simplified product information page, while a regulator might receive the complete machine-readable DPP dataset.

This resolution process involves several components:

• The data carrier (QR code, NFC tag, etc.) encoding the unique identifier.
• A resolver service that maps identifiers to data endpoints.
• A DPP data repository that stores and serves the passport information.
• Access control mechanisms that determine what data each stakeholder can access.

The ESPR envisions a decentralised architecture where different manufacturers operate their own DPP systems, with a central EU registry maintaining a directory of identifier-to-DPP mappings. This ensures that any authorised party can resolve any product identifier to its DPP data, regardless of which manufacturer created it.

Implementation Challenges for Manufacturers

Implementing unique product identification at scale presents several practical challenges that manufacturers must address.

Production line integration is often the most significant hurdle. Serialisation requires that each product receives a unique identifier during manufacture, and that this identifier is encoded onto a data carrier and applied to the product. For high-speed production lines manufacturing millions of units annually, this requires investment in marking equipment (laser engravers, inkjet printers, label applicators), vision systems for verification, and data management infrastructure to track which identifiers have been assigned.

Data management at scale is another challenge. A manufacturer producing ten million units per year must generate, store, and manage ten million unique identifiers, along with the associated DPP data for each. This requires robust database infrastructure, reliable data backup, and efficient query capabilities.

Supply chain coordination adds complexity. If products pass through multiple stages of manufacturing, assembly, and packaging, potentially across different companies and countries, the identifier must be consistently maintained and associated with the correct DPP data throughout. This requires agreed protocols for identifier assignment, data exchange formats, and system interoperability.

Finally, there is the question of legacy products. Products already on the market when ESPR requirements take effect may not have unique identifiers or DPPs. Delegated acts will need to address transitional arrangements for existing inventory.

Best Practices for Identifier Implementation

Organisations preparing for ESPR identifier requirements should follow established best practices drawn from industries with mature serialisation experience, such as pharmaceuticals (which already require serialised identifiers under the EU Falsified Medicines Directive).

• Start with GS1 standards: Unless your product category's delegated act specifies otherwise, building on GS1 standards provides the broadest interoperability and the most mature ecosystem of tools and services.
• Generate identifiers centrally: Maintain a central system for generating and managing unique identifiers to prevent duplication and ensure traceability.
• Verify at production: Implement verification systems (camera-based code readers) on production lines to confirm that data carriers are correctly printed and readable.
• Link identifiers to DPP data immediately: Establish the association between the unique identifier and its DPP data record at the point of manufacture, not as a subsequent batch process.
• Plan for data persistence: DPP data must be accessible for the lifetime of the product and potentially beyond. Design your data storage and access infrastructure for long-term availability.
• Test interoperability: Verify that your identifiers can be resolved by third-party systems, not just your own. Test with sample scanning applications and resolver services.

Early investment in these practices will pay dividends as compliance deadlines arrive and as the broader DPP ecosystem matures.

Identifiers and the ESPR Registry

The ESPR mandates the creation of an EU-wide DPP registry that will catalogue all Digital Product Passports for products placed on the EU market. Unique product identifiers are the keys that index this registry, enabling any authorised party to look up the DPP for any covered product.

The registry is expected to operate as a federated system, where manufacturers maintain their own DPP data but register identifier-to-endpoint mappings in the central registry. This architecture preserves manufacturer control over their data while enabling universal discoverability.

Manufacturers will need to register their identifiers and DPP endpoints with the EU registry as part of the market placement process. This registration must occur before the product is made available on the market, ensuring that the DPP is accessible from the moment the product reaches consumers.

The registry will also support market surveillance by enabling authorities to verify that products bear valid identifiers linked to compliant DPPs. Products without registered identifiers, or with identifiers that do not resolve to valid DPP data, will be identifiable as potentially non-compliant.

The Future of Product Identification

The ESPR's unique identifier requirement is part of a broader trend towards comprehensive product-level traceability. As digital infrastructure matures and data carrier technologies improve, the possibilities for product identification will expand significantly.

Emerging technologies such as digital watermarks, molecular tagging, and blockchain-verified identifiers offer new capabilities for anti-counterfeiting, material traceability, and automated sorting in recycling facilities. While not yet mandated by the ESPR, these technologies may feature in future delegated acts or industry best practices.

The convergence of product identification with the Internet of Things (IoT) is also noteworthy. Products equipped with connected sensors can transmit their identifiers automatically, enabling real-time tracking through supply chains, automated inventory management, and dynamic DPP updates based on actual usage patterns.

For businesses, the key takeaway is that unique product identification under the ESPR is not a one-time compliance exercise but the foundation for an evolving digital product infrastructure. The identifier system you implement today should be designed with extensibility in mind, capable of supporting future requirements and technologies as they emerge. Consult the ESPR timeline to understand when your product category will be required to implement these identifier systems.