--- title: "DPP Data Requirements: What Information You Need to Collect" description: EU Digital Product Passports require data across 16 EPRS categories — from material composition and supplier locations to carbon footprint and substances of concern. Here's exactly what to collect, where it lives, and how GS1 standards structure it. image: https://trackvision.ai/hubfs/blog-images/c1-a4-header.png --- [![Group 4638](https://trackvision.ai/hs-fs/hubfs/Group%204638.png?width=150&height=20&name=Group%204638.png "Group 4638")](https://www.trackvision.ai) [![Logo-Long-Blue-On-Invis2-1](https://trackvision.ai/hs-fs/hubfs/Logo-Long-Blue-On-Invis2-1.png?width=150&height=20&name=Logo-Long-Blue-On-Invis2-1.png "Logo-Long-Blue-On-Invis2-1")](https://www.trackvision.ai) [Platform](https://trackvision.ai/platform) [![Vector-2](https://trackvision.ai/hubfs/Vector-2.svg) ![Vector-1](https://trackvision.ai/hubfs/Vector-1.svg) Platform Overview](https://trackvision.ai/platform) [![gs1 epcis2](https://trackvision.ai/hubfs/gs1%20epcis2.svg) ![gs1 ecpis](https://trackvision.ai/hubfs/gs1%20ecpis.svg) GS1 EPCIS 2.0 Repository & API](https://trackvision.ai/capabilities/epcis-repository) [![gs1 digital link](https://trackvision.ai/hubfs/gs1%20digital%20link.svg) ![gs1 digital](https://trackvision.ai/hubfs/gs1%20digital.svg) GS1 Digital Link Resolver](https://trackvision.ai/capabilities/gs1-digital-link-resolver) [![digital identity](https://trackvision.ai/hubfs/digital%20identity.svg) ![digital identities](https://trackvision.ai/hubfs/digital%20identities.svg) Digital Identities & Serialization](https://trackvision.ai/capabilities/digital-identities-and-serialization) [![traceability](https://trackvision.ai/hubfs/traceability.svg) ![product traceability](https://trackvision.ai/hubfs/product%20traceability.svg) Product Traceability](https://trackvision.ai/capabilities/product-traceability) [![ai](https://trackvision.ai/hubfs/ai.svg) ![ai for supply](https://trackvision.ai/hubfs/ai%20for%20supply.svg) AI for Supply Chain](https://trackvision.ai/capabilities/ai-for-supply-chain) [![no code](https://trackvision.ai/hubfs/no%20code.svg) ![nocode config](https://trackvision.ai/hubfs/nocode%20config.svg) No-Code Configuration](https://trackvision.ai/capabilities/no-code-configuration) [![worflow](https://trackvision.ai/hubfs/worflow.svg) ![workflow](https://trackvision.ai/hubfs/workflow.svg) Workflow Engine](https://trackvision.ai/capabilities/workflow-engine) [![sensor data](https://trackvision.ai/hubfs/sensor%20data.svg) ![sensor data-1](https://trackvision.ai/hubfs/sensor%20data-1.svg) Sensor Data Management](https://trackvision.ai/capabilities/sensor-data) [![certification managment](https://trackvision.ai/hubfs/certification%20managment.svg) ![cert management](https://trackvision.ai/hubfs/cert%20management.svg) Certification Management](https://trackvision.ai/capabilities/certification-management) Solutions ![Frame-1](https://trackvision.ai/hubfs/theme/Frame-1.svg) ![regulatory comp-1](https://trackvision.ai/hubfs/regulatory%20comp-1.svg) Regulatory Compliance [![provenance assurance](https://trackvision.ai/hubfs/provenance%20assurance.svg) ![provenance assur](https://trackvision.ai/hubfs/provenance%20assur.svg) Provenance Assurance](https://trackvision.ai/solutions/provenance) [![recall monitor-1](https://trackvision.ai/hubfs/recall%20monitor-1.svg) ![recall monitoring-1](https://trackvision.ai/hubfs/recall%20monitoring-1.svg) Recall Monitoring](https://trackvision.ai/solutions/recall-monitoring) [![recall exec-2](https://trackvision.ai/hubfs/recall%20exec-2.svg) ![recall exec-3](https://trackvision.ai/hubfs/recall%20exec-3.svg) Recall Execution](https://trackvision.ai/solutions/recall-execution) [![diversion detect](https://trackvision.ai/hubfs/diversion%20detect.svg) ![diversion detect-1](https://trackvision.ai/hubfs/diversion%20detect-1.svg) Diversion Detection](https://trackvision.ai/solutions/product-diversion) [![waste](https://trackvision.ai/hubfs/waste.svg) ![waste reduct](https://trackvision.ai/hubfs/waste%20reduct.svg) Waste Reduction](https://trackvision.ai/solutions/waste-reduction) [![certification monitoring](https://trackvision.ai/hubfs/certification%20monitoring.svg) ![certification monit](https://trackvision.ai/hubfs/certification%20monit.svg) Certification Monitoring](https://trackvision.ai/solutions/certification-monitoring) [![cold chain](https://trackvision.ai/hubfs/cold%20chain.svg) ![cold chaing monit](https://trackvision.ai/hubfs/cold%20chaing%20monit.svg) Cold Chain Monitoring](https://trackvision.ai/solutions/cold-chain-monitoring) [![carbon](https://trackvision.ai/hubfs/carbon.svg) ![carbon footprint red](https://trackvision.ai/hubfs/carbon%20footprint%20red.svg) Carbon Footprint Reduction](https://trackvision.ai/solutions/carbon-footprint-reduction) [![fresh food](https://trackvision.ai/hubfs/fresh%20food.svg) ![fresh\_food](https://trackvision.ai/hubfs/fresh_food.svg) FSMA Section 204 Compliance](https://trackvision.ai/solutions/fsma-204) [![pharmacy](https://trackvision.ai/hubfs/pharmacy.svg) ![pharmacy-1](https://trackvision.ai/hubfs/pharmacy-1.svg) DSCSA Compliance](https://trackvision.ai/solutions/dscsa) [![recall dpp](https://trackvision.ai/hubfs/recall%20dpp.svg) ![recall dpp-1](https://trackvision.ai/hubfs/recall%20dpp-1.svg) Digital Product Passports](https://trackvision.ai/solutions/dpp) Industries [![fresh food](https://trackvision.ai/hubfs/fresh%20food.svg) ![fresh\_food](https://trackvision.ai/hubfs/fresh_food.svg) Fresh Food](https://trackvision.ai/industries/fresh-food) [![apparel](https://trackvision.ai/hubfs/apparel.svg) ![apparel-1](https://trackvision.ai/hubfs/apparel-1.svg) Apparel](https://trackvision.ai/industries/apparel) [![wine](https://trackvision.ai/hubfs/wine.svg) ![wine-1](https://trackvision.ai/hubfs/wine-1.svg) Wine & Spirits](https://trackvision.ai/industries/wine-and-spirits) [![grocery](https://trackvision.ai/hubfs/grocery.svg) ![grocery-1](https://trackvision.ai/hubfs/grocery-1.svg) Grocery](https://trackvision.ai/industries/grocery) [![restaurant](https://trackvision.ai/hubfs/restaurant.svg) ![restaurants](https://trackvision.ai/hubfs/restaurants.svg) Restaurants](https://trackvision.ai/industries/grocery) [![pharmacy](https://trackvision.ai/hubfs/pharmacy.svg) ![pharmacy-1](https://trackvision.ai/hubfs/pharmacy-1.svg) Pharmaceutical](https://trackvision.ai/industries/pharma) [Resources](https://trackvision.ai/resources) [![blog](https://trackvision.ai/hubfs/blog.svg) ![blog-1](https://trackvision.ai/hubfs/blog-1.svg) Blog](https://trackvision.ai/blog) [![Digital Link Icon](https://trackvision.ai/hubfs/qr-2.svg) ![qr-3](https://trackvision.ai/hubfs/qr-3.svg) What is GS1 Digital Link?](https://trackvision.ai/blog/what-is-gs1-digital-link) [![EPCIS Icon](https://trackvision.ai/hubfs/database-4.svg) ![database](https://trackvision.ai/hubfs/database.svg) What is GS1 EPCIS?](https://trackvision.ai/blog/what-is-gs1-epcis-2.0) [![diversion detect](https://trackvision.ai/hubfs/diversion%20detect.svg) ![diversion detect-1](https://trackvision.ai/hubfs/diversion%20detect-1.svg) Technical Documentation](https://docs.trackvision.ai/) [About us](https://trackvision.ai/about) [![recall dpp](https://trackvision.ai/hs-fs/hubfs/recall%20dpp.webp?width=35&height=28&name=recall%20dpp.webp) ![recall dpp-1](https://trackvision.ai/hubfs/recall%20dpp-1.svg) Our Team](https://trackvision.ai/about) [![share-2](https://trackvision.ai/hubfs/share-2.svg) ![share data](https://trackvision.ai/hubfs/share%20data.svg) Our Partners](https://trackvision.ai/partners) [Contact us](https://cta-eu1.hubspot.com/web-interactives/public/v1/track/click?encryptedPayload=AVxigLK%2FT2tXtCwLkNybssrDRz0W%2Fq8th3A7d917FyuSpeU0UfIL1XhhHv4zTr%2Bm%2BsTp3KoQ9jgV70Xu1z%2FF8iESdFL0l9dWkTO4WxGxrVxlJKEcEtUrWc3X2HcFmH6WCmv87%2BxNm4MaaeIdXsupa4qybdsJZYCRxo5NGGSwDJ3C644Y%2BA%3D%3D&portalId=143236257) [![Group 4638](https://trackvision.ai/hs-fs/hubfs/Group%204638.png?width=150&height=20&name=Group%204638.png "Group 4638")](https://www.trackvision.ai) [Platform](https://trackvision.ai/platform) Solutions Industries [Resources](https://trackvision.ai/resources) [About us](https://trackvision.ai/about) [Contact us](https://cta-eu1.hubspot.com/web-interactives/public/v1/track/click?encryptedPayload=AVxigLK%2FT2tXtCwLkNybssrDRz0W%2Fq8th3A7d917FyuSpeU0UfIL1XhhHv4zTr%2Bm%2BsTp3KoQ9jgV70Xu1z%2FF8iESdFL0l9dWkTO4WxGxrVxlJKEcEtUrWc3X2HcFmH6WCmv87%2BxNm4MaaeIdXsupa4qybdsJZYCRxo5NGGSwDJ3C644Y%2BA%3D%3D&portalId=143236257) back [Platform](https://trackvision.ai/platform) [![Vector-2](https://trackvision.ai/hubfs/Vector-2.svg) Platform Overview](https://trackvision.ai/platform) [![gs1 epcis2](https://trackvision.ai/hubfs/gs1%20epcis2.svg) GS1 EPCIS 2.0 Repository & API](https://trackvision.ai/capabilities/epcis-repository) [![gs1 digital link](https://trackvision.ai/hubfs/gs1%20digital%20link.svg) GS1 Digital Link Resolver](https://trackvision.ai/capabilities/gs1-digital-link-resolver) [![digital identity](https://trackvision.ai/hubfs/digital%20identity.svg) Digital Identities & Serialization](https://trackvision.ai/capabilities/digital-identities-and-serialization) [![traceability](https://trackvision.ai/hubfs/traceability.svg) Product Traceability](https://trackvision.ai/capabilities/product-traceability) [![ai](https://trackvision.ai/hubfs/ai.svg) AI for Supply Chain](https://trackvision.ai/capabilities/ai-for-supply-chain) [![no code](https://trackvision.ai/hubfs/no%20code.svg) No-Code Configuration](https://trackvision.ai/capabilities/no-code-configuration) [![worflow](https://trackvision.ai/hubfs/worflow.svg) Workflow Engine](https://trackvision.ai/capabilities/workflow-engine) [![sensor data](https://trackvision.ai/hubfs/sensor%20data.svg) Sensor Data Management](https://trackvision.ai/capabilities/sensor-data) [![certification managment](https://trackvision.ai/hubfs/certification%20managment.svg) Certification Management](https://trackvision.ai/capabilities/certification-management) back Solutions ![Frame-1](https://trackvision.ai/hubfs/theme/Frame-1.svg) Regulatory Compliance [![provenance assurance](https://trackvision.ai/hubfs/provenance%20assurance.svg) Provenance Assurance](https://trackvision.ai/solutions/provenance) [![recall monitor-1](https://trackvision.ai/hubfs/recall%20monitor-1.svg) Recall Monitoring](https://trackvision.ai/solutions/recall-monitoring) [![recall exec-2](https://trackvision.ai/hubfs/recall%20exec-2.svg) Recall Execution](https://trackvision.ai/solutions/recall-execution) [![diversion detect](https://trackvision.ai/hubfs/diversion%20detect.svg) Diversion Detection](https://trackvision.ai/solutions/product-diversion) [![waste](https://trackvision.ai/hubfs/waste.svg) Waste Reduction](https://trackvision.ai/solutions/waste-reduction) [![certification monitoring](https://trackvision.ai/hubfs/certification%20monitoring.svg) Certification Monitoring](https://trackvision.ai/solutions/certification-monitoring) [![cold chain](https://trackvision.ai/hubfs/cold%20chain.svg) Cold Chain Monitoring](https://trackvision.ai/solutions/cold-chain-monitoring) [![carbon](https://trackvision.ai/hubfs/carbon.svg) Carbon Footprint Reduction](https://trackvision.ai/solutions/carbon-footprint-reduction) back Industries [![fresh food](https://trackvision.ai/hubfs/fresh%20food.svg) Fresh Food](https://trackvision.ai/industries/fresh-food) [![apparel](https://trackvision.ai/hubfs/apparel.svg) Apparel](https://trackvision.ai/industries/apparel) [![wine](https://trackvision.ai/hubfs/wine.svg) Wine & Spirits](https://trackvision.ai/industries/wine-and-spirits) [![grocery](https://trackvision.ai/hubfs/grocery.svg) Grocery](https://trackvision.ai/industries/grocery) [![restaurant](https://trackvision.ai/hubfs/restaurant.svg) Restaurants](https://trackvision.ai/industries/grocery) [![pharmacy](https://trackvision.ai/hubfs/pharmacy.svg) Pharmaceutical](https://trackvision.ai/industries/pharma) back [Resources](https://trackvision.ai/resources) [![blog](https://trackvision.ai/hubfs/blog.svg) Blog](https://trackvision.ai/blog) [![Digital Link Icon](https://trackvision.ai/hubfs/qr-2.svg) What is GS1 Digital Link?](https://trackvision.ai/blog/what-is-gs1-digital-link) [![EPCIS Icon](https://trackvision.ai/hubfs/database-4.svg) What is GS1 EPCIS?](https://trackvision.ai/blog/what-is-gs1-epcis-2.0) [![diversion detect](https://trackvision.ai/hubfs/diversion%20detect.svg) Technical Documentation](https://docs.trackvision.ai/) back [About us](https://trackvision.ai/about) [![recall dpp](https://trackvision.ai/hs-fs/hubfs/recall%20dpp.webp?width=35&height=28&name=recall%20dpp.webp) Our Team](https://trackvision.ai/about) [![share-2](https://trackvision.ai/hubfs/share-2.svg) Our Partners](https://trackvision.ai/partners) back Regulatory Compliance [![fresh food](https://trackvision.ai/hubfs/fresh%20food.svg) FSMA Section 204 Compliance](https://trackvision.ai/solutions/fsma-204) [![pharmacy](https://trackvision.ai/hubfs/pharmacy.svg) DSCSA Compliance](https://trackvision.ai/solutions/dscsa) [![recall dpp](https://trackvision.ai/hubfs/recall%20dpp.svg) Digital Product Passports](https://trackvision.ai/solutions/dpp) Published: 30 April 2026 | [Dave Ashenhurst](https://trackvision.ai/blog/author/dave-ashenhurst) # DPP Data Requirements: What Information You Need to Collect Ask a brand about their Digital Product Passport data readiness and you'll hear something like: "We've got GTINs, product descriptions, country of origin — we're most of the way there." They believe it. They're wrong. A compliant DPP under the EU's [Ecodesign for Sustainable Products Regulation (ESPR 2024/1781)](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32024R1781) draws on data from across your entire supply chain — your ERP, your PLM, your Tier 1 factories, the dyeing facility three tiers upstream, and the certification bodies that audit all of them. Some of that data you hold today. A significant portion lives with partners who don't know yet that you'll be asking for it. And some of it doesn't exist anywhere — you'll need to build the processes to generate it. This post is a practical breakdown of what data a DPP must contain, where it comes from, and how GS1 standards structure it into a machine-readable, regulator-ready passport. In this guide, you will learn: - The EPRS 16-category framework that defines DPP data scope - Which fields are mandatory under ESPR Article 7 - The difference between static and dynamic data — and why it matters for your systems - Which data must come from your suppliers vs. your own internal systems - How GS1 Digital Link and EPCIS 2.0 structure everything into a compliant passport ## The EPRS 16-category framework: your data blueprint The European Parliamentary Research Service (EPRS) defined the data blueprint that underpins every EU DPP. It covers 16 categories of information that a DPP must be capable of holding. Not every category applies to every product type — but you need to understand all 16 before you can determine what's relevant to yours. The 16 categories are: 1. **Product description** — marketing specifications, dimensions, size, colour 2. **Composition** — material breakdown, origin, treatments applied 3. **Supply chain** — manufacturing locations at Tier 1 through Tier 4, facility Global Location Numbers (GLNs) 4. **Transportation** — import/export data, border crossings 5. **Documentation** — certifications such as OEKO-TEX, GOTS, and ISO 14001 6. **Environmental impact** — lifecycle carbon footprint (Scope 1, 2, and 3 emissions), water consumption 7. **Social impact** — worker safety records, labour conditions 8. **Animal welfare** — sourcing ethics for materials of animal origin 9. **Circularity** — durability metrics, repairability index, end-of-life options 10. **Health impact** — chemical safety, Substances of Concern (SoC) disclosures 11. **Brand info** — ownership, contact details, economic operator identity 12. **Communication media** — access point type (QR code, NFC, Digital Link) 13. **Granularity** — whether tracking is at model, batch, or item level 14. **Quantity** — production volumes per batch 15. **Costs** — lifecycle cost tracking 16. **Post-sale tracking** — resale, maintenance, repair history That's a substantial scope. But here's the useful framing: you don't need all 16 categories fully populated on day one. What you need is a clear picture of which categories your sector's delegated act will require — and the data collection infrastructure in place well before enforcement begins. Starting that process in 2026 is not early. It's on time. ## What ESPR Article 7 mandates for every product Beyond sector-specific rules, ESPR Article 7 and Annex III define data requirements that apply to every product carrying a DPP obligation. Think of this as your minimum viable dataset: - **Unique Product Identifier (UPI)** — a structured identifier that distinguishes a specific product, batch, or item. For most brands, this is built on the Global Trade Item Number (GTIN) - **Economic operator data** — manufacturer details, importer EORI numbers, and facility identifiers - **Declarations of conformity and technical documentation** — your regulatory paperwork, structured and accessible - **Disassembly instructions** — information for professional recyclers, required for circularity compliance - **Substances of Concern (SoC)** — under Article 7(5), restricted chemicals including PFAS must be tracked throughout the supply chain and disclosed to recyclers The SoC requirement is the one that catches most brands off guard. It's not enough to know what's in your finished product. You need chemical disclosure data from the factories that processed your raw materials. That's a supplier data problem — and it requires structured onboarding before you can solve it. ## Static data vs. dynamic data: why the distinction matters Before you start collecting anything, there's one distinction worth understanding clearly: the difference between static and dynamic fields. **Static data** doesn't change once the product is manufactured. For a garment, that includes: - Material composition (e.g., 95% cotton, 5% elastane) - Country of origin - Facility identifiers for each manufacturing stage - Base carbon footprint per batch - Care and safety instructions **Dynamic data** updates throughout the product's lifecycle. Examples include: - Changes in custody — who holds the product now - Repair and maintenance events - Resale or recommerce verification This distinction determines which systems need to feed into your DPP over time. Static data can be collected once at production and locked into the passport. Dynamic data requires event-based tracking infrastructure — specifically, a system built around EPCIS 2.0 events. More on that below. ## Where the data actually lives Here's the breakdown most DPP guides skip: the data you need doesn't live in one system, and a large portion of it isn't yours to begin with. ### Internal systems — data you already hold Your ERP, PLM, and PIM systems hold a solid chunk of the required data: - **ERP** — GTINs, batch numbers, production quantities, economic operator details, logistics data - **PLM** — product design specifications, material compositions, care instructions - **PIM** — marketing descriptions, size and colour variants, digital assets This covers roughly categories 1, 11, 12, 13, and 14 from the EPRS framework. It's a good start. It's not enough. ### Supplier data — the hard part The data that most brands lack — and that regulators will scrutinise most carefully — comes from upstream in the supply chain: - **Tier 1 suppliers** — factory audit reports, social compliance certifications, energy consumption data - **Tier 2 and Tier 3 suppliers** — raw material origins, chemical treatment disclosures, recycled content percentages, dyeing and finishing processes - **Certification bodies** — OEKO-TEX, GOTS, BSCI, fair trade certificates with valid dates and issuing bodies Categories 2, 3, 5, 6, 7, 8, and 10 from the EPRS framework are almost entirely supplier-dependent. You cannot self-certify this data. You need structured, auditable responses from the businesses upstream in your supply chain. Picture a market surveillance officer scanning your product QR code at the border. Either the chemical disclosure data from your Tier 2 dyeing facility is there, verified, and structured — or it isn't. What happens next isn't under your control. Not unless you've built the infrastructure ahead of time. This is why DPP compliance is fundamentally a supplier onboarding challenge, not a technology challenge. The technology is the tractable part. Getting clean, verified, auditable data from a dyeing facility in Bangladesh — that's where most projects slow down. ## Sector-specific requirements: textiles and apparel Two sectors are ahead of the rest in terms of regulatory clarity. ### Textiles and apparel Delegated acts for textiles are expected to take effect in 2027. The key data requirements already signalled include: - Strict material percentage itemisation, including recycled content and non-textile parts of animal origin - Chemical disclosures covering dyes, finishing chemicals, and microplastic shedding potential - Traceability links to upstream supplier DPPs, covering weaving, dyeing, and finishing stages - Circularity data: validated care instructions, repairability indices, and take-back programme links If you're in apparel, the [DPP requirements for textiles and apparel](https://www.trackvision.ai/blog/dpp-requirements-textiles-apparel) post goes deep on what the delegated acts look like in practice. ## How GS1 standards structure DPP data The EU requires DPP data to be machine-readable, structured, and interoperable across systems and borders. Two GS1 standards do this work in practice. ### GS1 Digital Link — the access layer A physical data carrier is required on every product carrying a DPP obligation. GS1 Digital Link upgrades a standard QR code into a web-resolvable URI that routes different users to different views of the same data, based on their access rights. Let's look at an example. A GS1 Digital Link URL for a batch of garments might look like: `https://id.trackvision.ai/01/05060512345601/10/BATCH-2024-A` Breaking this down: - **`/01/`** — the GS1 Application Identifier for a Global Trade Item Number (GTIN) - **`05060512345601`** — the 14-digit GTIN identifying the product - **`/10/`** — the Application Identifier for batch number - **`BATCH-2024-A`** — the specific batch When a consumer scans this QR code, they see material composition and care instructions. When a customs inspector scans it, they see compliance documentation. When a recycler scans it, they see disassembly instructions and SoC disclosures. Same code, same URL — different data served to different audiences, all managed by a GS1-compliant resolver. This is why using a proprietary QR code is a mistake. The interoperability mandates coming in 2027 require GS1 Digital Link. Any label printed today with a non-standard QR code will need to be reprinted. ### EPCIS 2.0 — the traceability engine Static data can be stored in a database. Dynamic data — the supply chain events, custody changes, repair history — requires an event-based standard. That standard is EPCIS 2.0 (Electronic Product Code Information Services), exchanged in JSON-LD format. EPCIS records the *what, where, when, and why* of supply chain events. For a garment moving from a finishing factory in Vietnam to a distribution centre in the Netherlands, an EPCIS event captures: - **What** — the GTIN and batch identifier of the goods - **Where** — the GLN of the originating facility and the destination - **When** — the timestamp of the event - **Why** — the business step (e.g., `shipping`) and the disposition (e.g., `in_transit`) As the product moves through its lifecycle — manufactured, exported, imported, sold, repaired, resold — EPCIS events build a verifiable, tamper-evident chain. That chain is what regulators mean when they require a DPP covering the full product lifecycle, not just the moment of manufacture. ## How TrackVision handles DPP data collection Knowing what data you need is one problem. Collecting it across a multi-tier supplier network, validating it, structuring it to GS1 standards, and keeping it current over time is another. TrackVision's [DPP platform](https://www.trackvision.ai/solutions/dpp) handles all of this in a single workflow. Products are imported from your existing systems. Suppliers are matched to products by category using GS1 GPC classifications. Structured data requests are sent to each supplier through a self-serve portal — suppliers can upload certificates, fill in material data, and provide environmental metrics without needing any technical knowledge of EPCIS or GS1 standards. TrackVision handles the structuring. The platform's Regulatory Expert System maps your specific product types against ESPR and EPRS requirements, identifies the gaps in your current data, and generates a prioritised collection plan. Compliance is tracked in real time, so you always know which products are ready and which are still missing supplier data. If you want a clear picture of what's missing before compliance deadlines arrive, [talk to us](https://www.trackvision.ai/contact) — a free gap analysis takes less than an hour. --- ## Frequently asked questions **What is the EPRS 16-category framework for Digital Product Passports?** The European Parliamentary Research Service (EPRS) 16-category framework defines the full scope of data a Digital Product Passport must be capable of holding. Categories cover product description, material composition, supply chain locations, environmental impact, circularity data, and post-sale tracking. Not every category applies to every product type, but the framework sets the outer boundary of DPP data requirements. **What data must come from suppliers for DPP compliance?** Supplier-sourced data includes raw material origins, chemical treatment disclosures (including Substances of Concern under ESPR Article 7(5)), recycled content percentages, factory audit reports, social compliance certifications, and energy consumption data at the facility level. This covers EPRS categories 2, 3, 5, 6, 7, 8, and 10 — and none of it can be self-certified by the brand. **What is the difference between static and dynamic DPP data?** Static DPP data doesn't change after manufacture: material composition, country of origin, facility identifiers, base carbon footprint. Dynamic data updates throughout the product's lifecycle: custody changes, repair events, resale records. Dynamic data requires event-based infrastructure such as EPCIS 2.0. **Why does a DPP require GS1 Digital Link instead of a standard QR code?** The EU's interoperability requirements mandate that the physical data carrier on the product be resolvable to different datasets for different audiences — consumers, customs officials, recyclers. GS1 Digital Link enables this via a single structured URL. Standard proprietary QR codes don't meet this requirement and will need to be replaced before enforcement deadlines. Delegated acts for textiles and apparel are expected to take effect in 2027. Brands in both sectors should be building their data collection infrastructure now — the 60–70% of required data that already exists in internal systems can be structured and audited immediately, before the supplier data collection phase begins. **How do I know which EPRS categories apply to my products?** Your sector's delegated act will specify which categories are mandatory — but that act may not be published until 2026 or 2027. The practical approach is to start with the Article 7 mandatories (UPI, economic operator data, SoC disclosures, disassembly instructions) and map your internal data against the full 16 categories in parallel. TrackVision's Regulatory Expert System automates this mapping against your specific product catalogue. 30 April 2026 | [Dave Ashenhurst](https://trackvision.ai/blog/author/dave-ashenhurst) share: Recommended for you [What is GS1 EPCIS 2.0?](https://trackvision.ai/blog/what-is-gs1-epcis-2.0) About the author Dave Ashenhurst I lead architecture and engineering. I use AI tools, like Claude Code, all day. ## Recommended reading NEW DSCSA [Case Study: How Hudson Scientific Hit Full DSCSA Compliance in 30 Days](https://trackvision.ai/blog/case-study-how-hudson-scientific-hit-full-dscsa-compliance-in-30-days) 25 August 2026 | [Curt Schacker](https://trackvision.ai/blog/author/curt-schacker) gs1 dpp [DPP in 2028: What Apparel Brands Need to Build Before the Deadline](https://trackvision.ai/blog/dpp-in-2028-what-apparel-brands-need-to-build-before-the-deadline) 17 August 2026 | [Curt Schacker](https://trackvision.ai/blog/author/curt-schacker) digital-link gs1 natural-trace [Full-Spectrum Product Authentication: Combining QR codes and Natural DNA tagging to fight food fraud](https://trackvision.ai/blog/full-spectrum-product-authentication-combining-qr-codes-and-natural-dna-tagging-to-fight-food-fraud) 10 June 2026 | [Jonathan Ling](https://trackvision.ai/blog/author/jonathan-ling) ## Get ahead with TrackVision updates Join our newsletter today and don't miss out on the opportunity to be part of a community driving innovation in tracking technology. Sign up now and be in the know! [![TrackVision\_Logo](https://trackvision.ai/hs-fs/hubfs/Logo-Long-Blue-On-Invis2-1.png?width=150&height=20&name=Logo-Long-Blue-On-Invis2-1.png "TrackVision_Logo")](https://www.trackvision.ai) ##### Headquarters ![Group 4266](https://trackvision.ai/hubfs/theme/Group%204266.svg) London United Kingdom ![Group 4266](https://trackvision.ai/hubfs/theme/Group%204266.svg) San Francisco United States [![Group 4508](https://trackvision.ai/hubfs/theme/Group%204508.svg) ![linkdin](https://trackvision.ai/hubfs/Group%204630.svg)](https://linkedin.com/company/trackvision-supply-chain-software/) - [Platform](https://trackvision.ai/platform) - [GS1 EPCIS 2.0 Repository](https://trackvision.ai/capabilities/epcis-repository) - [GS1 Digital Link Resolver](https://trackvision.ai/capabilities/gs1-digital-link-resolver) - [Digital Identities & Serialization](https://trackvision.ai/capabilities/digital-identities-and-serialization) - [Product Traceability](https://trackvision.ai/capabilities/product-traceability) - [AI for supply Chain](https://trackvision.ai/capabilities/ai-for-supply-chain) - [No Code Configuration](https://trackvision.ai/capabilities/no-code-configuration) - [Workflow and Rules Engine](https://trackvision.ai/capabilities/workflow-engine) - [Sensor Data Management](https://trackvision.ai/capabilities/sensor-data) - [Certification Management](https://trackvision.ai/capabilities/certification-management) - Solutions - [FSMA 204](https://trackvision.ai/solutions/fsma-204) - [DSCSA](https://trackvision.ai/solutions/dscsa) - [Digital Product Passport](https://trackvision.ai/blog) - [Provenance Assurance](https://trackvision.ai/solutions/provenance) - [Recall Monitoring](https://trackvision.ai/solutions/recall-monitoring) - [Recall Execution](https://trackvision.ai/solutions/recall-execution) - [Product Diversion](https://trackvision.ai/solutions/product-diversion) - [Waste Reduction](https://trackvision.ai/solutions/waste-reduction) - [Certification Monitoring](https://trackvision.ai/solutions/certification-monitoring) - [Cold Chain Monitoring](https://trackvision.ai/solutions/cold-chain-monitoring) - [Carbon Footprint Reduction](https://trackvision.ai/solutions/carbon-footprint-reduction) - Industries - [Fresh Food](https://trackvision.ai/industries/fresh-food) - [Apparel](https://trackvision.ai/industries/apparel) - [Wine & Spirits](https://trackvision.ai/industries/wine-and-spirits) - [Grocery](https://trackvision.ai/industries/grocery) - [Restaurants](https://trackvision.ai/industries/grocery) - [Pharmaceutical](https://trackvision.ai/industries/pharma) - [Resources](https://trackvision.ai/resources) - [Blog](https://trackvision.ai/blog) - [About us](https://trackvision.ai/about) - [Contact us](https://trackvision.ai/contact) Copyright © 2026, Trackvision AI Ltd | [Terms & Conditions](https://trackvision.ai/terms-conditions) | [Privacy Policy](https://trackvision.ai/privacy-policy) ```json { "@context" : "https://schema.org", "@type" : "BlogPosting", "author" : { "@type" : "Person", "name" : "Dave Ashenhurst", "url" : "https://trackvision.ai/blog/author/dave-ashenhurst" }, "dateModified" : "2026-05-07T09:07:29.761Z", "datePublished" : "2026-04-30T09:16:03.000Z", "headline" : "DPP Data Requirements: What Information You Need to Collect", "image" : [ "https://trackvision.ai/hubfs/blog-images/c1-a4-header.png" ], "mainEntityOfPage" : { "@id" : "https://trackvision.ai/blog/dpp-data-requirements", "@type" : "WebPage" }, "publisher" : { "@type" : "Organization", "logo" : { "@type" : "ImageObject", "url" : "https://trackvision.ai/hubfs/Logo-Long-Blue-On-Invis2-1.png" }, "name" : "Trackvision AI Ltd" } } ``` ```json { "@context" : "https://schema.org", "@type" : "FAQPage", "mainEntity" : [ { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "The European Parliamentary Research Service (EPRS) 16-category framework defines the full scope of data a Digital Product Passport must be capable of holding. Categories cover product description, material composition, supply chain locations, environmental impact, circularity data, and post-sale tracking. Not every category applies to every product type, but the framework sets the outer boundary of DPP data requirements." }, "name" : "What is the EPRS 16-category framework for Digital Product Passports?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Supplier-sourced data includes raw material origins, chemical treatment disclosures (including Substances of Concern under ESPR Article 7(5)), recycled content percentages, factory audit reports, social compliance certifications, and energy consumption data at the facility level. This covers EPRS categories 2, 3, 5, 6, 7, 8, and 10 — and none of it can be self-certified by the brand." }, "name" : "What data must come from suppliers for DPP compliance?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Static DPP data doesn't change after manufacture: material composition, country of origin, facility identifiers, base carbon footprint. Dynamic data updates throughout the product's lifecycle: custody changes, repair events, resale records, and — for batteries — real-time State of Health. Dynamic data requires event-based infrastructure such as EPCIS 2.0." }, "name" : "What is the difference between static and dynamic DPP data?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "The EU's interoperability requirements mandate that the physical data carrier on the product be resolvable to different datasets for different audiences — consumers, customs officials, recyclers. GS1 Digital Link enables this via a single structured URL. Standard proprietary QR codes don't meet this requirement and will need to be replaced before enforcement deadlines." }, "name" : "Why does a DPP require GS1 Digital Link instead of a standard QR code?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "The Battery Passport is the first mandatory DPP, with enforcement beginning 18 February 2027. Delegated acts for textiles and apparel are expected to take effect in 2027. Brands in both sectors should be building their data collection infrastructure now — the 60–70% of required data that already exists in internal systems can be structured and audited immediately, before the supplier data collection phase begins." }, "name" : "When do DPP data requirements take effect for textiles and batteries?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Your sector's delegated act will specify which categories are mandatory — but that act may not be published until 2026 or 2027. The practical approach is to start with the Article 7 mandatories (UPI, economic operator data, SoC disclosures, disassembly instructions) and map your internal data against the full 16 categories in parallel. TrackVision's Regulatory Expert System automates this mapping against your specific product catalogue." }, "name" : "How do I know which EPRS categories apply to my products?" } ] } ```