Use case
One thread through the operation:
the serial number.
Traceability is not a module. It is the consequence of a single decision taken at intake - that the unit of record is the device, not the pallet - and of every later stage writing to that same record.
The job
Three parties, three different questions.
A refurbishment operation is asked for traceability by three parties who mean different things by it. A record that answers only one of them is the common and expensive mistake, because the data cannot be reconstructed afterwards.
The regulator asks about destination
Equipment prepared for reuse leaves the waste stream; equipment recycled does not. The distinction is decided on the floor, device by device, and it is reportable.
The client asks for a discharge of liability
Evidence that a data-protection problem was disposed of, unit by unit, in a form their own auditors will accept - including the devices where erasure failed.
The auditor samples and follows
They pick a few items and follow them end to end. What is being tested is not the volume of data but whether the trail holds and cannot have been silently altered.
What the ERP records
Written where the work happens, not reconstructed after.
Each stage writes to the same device record. This is the list already detailed on the ERP page, read from the traceability angle.
-
01
A unique internal serial from entry
Controlled input and automatic tracking, with the client linked at day zero and the IMEI captured at intake where the device has one. No duplicates, no orphan device.
-
02
Erasure and audit evidence tied to the serial
Blancco reports flow in without re-entry and other audit tools can be plugged in. Certificates are exportable in one click, from the device rather than from an archive.
-
03
Repair history with its real cost
A device that fails audit generates its repair order with the diagnosis attached. Parts, time spent and real cost are measured per device, not per batch.
-
04
Disposition and materials
Devices beyond economic repair follow a dedicated, traced flow. Weight and materials from dismantling feed EPR scheme declarations directly.
-
05
Location at all times
Multi-warehouse stock at serial level: locations, transfers and inventories, with asset tags printed from the ERP itself.
What this is not
The boundaries, stated plainly.
- An ERP does not make an operation compliant. It produces the per-device evidence a compliance claim can rest on; which standard applies to you is set by your clients and your own scope.
- The per-device history that a Digital Product Passport will require is captured today. Passport export itself is on the ERP roadmap, targeted for Q4 2026, and is not shipped.
- Erasure certificates are issued by Blancco, not by REAV. The ERP files them against the device.
- None of this recovers history that was never captured. An operation that tracked by lot cannot reconstruct per-device records retroactively.
FAQ