Data Audit Guide

You Already Have More DPP Data Than You Think

Brands approaching DPP preparation often assume they are starting from zero. They are not. REACH compliance records, care label composition data, certification documentation, supplier audit reports — all of this feeds directly into DPP data requirements. The challenge is not collecting new data. It is structuring and connecting what you already have.

Existing Data Sources REACH · Labels · Certs · Audits
REACH compliance → DPP Category 7
Care labels → DPP Category 6
Certifications → DPP Category 9
Supplier data → DPP Categories 1–4
Map Your Data →

The Real Starting Point for DPP Data

Before requesting a single piece of new data from a supplier, every brand should audit what it already holds. The answer is almost always more than expected.

EU textile brands are already subject to a range of regulatory obligations that generate structured product data: REACH chemical compliance, the EU Textile Labelling Regulation, EPR registration requirements, and any voluntary certification schemes they participate in. Each of these compliance processes produces data that maps directly onto DPP data categories.

The problem is not a data shortage. It is a data architecture problem: the same information exists in multiple disconnected systems — a compliance tool here, a shared drive there, a PLM database somewhere else — with no single product identifier linking it all together and no API layer making it accessible to a DPP endpoint.

Structuring and connecting what you already have is typically faster, cheaper, and more impactful than starting new data collection processes. It is also the logical first step — because until you know what you have, you cannot know what you are missing.

How Your Existing Compliance Data Maps to DPP Categories

Every major EU compliance obligation you already manage generates data that feeds one or more DPP categories directly.

1

REACH Compliance Records

Maps to: DPP Category 7 — Compliance & Chemical Safety

REACH compliance documentation — SVHC substance declarations, restricted substance test reports, supplier declarations of conformity — is among the most directly usable existing data for DPP purposes. It is already product-linked, already generated at the regulatory standard required, and already maintained as structured documentation in most brands' compliance systems.

What you likely already have:

  • SVHC (Substance of Very High Concern) declarations per product or material
  • Restricted substance list test reports from accredited laboratories
  • Supplier REACH declarations and declarations of conformity
  • OEKO-TEX or equivalent chemical safety certificates

What needs to happen:

  • Link each compliance document to a specific product identifier (not just a material type or season)
  • Digitize any paper-based records into a structured, queryable format
  • Confirm validity dates and flag records requiring renewal
2

EU Textile Labelling Data

Maps to: DPP Category 4 — Material Composition

The EU Textile Labelling Regulation already requires accurate fibre composition to be declared on every garment label sold in the EU. This composition data — the percentages of each fibre type in the product — is a core DPP data requirement. You are already collecting and verifying it. The gap is typically that the DPP requires component-level composition (body fabric, lining, trim, thread separately), while the care label typically shows an overall garment composition.

What you likely already have:

  • Overall garment fibre composition (for care label compliance)
  • Supplier fibre composition declarations
  • Any fibre testing results verifying declared composition

What needs to happen:

  • Request component-level breakdown from suppliers (body, lining, trim, thread separately)
  • Structure composition data as machine-readable records linked to product identifiers
  • Confirm recycled content percentage and verification basis where applicable
3

Third-Party Certifications

Maps to: DPP Category 9 — Sustainability & Environmental Performance

Certifications from bodies such as GOTS, OEKO-TEX, GRS, and the EU Ecolabel represent verified third-party claims about a product's environmental and social performance. In the DPP, certifications are among the highest-credibility data points — they are substantiated by an independent body, tied to a certificate number that can be verified, and carry an expiry date that the DPP system must track.

What you likely already have:

  • Certificate numbers and issuing body documentation for all active certifications
  • Certification scope documentation (which products, which production stages)
  • Validity dates and renewal schedules
  • Certification logos and usage rights documentation

What needs to happen:

  • Link each certificate to the specific products it covers (not just to the brand or season)
  • Digitize any paper-based certificates into structured records with validity dates
  • Establish a governance process to update DPP records when certifications lapse or are renewed
4

Supplier Audit and Factory Data

Maps to: DPP Category 2 — Supply Chain Information

