Build Your Digital Product Passport with Data You Already Own

TL;DR: Most fashion brands already hold a significant portion of the data needed for EU Digital Product Passports — in PLM systems, ERP databases, supplier onboarding records, and existing certifications. The challenge is not a data shortage. It is a structural one: connecting, verifying, and organizing what already exists into DPP-ready infrastructure before mandatory compliance begins.

The conversation around Digital Product Passports tends to start in the wrong place. Brands hear "126 data points," "item-level serialization," and "lifecycle assessment per variant" and conclude that DPP readiness requires building something entirely new from the ground up. It does not.

Much of what a DPP requires — material composition, supplier locations, country of manufacture, certifications — is information fashion brands already collect. It lives in product specs, onboarding questionnaires, quality control reports, and ERP systems. The problem is rarely that the data does not exist. The problem is that it is scattered across departments, locked in spreadsheets, and structured in ways that cannot feed a compliant digital passport automatically.

This article is the fourth in NormaTrack's series on EU compliance, DPP, and supply chain traceability. Where earlier articles covered what a Digital Product Passport is, why supplier data is the hardest part of DPP readiness, and what ESPR means for fashion brands, this one gets practical. The focus here is on what you already have, what it maps to, and how to begin turning existing product and supplier data into DPP-ready infrastructure — without months of configuration or external consultants.

The ESPR Delegated Acts for textiles and footwear are expected in mid-2027. That sounds distant. It is not. The data collection pipelines, supplier relationships, and system integrations needed to run a DPP program at catalog scale take months to build and test. Brands that begin now with the data they already own will be ready. The ones that wait for regulatory finalization will not.

What Data Does a Digital Product Passport Actually Require?

Before assessing what you already have, it helps to be specific about what a DPP needs to contain.

Under the Ecodesign for Sustainable Products Regulation (ESPR), Digital Product Passports will require structured, verified, product-specific data accessible via a persistent digital carrier — typically a QR code or RFID tag. A DPP is not a sustainability landing page or a supplier list with a QR code attached. It is a living data system with defined access tiers: some fields visible to consumers, others to brands and regulators, and others specifically for circularity actors like recyclers and resellers.

The Trace4Value pilot project, run in cooperation with GS1 Sweden and the Swedish Institute of Standards, identified 126 likely data points for textile products, based on existing EU regulatory frameworks and ESPR drafts. Of those, approximately 25 to 30 are visible to end consumers at the point of scanning. The full dataset spans several categories:

• Material composition and recycled content — fiber type, percentages, origin

• Supplier identity and facility location — name, address, tier level (Tier 1 through Tier 4)

• Chain-of-custody documentation — certifications such as GOTS, OEKO-TEX, GRS

• Country of manufacture — processing and finishing locations

• Durability and reparability information — care instructions, repairability indicators

• Substances of concern — chemical safety data, REACH compliance

• End-of-life and recyclability guidance — disassembly instructions, recycling pathways

• Environmental impact indicators — product carbon footprint, calculated using a recognized methodology such as Product Environmental Footprint (PEF) or ISO 14040

Importantly, several of these categories overlap with data that fashion brands already collect for other purposes — EU Ecolabel compliance, REACH chemical registrations, retailer onboarding requirements, and internal product development processes. That overlap is where DPP readiness can begin immediately.

Where Is Your DPP-Ready Data Already Sitting?

Your PLM System or Product Database

Product Lifecycle Management systems are the most data-dense starting point for most brands. A well-maintained PLM holds bill of materials (BOM) data, material composition by SKU, colorway and variant specifications, and often country of manufacture. All of these map directly to core DPP fields.

The caveat: PLM data quality varies. Composition data entered as "65% polyester, 35% cotton" with no origin detail is a partial match, not a complete one. But it is a foundation — and a much faster one to build on than starting from scratch.

Your Supplier Onboarding Records

Most brands collect supplier information during onboarding: facility name, address, contact details, certifications held. This maps to the supplier identity and chain-of-custody sections of a DPP. The gap is typically depth — onboarding records often capture Tier 1 (the manufacturer) but rarely Tier 2 (the fabric mill) or Tier 3 and 4 (yarn spinners, raw fiber producers).

