One self-hosted console to run your entire business — commerce, ERP, HRM, CRM & manufacturing

Digital Product Passports Are Coming: What Product Data to Start Collecting Now

The EU Digital Product Passport reaches sellers worldwide. See which dates are firm, what a passport holds for one T-shirt, and a 12-month plan to get supplier, batch and product data ready.

Author

Anichur Rahaman

1 month ago10 min read1 views
Digital Product Passports Are Coming: What Product Data to Start Collecting Now

"For style TS-210, please send the fibre content, the list of factories and the batch record for the units we received in May." The email from a distributor in Germany lands on a Tuesday morning with the purchasing lead of a small fashion brand, which ships from outside Europe to customers in the EU.

The fibre content is in a supplier PDF somewhere. The factory list lives in one person's head. The batch record is a line in a spreadsheet that does not mention the fabric lot. It takes four days and three people to answer, and the answer is partly a guess.

That email is a small preview of the EU Digital Product Passport. It is a product-data problem long before it is a QR-code problem, and the businesses that start collecting clean product and supplier data now will answer in minutes instead of days. This article explains what the passport is, who it reaches, which dates are firm, and what to build over the next twelve months.

What a digital product passport is

The passport comes from the Ecodesign for Sustainable Products Regulation, Regulation (EU) 2024/1781, known as ESPR, which has been in force since 18 July 2024. A digital product passport (DPP) is a structured set of data about one product, reachable by scanning a data carrier such as a QR code on the product, its packaging or its papers.

Three technical rules shape everything else. The carrier points to a persistent unique product identifier, for example a GS1 Digital Link built from a GTIN plus a batch or serial number. The data must be machine-readable and based on open standards, so it can move between systems without vendor lock-in. And access is tiered: a shopper sees materials, repair and recycling guidance, while authorities and recyclers can see more.

Five-step flow from suppliers to product master, passport, QR code on the product and the people who scan it, with public, authority and business access tiers underneath
The passport is the last link of a chain that starts with a supplier's declaration.

The EU registry does not store your passports. The Commission launched the central DPP registry in July 2026; it is an index. The full passport stays with the company that placed the product on the market, or with an authorised service provider it hires.

Who is affected, including sellers outside the EU

ESPR applies to products placed on the EU market, wherever they were made. A factory in Vietnam, a brand in Turkey and a marketplace seller in Brazil are all in scope once a covered product reaches an EU buyer. For imports, the importer or an authorised representative in the EU carries the legal responsibility, which means they will ask their non-EU suppliers for the data.

Some product types sit outside ESPR altogether, including food, feed, medicines and motor vehicles. Everything else is a candidate. But ESPR is a framework: it creates no product rules by itself. Each product group gets its own delegated act that names the data fields, the carrier and the date.

Flowchart with three decision diamonds: placed on the EU market, product group has a delegated act, which date applies, leading to naming a data owner
Three questions decide whether the passport reaches you, and when.

The dates, as of August 2026

Some dates are fixed in law. Others are targets in the Commission's working plan and can slip. Treat the table as a map, and check the latest delegated acts before you commit a budget to any row marked indicative.

MilestoneDateStatus
ESPR in force18 July 2024Fixed
Working plan 2025 to 2030 adoptedApril 2025Fixed; mid-term review planned for 2028
Central DPP registry liveJuly 2026Fixed; it creates no filing duty for sellers yet
Ban on destroying unsold apparel, accessories and footwear, large companies19 July 2026Fixed
Battery passport for EV, light-transport and industrial batteries above 2 kWh18 February 2027Fixed (Regulation (EU) 2023/1542)
Delegated acts: iron and steel, then textiles, tyres, aluminium, furniture, mattressesPlanned from 2026 through 2029Indicative; check the latest delegated acts
Destruction ban, medium-sized companies19 July 2030Fixed; micro and small companies are exempt

The working plan names steel and aluminium, textiles (apparel first), furniture, tyres and mattresses as the first product groups, plus a number of energy-related products. Obligations in a delegated act normally start at least 18 months after the act enters into force, unless the Commission shortens that for a good reason. For a seller of T-shirts that means the passport is probably a 2028 or 2029 event. Collecting the data takes longer than that.

Why it is a data problem first

Look at what a passport asks for: material composition, recycled content, where each stage was made, hazardous substances, durability, repair and spare parts, carbon footprint, end-of-life instructions, and a link to the exact batch. Almost none of that is created by your website or your sales team.

It sits in four places. Supplier declarations hold materials and substances. The product master holds identifiers, care and repair data. Batch and lot records hold what was made when, and from which inputs. Company records hold the legal entity that answers for the product. The problem is that these four rarely agree on what a "product" is.

Matrix of eight data types against four product families, each cell marked core, likely or later
An illustrative readiness board: collect the core fields now, and wait for the delegated act on the rest.

The board is illustrative. Final fields come from each delegated act. But material content, origin, batch identity and substance declarations appear in almost every draft, so they are safe to start on.

A worked example: one T-shirt

