Digital product passport data requirements come from Annex III of the ESPR (Ecodesign for Sustainable Products Regulation), a menu each product-group delegated act turns into a field list, and, for batteries, from Batteries Regulation Annex XIII.
You do not have to wait for your act. Start a data inventory now that records where each likely item lives, who owns it and who may see it.
This guide is for the operator placing goods on the EU market that must make a Digital Product Passport (DPP) available. New to the topic? Start with what a digital product passport is.
What are digital product passport data requirements?
Digital product passport data requirements are the data elements that a product-group delegated act selects from ESPR Annex III and Article 7, plus any data that other EU law adds. Each element must be accurate, complete and up to date (Article 9(1)), structured and machine-readable where appropriate (Article 10(1)(d)), and linked to a unique product identifier.
As of October 2026, no ESPR delegated act setting digital product passport data requirements has been adopted. Batteries are the binding exception, from . Toys and detergents have adopted passport field lists in their own regulations, but those apply later.
Which data can a delegated act require?
Annex III is the menu behind ESPR digital product passport data requirements: each act specifies which data "are to or can be included". So the sheet described below gives every row a status: law, expected or voluntary (such as an EU Ecolabel award). Group the menu into five blocks.
| Block | Anchor | Contents | Status |
|---|---|---|---|
| 1. Identity | III(b)–(d); Art. 27(5) | Unique product identifier; GTIN of product and parts; commodity code; type, batch or serial number | Expected; marking is law once your act applies |
| 2. Operators, facilities | III(g)–(k); Art. 27(6), 29(3) | Manufacturer ID and contact; other operator and facility IDs; importer contact and EORI; EU responsible operator | Expected; public contact is law once your act applies |
| 3. Documents, back-up | III(e), (f), (l); Art. 27(7) | Declaration of conformity, technical documentation, certificates; manuals, safety information; back-up provider | Expected; digital instructions are law once your act applies |
| 4. Product-specific | III(a); Art. 7(2)(b) | Performance (repairability, durability, footprint); use and repair; disassembly and end of life | Expected; your act decides |
| 5. Substances of concern | III(a); Art. 7(5) | Name, identifiers, location, concentration or range | Expected by default; your act sets thresholds |
Copy the five blocks as the sections of your sheet. For blocks 1–3, the Joint Research Centre (JRC) methodology behind future acts proposes one definition for every product group, drawn from vocabularies such as the GS1 Web Vocabulary or Schema.org.
That proposal is not law, but it makes these rows safe to prepare now. Blocks 4–5 wait for your act.
Where does each item live in your company?
Set up one sheet for all your digital product passport data requirements: one row per data element, twelve columns. Paste this header into cell A1 and split it at the commas (Data, then Text to columns):
element,legal anchor,status,granularity,system of record,owner,supplier-dependent,access tier,format/unit/vocabulary,evidence,update trigger,default or specific
Status is law, expected or voluntary; granularity is model, batch or item; access tier is one of four tags (see the tagging section). One row of digital product passport data requirements, filled across all twelve columns:
| Column | Worked example: recycled content |
|---|---|
| Legal anchor | ESPR Art. 7(2)(b)(i) |
| Status | Expected |
| Granularity | Batch |
| System of record | Supplier certificates |
| Owner | Procurement (one named person) |
| Supplier-dependent | Yes |
| Access tier | Public (value only) |
| Format/unit/vocabulary | % by weight |
| Evidence | Chain-of-custody certificate |
| Update trigger | Supplier or material change |
| Default or specific | Default until the supplier delivers |
This map shows where digital product passport data requirements usually land in a manufacturing company. It fills seven of the twelve columns; add the rest in the gap analysis. "Law" means fixed by the ESPR once your act applies; access tags are provisional.
| Data element | Anchor | Status | System of record | Owner | Provisional access | Evidence |
|---|---|---|---|---|---|---|
| Unique product identifier | III(b) | Expected | ERP item master | Master data | Public | Numbering rule |
| GTIN of product and parts | III(c) | Expected | ERP or PIM (product information); PLM for parts | Master data | Public | GS1 licence |
| Commodity code (CN/TARIC) | III(d) | Expected | ERP customs module, broker | Trade compliance | Authorities | Classification record |
| Declaration of conformity | III(e) | Expected | Quality management system (QMS) | Regulatory | Public | Signed DoC |
| Technical file, test reports, certificates | III(e) | Expected | QMS; lab | Quality | Authorities | Report |
| Manuals, safety information | III(f); Art. 27(7) | Law (digital instructions) | PIM or DAM (digital assets) | Technical writing | Public | Version per language |
| Manufacturer ID and contact | III(g); Art. 27(6) | Law (contact) | ERP company master | Master data | Public | Registration |
| Other operator and facility IDs | III(h)–(i) | Expected | ERP vendor, plant master | Procurement | Authorities | Supplier records |
| Importer contact and EORI | III(j); Art. 29(3) | Law (contact) | Customs, logistics | Trade compliance | Public (contact) | EORI record |
| EU responsible operator | III(k) | Expected | Regulatory register | Regulatory | Public | Mandate |
| Back-up provider reference | III(l) | Expected | Contract register | IT | Authorities | Contract |
| Performance scores, footprint | Art. 7(2)(b)(i) | Expected | Test lab; LCA tool | R&D; sustainability | Public (value) | Test report, LCA study |
| Recycled content | Art. 7(2)(b)(i) | Expected | Supplier certificates | Procurement | Public (value) | Chain of custody |
| Disassembly information | Art. 7(2)(b)(iii) | Expected | PLM, engineering | Engineering | Legitimate interest | Disassembly guide |
| Substances: name, CAS, location, concentration | Art. 7(5) | Expected | Supplier material declarations | Product compliance | Public (name, location, range) | Declaration, test |
The JRC's draft textile study found commercial data structured in ERP and electronic data interchange (EDI) systems, but claims, technical data and certificates in emails, PDF test reports and spreadsheets.
A value that exists only inside a PDF is therefore a gap, even if it is right; documents such as the declaration of conformity can stay documents.
Fill the first eleven rows now. They cover Annex III points (b) to (l), which the JRC proposes to define alike for every product group. Mark every Article 7 row "awaiting act" and name one owner per row, not per department. That part of your digital product passport data requirements can be prepared before any act.
How do you turn the 71 battery data points into your sheet?
Annex XIII of the Batteries Regulation holds the first digital product passport data requirements with a full field list to apply, from . It mixes model data with data on each battery, including data from its use (Article 77(2)).
The Commission's guidance "Digital Batteries Passport – data points by category" (version 2.0, DG GROW) lists 71 data points for electric vehicle (EV), light means of transport (LMT) and industrial batteries over 2 kWh, with legal source and applicability for each.
It is the most detailed passport inventory the Commission has published, though non-binding and not an official Commission position.
Load it row by row. This table turns each block of the battery's digital product passport data requirements into an action:
| Block | Annex XIII content | Do now |
|---|---|---|
| Identity | Unique identifier (Art. 77(3)); model, batch or serial number, place and date of manufacture (1(a)) | Fill now |
| Documents | Declaration of conformity, public (1(r)); test reports, authorities only (3) | Fill now |
| Performance | Capacity, voltage, power, lifetime, efficiency (1(g)–(p)) | Fill now; cycle-life, round-trip efficiency and C-rate only for some industrial batteries |
| Per-battery values | Capacity fade, power fade, resistance, expected lifetime (4(a)) | Fill now for EV and LMT; "if applicable" for industrial |
| Substances | Chemistry, hazardous substances, critical raw materials, public (1(b)); detailed composition, legitimate interest (2(a)) | Fill now; request detailed composition from the cell supplier |
| End of life | Dismantling information, safety measures, legitimate interest (2(c)–(d)) | Fill now |
| Carbon footprint | Declaration and label, public (1(c)) | Wait for the implementing act on its format; n/a if non-rechargeable |
| Recycled content | Shares of cobalt, lithium, nickel, lead (1(e)) | Wait for its own date; only materials the battery contains |
| Due diligence | Responsible sourcing information (1(d)) | Wait until ; only if Article 47 does not exempt you |
| Use phase | State of health, status, cycles, negative events, temperature, state of charge (4(b)–(d)) | Status: fill now; the rest mostly "if applicable", from the battery management system |
Real composition. The Commission says a chemistry label such as "LFP" is not detailed composition. It considers a 1% (DIN SPEC) or 0.1% (draft CEN technical specification) threshold potentially reasonable. Ask your cell supplier for values at that depth.
Not a battery maker? Copy the guidance's pattern for your own digital product passport data requirements: its legal source and applicability columns become your legal anchor and status columns.
See our battery passport guide, the battery carbon footprint guide and the battery due diligence guide for the Article 47 test.
How do you add your product group's fields before its act is final?
Blocks 4–5 wait for your act, but drafts come first. Each time a JRC study, call for evidence or draft act appears, run this routine so expected digital product passport data requirements enter your sheet clearly marked:
- Copy the field list (compliance lead) into block 4 or 5, one row per field.
- Tag it "expected" (compliance lead) with source and date, for example "expected (JRC draft, April 2026)".
- Map it to a document you already issue (function head), such as a certificate or test report, before designing anything new.
- Score it (data owner) on the five tests in the gap analysis below.
Steel example. The Commission's call for evidence considers information on carbon footprint, recycled content and substances that make products harder to recycle; adoption is indicated for (expected).
The JRC proposes the heat number as mandatory batch identifier: map the mill certificate's heat number to "batch identifier, expected (JRC proposal)".
Final-product makers add a "steel content" row marked open, as one JRC scope option would put steel data in their passports.
Textile example. The act is indicated for (expected). The JRC's May 2026 study is a draft external study, not a Commission position; our textile DPP data guide lists its fields.
Public or restricted: how should you tag each field?
Each delegated act sets who sees what (ESPR Article 9(2)(f)), so every access tag you set today is provisional. Two models help:
- Battery pattern (law): public, legitimate interest, authorities. The act defining legitimate interest was due by (Batteries Regulation Article 77(9)); a Commission draft for public feedback is planned for (expected).
- JRC illustration (proposal): five tiers from public to regulatory; data for specific business customers falls outside the legal basis and is managed by the data owner.
Use four tags only (public, legitimate interest, authorities, contract) and choose one per row of your digital product passport data requirements by field type:
| Field type | Provisional tag | Basis |
|---|---|---|
| Summary value (score, footprint, recycled-content share) | Public | Battery Annex XIII point 1 values are public |
| Evidence: test reports, calculations | Authorities | Battery Annex XIII point 3 |
| Detailed composition, dismantling information | Legitimate interest | Battery Annex XIII point 2 |
| Recipes, exact concentrations | Authorities; publish a maximum or range | ESPR Art. 7(5)(c) |
| Customer personal data | Leave out without explicit consent | ESPR Art. 10(1)(e) |
| Data only for specific business customers | Contract | JRC methodology, Annex 8 |
How do you run a data gap analysis?
A gap analysis turns digital product passport data requirements into a dated work list. Five steps, one owner each:
- List the rows by block (compliance lead): the map above, or the 71 guidance points for batteries.
- Find system and owner (function heads): one name per row.
- Score each field 0–2 (data owner) on the five tests below.
- Mark default or specific (sustainability, procurement). The JRC expects much supplier data, such as carbon footprint or recycled content, to start as defaults.
- Sort and date (compliance lead): fix internally, request from supplier, or wait for the act, each with an owner and a date.
| Test | 0 | 1 | 2 |
|---|---|---|---|
| Exists? | Nowhere | Owner unclear | Named system and owner |
| Structured? | PDF or email | Spreadsheet | Field with unit and vocabulary |
| Granularity? | Product family | Model only | Finest level expected |
| Evidenced? | No document | Not linked | Linked, verifier named |
| Current? | No rule | Ad hoc | Trigger and version set |
A workable cut-off: any 0, or a total below 7 of 10, puts the row on the gap list.
For key rows, add the per-field attributes the JRC methodology proposes for future digital product passport data requirements: required accuracy, recency, completeness, provenance, who provides and verifies, update timing, confidentiality. This is step 2 of our DPP implementation plan.
How do you keep passport data current?
Article 9(1) makes accuracy a continuing duty, as does Article 77(4) of the Batteries Regulation. Without triggers, digital product passport data requirements are met at launch and missed a month later. Set a trigger per field and version every change:
| Trigger | Fields | Action |
|---|---|---|
| Design change | Parts, materials, substances, disassembly | New version; check conformity (Art. 27(4)) |
| Supplier or material change | Recycled content, footprint, substances, composition | New declaration; reset default/specific flag |
| New or expired certificate | Evidence, DoC | Replace link; keep old version |
| Correction or recall | Any; safety information | Correct, log reason, keep history |
| Remanufacturing, repurposing | Status, operator | New passport linked to the original (ESPR Art. 11(d); BR Art. 77(7)) |
| New schema version | Field set | Re-map; new fields arrive in a new version |
Battery use-phase data must be updated at least when a change in the battery's status occurs or is considered (Commission battery FAQ).
Which data-quality rules will your passport be checked against?
Your digital product passport data requirements face three different checks:
| Who checks | What it tests | What you keep or do |
|---|---|---|
| EU registry (automatic) | Form: required elements, structure, format, value type, vocabulary (Implementing Regulation (EU) 2026/1778, Art. 2(12)) | Validate the whole file before every upload |
| Market surveillance authorities | Substance: whether values are correct (recital 16) | Keep the evidence behind every value |
| The schema | Scope: at least its required attributes, at most required plus optional (User Guide v1.03); voluntary data kept separate (DPP FAQ) | Map each field to a schema attribute; flag voluntary fields |
Upload mechanics, including why one error rejects a whole multi-passport file, are in our registry guide.
Tag each row with one of the JRC draft textile study's three verification types (tested, calculated or chain-of-custody, identification); the type tells you which evidence to keep.
Run nine checks on your digital product passport data requirements before any upload:
| Check | How to test | Owner | When |
|---|---|---|---|
| 1. Required fields present | Compare columns with the schema's required attributes | Compliance lead | Each schema version |
| 2. Vocabularies and units | Validate values against code lists | Data owner | Every upload |
| 3. Valid, unique identifiers | Recompute GTIN check digits; deduplicate the identifier column | Master data | Every upload |
| 4. One version of truth | Compare label, technical file and supplier record | Quality | Every new version |
| 5. Evidence linked | Filter for values with an empty evidence column | Data owner | Every upload |
| 6. Voluntary fields separate | Check every voluntary row carries the flag | Compliance lead | Each schema version |
| 7. No customer personal data | Search free text for names, emails, addresses | Data protection | Every upload |
| 8. Free text translated | List free-text fields per market language (ESPR Art. 7(8)) | Technical writing | Each new market or text change |
| 9. Whole file validated | Run the validator on the full file | IT | Before any batch upload |
Walkthrough: a hypothetical storage-battery assembler in Plzeň
Take a hypothetical Plzeň firm assembling three models of 10 kWh stationary storage cabinets, about 90 a month, with cells from one non-EU supplier. A stationary battery energy storage system is an industrial battery; these exceed 2 kWh, so each cabinet needs a passport.
The firm completes the battery, so it is the manufacturer (Commission battery FAQ).
Weeks 1–2 (compliance lead): load the 71 guidance points. In the industrial column, our count gives 32 mandatory, 27 conditional or optional and 12 not to be filled.
Of those 12, eight wait for later dates: the carbon footprint declaration and label, due diligence, four recycled-content shares and instructions for use (held pending an amendment). Two repeat earlier points; two do not apply to industrial batteries.
The cells are lithium iron phosphate, so only the lithium recycled-content row stays, dated; the cobalt, nickel and lead rows do not apply (Commission battery FAQ). The due diligence row stays only if the Article 47 turnover test does not exempt the firm or its group; the compliance lead checks that first.
Week 3 (function heads): owners named: master data for identifiers, engineering for part numbers and dismantling, quality for the declaration and test reports, firmware for use-phase data. Procurement sends the cell supplier a dated request for cathode, anode and electrolyte composition.
Week 4 (data owners, compliance lead): every row scored on the five tests. Hypothetical result for the 32 mandatory points:
- 18 pass the cut-off.
- 9 are fixed internally, each with an owner and a date, among them dismantling information (engineering) and test-report links (quality).
- 5 go to the cell supplier, among them detailed composition and cell resistance.
The dated rows (carbon footprint, the lithium share and, if it applies, due diligence from ) sit on a separate wait list. That gap list is the firm's digital product passport data requirements in dated form.
Counterfactual: in month 3 the firm adds a second LFP cell supplier, but the composition rows have no "supplier or material change" trigger. Cabinets with the new cells get passports showing the first supplier's composition.
They pass every format check, because the values are well formed, yet an authority comparing cells with passports would find them inaccurate (Batteries Regulation Article 77(4)). The trigger table would have forced a new declaration and version before the first new cabinet shipped.
Edge cases: what if your situation is different?
These cases change who fills a row, not the digital product passport data requirements themselves.
- Contract manufacturer and brand. Whoever markets the product under its own name or trademark is the manufacturer (ESPR Article 2(42)). Record who supplies each field and whose GS1 licence the GTINs come from.
- Two passport laws. When two laws set digital product passport data requirements for one product, register at the most granular level either requires (Implementing Regulation (EU) 2026/1778, Article 8(3)).
- Supplier will not share. Use a flagged default and log a dated request. For non-EU suppliers outside direct EU oversight, the JRC's draft textile study points to contractual arrangements, recognised third-party assessments or mutually accepted certification schemes.
- Confidential recipes. Keep exact values restricted; Article 7(5)(c) allows a maximum concentration or a range.
- Products already on sale. Units placed on the market after your act applies need a passport, even for an old model; check the act's transitional rules. A battery remanufactured after the battery passport starts needs one (Commission battery FAQ).
Zoom out: what is settled and what should you watch?
Settled (law): the Annex III menu; Article 7(2)(b) and 7(5); the accuracy duty in Article 9(1); the registry's semantic checks; battery Annex XIII; adopted passport lists for toys and detergents.
Watch list: each event below reopens part of your digital product passport data requirements sheet.
| Event | Step to rerun |
|---|---|
| Steel act draft, adoption indicated for (expected) | Add its fields to blocks 4–5 with the four-step routine |
| Textile act draft, adoption indicated for (expected) | Same routine for textile rows |
| Battery access-rights act adopted (overdue) | Replace the provisional access tags on battery rows |
| Battery carbon footprint and recycled-content rules apply | Move those rows from wait to fill |
| Battery semantic catalogue published | Fill the format/unit/vocabulary column; run the nine checks |
| Proposal COM(2025) 504 adopted (awaits Parliament's plenary vote) | Check its "digital contact" definition and electronic documents against blocks 2–3 |
Digital product passport data requirements will differ by act; the structure will not. Build the sheet now: the act only decides which rows become mandatory.
What should you do in the next 30 days?
Seven actions turn digital product passport data requirements into a working sheet:
- Days 1–3, compliance lead: copy the header row and the five blocks.
- Week 1, master data: fill the eleven rows for Annex III points (b) to (l).
- Week 1, function heads: name one owner per row.
- Week 2, compliance lead: tag status and provisional access.
- Weeks 2–3, data owners: score each row on the five tests.
- Week 3, procurement: send dated supplier requests; log defaults.
- Week 4, compliance lead: issue the gap list with owners and dates; battery makers check it against the 71 points.
Test identifier-to-passport links with the free GS1 Digital Link QR generator: no signup, and it runs in your browser. Passmith also has a free plan.
Further reading: What is a digital product passport? · Textile DPP data · Battery passport · DPP implementation: 8 steps
Frequently asked questions
What are the digital product passport data requirements for my product?
Is there an official DPP data template?
Who decides which passport data is public?
Does the battery passport include the carbon footprint at the start?
Can we add voluntary data to the passport?
Will the registry check that our data is correct?
Which systems hold DPP data?
Sources
- Regulation (EU) 2024/1781 (ESPR) — EUR-Lex — 2026-10-07
- Regulation (EU) 2023/1542 (Batteries Regulation) — EUR-Lex — 2026-10-07
- Commission Implementing Regulation (EU) 2026/1778 on the digital product passport registry — EUR-Lex — 2026-10-07
- Regulation (EU) 2025/2509 on the safety of toys, Annex VI (digital product passport) — EUR-Lex — 2026-10-07
- Regulation (EU) 2026/405 on detergents, Annex VI (digital product passport) — EUR-Lex — 2026-10-07
- European Commission (DG GROW) — Guidance Document: Digital Batteries Passport – data points by category, Version 2.0 (15 August 2026) — 2026-10-07
- European Commission — EU Digital Product Passport FAQ for Batteries — 2026-10-07
- European Commission — Frequently Asked Questions on the Digital Product Passport — 2026-10-07
- European Commission — DPP Registry User Guide for Economic Operators, v1.03 (16 September 2026) — 2026-10-07
- JRC (Chawla et al.) — Methodology for defining data requirements for the Digital Product Passport under the ESPR framework, JRC145830 (2026) — 2026-10-07
- JRC — Study on DPP content for textile apparel products under ESPR (draft external study, 13 May 2026) — 2026-10-07
- JRC — Second stakeholder consultation, ESPR iron & steel draft preparatory study (13 April 2026) — 2026-10-07
- European Commission — Have Your Say 17672: Ecodesign requirements for iron and steel products (call for evidence Ares(2026)5076198) — 2026-10-07
- Proposal COM(2025) 504 amending Regulation (EU) 2024/1781 and other acts as regards digitalisation and common specifications — EUR-Lex — 2026-10-07
- European Parliament Legislative Observatory — procedure 2025/0134(COD) — 2026-10-07

