Pickup success rate · KPI 1, operational stability
PLOM-confirmed pickups over the attempts whose outcome the recorded data settles
(attempts − userSideFailures − unresolvedSessions).
How the attempts resolved
Table view
Success rate by actor
Same definition, split by who was at the locker. Courier pickups are returns runs.
Table view
Failure reasons
Counts per machine-readable reason, as the service reports them.
Table view
Courier loading pace · KPI 2, loading sessions
Minutes per parcel per session, measured between consecutive confirmed parcels — not across the scan window, which also holds rejected scans and idle time. Intervals longer than the session gap are pauses and are not counted; a session left with no interval has no measurable pace and is not plotted.
Table view — every session, measured or not
Parcels loaded per day · KPI 3.1, deliveries per day
Confirmed load closes per UTC calendar day. Quiet days are returned as zero, so a gap looks like a gap.
Table view
Loaded vs unloaded per day · derived from KPI 3.1 + the raw export
Parcels in against parcels out, side by side per UTC day. Loads are the KPI 3.1 figure; pickups are counted from the raw event export, because no endpoint reports them per day.
Table view — sortable
Picked up within 24 h · KPI 3.2
Load-to-pickup latency per parcel, linked on the PLOM order number.
Table view — coverage gaps
Pickup latency distribution
Picked-up parcels by elapsed time. Parcels still in the locker are excluded and counted as pending.
Table view
Raw event export
The flat tracking rows every value above is computed from.