DPP Technical Architecture for Textiles: What the EU Parliament Study Specifies

Technical choices for a textile DPP should follow evidence, not vendor buzzwords. This primer reflects the European Parliament STOA study Digital product passport for the textile sector (PE 757.808, June 2024).

Three building blocks (study definition)

Product identifier — unique item, batch, or product reference (granularity can change over the lifecycle).
Data — product, process, and stakeholder information collected along the value chain.
Physical link — connects the product to the data (label, QR code, barcode, NFC, etc.).

Complex products: components may have their own passports; assembled product DPP aggregates component data.

Five practical layers (how teams implement it)

Layer	Study-aligned approach
Carrier	QR, barcode, NFC, or label serial — no mandated technology
Identifier	Batch or unique ID + brand/product reference
Resolver	URL or system that returns the right dataset for that ID — format set by future delegated acts / standards (study cites CIRPASS work, not a fixed GS1 Digital Link obligation)
Data model	Phase 1 mandatory themes first; full 16 category model later
Storage & access	Data with the economic operator; varying access by stakeholder (study Section 5.1)

Carriers: QR, barcode, NFC, RFID

The study discusses barcode, watermark, QR code, RFID, and other carriers to compare environmental and operational impact. It does not require NFC or RFID for all apparel.

Practical SME default: QR code on hangtag or care label — low cost, works on standard smartphones.

RFID: useful in logistics; consumer-facing DPP access via RFID is not assumed in Phase 1. Survey: lifecycle monitoring after first sale is hard unless RFID is widespread at sale/repair/waste points.

Use dynamic resolution (server-side destination) so data can be corrected without reprinting every code — consistent with versioned, auditable records in the study.

Identifier granularity

The study explicitly allows:

Batch / reference identification for high-volume goods
Unique identification for individually made or luxury items
Additional unique ID after manufacture or purchase

Do not assume every t-shirt needs a serial number on day one.

Public vs restricted data (mandatory design choice)

The study’s generic model gives stakeholders private and open access to different fields. Survey feedback:

Need-based transparency
Different user views (consumer vs recycler vs authority vs brand)
Protect confidential business information (e.g. full supplier lists)

Example mapping aligned with the study:

Field type	Typical consumer access	Typical restricted access
Recycled content, recyclability, microfibers	Public	—
Dangerous substances (summary)	Public where legally required	Detail for authorities
Process country / region	Public in Phase 1	Exact facility name
Certificates, audit reports	Summary	Full documents for B2B
Manufacturing costs	Not mandatory	Should not be public

Phase 2 interoperability (2030 in the study)

The advanced DPP phase recommends:

Interoperability between PIM, PLM, ERP, LCA, certification systems and the DPP (APIs, common protocols)
Standardisation between tracking supports (QR, barcode, etc.) from raw material to recycler

Phase 1 does not require full stack integration — but architecture should not block it.

Blockchain

The study mentions blockchain among technologies brands use for transparency (Fashion Pact fieldwork). It is not a DPP requirement. Survey and policy text treat DPP as an information and access problem first.

Audit trail

Stakeholders stress data quality, reliability, and verified vs merely declared information. Implement:

Version number and last updated timestamp
Author or system source
Link to source documents where claims are certificate-based

Delegated acts under ESPR are expected to define how long DPP data must remain available and who may update it.

Technical checklist (study-aligned)

Supports batch and unique identifiers?
QR and/or barcode (and optional NFC)?
Public/restricted field control per audience?
Versioned change history?
EU-hosted storage if you operate in the EU (GDPR; study: data with operator)?
Export of your data (avoid lock-in before Phase 2 interoperability)?
Phase 1 fields: recycled content, substances, microfibers, recyclability, process locations, packaging, innocuousness?

A “no” on items 3, 4, or 7 means the tool is not aligned with the study’s deployment path.