When the EU announced that large enterprises would be prohibited from destroying unsold consumer goods — textiles first, then electronics — many brands responded by accelerating their DPP implementation. Add a QR code to the label, register with a registry, call it done.
This response misunderstands what the destruction ban actually requires.
What the Regulation Requires
The EU Ecodesign Regulation destruction ban (entering force for large enterprises in 2025, SMEs in 2026) does not just prohibit destruction. It requires economic operators to demonstrate that destruction did not occur. This is an evidentiary obligation, not just a prohibition.
For a fashion brand with 100,000 units of unsold seasonal stock, demonstrating that none of those units was destroyed means having:
- A record of every unit's unique identifier at the time it left your possession
- Documentation of where each unit went (returned to supplier, sold at outlet, donated to charity, recycled)
- For recycled or donated units: documentation from the receiving organisation
- The ability to produce this documentation to a market surveillance authority on demand
A QR code on a label establishes that the product exists and has a DPP. It does not establish what happened to the product after it left your warehouse.
The Unit-Level Problem
Most brands track inventory at the SKU level, not the unit level. They know they had 5,000 units of SKU-1234 and sold 3,200. They do not know the individual serial number of each unit, which units went to which retail location, or what happened to the 1,800 units that did not sell.
The destruction ban requires unit-level accountability for disposal. This requires unit-level serialisation — each physical product has a unique identifier, and its disposition is tracked at the unit level. This is a significant operational change for brands that have never serialised their inventory.
RAIN RFID (Radio Frequency Identification) is the practical technology for unit-level serialisation of textiles at scale. Each garment gets an RFID tag with a unique TID (Tag Identifier) that cannot be cloned. The TID is registered against the product's DPP. When the garment is disposed of — recycled, donated, or sold — the RFID tag is scanned and the lifecycle status updated.
Why Existing ERP Systems Are Not Enough
Enterprise resource planning systems track inventory at the SKU or batch level for cost accounting purposes. They are not designed for unit-level serialisation with lifecycle status tracking. Adding unit-level destruction compliance to an ERP is possible but requires significant customisation.
The practical path for most mid-market fashion brands is:
- Assign serial identifiers at manufacture — either RAIN RFID tags (for high-value items where hardware cost is justified) or QR code labels with unique serial numbers
- Register each serial identifier against a DPP record in a system that supports lifecycle status updates
- Update lifecycle status when units are sold (status: active → customer), donated (status: active → donated), recycled (status: active → deactivated with recycling documentation), or returned (status: active → returned)
- Retain the lifecycle history for the regulatory retention period
The DPP as Destruction Audit Trail
A properly implemented DPP system with unit-level lifecycle tracking is simultaneously a destruction-ban compliance tool. The dppStatus field in an ESPR-compliant DPP can hold values: active, deactivated, destroyed, remanufactured. The deactivated status with an accompanying disposal record (recycling certificate, donation confirmation) is the evidentiary basis for demonstrating compliance with the destruction ban.
Brands that implement DPPs at the unit level — rather than the model level — get the destruction ban audit trail as a side effect of compliance with the DPP mandate. Brands that implement DPPs at the model level (one DPP for all units of a SKU) do not.
The choice between model-level and unit-level DPP implementation is a strategic compliance decision, not just a technical one.
PassportLab supports granularity levels: MODEL, BATCH, and ITEM (unit-level). See the granularity options or talk to our compliance team about unit-level implementation for your product range.