DPPApplicability testEU

EU Digital Product Passport Applicability Test

Decide whether a product group may need a Digital Product Passport under ESPR, a product-specific delegated act, or the separate battery passport rules.

Use this as a grounded triage record for product scope, operator role, readiness signals, exclusions, passport design inputs, and evidence.

Author
Sorena AI
Published
May 9, 2026
Updated
May 9, 2026
Sections
6

Structured answer sets in this page tree.

Primary sources
3

Cited legal and guidance references.

Publication metadata
Sorena AI
Published May 9, 2026
Updated May 9, 2026
Overview

A Digital Product Passport is not required for every product immediately just because ESPR is in force. Under ESPR, the practical trigger is a product-specific delegated act that makes a passport part of the information requirements for that product group. Batteries have their own passport rule under Regulation (EU) 2023/1542. This test helps teams separate current legal triggers from preparation signals.

Section 1

Step 1: decide whether the product is in ESPR's starting scope

Start with the product itself, not the sales channel or the sustainability claim. ESPR applies broadly to physical goods placed on the EU market or put into service, including components and intermediate products. That makes many manufactured products plausible candidates for future product-group rules.

Record any grounded exclusion before continuing. ESPR excludes food, feed, medicinal products, veterinary medicinal products, living plants, animals and micro-organisms, products of human origin, plant and animal products directly related to future reproduction, and certain vehicle aspects already regulated under specified vehicle legislation. Products whose sole purpose is defence or national security are excluded from product groups when ecodesign requirements are set.

  • Name the product, component, intermediate product, or energy-related product being tested.
  • Record whether it is placed on the EU market, made available on the EU market, or put into service in the EU.
  • Check whether one of ESPR's explicit exclusions applies before using DPP preparation resources.
  • For second-hand, refurbished, repaired, or remanufactured products, note that ESPR treats remanufactured products as new products when they fall within a delegated act's scope.
Section 2

Step 2: look for the product-specific delegated act

A general ESPR scope match is not the same as a live passport obligation. ESPR says passport requirements are set in delegated acts adopted for product groups. The delegated act should define the covered product group, relevant commodity codes and descriptions, ecodesign requirements, verification approach, information requirements, transition period, and review date.

For DPP applicability, the decisive questions are whether the delegated act requires a passport, what data must or may be included, which data carrier is required, whether the passport is at model, batch, or item level, who may access or update each data class, and how long the passport must remain available.

  • Search for an adopted delegated act that covers the exact product group and commodity codes.
  • Do not treat the ESPR framework alone as proof that a product can only be sold with a DPP.
  • Extract any DPP-specific requirements from the delegated act: data fields, carrier, placement, level, access rights, update rights, and availability period.
  • If there is no adopted product rule yet, classify the product as a monitoring or preparation candidate, not as DPP-applicable.
Recommended next step

Turn DPP applicability into a product evidence record

Use the applicability result to map product groups, operator roles, delegated-act gaps, identifiers, supplier evidence, and passport architecture before teams publish or ship DPP claims.

Section 3

Step 3: classify the economic operator role

The passport owner is usually found by following the operator role. ESPR defines economic operators as manufacturers, authorised representatives, importers, distributors, dealers, and fulfilment service providers. The strongest DPP creation and conformity duties sit with the operator placing the covered product on the market or putting it into service.

Manufacturers must ensure covered products meet the delegated act, are accompanied by required information, and have a DPP where required. Importers must place only compliant covered products on the market and check, where applicable, that the DPP and back-up copy are available. Dealers must ensure customers and potential customers can easily access the DPP, including in distance selling.

  • Manufacturer: owns design, technical documentation, conformity assessment, declaration, marking, required information, and DPP availability for covered products.
  • Importer: checks manufacturer conformity work, required documents, marking, DPP availability, and its own contact information before placing third-country products on the EU market.
  • Distributor: performs due-care checks before making covered products available and protects compliance during storage or transport.
  • Dealer or online seller: makes DPP access visible to customers and potential customers, including before distance-sale purchase commitments.
  • Fulfilment service provider: protects compliance during warehousing, packaging, addressing, or dispatch.
Section 4

Step 4: rate product-group readiness without inventing a deadline

