01
Unique product identifier
A persistent identifier distinguishes the model, batch or individual item at the level required by the applicable product rules.
Identifier and carrier guide
Digital Product Passport QR Codes, NFC and Product Identifiers
A practical guide to choosing the physical access method—and designing the identity, resolver and product-data architecture that makes it trustworthy.
Updated 15 September 2026Industrial implementation guideGeneral guidance, not legal advice
Start with the right question
The tag is not the passport
A QR code or NFC tag is a data carrier: it helps a person or system access an identifier. The Digital Product Passport is the governed digital record behind that access point.
A durable carrier attached to a product can still fail as a DPP implementation if it points to the wrong identity, exposes restricted information, breaks when a URL changes or leads to an unstructured document that cannot be maintained.
The access chain
Four layers from the physical product to the passport
02
Physical data carrier
A QR code, NFC tag or another suitable carrier encodes a standards-based identifier or resolvable link on the product, packaging or documentation.
03
Resolver
The resolver converts the scanned or tapped value into the correct digital destination without coupling the product permanently to one website structure.
04
Digital Product Passport
The passport serves structured product information, evidence and role-appropriate views while preserving governance and lifecycle history.
Design principle
Keep the identifier persistent and the resolver stable. This allows the underlying passport service, permissions and content to evolve without replacing every physical carrier.
Carrier comparison
QR, NFC, RFID and GS1 Digital Link serve different jobs
These are not always mutually exclusive. A manufacturer may use QR for universal public access, NFC for a durable tap experience, and RFID for internal operations—provided every access path is governed against the correct product identity.
| Option | Interaction | Where it helps | What to validate |
|---|---|---|---|
| QR code | Camera scan | Low cost, easy to print, broad smartphone access | Abrasion, contamination, line of sight and print permanence |
| NFC | Tap at close range | Fast mobile interaction, embedded or rugged tag options, no camera aiming | Tag cost, material compatibility, attachment and write protection |
| RFID | Reader-based radio scan | Bulk or longer-range operational identification where suitable | Specialist readers, frequency choice, environment and process integration |
| GS1 Digital Link | Standards-based web identifier | Connects established product identifiers to multiple digital resources | Identifier governance, resolver design and correct implementation |
Industrial selection
Choose for the operating environment
The cheapest tag can become expensive if it detaches, becomes unreadable or forces field teams into an impractical scan process. Test samples on the real product before scaling procurement.
- Does the applicable product-specific rule specify the carrier or its placement?
- Will the carrier sit on the product, packaging or accompanying documentation?
- Must it survive abrasion, water, chemicals, UV, heat, laundering or outdoor use?
- Will customers use ordinary smartphones, or will operators use industrial readers?
- Is line-of-sight scanning practical in the real operating environment?
- Does the product contain metal, liquids or materials that affect radio performance?
- Is the passport model-, batch- or item-level, and how many carriers will be produced?
- Can the encoded destination remain stable if the platform or domain changes?
Multiple carriers, one identity
Use QR and NFC without creating duplicate passports
When QR and NFC provide access to the same product passport, they can encode the same stable resolver URL. The system should treat that as one logical identity and preserve one authoritative passport history.
QR scanhttps://…/r/product-token
NFC taphttps://…/r/product-token
ResolverOne product identity
PassportOne governed record
A practical pilot workflow
- 1Create the product master and required passport template
- 2Create the batch or serialised asset
- 3Issue the persistent product identifier
- 4Generate and test the resolver URL
- 5Encode the URL in QR and/or NFC
- 6Attach the carrier without affecting product safety
- 7Publish the passport and test access on real devices
- 8Record replacement or status changes without rewriting history
EU architecture in 2026
Identifiers now connect to an operational DPP ecosystem
The EU DPP Registry launched in July 2026 with a testing environment. It registers required identifiers and associated metadata, while detailed product data remains decentralised. The applicable product legislation still determines when a passport and registration are mandatory.
EN 18219:2026
Unique identifiers
EN 18220:2026
Data carriers
Registry access
Secure user interface or API
Decentralised data
Product information remains with the responsible system
Test the complete physical-to-digital chain
Connect one real product to a governed DPP
UniQorn Trace™ supports standards-based product identity, QR and NFC access, controlled evidence, stakeholder permissions and lifecycle events in a multi-tenant DPP SaaS platform.
Common questions
DPP QR code and NFC FAQ
Does a Digital Product Passport require a QR code?
Not universally. ESPR requires the passport to be connected through a data carrier to a persistent unique product identifier, while product-specific rules can define the required carrier and where it must appear. QR is common, but it is not the only possible technology.
Can NFC be used for a Digital Product Passport?
NFC can provide convenient tap access where the tag, attachment, smartphone compatibility and operating environment are suitable. The applicable product rules and harmonised data-carrier requirements must still be checked.
Can the same DPP use both QR and NFC?
Yes, a product can use more than one access method when the implementation is governed correctly. If QR and NFC encode the same resolver URL, they should normally resolve to the same logical product identity rather than create conflicting passport records.
What is the difference between a product identifier and a data carrier?
The identifier is the persistent value that identifies the product, batch or item. The data carrier is the physical or digital mechanism—such as a QR code or NFC tag—that carries or provides access to that value.
Should the full passport data be stored on the NFC tag or QR code?
Usually no. The carrier normally contains a compact identifier or resolver link, while governed passport data is maintained in the digital system. This supports updates, permissions, structured data and continuity.
How does the EU DPP Registry affect identifiers?
The Registry stores required registration information, including unique identifiers and associated metadata, while detailed product data remains decentralised. Registration scope and timing still depend on the legislation applicable to the product.
Primary sources
See Regulation (EU) 2024/1781, particularly Articles 9–11; Commission Implementing Decision (EU) 2026/1736 for the harmonised standards; and the European Commission Registry announcement. Verify current product-specific legislation before implementation.
Editorial note: Carrier suitability depends on the product, operating environment and applicable legislation. This guide is not legal, safety or conformity-assessment advice.