Social and environmental factory audits — whether conducted through audit programmes, multi-stakeholder initiatives, or self-assessments — generate facility-level data that directly feeds DPP supply chain requirements. Factory names, addresses, and production stage information collected for audit purposes map directly onto DPP Category 2 requirements.

What you likely already have:

  • Tier 1 factory list with names and addresses (from audit registrations)
  • Production stage information for each facility
  • Country of manufacture for each product
  • Any Tier 2 supplier data collected as part of extended audit programmes

What needs to happen:

  • Standardize facility naming (the same factory should appear identically across all systems)
  • Link facility data to specific products, not just to seasons or buyer relationships
  • Add country of origin of raw materials (distinct from country of manufacture)
  • Assign standardized facility identifiers where possible
5

Care Instruction Data

Maps to: DPP Category 6 — Care Information

Care instructions required on EU garment labels are already a regulatory requirement under the EU Textile Labelling Regulation. The content is defined and verified for every product — it simply needs to exist in a machine-readable digital format rather than only as a care symbol strip on a physical label.

What you likely already have:

  • Care instruction content for every product (washing, drying, ironing, bleaching)
  • Care symbol specifications used in label production
  • Language-specific care instruction text for each EU market

What needs to happen:

  • Convert care instructions from label artwork files into structured, machine-readable data fields
  • Link care instruction records to product identifiers
  • Add repair and spare parts information where available
6

EPR Registration Data

Maps to: DPP Categories 1 & 3 — Brand Information & Product Information

EPR (Extended Producer Responsibility) registration in EU member states requires brands to provide product volume and category data — often at a level of detail that overlaps with DPP product identity requirements. The product classification, weight, and volume data collected for EPR fee calculation feeds directly into DPP product information fields.

What you likely already have:

  • Product category classifications used for EPR fee calculation
  • Product weight data per category
  • Volume of units placed on market by country
  • Brand and importer registration details

What needs to happen:

  • Map EPR product categories to DPP product type classifications
  • Link EPR volume data to DPP product records where applicable
  • Confirm that importer and responsible economic operator details are consistent across EPR and DPP records

The Real Challenge: Structuring and Connecting

Having the data is only half the problem. The other half is making it usable for DPP purposes.

Existing compliance data was generated for specific regulatory purposes — REACH compliance, label verification, audit evidence. It was not generated with DPP in mind, which means it typically has several characteristics that make it difficult to use directly in a DPP system:

No Consistent Product Identifier

REACH records may reference a material. Audit data may reference a factory and a season. Certification data may reference a product line. None of these use the same identifier, making it impossible to automatically link records for the same product across systems. The first step is establishing a master product identifier that can be used consistently across all data sources — and retroactively mapping existing records to that identifier.

Non-Machine-Readable Formats

Test reports are PDFs. Supplier declarations are scanned documents. Certification documentation is images. Audit reports are Word documents. None of this is directly queryable via API or servable as structured DPP data. Digitizing and structuring this content — extracting the relevant data fields into a machine-readable format — is time-consuming but necessary work.

Granularity Mismatches

DPP requires data at the individual product level — linked to a specific serialized unit identifier. Existing compliance data is often at a higher level of aggregation: by material type, by production batch, by season, or by supplier. Disaggregating this data to the product level — or establishing which product-level records inherit which compliance data — requires deliberate data mapping work.

Inconsistent Supplier Naming

The same factory may appear as "ABC Tekstil A.S." in the ERP, "ABC Textiles" in the audit system, and "ABC Ltd." in the REACH declaration. Automated data linking fails when the same entity appears under different names across systems. Supplier name standardization — establishing a canonical name for each supplier and normalizing it across all systems — is essential groundwork for any data consolidation effort.

How to Audit Your Existing DPP Data

A practical four-step process to map what you have, identify what you are missing, and prioritize what to do next.

1

List Every System That Holds Product Data

Start by identifying every place in your organization where product-related data is stored: PLM, ERP, compliance management tools, shared drives, supplier portals, email archives, spreadsheets. Include data held by third parties on your behalf — certification bodies, audit firms, testing laboratories. This inventory is your data landscape map.