When no delegated act has yet been identified, readiness should be based on official prioritisation signals rather than guessed compliance dates. ESPR's first working plan must prioritise iron and steel, aluminium, textiles including garments and footwear, furniture including mattresses, tyres, detergents, paints, lubricants, chemicals, relevant energy-related products, ICT products, and other electronics.

Treat these product groups as higher-readiness candidates for data preparation, supplier evidence mapping, identifier design, and monitoring. That does not mean every product in the list already has a DPP obligation. It means the product group has an official prioritisation signal for future ecodesign work.

  • High readiness: the product group is named in ESPR's first-working-plan priority list or already has an adopted delegated act.
  • Medium readiness: the product is a component, intermediate product, or adjacent product likely to be affected by a prioritised group or horizontal information requirement.
  • Lower readiness: the product is in ESPR's broad scope but has no grounded prioritisation signal in the available sources.
  • Blocked: the business needs an exact application date, threshold, or product-specific field list but no adopted delegated act or cited source supports it.
Section 5

Step 5: separate ESPR DPP from the battery passport

Battery passports are not merely a future ESPR preparation item. Regulation (EU) 2023/1542 separately requires an electronic battery passport from 18 February 2027 for each LMT battery, each industrial battery with a capacity greater than 2 kWh, and each electric vehicle battery placed on the market or put into service.

If the product includes a battery, test the battery as its own regulated item. The battery passport is accessible through a QR code linked to a unique identifier, includes model and individual-battery information from Annex XIII, and must be accurate, complete, and up to date. The economic operator placing the battery on the market owns that responsibility, although it may authorise another operator to act on its behalf.

  • Check whether the battery is an LMT battery, an electric vehicle battery, or an industrial battery above the grounded capacity threshold.
  • Do not use the battery passport rule to claim that the host product already has an ESPR DPP unless a product-specific ESPR delegated act supports that claim.
  • When a battery is reused, repurposed, or remanufactured, check whether a new battery passport linked to the original passport is needed.
  • Keep the battery passport evidence separate from the host-product ESPR applicability record.
Section 6

Step 6: collect the evidence a reviewer will need

A useful applicability record should let a product manager, customs owner, market-surveillance responder, or data architect see why the product is in scope, out of scope, preparing, or blocked. It should not be a generic checklist.

For an in-scope product, preserve the delegated act extract and the DPP implementation decisions. For a preparation candidate, preserve the ESPR scope analysis and readiness reason, but label missing product-specific obligations as open. For a battery, preserve the Article 77 category test and the Annex XIII data mapping.

  • Product identity: name, model or family, component/intermediate status, EU market activity, and commodity code if available.
  • Scope decision: ESPR broad-scope result, explicit exclusion check, and any second-hand, refurbished, repaired, or remanufactured status.
  • Delegated-act evidence: adopted act title, product-group definition, commodity codes, DPP data fields, carrier, level, access rights, update rights, and availability period.
  • Operator evidence: manufacturer, importer, distributor, dealer, fulfilment service provider, and any Union responsible economic operator identifiers needed for the passport.
  • Architecture evidence: unique product identifier, data carrier placement, service-provider back-up copy, registry upload plan, web-portal exposure, and customs identifier flow where applicable.
  • Open facts: dates, thresholds, penalties, or field-level requirements that are not yet supported by an adopted delegated act or a cited source.
Primary sources

References and citations

commission.europa.eu
Referenced sections
  • Commission overview identifies the DPP as a product identity card for products, components, and materials and links ESPR to future product information rules.
"a digital identity card for products, components, and materials"
eur-lex.europa.eu
Referenced sections
  • Articles 9 to 15 and Annex III identify DPP data, unique identifiers, data carrier, registry, web portal, and customs-control evidence to capture when a product is covered.
"data carrier to a persistent unique product identifier"
Related guides

Explore more topics

Annex III Data Model Planning for EU Digital Product Passports
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
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
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
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
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
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
Build EU Digital Product Passport governance controls for data owners, supplier evidence, access logs, validation checks, audit records, and product release gates.
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.
DPP registry and web portal integration under EU ESPR
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
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
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
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
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
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 architecture and integration
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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?
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?
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?
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?
DPP responsibility under the EU ESPR: how manufacturers, importers, distributors, suppliers, service providers, and delegated acts fit together.