Take a cotton T-shirt, model TS-210, produced as batch B-0412 of 3,000 units. The fields below are an illustration of what a textile passport could contain, not the legal list. What matters is the right-hand column: every field has exactly one system that owns it.

Passport fieldIllustrative valueSource system
Unique identifierGTIN plus batch B-0412Product master
Fibre composition100% cottonSupplier declaration from the fabric mill
Recycled content0%Supplier declaration
Production sitesMill A (fabric), Factory B (sewing)Supplier master and purchase order
Dyes and finishing chemicalsTested against a restricted-substances listSupplier test report
Care and durabilityMachine wash 40 °C, rated for 40 washesProduct master (tech pack)
Carbon footprint4.1 kg CO2e per unit, with method namedSupplier or life-cycle study
Batch date and quantity12 May 2026, 3,000 unitsBatch record in inventory
End-of-life guidanceCollect for textile recyclingProduct master
Responsible EU operatorImporter name and addressCompany master

Now follow the records. The purchase order PO-7781 buys 3,150 metres of fabric from Mill A. The goods receipt creates fabric lot F-88 and attaches the mill's declaration to it. The cutting order consumes F-88 and writes 3,000 shirts into batch B-0412, so B-0412 now points back to F-88 and the declaration. When the German distributor scans the QR code, the passport resolves the batch, follows that link, and returns the fibre content with a date and a document behind it. If the mill sends a corrected declaration in October, only lot F-88 changes, and every batch built from it inherits the fix.

What your systems need

Catalogue and product master

You need one record per model, with a stable identifier that never gets reused and variants that map to it. Free-text description fields cannot carry a passport. Add structured attributes for composition, care, repair and end-of-life, each with an owner and a last-reviewed date.

Purchasing and supplier data

Treat declarations as documents with an expiry date, linked to the supplier and to the material, not to a folder on someone's laptop. Add the declaration to your purchase terms: no declaration, no purchase order release. Record the site that made each stage, not only the company that invoices you.

Inventory and batches

This is where most businesses are weakest. If stock is only a quantity per SKU, you cannot answer "which batch". You need lot or batch tracking at receipt and at production, and every stock movement should carry the lot. Without it, a passport can describe the model but not the shirt in the customer's hand.

The destruction ban is an inventory rule

Since 19 July 2026, large companies may not destroy unsold apparel, clothing accessories and footwear in the EU, with exceptions the Commission defined for cases such as safety risks or damaged goods. Medium-sized companies follow in 2030. Large companies already have to disclose the volumes of unsold goods they discard.

The practical effect is on how you plan stock. Overbuying now has a visible cost, because the exit route of a landfill or an incinerator is closed. Companies will need accurate sell-through by style, markdown rules, donation and resale channels, and a record of what happened to each leftover lot. That is the same batch-level inventory data the passport needs.

A 12-month plan

You do not need to wait for a delegated act to start. This sequence works for any product family and costs mostly time:

  1. Months 1 to 2: scope. List every product you ship to the EU, grouped by the product groups in the working plan. Name one person who owns product data.
  2. Months 2 to 4: clean the master. One record per model, a permanent identifier, structured composition and care fields. Retire duplicates.
  3. Months 3 to 6: supplier requests. Ask the top suppliers by volume for material declarations, site lists and certificates. Store them as dated documents against the supplier and material.
  4. Months 5 to 8: batch tracking. Switch on lot numbers at receipt and production. Test by tracing five finished batches back to a fabric or component lot.
  5. Months 8 to 10: pilot a passport. Pick one model, generate a public page and a QR code, and let a colleague scan it from a printed label.
  6. Months 10 to 12: review the delegated acts. Compare your fields against whatever has been published and close the gaps.

What to measure

Four numbers tell you whether the data is getting better. Share of active models with complete composition and care fields. Share of purchased materials with a valid, unexpired supplier declaration. Share of finished batches you can trace to an input lot in under five minutes. And the time it takes to answer a data request like the German distributor's. An illustrative target for the first year is 90% on the first three, and an answer in under an hour.

Back to the email

Return to the distributor's Tuesday email. With the fabric lot linked to a dated declaration, the factory list held in the supplier master, and the batch record pointing at both, the purchasing lead replies with a link instead of a chase. Nobody guesses. If the same question comes from a customs authority or a recycler in 2028, the answer is the same link, with a different access tier.

Key takeaways

  • The Digital Product Passport applies to products placed on the EU market, wherever the seller is based, and reaches non-EU businesses through the importer.
  • ESPR is a framework. Rules arrive product group by product group in delegated acts, so check the latest acts before relying on any indicative date.
  • Fixed dates today: the destruction ban for large companies from 19 July 2026, and the battery passport from 18 February 2027.
  • Most passport fields live with suppliers, so declarations, site lists and lot numbers are the first thing to collect.
  • Give every field one owning system, and make batches link back to input lots and their declarations.
  • Measure completeness and response time, not whether a QR code exists.

Anichur Rahaman is a software architect and the creator of StoreConsole. He designs commerce and ERP systems for growing businesses, with a focus on event-driven architecture, data integrity and self-hosted operations.

About the Author

Anichur Rahaman

Continue Reading