ESPR requires a DPP to be accessible through a data carrier, but the carrier choice depends on the applicable delegated act and the product context.
Use QR, NFC, DataMatrix, RFID, or another carrier only after checking placement, identifier, standards, durability, accessibility, and scan experience.
Structured answer sets in this page tree.
Cited legal and guidance references.
For an EU Digital Product Passport, the immediate question is not whether QR code or NFC is universally required. ESPR sets essential requirements for a data carrier, unique identifiers, interoperability, access rights, and standards alignment. The practical carrier choice then depends on the product group delegated act and on whether the carrier can remain readable, accessible, and linked to the right passport data for the product's use context.
A practical comparison for choosing a DPP data carrier under ESPR without treating either option as universally mandated.
Best fit where a visible, printed, camera-readable route to the DPP is enough and one-by-one scanning is acceptable.
Best fit where close-range tap access, protected placement, or embedded tagging is worth the extra cost and electronics burden.
| Dimension | QR code | NFC | Operational implication |
|---|---|---|---|
| Scope boundary | QR codes are the more straightforward choice when the DPP must be reachable with a phone camera and a visible printed carrier is acceptable. | NFC is the better fit when the DPP should be reached by close-range tap and the product can carry an embedded or protected tag. | Use QR for simple public access and NFC for protected, close-range access; in both cases, the delegated act still controls the exact carrier and placement. |
| Covered actors | QR works with a visual camera scan and is familiar for public access, but it needs line of sight, contrast, enough size, and a readable quiet zone. | NFC uses close-range tap interaction and does not need a visible printed code, but users need to know where to tap and devices must align closely. | Prototype the actual customer, repairer, recycler, and authority scan or tap path before artwork and tooling are frozen. |
| Trigger | QR durability depends on print quality, direct marking, label material, product surface, and environmental exposure. | NFC can be embedded or protected, but tag life, material compatibility, damage, and radio-frequency interference still need testing. | Use accelerated and real-use tests for abrasion, weather, cleaning, and handling instead of assuming a lab symbol will survive the product life. |
| Core obligations | QR can hold more data than a linear barcode, but dense payloads make the code bigger and harder to scan. A resolvable identifier or link is usually cleaner. | NFC can carry on-tag data or a link, but capacity and read behavior depend on the selected tag and implementation. | Keep the DPP data in the information system; keep the carrier focused on the unique identifier, resolver, or other minimal access data. |
| Evidence record | QR needs visible placement, readable surrounding text, and alternatives for users who cannot easily locate or scan a printed symbol. | NFC needs tactile or visible cues, clear tap instructions, and alternatives for users whose device or assistive workflow cannot use tap access. | Do not make scan-only access the only practical path where it would exclude customers or professional users who need the DPP. |
| Timing and deadlines | QR is typically a printed carrier and can be cheaper at scale, but reprinting may be needed if the carrier or label becomes obsolete or unreadable. | NFC adds electronics and cost, and the CEN-CENELEC guidance flags environmental burden as a consideration for RFID and NFC tags. | For high-volume products, compare lifecycle impact and replacement risk, not just unit price. |
| Enforcement | QR is the practical default when a public, low-cost, camera-readable carrier is enough and the product can keep a printed symbol visible. | NFC is the practical default when the product needs a protected tap interface and the extra cost and instructions are justified. | Match the carrier to the product environment first, then check the delegated act for any product-group rule on carrier type, placement, or access. |
| Overlap and reuse | QR can double as the visual access point for a DPP portal and a consumer-facing product label, which makes it useful when one printed symbol has to do most of the work. | NFC is better when the DPP needs to be embedded, protected, or shielded from wear, even if that means it is less obvious to customers at a glance. | Choose QR when the same printed carrier should support both labeling and DPP access; choose NFC when durability and embedded placement matter more than visibility. |
| Practical decision rule | Choose QR if your priority is a low-cost carrier that consumers can scan immediately with a camera and the product can tolerate a visible printed code. | Choose NFC if your priority is a protected tap experience, the product surface is hard to print on, or the tag needs to be embedded for durability. | If neither fit works well on its own, use a second carrier or another option allowed by the delegated act rather than forcing one weak choice. |
QR codes are the more straightforward choice when the DPP must be reachable with a phone camera and a visible printed carrier is acceptable.
NFC is the better fit when the DPP should be reached by close-range tap and the product can carry an embedded or protected tag.
Use QR for simple public access and NFC for protected, close-range access; in both cases, the delegated act still controls the exact carrier and placement.
QR works with a visual camera scan and is familiar for public access, but it needs line of sight, contrast, enough size, and a readable quiet zone.
NFC uses close-range tap interaction and does not need a visible printed code, but users need to know where to tap and devices must align closely.
Prototype the actual customer, repairer, recycler, and authority scan or tap path before artwork and tooling are frozen.
QR durability depends on print quality, direct marking, label material, product surface, and environmental exposure.
NFC can be embedded or protected, but tag life, material compatibility, damage, and radio-frequency interference still need testing.
Use accelerated and real-use tests for abrasion, weather, cleaning, and handling instead of assuming a lab symbol will survive the product life.
QR can hold more data than a linear barcode, but dense payloads make the code bigger and harder to scan. A resolvable identifier or link is usually cleaner.
NFC can carry on-tag data or a link, but capacity and read behavior depend on the selected tag and implementation.
Keep the DPP data in the information system; keep the carrier focused on the unique identifier, resolver, or other minimal access data.
QR needs visible placement, readable surrounding text, and alternatives for users who cannot easily locate or scan a printed symbol.
NFC needs tactile or visible cues, clear tap instructions, and alternatives for users whose device or assistive workflow cannot use tap access.
Do not make scan-only access the only practical path where it would exclude customers or professional users who need the DPP.
QR is typically a printed carrier and can be cheaper at scale, but reprinting may be needed if the carrier or label becomes obsolete or unreadable.
NFC adds electronics and cost, and the CEN-CENELEC guidance flags environmental burden as a consideration for RFID and NFC tags.
For high-volume products, compare lifecycle impact and replacement risk, not just unit price.
QR is the practical default when a public, low-cost, camera-readable carrier is enough and the product can keep a printed symbol visible.
NFC is the practical default when the product needs a protected tap interface and the extra cost and instructions are justified.
Match the carrier to the product environment first, then check the delegated act for any product-group rule on carrier type, placement, or access.
QR can double as the visual access point for a DPP portal and a consumer-facing product label, which makes it useful when one printed symbol has to do most of the work.
NFC is better when the DPP needs to be embedded, protected, or shielded from wear, even if that means it is less obvious to customers at a glance.
Choose QR when the same printed carrier should support both labeling and DPP access; choose NFC when durability and embedded placement matter more than visibility.
Choose QR if your priority is a low-cost carrier that consumers can scan immediately with a camera and the product can tolerate a visible printed code.
Choose NFC if your priority is a protected tap experience, the product surface is hard to print on, or the tag needs to be embedded for durability.
If neither fit works well on its own, use a second carrier or another option allowed by the delegated act rather than forcing one weak choice.
No universal QR-code or NFC mandate is supported by the grounding sources. ESPR says the data carrier must be physically present on the product, packaging, or accompanying documentation as specified in the applicable delegated act. It also requires the data carrier and unique product identifier to comply with the standards referenced in Annex III, or equivalent European or international standards until harmonised standards are published.
That means a DPP team should treat QR and NFC as carrier options, not as automatic legal conclusions. The product group delegated act, when applicable, is the control point for where the carrier must sit and what product level it identifies: model, batch, or item.
Supports the legal baseline: DPP access through a data carrier, delegated-act control over placement, unique product identifier requirements, and Annex III identifier standards.
A QR code is usually strongest when the user needs a visible, low-cost, phone-camera route to a web-resolvable DPP page and one-by-one manual scanning is acceptable. The CEN-CENELEC DPP design guidance treats QR codes as one of the main carrier options and notes that smartphone camera applications can read a QR code URI and hand it to the browser in a default consumer flow.
The weak points are physical durability, line-of-sight scanning, label space, and information density. More encoded characters increase the size and scanning burden, so a DPP QR code should normally carry a resolvable identifier or link rather than trying to store the passport itself.
Supports QR-code selection criteria: phone-camera access, line-of-sight reading, label placement, quiet-zone concerns, payload-size effects, and durability considerations.
Check whether the chosen carrier, identifier, resolver, and public access path match ESPR requirements and the product's real scanning environment.
NFC is stronger where close-range tap access is acceptable, the product surface makes printed codes unreliable, or the product needs a more durable embedded carrier. The CEN-CENELEC guidance lists passive RFID tags such as NFC among the main carrier options and distinguishes NFC's close-proximity alignment from QR-code line-of-sight scanning.
NFC is not automatically better. It adds electronic components, cost, environmental burden, and a different failure mode. It also requires the user to know where to tap, so physical cues and accessible instructions matter.
Supports NFC selection criteria: passive RFID as a carrier option, close-proximity alignment, durability considerations, and cost/environment tradeoffs.
Freeze the data carrier only after testing the real product, not just the artwork. ESPR requires easy, free-of-charge access to DPP data according to access rights, while the design guidance highlights reading context, reading distance, lifespan, data capacity, speed, alignment, placement, and accessibility.
The evidence should show that the carrier identifies the right product level, resolves to the right DPP, survives the expected use environment, and works for customers, repairers, recyclers, market surveillance authorities, and other intended users.
Supports DPP requirements for easy access, access rights, machine-readable interoperable data, standards alignment, and identifier lifecycle rules.
Supports practical test criteria for reading mode, distance, lifespan, payload, placement, online access, and vulnerable-consumer accessibility.
"Main options for data carriers"
"Identify, capture and share"