Collection, sorting and recycling already generate large amounts of data. The key is to connect this information into a reliable data and evidence chain.
With the introduction of European Extended Producer Responsibility for textiles, reliable information on collection, sorting, reuse and recycling is becoming increasingly important.
Germany is preparing a dedicated Textile Act for this purpose. The key points paper published in March 2026 provides, among other things, that future producer responsibility organisations (Organisationen für Herstellerverantwortung, OfH) will be required to ensure data collection for reporting purposes and to report on collected and recovered quantities. Under the current concept, quantities sent to fibre-to-fibre recycling are also expected to be reported separately.
This brings one question increasingly into focus:
How can we trace what actually happens to collected textiles after they are returned?Wie lässt sich nachvollziehen, was mit gesammelten Textilien nach der Rückgabe tatsächlich passiert?
Plenty of data – but no continuous data chain yet
A large amount of information is already generated along the textile waste management and recycling chain.
Collection points know the location, time and, where applicable, the contents of a return. Waste management companies document emptying operations, transport and weights. Sorting operators know the actual material fractions. Reuse partners and recyclers ultimately record which quantities have been received, reused or treated.
However, this information is generated by different actors and often stored in different systems.
For reliable traceability, storing individual data points is therefore not enough. The decisive factor is to connect them unambiguously.
The collection point forms the digital starting point
A traceable data chain should begin as early as possible.
With digital collection infrastructure, relevant information can already be captured at the point of return, for example:
- Collection point or container ID
- Time of return
- Bag- oder Transaktions-ID
- Product category
- Available material information
- Weight or quantity
- Source of the respective information
This gives the material flow a clearly defined digital starting point. However, these data only describe the beginning of the process.
A recorded product characteristic is not yet proof of recycling. A documented return is not yet confirmed recovery. Likewise, a collected quantity must not automatically be interpreted as a recycled quantity.
Subsequent process data must therefore be generated where the respective operations are actually carried out.
Handover events create a Chain of Custody
When a container is emptied or a collection batch is picked up, responsibility changes. At this point, further information is generated:
- Who took over the batch?
- When did the handover take place?
- What quantity was actually weighed?
- Where was the material transported?
- Which facility received it?
When this information is linked to the original collection batch, a Chain of Custody is created – a traceable chain of handovers and responsibilities.
The material flow therefore develops step by step:
Return → Collection Batch → Transport → Sorting Input
Each process partner adds the information for which they are actually responsible.
At the sorting facility, a collected quantity becomes a differentiated material flow
Sorting is one of the most important stages within the data chain.
Only at this stage does it become clear which fractions actually result from the collected quantity.
Depending on the material, the following pathways may result, for example:
- Preparing for reuse
- Fibre-to-fibre recycling
- Other material recycling
- Other recovery
- Residual or contaminant fractions
These results should not be derived or estimated from previous collection data. They must be documented by the responsible sorting operator. This also changes the structure of the material flow. One original collection batch may produce several new output batches.
Split, Merge and Batch Genealogy
In real-world recycling processes, material flows are regularly split and later combined again. When a batch is divided into several fractions during sorting, this is a Split. If, for example, similar cotton fractions from different collection areas are subsequently processed together, this creates a Merge.
A traceability system must therefore not only store individual quantities, but also be able to map the relationships between them:
Which new batch originated from which previous batch?
This history of origin and processing is referred to as Batch Genealogy. In this way, the material flow remains traceable even when complete physical item-level tracking is no longer possible.
Traceability does not mean tracking every single garment
Complete item-level tracking from return to recycled fibre is often neither necessary nor realistic for today’s post-consumer textile streams. Product labels may be missing. Older textiles do not have a digital product identity. In addition, materials are combined during sorting and recycling.
A practical infrastructure should therefore operate at several levels:
Item-Level, where unique product data are available.
Bag or Transaction Level, when several products are returned together.
Batch-Level, once material flows are collected, transported, sorted or processed.
The key is not to track every T-shirt individually at any cost. What matters is that the relevant material flow remains traceable across its different process stages.
Mass Balance checks the plausibility of the material flow
As soon as batches are split or combined, Mass Balance becomes particularly important.
The basic principle is:
Input = Output + documented losses or deviations
A digital system can therefore check, for example:
- What quantity was handed over?
- What quantity was confirmed by the next partner?
- Which output fractions were reported?
- Do input and output plausibly correspond?
- Are existing discrepancies documented?
This turns pure data collection into a control and evidence infrastructure. It is not only the existence of a data record that matters, but also its plausibility within the overall material flow.
A value is only as reliable as its source
The quality of individual data must also remain visible.
A weight value, for example, may come from very different sources:
- Calibrated weighing equipment
- Weighing ticket from a waste management company
- Inbound weighing at a sorting facility
- Sensor system
- Manual estimate
Formally, the same value may appear in all cases. Its reliability, however, is different.
A transparent data structure should therefore additionally document:
Who generated the value?
When was it generated?
How was it determined?
What source or evidence supports it?
Is the value measured, confirmed, estimated or calculated?
Transparency therefore does not mean displaying as many figures as possible on a dashboard. Transparency means being able to trace the origin and reliability of a value.
“Collected”, “Sent for Recycling” and “Recycled” must remain separate
This distinction is particularly important for reporting and sustainability communication.
When a textile batch is delivered to a recycler, it can initially only be documented that it was sent for recycling.
Only once the recycler confirms the material input and treatment can corresponding evidence of recovery be provided. The quantity of recycled material actually produced may also differ from the quantity delivered.
At a minimum, the following states must therefore remain separate within a reliable data chain:
Collected → Sent for Recycling → Recycled
Only in this way can statements about the material flow later be substantiated correctly.
Each actor remains responsible for their own process data
A shared data platform does not mean that a single operator assumes responsibility for all physical processes.
Responsibilities remain clearly distributed:
The collector documents the collection.
The waste management company documents emptying, transport and handover.
The sorting operator documents the incoming material, the sorting process and the resulting fractions.
The reuse partner documents the quantities received and those actually suitable for reuse.
The recycler documents material input, the treatment process and the treatment outcome.
The task of a digital infrastructure is to connect this information in a structured way, make its origin visible and check the data chain for completeness and plausibility.
From process data to EPR reporting
For municipalities and future producer responsibility organisations, these operational data must subsequently be consolidated into usable reports.
Relevant questions include, for example:
- How much was collected?
- What quantities were sent for preparing for reuse?
- What quantities entered recycling processes?
- What proportion was sent to fibre-to-fibre recycling?
- What quantities underwent other recovery?
- Where are there data gaps or unexplained discrepancies?
The German key points paper explicitly provides for data collection for reporting purposes by future producer responsibility organisations. This creates a new digital task between the physical material flow and regulatory reporting:
Data from different actors must be consolidated into a consistent and traceable material flow.
The Role of ELOOP
ELOOP starts at the first point of the material flow: the return.
The ELOOP Container and digital return infrastructure can capture the beginning of a textile material movement in a structured way. The key, however, is to ensure that these data do not remain isolated.
The ELOOP data platform is designed to connect information from subsequent process stages:
Return
→ Collection Batch
→ Emptying and Handover
→ Transport
→ Sorting
→ Reuse or Recycling
→ Recovery Outcome
→ Reporting
ELOOP does not replace waste management companies, sorting operators or recyclers. The respective process partners remain responsible for their operational activities and the data generated from them.
ELOOP takes on a different role:
to structure, connect and make data along the material flow traceably available.
Erfassen. Verbinden. Nachweisen.
The role of ELOOP can therefore be concentrated into three functions.
Capture
The material flow receives a clearly defined digital starting point at the collection point.
Connect
Data from waste management companies, logistics providers, sorting operators, reuse partners and recyclers are linked through unique events, handovers and batches.
Verify
Quantities, process steps and related documents are consolidated into a traceable data and evidence chain.
Capture → Connect → Verify
This transforms individual process data into a digitally traceable material flow.
EPR is therefore also an interoperability challenge
The future textile EPR system will have to connect different actors and existing IT systems. Municipalities, producer responsibility organisations, waste management companies, sorting operators, reuse organisations and recyclers will not necessarily work with the same software.
A scalable data infrastructure should therefore support open and standardised interfaces, for example:
- APIs
- Structured data imports
- Standardised batch IDs
- Defined status and process codes
- Documented handovers
- Standardised reporting formats
The objective is not to force every participant to work within the same system. The objective is to connect different systems through a common data logic.
The next infrastructure layer in textile recycling is digital
When discussing post-consumer textiles, the focus is often first placed on physical infrastructure:
Containers, collection points, vehicles, sorting facilities and recycling capacities.
This infrastructure remains indispensable. However, EPR creates a second layer in parallel:
the digital infrastructure behind the material flow.
A weighing ticket alone does not create traceability. A recycling certificate alone does not automatically show which collection the material originated from. Only when collection, handover, sorting and recovery are connected does a reliable data chain emerge.
This is exactly where ELOOP sees its future role:
as the digital connection between collection, waste management, sorting, reuse, recycling and reporting.
ELOOP
Erfassen. Verbinden. Nachweisen.
From the first return event to a traceable recovery outcome.
Legal status
This article reflects the legal and regulatory status as of 18 August 2026.
Directive (EU) 2025/1892 provides the European legal framework for Extended Producer Responsibility for textiles. Germany is preparing national implementation through a dedicated Textile Act. The key points paper published by the Federal Ministry for the Environment on 27 March 2026 describes the structures and requirements currently envisaged, but does not yet constitute the final German Textile Act.
This article is provided for general information purposes only and does not constitute legal advice.