Deployment blueprint
Pharmaceutical distribution has two audit questions: was the product held in condition the whole way, and was the person really where the timesheet says. We answer both from one platform — cold-chain-aware vehicle tracking for the B2B fleet, and face-verified, zone-bound attendance for the field team.
Built for this scale
The challenges
Two separate assurance problems — product condition and workforce presence — usually solved by two vendors who never reconcile.
Challenge
Temperature is logged by a standalone datalogger and read at delivery, so a warming load is discovered when it is already a write-off. Worse, the reading has no position attached, which makes the cause — a long door-open at the third stop — impossible to identify.
Challenge
Selfie check-in without liveness detection is defeated by holding up a picture of a colleague. GPS check-in without a boundary is defeated by punching in from the car park, or from home. Either way the timesheet becomes a document nobody can rely on.
Challenge
A representative's call report says the pharmacy was visited. Nothing in the system distinguishes that from a phone call made in a nearby café, so coverage planning and incentive calculations run on self-reported activity.
Challenge
Distributors and 3PL partners legitimately need to see their own shipments and their own staff. Giving them a login to the whole operation is not an option, and running a separate system per partner does not scale.
How it would work
The fleet side runs on the same telematics spine as any other operation — live position, trips, geofences, driving events — with temperature probes feeding readings into the trip record rather than into a separate logger. The workforce side runs on a punch that has to satisfy two independent checks: a face match with liveness detection against the employee's enrolled template, and a point-in-polygon test of the GPS position against that employee's assigned zone. Device-level mock-location signals are treated as a rejection reason in their own right. Field visits are checked against the specific site's geometry instead of the home zone, so a customer call is confirmed where it happened.
The architectural point
The reason to run both on one platform is that the organisation hierarchy does the hard part once. A distributor, a regional office, or a 3PL partner is a node in the tree, and everything beneath it — vehicles, employees, zones, shifts, reports — is scoped automatically. Adding a trading partner is an administrative action, not a deployment. And because attendance, shifts, visits, and vehicle trips are records in the same system, a discrepancy between where a representative punched in and where the delivery vehicle actually went is a query rather than a reconciliation project.
Vehicles live
184
Checked in
612
Rejected punches
17
Temp excursions
1
Distribution & workforce
livePunch rejected · outside assigned zone
Rep 2041 · 1.2 km from Zone North
Punch rejected · liveness failed
Screen image detected · re-attempt logged
Visit confirmed · pharmacy 118
Face matched · inside site geometry
Verified check-ins · last 12 days
Illustrative console view — sample data, not a live operation.
Platform capabilities
Cold-chain-aware fleet tracking, verified attendance, and field-visit confirmation on one multi-tenant platform.
Check-in requires a face match against the enrolled template plus a liveness check, so a held-up photograph or a screen image is rejected rather than accepted.
The punch position is tested against the employee's assigned zone geometry. Outside the boundary, no GPS fix, or a mock-location device each produce a specific, recorded rejection reason.
ExploreA field visit is validated against that customer site's own geometry, turning a call report into a confirmed presence with a timestamp.
ExploreTemperature readings ride with position and trip, so an excursion is traceable to a stop and exportable as a per-shipment history.
ExploreRosters and shift patterns per employee, with late, missing, and out-of-zone punches surfaced as exceptions instead of found at payroll.
Trading partners get a scoped view of their own vehicles, staff, and reports through the organisation hierarchy, under your branding.
ExploreHardware in the field
Standard phones for the field team, plus the vehicle-side sensing that makes a shipment's condition provable.
Attendance, visits, and job updates run on standard Android and iOS handsets — the camera and GPS are the attendance hardware, so there is nothing to issue or replace.
ExplorePosition, ignition, and driving events across the distribution fleet, registered by IMEI and paired to a SIM from inventory.
ExploreReefer and cold-box probes pair with the vehicle's tracker so readings arrive attached to the trip rather than in a separate log to be matched up later.
ExploreWhere a load needs sealing, remotely controlled locks record every open and close with position, so custody transfers only at authorised stops.
ExploreIntegrations
Connected to the HR, ERP, and quality systems that already govern the operation.
Verified attendance and shift records export to payroll, so the hours that get paid are the hours that were validated in the field.
Orders, shipments, and delivery confirmations reconcile against the trip and custody record rather than being matched by hand.
Per-shipment temperature histories and custody events export in the form quality teams and auditors ask for.
Internal staff and partner users authenticate against the existing directory, with access scoped by position in the organisation tree.
FAQ
Short answers here — the detailed version is a conversation whenever you're ready.
Discuss your deployment
Sovereign-data-friendly. Enterprise multi-org architecture. Built to integrate with the devices, SIM providers, and back-office systems you already run.
