A stolen-device register, in build
Flag a serial once, and other WipeTrail operators can check it at intake. This one is on the 2026 roadmap — here is how it will work, and what is live today.
A stolen laptop is worthless to an honest operator and a liability if it slips through. WipeTrail already records the serial number of every device you handle. The next step, in build for 2026, is a shared register: a serial reported stolen is flagged once and visible to other WipeTrail operators at intake — something a single-tenant system structurally cannot do. It is not live yet, and we would rather say so plainly than let you assume otherwise.
What is live today
Every device you take in carries its serial number, its asset tag and its own event trail from intake to outcome. That record is the foundation the register is built on.
What the register will add
Intake staff will see a flag the moment a flagged serial is scanned in, before it enters your process or your shop.
Why we are building it
It reduces the risk of handling stolen goods and gives your customers another reason to trust your chain of custody — and it only works if operators share it.
Frequently asked questions
Is the stolen-device register live?
Not yet. Serial-level device records are live today; the shared register is in build for 2026 and we will say so here when it ships.
Will it share our customer data?
No. Only the device-level flag will be shared; your customer and commercial data stay isolated to your instance.
Why can’t a normal ITAD ERP do this?
A single-tenant ERP only knows its own devices. A register only works if it spans operators, which is why we are building it across the WipeTrail network rather than inside one instance.
Ready when you are
See WipeTrail on your own kit.
Walk the whole flow first — collection to certified wipe to resale — then tell us your device volumes. Your own instance can be live well before the DWTS deadline.
Take the walkthrough →