ESPR requires a DPP to be accessible through a , 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.
ESPR does not select QR code or NFC for every Digital Product Passport. The product-group delegated act specifies the carrier and its placement. Separate legislation can be more specific: the Batteries Regulation requires a QR code for covered battery passports from 18 February 2027.
A practical comparison for choosing a DPP 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. |
Sources (1) | |||
| Scan and tap interaction | 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. |
Sources (2)
| |||
| Durability and interference | 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. |
Sources (2)
| |||
| Payload and storage capacity | 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. |
Sources (2)
| |||
| Accessibility and fallback access | 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. |
Sources (2)
| |||
| Cost and environmental burden | 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. |
Sources (2)
| |||
| Product fit and legal carrier rules | QR is a practical candidate when public, low-cost, camera-readable access is enough and the product can keep a printed symbol visible. | NFC is a practical candidate when the product needs a protected tap interface and the extra cost and instructions are justified. | Check the applicable legal act first. If it leaves a choice, match the carrier to the product environment and document the decision. |
Sources (1) | |||
| 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 can suit a DPP that needs embedded or protected placement, although it is less obvious to customers at a glance. | Where the applicable rule permits either option, compare the need for visible access with the need for protected placement. |
Sources (1) | |||
| 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 works well alone, check whether the delegated act permits another carrier or more than one carrier before changing the design. |
Sources (1) | |||
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.
Sources (1)
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.
Sources (2)
Primary legal source for DPP essential requirements, including data carriers, unique product identifiers, access rights, interoperability, registry links, and Annex III identifier standards.
data carrier and the unique product identifier
Technical design guidance used for QR/NFC carrier tradeoffs, scanner experience, durability, placement, payload, accessibility, and online DPP portal access.
Main options for data carriers
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.
Sources (2)
Primary legal source for DPP essential requirements, including data carriers, unique product identifiers, access rights, interoperability, registry links, and Annex III identifier standards.
data carrier and the unique product identifier
Technical design guidance used for QR/NFC carrier tradeoffs, scanner experience, durability, placement, payload, accessibility, and online DPP portal access.
Main options for data carriers
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.
Sources (2)
Primary legal source for DPP essential requirements, including data carriers, unique product identifiers, access rights, interoperability, registry links, and Annex III identifier standards.
data carrier and the unique product identifier
Technical design guidance used for QR/NFC carrier tradeoffs, scanner experience, durability, placement, payload, accessibility, and online DPP portal access.
Main options for data carriers
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.
Sources (2)
Primary legal source for DPP essential requirements, including data carriers, unique product identifiers, access rights, interoperability, registry links, and Annex III identifier standards.
data carrier and the unique product identifier
Technical design guidance used for QR/NFC carrier tradeoffs, scanner experience, durability, placement, payload, accessibility, and online DPP portal access.
Main options for data carriers
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.
Sources (2)
Primary legal source for DPP essential requirements, including data carriers, unique product identifiers, access rights, interoperability, registry links, and Annex III identifier standards.
data carrier and the unique product identifier
Technical design guidance used for QR/NFC carrier tradeoffs, scanner experience, durability, placement, payload, accessibility, and online DPP portal access.
Main options for data carriers
QR is a practical candidate when public, low-cost, camera-readable access is enough and the product can keep a printed symbol visible.
NFC is a practical candidate when the product needs a protected tap interface and the extra cost and instructions are justified.
Check the applicable legal act first. If it leaves a choice, match the carrier to the product environment and document the decision.
Sources (1)
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 can suit a DPP that needs embedded or protected placement, although it is less obvious to customers at a glance.
Where the applicable rule permits either option, compare the need for visible access with the need for protected placement.
Sources (1)
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 works well alone, check whether the delegated act permits another carrier or more than one carrier before changing the design.
Sources (1)
No universal QR-code or NFC mandate is supported by the sources. ESPR says the 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.
A DPP team should therefore treat QR and NFC as design options until the applicable rule is known. For ESPR products, the delegated act controls where the carrier sits and whether the passport identifies a model, batch, or item. For covered batteries, Article 77 of the Batteries Regulation requires a QR code linked to the battery's unique identifier.
Citations (2)
Supports the legal baseline: DPP access through a data carrier, delegated-act control over placement, unique product identifier requirements, and Annex III identifier standards.
physically present on the product, its packaging or on documentation
Article 77 sets the battery-passport scope and date; Article 77(3) requires the passport to be accessible through a QR code linked to a unique identifier.
accessible through the QR code
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.
Citations (1)
Supports QR-code selection criteria: phone-camera access, line-of-sight reading, label placement, quiet-zone concerns, payload-size effects, and durability considerations.
QR-codes and DataMatrixes require line-of-sight
Check whether the chosen carrier, identifier, resolver, and public access path match ESPR requirements and the product's real scanning environment.
NFC can be a stronger design option where close-range tap access is acceptable, the product surface makes printed codes unreliable, or the product needs a protected 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 adds electronic components, cost, environmental burden, and a different failure mode. Users also need to know where to tap, so physical cues and accessible instructions matter.
Citations (1)
Supports NFC selection criteria: passive RFID as a carrier option, close-proximity alignment, durability considerations, and cost/environment tradeoffs.
NFC tags require alignment in close proximity
Freeze the 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.
Citations (2)
Supports DPP requirements for easy access, access rights, machine-readable interoperable data, standards alignment, and identifier lifecycle rules.
free of charge and easy access
Supports practical test criteria for reading mode, distance, lifespan, payload, placement, online access, and vulnerable-consumer accessibility.
multiple ways to represent information and user interaction
"Main options for data carriers"
"QR-codes and DataMatrixes require line-of-sight"
"NFC tags require alignment in close proximity"
"multiple ways to represent information and user interaction"
"data carrier and the unique product identifier"
"physically present on the product, its packaging or on documentation"
"free of charge and easy access"
"accessible through the QR code"
FAQ on customs access under the EU Digital Product Passport: what customs can verify, how the registry and public portal differ, and how access rights limit DPP data.
FAQ on how ESPR Digital Product Passport identifiers connect products, economic operators, facilities, data carriers, resolvers and registry evidence.
How to separate public, restricted, authority, and customs access in EU Digital Product Passport designs under ESPR and battery passport rules.
FAQ on the ESPR Digital Product Passport registry: what it stores, who uploads data, how identifiers work, and what teams should avoid assuming.
FAQ on EU Digital Product Passport product priority: batteries have a separate passport rule, while ESPR product groups depend on the working plan and delegated acts.
DPP responsibility under the EU ESPR: how manufacturers, importers, distributors, suppliers, service providers, and delegated acts fit together.
Plan EU Digital Product Passport data fields, identifiers, access rights, update owners, registry inputs, and evidence records against ESPR Annex III and product-specific delegated acts.
Compare EU Digital Product Passports with digital twins: legal access duties, identifiers, public and restricted data, evidence, governance, and reuse limits.
Compare EU regulated digital product passports with paper, PDF, web, and internal product passports across access, identifiers, data carriers, restricted data, customs checks, registry, and interoperability.
Review public, restricted, and customs access for EU Digital Product Passports, including registry handoffs, portal access rights, and release-for-free-circulation evidence.
Assign accountable owners for EU Digital Product Passport data, access rights, supplier inputs, resolver links, registry uploads, verification checks, and retained evidence.
An intake workflow for EU Digital Product Passport data models: product scope, legal status, field owner, evidence, access class, identifiers, carrier, registry mapping, and publication readiness.
Build EU Digital Product Passport governance controls for data owners, supplier evidence, access logs, validation checks, audit records, and product release gates.
EU Digital Product Passport Registry and web portal integration guide based on official sources: identifiers, carriers, access rights, providers, and lookup design.
Compare the ESPR Digital Product Passport framework with the EU Batteries Regulation battery passport by scope, timing, data, access rights, identifiers, registry, governance, and evidence.
Compare the EU Digital Product Passport with EPREL: product-passport scope, energy-label database role, access model, identifiers, data carriers, and overlap limits.
Compare EU Digital Product Passport requirements with GS1 Digital Link: legal scope, identifiers, data carriers, access rights, registry, portal, customs checks, and implementation consequences.
How ESPR Digital Product Passport access should be split across public users, restricted actors, authorities, customs, the EU registry, and the web portal.
DPP architecture guidance for data carriers, product identifiers, resolver lookup paths, access rights, registry integration, and interoperability without premature protocol mandates.
Check whether an ESPR delegated act or battery passport rule may require a Digital Product Passport, which operator owns it, and what evidence to keep.
Guide to EU Digital Product Passport architecture: data carriers, identifiers, access rights, registry, portal, supplier flows, customs checks, and governance.
A concrete EU Digital Product Passport readiness checklist covering product-group scope, passport fields, identifiers, data carriers, access rights, supplier evidence, registry preparation, and publication controls.
EU Digital Product Passport compliance guide covering ESPR passport data, identifiers, data carriers, access rights, registry readiness, supplier validation, and evidence.
How to choose DPP data carriers, identifiers, access rights, and scanning UX under ESPR Articles 9-14, with QR, NFC, RFID, registry, and customs constraints.
How to plan Digital Product Passport data fields under ESPR: delegated-act scope, Annex III data categories, access rights, customs data, and supplier validation.
EU Digital Product Passport calendar covering the live DPP Registry, ESPR product-rule milestones, and fixed battery passport dates.
Direct answers on EU Digital Product Passport scope, creators, product groups, registry, customs checks, access rights, identifiers, data carriers, and governance.
How to design Digital Product Passport identifiers, QR or other data carriers, resolver links, registry records, access paths, and evidence without overclaiming the EU rules.
How EU Digital Product Passport breaches can lead to national penalties, corrective action, market restrictions, and customs holds under ESPR or battery law.
Prepare product groups for EU Digital Product Passport rules by tracking ESPR delegated-act status, data fields, suppliers, identifiers, access rights, and registry handoffs.
Overview of EU Digital Product Passport requirements under ESPR: product-specific delegated acts, data fields, identifiers, carriers, registry, access rights, supplier data validation, and open points.
Build a supplier data validation file for EU Digital Product Passports: source owner, product link, access class, data model fit, evidence quality, approval record, and release gate.
Select Digital Product Passport vendors against ESPR requirements for identifiers, data carriers, access rights, decentralized storage, registry readiness, portal access, and verification evidence.
A checklist for preparing a product group for an EU Digital Product Passport delegated act, covering data fields, suppliers, identifiers, carriers, access rights, and registry readiness.
Guidance for using QR codes and other data carriers in EU Digital Product Passport programs, including unique identifiers, access, resolver testing, and evidence.
A workflow for checking supplier data before it is used in an EU Digital Product Passport, covering product linkage, evidence, owners, access class, and approval records.
A visitor-friendly explanation of EU Digital Product Passports under ESPR: product data, identifiers, data carriers, access rights, registry, web portal, and delegated acts.