2

Map Each Source to the 9 DPP Categories

For each system identified, document which DPP data categories it contributes to and at what level of completeness and structure. Use the DPP Data Checklist as your mapping framework. This step reveals both the richness of what you already hold and the gaps that require new data collection.

Open the Checklist →
3

Identify the Structuring Work Required

For each data source, assess: Is it machine-readable? Is it linked to a consistent product identifier? Is it at the right level of granularity (product-level, not season or batch level)? Is it current and valid? The answers identify where data exists but needs structuring work before it can be used in a DPP system — which is typically a larger body of work than collecting missing data from scratch.

4

Prioritize and Sequence

Rank your existing data sources by ease of structuring and DPP impact. REACH records linked to specific products and already in digital format are high priority — low effort, high value. Scanned paper test reports from 2019 that are not product-linked are lower priority — high effort, potentially low value if the products they cover are no longer in production. Focus structuring effort where it creates the most coverage most quickly.

What Existing Data Typically Cannot Cover

Even after a thorough audit, most brands will find genuine data gaps that require new collection efforts.

Tier 2 and Tier 3 Supply Chain Data

Most existing audit and sourcing data covers Tier 1 suppliers. The facility-level data for dyehouses, spinning mills, and raw material origins that DPP requires typically does not exist in internal systems and must be collected directly from the supply chain.

Component-Level Material Composition

Care label compliance generates overall garment composition, not the component-level breakdown DPP requires. Body fabric, lining, trim, and thread compositions must be requested from suppliers separately — this data does not typically exist in internal systems.

Repairability and End-of-Life Information

Information about spare parts availability, repair instructions, and disassembly guidance is rarely systematically documented in any existing compliance system. This requires deliberate new data collection — typically from product development teams and suppliers.

Environmental Performance Data

Carbon footprint, water use, and energy consumption data requires primary supplier data collection (energy records, water use figures) that most brands have not yet systematically gathered. This is also the category most affected by methodology standards still in development.

Frequently Asked Questions

If we already comply with REACH and EU Textile Labelling, are we partially DPP-ready?
Yes — those compliance processes generate data that will be required in the DPP. However, the DPP requires that data to be structured in a standardized, machine-readable, digitally accessible format and linked to a unique product identifier via an interoperable IT system. Compliance data that exists only in paper form, in fragmented internal systems, or linked to materials rather than individual products still needs significant structuring work to become DPP-ready. The data exists; the architecture does not yet.
Can we use our existing PLM system as the DPP data source?
A PLM system can be a valuable data source for DPP purposes — particularly for material composition and product identity data. However, most PLM systems are not designed to expose product data via external-facing APIs, do not support serialized unit-level identifiers, and do not handle dynamic data updates from circular economy operators. The PLM can feed data into a DPP platform, but it cannot function as the DPP system itself in most cases. The integration between PLM and DPP platform is a key IT architecture decision.
How do we handle compliance data that covers materials rather than specific products?
This is a common data mapping challenge. The approach is to establish which products use which materials, and then inherit the material-level compliance record at the product level. If a specific fabric has a REACH test report confirming no SVHCs, all products made from that fabric can reference that report in their DPP compliance data. The key requirement is that the linkage between product and material compliance record is documented and traceable — so that a regulator auditing the DPP can follow the chain from product to compliance evidence.
How long does it typically take to audit and structure existing compliance data?
For a mid-sized brand with several hundred active SKUs, a full data audit and structuring exercise typically takes 3 to 6 months of focused effort. The most time-consuming elements are supplier name standardization, linking compliance records to product identifiers, and digitizing paper-based documents. Brands that use a DPP platform with structured data import tools can accelerate this process — but the data review and validation work cannot be fully automated and requires human judgment throughout.

Ready to test epassportify with a pilot product line?

Join the pilot for early access, onboarding support, and direct input on feature development.

Requirements evolve—structured data keeps you upgrade-ready.

Explore epassportify