DPP compliance under ESPR is expected to require traceability to the raw material level for many product types. Brands whose supplier data currently stops at Tier 1 have a clear next step: extend data collection down the chain, starting with the suppliers they work with most consistently.

Your Existing Certifications and Compliance Documents

GOTS, OEKO-TEX, GRS, and REACH compliance records are directly reusable DPP inputs. Certification bodies already collect and verify much of the same data a DPP requires, which means brands with active certification programs are not starting from zero — they are organizing and connecting what is already verified.

Certifications also carry another advantage: they are third-party verified. DPP data quality requirements prioritize primary, verified data over self-reported claims. If your certifications are current and attached at the right supply chain node, they add immediate credibility to your passport data.

Your ERP and Purchase Order Data

ERP systems often contain supplier names, facility addresses, purchase quantities, and shipment data at SKU level. This feeds into supplier location and chain-of-custody fields. Some brands also store material test reports and quality control documentation within their ERP, which can provide additional data points on fiber composition and chemical compliance.

How to Map Your Existing Data to DPP Requirements: A Four-Step Approach

Step 1: Run a data audit against the expected DPP data categories

Before anything else, map what you currently hold against the core DPP data categories listed above. This does not need to be exhaustive — focus on the categories with the highest likelihood of being mandatory under the ESPR Delegated Acts. Material composition, supplier identity, country of manufacture, and certifications are the most consistent starting points across all pilot frameworks to date.

For each category, answer three questions: Do we have this data? Where does it live? Is it structured and accessible, or locked in documents and email threads?

Step 2: Distinguish structured data from unstructured data

Structured data — information held in databases, spreadsheets with consistent formatting, or PLM/ERP systems — can be imported and mapped programmatically. Unstructured data — PDFs, email attachments, scanned certificates — requires extraction or manual entry before it becomes usable.

Prioritize getting your structured data into a single system first. Unstructured data can be addressed progressively.

Step 3: Pilot on your most data-rich product lines

You do not need a complete data set across your entire catalog to begin. Start with the product lines where your data is most complete: your longest-standing supplier relationships, your most traceable materials, or the categories where you already hold certifications at multiple supply chain tiers.

A working DPP pilot on 20 products teaches you more about your actual gaps than a gap analysis spreadsheet on 2,000 SKUs. It also creates a replicable template — one that can scale once the structure is proven.

Step 4: Identify where supplier data collection is genuinely missing

After the audit, the gaps that remain are usually in deeper supply chain tiers and in environmental impact calculations. These are the areas where you will need to build new data collection workflows — typically through a supplier portal or structured data requests — rather than simply reorganizing existing information.

Plan this step with realistic timelines. Engaging new suppliers in data sharing requests, especially at Tier 2 and beyond, involves relationship-building and education. Brands that started this process in 2024 and 2025 consistently report that supplier response cycles are longer than expected, and that the conversations require context-setting, not just data templates.

Why Existing Systems Cannot Do This Alone

Here is where many brands hit a structural barrier. The data exists. The audit is done. The gaps are identified. But the systems holding the data were not designed to generate a DPP.

A PLM system manages product development. An ERP manages operations and finance. A certification portal tracks compliance status. None of these systems produce a machine-readable, EU-standard digital product passport with a unique product identifier, a scannable QR code, automated LCA output, and tiered data access controls.

Connecting these systems manually — through spreadsheet exports, copy-paste workflows, and consultants reconciling formats across tools — is neither scalable nor audit-ready. At catalog scale, it collapses.

What DPP-ready infrastructure requires is a layer that sits across your existing systems: importing data from your current tools, structuring it against DPP requirements, running environmental calculations automatically, and publishing live passports at the variant level as your product data changes.

How NormaTrack Turns Existing Data into DPP Infrastructure

NormaTrack is built specifically for this transition. The platform connects to the tools fashion and textile brands already use — including Shopify, SAP, Microsoft Dynamics, Google Sheets, Airtable, BigCommerce, EcoVadis, and more than 20 other integrations — and transforms existing product and supplier data into EU-compliant Digital Product Passports without requiring consultants or months of configuration.

The import process starts with what you already have. Drop in a CSV or Excel file and NormaTrack automatically maps your columns — SKU, material composition, origin country — flagging errors before they reach your passport. There is no manual reformatting, no IT project required to begin.

