--- title: "DPP QR code vs NFC data carrier choices under EU ESPR" canonical_url: "https://www.sorena.io/artifacts/eu/digital-product-passport/faq/qr-code-vs-nfc-carrier-choices" source_url: "https://www.sorena.io/artifacts/eu/digital-product-passport/faq/qr-code-vs-nfc-carrier-choices" author: "Sorena AI" description: "How to choose QR code, NFC, or another data carrier for an EU Digital Product Passport without assuming ESPR mandates one universal carrier." published_at: "2026-05-09" updated_at: "2026-05-09" keywords: - "EU Digital Product Passport" - "ESPR data carrier" - "DPP QR code" - "DPP NFC" - "unique product identifier" - "Digital Product Passport" - "ESPR" - "data carrier" - "QR code" - "NFC" --- **[SORENA](https://www.sorena.io/)** - AI-Powered GRC Platform [Home](https://www.sorena.io/) | [Solutions](https://www.sorena.io/solutions) | [Artifacts](https://www.sorena.io/artifacts) | [About Us](https://www.sorena.io/about-us) | [Contact](https://www.sorena.io/contact) | [Portal](https://app.sorena.io) --- # DPP QR code vs NFC data carrier choices under EU ESPR How to choose QR code, NFC, or another data carrier for an EU Digital Product Passport without assuming ESPR mandates one universal carrier. *FAQ* *DPP* *ESPR* ## EU Digital Product Passport QR code vs NFC data carrier choices 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. 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. ## QR code vs NFC for an EU Digital Product Passport A practical comparison for choosing a DPP data carrier under ESPR without treating either option as universally mandated. - **QR code**: Best fit where a visible, printed, camera-readable route to the DPP is enough and one-by-one scanning is acceptable. - **NFC**: 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 | Sources | | --- | --- | --- | --- | --- | | 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. | [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj?ref=sorena.io) | | 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. | [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj?ref=sorena.io) - Primary legal source for DPP essential requirements, including data carriers, unique product identifiers, access rights, interoperability, registry links, and Annex III identifier standards.
[CEN-CENELEC CWA 18186:2025 Digital Product Passport design guidance](https://www.cencenelec.eu/media/CEN-CENELEC/CWAs/RI/2025/cwa18186_2025.pdf?ref=sorena.io) - Technical design guidance used for QR/NFC carrier tradeoffs, scanner experience, durability, placement, payload, accessibility, and online DPP portal access. | | 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. | [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj?ref=sorena.io) - Primary legal source for DPP essential requirements, including data carriers, unique product identifiers, access rights, interoperability, registry links, and Annex III identifier standards.
[CEN-CENELEC CWA 18186:2025 Digital Product Passport design guidance](https://www.cencenelec.eu/media/CEN-CENELEC/CWAs/RI/2025/cwa18186_2025.pdf?ref=sorena.io) - Technical design guidance used for QR/NFC carrier tradeoffs, scanner experience, durability, placement, payload, accessibility, and online DPP portal access. | | 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. | [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj?ref=sorena.io) - Primary legal source for DPP essential requirements, including data carriers, unique product identifiers, access rights, interoperability, registry links, and Annex III identifier standards.
[CEN-CENELEC CWA 18186:2025 Digital Product Passport design guidance](https://www.cencenelec.eu/media/CEN-CENELEC/CWAs/RI/2025/cwa18186_2025.pdf?ref=sorena.io) - Technical design guidance used for QR/NFC carrier tradeoffs, scanner experience, durability, placement, payload, accessibility, and online DPP portal access. | | 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. | [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj?ref=sorena.io) - Primary legal source for DPP essential requirements, including data carriers, unique product identifiers, access rights, interoperability, registry links, and Annex III identifier standards.
[CEN-CENELEC CWA 18186:2025 Digital Product Passport design guidance](https://www.cencenelec.eu/media/CEN-CENELEC/CWAs/RI/2025/cwa18186_2025.pdf?ref=sorena.io) - Technical design guidance used for QR/NFC carrier tradeoffs, scanner experience, durability, placement, payload, accessibility, and online DPP portal access. | | 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. | [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj?ref=sorena.io) - Primary legal source for DPP essential requirements, including data carriers, unique product identifiers, access rights, interoperability, registry links, and Annex III identifier standards.
[CEN-CENELEC CWA 18186:2025 Digital Product Passport design guidance](https://www.cencenelec.eu/media/CEN-CENELEC/CWAs/RI/2025/cwa18186_2025.pdf?ref=sorena.io) - Technical design guidance used for QR/NFC carrier tradeoffs, scanner experience, durability, placement, payload, accessibility, and online DPP portal access. | | 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. | [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj?ref=sorena.io) | | 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. | [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj?ref=sorena.io) | | 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. | [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj?ref=sorena.io) | Sources for Scope boundary: - [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj?ref=sorena.io) Sources for Covered actors: - [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj?ref=sorena.io) - Primary legal source for DPP essential requirements, including data carriers, unique product identifiers, access rights, interoperability, registry links, and Annex III identifier standards. - Quote: "data carrier and the unique product identifier" - [CEN-CENELEC CWA 18186:2025 Digital Product Passport design guidance](https://www.cencenelec.eu/media/CEN-CENELEC/CWAs/RI/2025/cwa18186_2025.pdf?ref=sorena.io) - Technical design guidance used for QR/NFC carrier tradeoffs, scanner experience, durability, placement, payload, accessibility, and online DPP portal access. - Quote: "Main options for data carriers" Sources for Trigger: - [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj?ref=sorena.io) - Primary legal source for DPP essential requirements, including data carriers, unique product identifiers, access rights, interoperability, registry links, and Annex III identifier standards. - Quote: "data carrier and the unique product identifier" - [CEN-CENELEC CWA 18186:2025 Digital Product Passport design guidance](https://www.cencenelec.eu/media/CEN-CENELEC/CWAs/RI/2025/cwa18186_2025.pdf?ref=sorena.io) - Technical design guidance used for QR/NFC carrier tradeoffs, scanner experience, durability, placement, payload, accessibility, and online DPP portal access. - Quote: "Main options for data carriers" Sources for Core obligations: - [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj?ref=sorena.io) - Primary legal source for DPP essential requirements, including data carriers, unique product identifiers, access rights, interoperability, registry links, and Annex III identifier standards. - Quote: "data carrier and the unique product identifier" - [CEN-CENELEC CWA 18186:2025 Digital Product Passport design guidance](https://www.cencenelec.eu/media/CEN-CENELEC/CWAs/RI/2025/cwa18186_2025.pdf?ref=sorena.io) - Technical design guidance used for QR/NFC carrier tradeoffs, scanner experience, durability, placement, payload, accessibility, and online DPP portal access. - Quote: "Main options for data carriers" Sources for Evidence record: - [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj?ref=sorena.io) - Primary legal source for DPP essential requirements, including data carriers, unique product identifiers, access rights, interoperability, registry links, and Annex III identifier standards. - Quote: "data carrier and the unique product identifier" - [CEN-CENELEC CWA 18186:2025 Digital Product Passport design guidance](https://www.cencenelec.eu/media/CEN-CENELEC/CWAs/RI/2025/cwa18186_2025.pdf?ref=sorena.io) - Technical design guidance used for QR/NFC carrier tradeoffs, scanner experience, durability, placement, payload, accessibility, and online DPP portal access. - Quote: "Main options for data carriers" Sources for Timing and deadlines: - [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj?ref=sorena.io) - Primary legal source for DPP essential requirements, including data carriers, unique product identifiers, access rights, interoperability, registry links, and Annex III identifier standards. - Quote: "data carrier and the unique product identifier" - [CEN-CENELEC CWA 18186:2025 Digital Product Passport design guidance](https://www.cencenelec.eu/media/CEN-CENELEC/CWAs/RI/2025/cwa18186_2025.pdf?ref=sorena.io) - Technical design guidance used for QR/NFC carrier tradeoffs, scanner experience, durability, placement, payload, accessibility, and online DPP portal access. - Quote: "Main options for data carriers" Sources for Enforcement: - [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj?ref=sorena.io) Sources for Overlap and reuse: - [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj?ref=sorena.io) Sources for Practical decision rule: - [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj?ref=sorena.io) ### Practical carrier selection rule - Use QR when the carrier should be visible, cheap to print, and easy for a consumer to scan with a phone camera. - Use NFC when the carrier should be embedded or protected and the user can reasonably be guided to tap in close proximity. - Use a second carrier or another allowed option when a single QR code or NFC tag would be too fragile, hard to access, or too costly to maintain over the product life. - Document fallback access for distance selling, damaged carriers, and users who cannot scan or tap. ## Does ESPR require QR code or NFC for every Digital Product Passport? 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. - Check the delegated act for the product group before selecting the carrier or placement. - Confirm whether the passport data refers to a model, batch, or item. - Keep the carrier and the unique product identifier aligned with ISO/IEC 15459 or equivalent standards where relevant. - Avoid saying that ESPR itself requires QR code, NFC, or any single carrier for every product. Sources for this answer: - [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj?ref=sorena.io) - Supports the legal baseline: DPP access through a data carrier, delegated-act control over placement, unique product identifier requirements, and Annex III identifier standards. ## When is a QR code the stronger DPP carrier choice? 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. - Use QR where visual scanning, printed labels, and broad consumer access matter. - Test label size, contrast, quiet zone, print method, substrate, abrasion, weather exposure, and cleaning exposure. - Place plain-language text near the code so users know it opens the DPP information portal. - Prefer a stable resolver or URL pattern over dense payloads that make the code harder to scan. Sources for this answer: - [CEN-CENELEC CWA 18186:2025 Digital Product Passport design guidance](https://www.cencenelec.eu/media/CEN-CENELEC/CWAs/RI/2025/cwa18186_2025.pdf?ref=sorena.io) - Supports QR-code selection criteria: phone-camera access, line-of-sight reading, label placement, quiet-zone concerns, payload-size effects, and durability considerations. ## When is NFC the stronger DPP carrier choice? 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. - Use NFC where an embedded or protected tag is more realistic than a scannable printed symbol. - Validate tap location, alignment, metal interference, casing material, and expected service environment. - Provide a visible fallback or instruction because NFC is not self-explanatory to every user. - Assess cost and environmental impact before deploying NFC at high product volumes. Sources for this answer: - [CEN-CENELEC CWA 18186:2025 Digital Product Passport design guidance](https://www.cencenelec.eu/media/CEN-CENELEC/CWAs/RI/2025/cwa18186_2025.pdf?ref=sorena.io) - Supports NFC selection criteria: passive RFID as a carrier option, close-proximity alignment, durability considerations, and cost/environment tradeoffs. ## What should teams test before freezing the carrier design? 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. - Identifier: model, batch, or item level; unique product identifier; operator and facility identifiers where required. - Resolution: what the scanner reads, where it resolves, what happens if the first repository is unavailable, and how backup access is handled. - Physical durability: print or tag method, substrate, abrasion, moisture, UV, chemicals, cleaning, temperature, and expected product life. - Scanner UX: camera or tap workflow, distance, angle, lighting, error messages, no-app access where feasible, and online marketplace access where customers cannot touch the product. - Accessibility: text cues, placement reachable by users, compatibility with assistive use patterns, and alternatives where a scan-only path would exclude users. - Standards record: applied data-carrier, identifier, resolver, labelling, and accessibility standards, including any product-group delegated-act rule. Sources for this answer: - [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj?ref=sorena.io) - Supports DPP requirements for easy access, access rights, machine-readable interoperable data, standards alignment, and identifier lifecycle rules. - [CEN-CENELEC CWA 18186:2025 Digital Product Passport design guidance](https://www.cencenelec.eu/media/CEN-CENELEC/CWAs/RI/2025/cwa18186_2025.pdf?ref=sorena.io) - Supports practical test criteria for reading mode, distance, lifespan, payload, placement, online access, and vulnerable-consumer accessibility. ## Primary sources - [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj?ref=sorena.io) - [CEN-CENELEC CWA 18186:2025 Digital Product Passport design guidance](https://www.cencenelec.eu/media/CEN-CENELEC/CWAs/RI/2025/cwa18186_2025.pdf?ref=sorena.io) - Technical design guidance used for QR/NFC carrier tradeoffs, scanner experience, durability, placement, payload, accessibility, and online DPP portal access. - Quote: "Main options for data carriers" - [GS1 Digital Product Passport standards overview](https://www.gs1.org/standards/standards-emerging-regulations/DPP?ref=sorena.io) - Standards-body source for GS1 DPP implementation context, including identifier, capture, and sharing standards relevant to data-carrier implementation. - Quote: "Identify, capture and share" ## Topic Guides - [Annex III Data Model Planning for EU Digital Product Passports](/artifacts/eu/digital-product-passport/annex-iii-data-model-planning.md): 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. - [Digital Product Passport vs Digital Twin](/artifacts/eu/digital-product-passport/dpp-vs-digital-twin.md): Compare EU Digital Product Passports with digital twins: legal access duties, identifiers, public and restricted data, evidence, governance, and reuse limits. - [Digital Product Passport vs Paper Product Passports](/artifacts/eu/digital-product-passport/dpp-vs-traditional-product-passports.md): 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. - [DPP customs access review workflow for ESPR products](/artifacts/eu/digital-product-passport/customs-access-review-workflow.md): Review public, restricted, and customs access for EU Digital Product Passports, including registry handoffs, portal access rights, and release-for-free-circulation evidence. - [DPP Data Governance RACI Template for EU Digital Product Passports](/artifacts/eu/digital-product-passport/dpp-data-governance-raci-template.md): Assign accountable owners for EU Digital Product Passport data, access rights, supplier inputs, resolver links, registry uploads, verification checks, and retained evidence. - [DPP data-model intake workflow for EU Digital Product Passports](/artifacts/eu/digital-product-passport/dpp-data-model-intake-workflow.md): A grounded intake workflow for EU Digital Product Passport data models: product group, delegated-act status, source owner, supplier data, access class, identifiers, carrier, checks, and publication readiness. - [DPP Governance, Verification and Audit Controls](/artifacts/eu/digital-product-passport/governance-verification-and-audit.md): Build EU Digital Product Passport governance controls for data owners, supplier evidence, access logs, validation checks, audit records, and product release gates. - [DPP registry and web portal integration under EU ESPR](/artifacts/eu/digital-product-passport/dpp-registry-and-web-portal-integration.md): Grounded guide to EU Digital Product Passport registry and web portal integration under ESPR, covering identifiers, data carriers, access rights, service providers, and lookup design. - [DPP vs Battery Passport: ESPR and Battery Regulation Comparison](/artifacts/eu/digital-product-passport/dpp-vs-battery-passport.md): 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. - [DPP vs EPREL Comparison](/artifacts/eu/digital-product-passport/dpp-vs-eprel.md): Compare the EU Digital Product Passport with EPREL: product-passport scope, energy-label database role, access model, identifiers, data carriers, and overlap limits. - [DPP vs GS1 Digital Link: Duties vs Standard](/artifacts/eu/digital-product-passport/dpp-vs-gs1-digital-link.md): Compare EU Digital Product Passport requirements with GS1 Digital Link: legal scope, identifiers, data carriers, access rights, registry, portal, customs checks, and implementation consequences. - [EU Digital Product Passport access: public, restricted, and customs views](/artifacts/eu/digital-product-passport/public-restricted-and-customs-access.md): How ESPR Digital Product Passport access should be split across public users, restricted actors, authorities, customs, the EU registry, and the web portal. - [EU Digital Product Passport API and resolver architecture](/artifacts/eu/digital-product-passport/api-and-resolver-architecture.md): Grounded DPP architecture guidance for data carriers, product identifiers, resolver lookup paths, access rights, registry integration, and interoperability without premature protocol mandates. - [EU Digital Product Passport Applicability Test](/artifacts/eu/digital-product-passport/applicability-test.md): 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. - [EU Digital Product Passport architecture and integration](/artifacts/eu/digital-product-passport/architecture-and-integration.md): Grounded guide to EU Digital Product Passport architecture: data carriers, identifiers, access rights, registry, portal, supplier flows, customs checks, and governance. - [EU Digital Product Passport checklist](/artifacts/eu/digital-product-passport/checklist.md): 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: ESPR requirements](/artifacts/eu/digital-product-passport/compliance.md): Grounded EU Digital Product Passport compliance guide covering ESPR passport data, identifiers, data carriers, access rights, registry readiness, supplier validation, and evidence. - [EU Digital Product Passport Data Carriers, Access Control, and UX](/artifacts/eu/digital-product-passport/data-carriers-access-control-and-ux.md): 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. - [EU Digital Product Passport data requirements and fields](/artifacts/eu/digital-product-passport/data-requirements-and-fields.md): 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 deadlines and compliance calendar](/artifacts/eu/digital-product-passport/deadlines-and-compliance-calendar.md): Grounded EU Digital Product Passport calendar for ESPR and battery passport milestones, with product-group dates flagged as dependent on delegated acts. - [EU Digital Product Passport FAQ](/artifacts/eu/digital-product-passport/faq.md): Direct answers on EU Digital Product Passport scope, creators, product groups, registry, customs checks, access rights, identifiers, data carriers, and governance. - [EU Digital Product Passport identifier and data carrier design](/artifacts/eu/digital-product-passport/unique-identifier-and-data-carrier-design.md): 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. - [EU Digital Product Passport penalties and enforcement](/artifacts/eu/digital-product-passport/penalties-and-fines.md): What ESPR says about Digital Product Passport penalties, Member State fine rules, market surveillance, customs checks, and unresolved product-specific delegated acts. - [EU Digital Product Passport Product Group Readiness](/artifacts/eu/digital-product-passport/product-group-readiness.md): Prepare product groups for EU Digital Product Passport rules by tracking ESPR delegated-act status, data fields, suppliers, identifiers, access rights, and registry handoffs. - [EU Digital Product Passport requirements under ESPR](/artifacts/eu/digital-product-passport/requirements.md): source-linked 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. - [EU Digital Product Passport supplier data validation controls](/artifacts/eu/digital-product-passport/supplier-data-validation.md): 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. - [EU DPP customs access: registry, portal, and restricted data](/artifacts/eu/digital-product-passport/faq/customs-access.md): 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. - [EU DPP implementation playbook and vendor selection](/artifacts/eu/digital-product-passport/implementation-playbook-and-vendor-selection.md): Select Digital Product Passport vendors against ESPR requirements for identifiers, data carriers, access rights, decentralized storage, registry readiness, portal access, and verification evidence. - [EU DPP Product-Group Readiness Checklist](/artifacts/eu/digital-product-passport/product-group-readiness-checklist.md): A source-grounded 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. - [EU DPP QR Code and Data Carrier Implementation Guide](/artifacts/eu/digital-product-passport/dpp-qr-code-implementation-guide.md): Grounded guidance for using QR codes and other data carriers in EU Digital Product Passport programs, including unique identifiers, access, resolver testing, and evidence. - [EU DPP supplier data validation workflow](/artifacts/eu/digital-product-passport/supplier-data-validation-workflow.md): A grounded 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. - [EU DPP unique identifier requirements: product, operator and facility IDs](/artifacts/eu/digital-product-passport/faq/unique-identifier-requirements.md): FAQ on how ESPR Digital Product Passport identifiers connect products, economic operators, facilities, data carriers, resolvers and registry evidence. - [Public vs restricted EU Digital Product Passport data](/artifacts/eu/digital-product-passport/faq/public-vs-restricted-passport-data.md): How to separate public, restricted, authority, and customs access in EU Digital Product Passport designs under ESPR and battery passport rules. - [What is a Digital Product Passport under ESPR?](/artifacts/eu/digital-product-passport/what-is-a-dpp.md): A visitor-friendly explanation of EU Digital Product Passports under ESPR: product data, identifiers, data carriers, access rights, registry, web portal, and delegated acts. - [What is the EU Digital Product Passport registry?](/artifacts/eu/digital-product-passport/faq/dpp-registry.md): FAQ on the ESPR Digital Product Passport registry: what it stores, who uploads data, how identifiers work, and what teams should avoid assuming. - [Which products come first for the EU Digital Product Passport?](/artifacts/eu/digital-product-passport/faq/which-products-come-first.md): 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. - [Who must create an EU Digital Product Passport?](/artifacts/eu/digital-product-passport/faq/who-must-create-a-digital-product-passport.md): DPP responsibility under the EU ESPR: how manufacturers, importers, distributors, suppliers, service providers, and delegated acts fit together. *Recommended next step* *Placement: after carrier test section* ## Review DPP carrier and identifier design Check whether the chosen carrier, identifier, resolver, and public access path match ESPR requirements and the product's real scanning environment. - [Open Research Copilot](/solutions/research-copilot.md): Ask DPP carrier and identifier questions against cited ESPR and standards material. - [Discuss DPP implementation](/contact.md): Review product-level carrier, resolver, and evidence decisions with Sorena. --- [Privacy Policy](https://www.sorena.io/privacy) | [Terms of Use](https://www.sorena.io/terms-of-use) | [DMCA](https://www.sorena.io/dmca) | [About Us](https://www.sorena.io/about-us) (c) 2026 Sorena AB (559573-7338). All rights reserved. Source: https://www.sorena.io/artifacts/eu/digital-product-passport/faq/qr-code-vs-nfc-carrier-choices