Live scan maps
Where every code is being scanned, as it happens. Diversion shows up as a shape on a map rather than a line in a spreadsheet.
For commercial and supply chain teams
Where it shipped, and where it actually turned up
You know which distributor took which batch. What you usually cannot see is where those units were finally scanned — and the gap between the two is where diversion lives.
Because every unit carries its own identity, that gap is measurable per batch, per region and per customer, rather than inferred from falling sales in a territory months later.
What surfaces
Movement you can act on
Batch against territory
Units allocated to one market appearing consistently in another — the pattern that distinguishes a leak from a tourist.
Timing
How long after despatch a batch surfaces, and where. Slow, distant first scans read very differently from fast, local ones.
The conversation it changes
Evidence, not accusation
Grey-market conversations with a distributor are difficult because they usually start with suspicion and no data. A per-code record moves the discussion onto what happened to which units, which is a commercial conversation rather than a confrontation.
Export per batch as CSV for a review meeting, or push events into your own systems over the API.
Test it on one product line
Pick a line with a diversion question attached to it and code a single run. The pattern is usually legible within a few weeks of the units reaching the field.
info@optrical.com
+44 (0)114 352 0777