From there, NormaTrack maps each product variant to its full supply chain, tier by tier, from raw fiber to finished garment. Certifications attach at every supply chain node. LCA is calculated automatically per variant using ISO 14040 methodology — not estimated per collection, not outsourced to a consultant, but computed per SKU in bulk as your data updates.

Every variant gets a live digital product passport and a generated QR code. Visibility controls let brands decide which fields are public (materials, carbon footprint, origin) and which remain internal (supplier names, raw LCA data, costs). Compliance gap detection flags missing data against ESPR, GOTS, and ISO 14040 requirements before they become an audit problem.

Setup takes days, not months. No technical background is required to get started.

Request a demo to see NormaTrack with your own catalog data →

The Right Time to Start Is Before the Rules Are Final

A common objection to beginning DPP work now is that the ESPR Delegated Acts are not finalized. The exact data fields, access structures, and technical standards for textiles are expected in 2027. Why build infrastructure against requirements that may still change?

Because the data collection problem does not wait for regulatory finalization. Supplier data takes months to gather and verify. Supply chain mapping below Tier 1 requires relationship-building that cannot be accelerated at the last minute. Item-level serialization — unique identifiers per garment, not per batch — is a structural decision that is far cheaper to design correctly at the outset than to rework under a live compliance deadline.

The brands that participated in early DPP pilots consistently found the same thing: the regulatory gap was not the hard part. The data infrastructure gap was. And closing it takes longer than the deadlines leave room for, if you start too late.

Brands that begin now, with the data they already have, gain something that regulation-waiters cannot buy at the last minute: time to test, fix mistakes, and scale what works.

Explore a live DPP sample to see what compliant passports look like in practice →

Frequently Asked Questions

Can fashion brands start building Digital Product Passports before the ESPR Delegated Acts are finalized?

Yes, and doing so is strongly recommended. The ESPR Delegated Acts for textiles and footwear are expected in mid-2027. However, the data collection pipelines, supplier relationships, and system integrations required to run DPPs at scale take many months to establish. Brands that begin building data infrastructure now — using existing product and supplier data — will be in compliance-ready position when the final requirements are published.

What existing data can fashion brands use to start building DPPs?

Fashion brands typically already hold several DPP-relevant data types: material composition data in PLM systems, supplier names and facility locations in ERP and onboarding records, existing certifications such as GOTS, OEKO-TEX, and GRS, and country of manufacture data at SKU level. The challenge is not a data shortage but a structural one — connecting and organizing this data into a format that can generate compliant, machine-readable digital product passports.

How many data points does a textile DPP require?

The official data requirements will be set in the ESPR Delegated Acts expected in 2027. The Trace4Value pilot project, conducted in cooperation with GS1 Sweden and the Swedish Institute of Standards, identified 126 likely data points for textiles based on existing EU regulatory frameworks. Approximately 25 to 30 of those are visible to consumers at the point of scanning. The remainder are structured across access levels for brands, suppliers, regulators, and circularity actors.

Does DPP compliance apply to fashion brands headquartered outside the EU?

Yes. Any brand placing textile or footwear products on the EU market is subject to ESPR DPP requirements, regardless of where the brand is headquartered. International brands distributing into European markets need to prepare in the same way as EU-based brands.

What is the difference between a Digital Product Passport and a QR code on a label?

A QR code is the physical access point — it connects a consumer or regulator to the DPP data. The DPP itself is the underlying data system: a structured, verified, interoperable record of a product's materials, supply chain, environmental impact, and lifecycle information. A QR code linking to a supplier list or a sustainability PDF does not constitute a DPP. Compliance under ESPR will require a standardized data infrastructure, not a digital brochure.

How does NormaTrack help brands start building DPPs with existing data?

NormaTrack imports existing product and supplier data from tools brands already use — including Shopify, SAP, Google Sheets, Airtable, Microsoft Dynamics, EcoVadis, and more than 20 other integrations. The platform maps supply chains from Tier 1 to Tier 4, calculates LCA automatically per variant using ISO 14040 methodology, detects compliance gaps, and generates EU-compliant digital product passports with QR codes at catalog scale. Setup takes days, not months, and no consultants are required.