regulations

JRC Apparel DPP Study: Batch ID Minimum, Model-Level Data

JRC study: batch IDs are the minimum for apparel DPPs; most data is at model level and item IDs are voluntary.

7/10/2026 · 8 min read · InfoDPP

A Public Research Input for the Apparel DPP

On 13 May 2026, the JRC Product Bureau published a Study on DPP content for textile apparel products under ESPR prepared for the Joint Research Centre as part of the preparatory work. It is a public research input, not a Commission position or a legislative proposal. Across 95 pages, its authors recommend a concrete list of data points and address, data point by data point, the question apparel companies ask most often: at what level should a DPP be established: model, batch or item?

The study concerns final textile apparel products and apparel accessories. It does not propose DPP requirements for intermediate textile products such as fibres, yarns or fabrics. Its findings still require stakeholder validation and refinement during the impact assessment. The DG GROW presentation of 27 May 2026 places adoption of the textiles act in Q3 or Q4 2027 and mandatory DPP application in 2029. This is a current Commission planning signal, not binding law.

Model, Batch or Item: What ESPR Actually Says

The ESPR leaves granularity open by design. Article 9(2) requires each product-specific delegated act to specify “whether the digital product passport is to be established at model, batch or item level, and the definition of such levels”. Recital 33 offers indicative descriptions: a model is a version of a product whose units share the technical characteristics relevant to ecodesign requirements and the same model identifier; a batch is a subset of a model produced in a specific plant at a specific moment; and an item is a single unit.

The study underlines why this choice matters: granularity is one of the main cost drivers of DPP implementation, and requirements that diverge from existing industry practice, such as jumping to item level where it is not already used, can significantly increase compliance costs.

The Study’s Proposal: Batch Identifiers as the Minimum

For apparel, the JRC proposes a tiered construction:

Batch identifiers as the minimum requirement. Every passport would be anchored to a batch-level identifier, populated with batch- or model-level information depending on the data point.
Most data points at model level. Fibre composition, care and repair instructions, recyclability scores, footprint indicators and the conformity declaration are recommended at model level.
Batch level where variability is material. Producer and facility identification, internally self-declared mechanical test data, chemical information (substances of concern), and some supporting data or certifications for material claims are recommended at batch level.
Item level stays voluntary. The study analyses voluntary item-level identifiers so that frontrunners, for example in the luxury segment, can invest early; an item passport would inherit model and batch data under an inheritance model.

Operators could always disclose data at a finer level voluntarily. The study explicitly wants to avoid penalising companies that are ahead of the curve.

Where Each Data Point Would Sit

A condensed view of the study’s per-data-point proposal (Table 13 in the original):

Data area	Proposed level
Unique product identifier	Item (analysed as a voluntary layer)
Batch ID, producer and facility identification	Batch
Model ID, product category, commodity code	Model
Fibre composition and component specification	Model
Robustness score, care and repair information	Model (repair information voluntary)
Mechanical-property checks (visual inspection, spirality and dimensional change) and the related conformity certification	Batch when self-declared; model when third-party certified
Substances of concern (list, location, concentration)	Batch
Recyclability score and its conformity certification	Model
Recycled content	Percentage and amount: model; waste type, weight and certification: batch
Organic content (voluntary)	Percentage and amount: model; certification: batch
Carbon and environmental footprint	Model, as a baseline

Two justifications are worth quoting. Producer identification sits at batch level because the manufacturing facility, and even the importer, can differ within one model. Chemical data sits at batch level because dyes vary between colours, with the study proposing a worst-case disclosure covering all chemicals associated with all colours within a batch.

A Model Definition That Changes the Maths

The study also sharpens the definitions it works with. A model is “a version of a product of which all units share the same technical characteristics, pattern and construction, not necessarily requiring colour and size distinctions”. A batch is a subset of a model produced in a specific plant at a specific moment under the same conditions, materials and processes.

For apparel companies this is one of the document’s most consequential lines. Sizes would not necessarily multiply the number of passports, and colour variants would not automatically become separate models either, because colour chemistry is handled through batch-level data. A trouser model sold in three colours and a full size run could remain one model for most data points.

The study grounds this in current practice: most textile companies manage product data at model level for external communication, use batch data internally for production, quality testing and certification, and rarely track individual items. Aligning DPP granularity with those existing practices is an explicit goal of the proposal.

Fewer Surprises for Online Retail

Anything batch-level raises an obvious e-commerce problem: an online marketplace cannot guarantee which batch a customer will receive. The study acknowledges this and points to Article 9(2), under which the delegated act defines how information is made accessible to customers before they are bound by a contract. Its suggestion: platforms could display model-level data or a representative batch passport at the offer stage, with the full passport at the required granularity available once a physical product is assigned to the order.

What the Study Is Not

It is not the delegated act. The legal decision on granularity, definitions and field lists will only be taken in the textile delegated act.
It is not a final field list. The proposed data points and levels can still change during the impact assessment and the legislative process.
It does not set a binding application date. The DG GROW presentation is a planning signal for 2029; the future delegated act will determine the legal requirements and application provisions.
It does not cover all textiles. The proposed DPP scope is final textile apparel products and apparel accessories, not intermediate products such as fibres, yarns and fabrics.

The status is comparable to the horizontal JRC data methodology we covered in March: research that reduces guesswork but does not replace the legal text. And as we outlined in our fashion industry guide, the delegated act is still being developed; what has changed is that a concrete, public granularity recommendation is now available.

Practical Takeaway for Textile Brands

Inventory your data at model level first. Fibre composition, care and repair information, recyclability and footprint data are proposed at model level, and that is where most existing product data already lives.
Map your batch traceability. Production plant, internal test results and chemical declarations per production run are proposed as the batch layer. Most manufacturers already hold this in quality systems; the task is connecting it to a batch identifier.
Do not assume every size needs a separate model. Under the proposed definitions, size variants do not necessarily require separate models, and colour chemistry is handled through batch data rather than separate model passports.
Treat item level as a strategic option, not an obligation. Unless there is a business case such as resale, repair services or authentication, the proposal keeps item identifiers voluntary.
Plan for language requirements. The study recommends that DPP information be understandable and accessible in all official EU languages, with free-text fields translated by the economic operator or its DPP service provider. The delegated act must still set the actual requirements.

Official Sources

Getting your model-level product data in order is the first practical DPP step for apparel. Start free on OriginPass.eu and structure a product record you can carry into the textile delegated act.

← Back to Blog