Refrigerated logistics in the Gulf is a high-stakes business. Ambient temperatures touch 48°C through the summer months. A compressor that stalls for thirty minutes can spoil a full pallet of pharmaceuticals or perishable food. The operational margins are thin and the consequences of a missed alert are not.
A leading cold-chain logistics operator in the United Arab Emirates came to us in late 2025 with a familiar problem: they were running a 240-vehicle fleet across the UAE, with two more vendors' tracking platforms layered on top, and almost no operational visibility. They had data. What they didn't have were signals.
What follows is what we deployed, what changed in 90 days, and what surprised us along the way.
The starting point
Before ViaLoop, the operator's fleet ran on a mix of two hardware-vendor dashboards plus a manual reconciliation step in spreadsheets. The team described it as "three sources of truth, none of them complete."
The most acute problems they wanted to solve:
- Idle time — drivers were leaving engines running while loading and unloading, particularly at distribution hubs in Sharjah and Abu Dhabi. Fuel was being burned for no operational reason. The operations team estimated this was significant but couldn't put a number on it.
- Route deviations — refrigerated routes are time-critical. Drivers occasionally took longer routes for personal reasons (a stop near home, a detour to refuel at a familiar station), adding 8–15 km per trip. Compounded across 240 vehicles, this was material.
- Reactive temperature alerts — the existing platforms alerted when a refrigeration unit failed. By that point, the cargo was already at risk. There was no predictive signal, no "the compressor's drawing more current than usual, please service before something breaks".
- SIM and connectivity gaps — vehicles regularly went dark for an hour or more on routes outside Dubai. The team had assumed this was unavoidable. It wasn't.
What we deployed
The first decision was to not replace any hardware. The operator had Teltonika units in 180 vehicles and Concox units in the other 60. Standard playbook from their previous vendors would have been to rip and replace. Our playbook is hardware-agnostic — we wrote our protocol parsers to ingest both vendors' data into a single unified stream.
On top of that, we layered:
- A multi-carrier roaming SIM across the existing devices. The previous setup used a single Etisalat SIM per vehicle. We swapped in roaming SIMs that fail over between Etisalat, du, and the broader regional carriers. Connectivity gaps on inter-emirate routes vanished within two weeks.
- Idle-time alerts with thresholds calibrated per route — a 10-minute idle at a distribution hub is normal; a 10-minute idle at a roadside stop is not. The platform learned the difference within the first three weeks of operation.
- Geofence-based route compliance — every approved customer location, refuelling station, and yard was geofenced. Deviations now produce a single coherent alert ("Vehicle 042 took an unapproved 11 km detour to a non-approved stop") instead of dozens of low-signal pings.
- Predictive temperature signals — by combining ambient temperature, compressor load, and door-open events, the platform now flags compressors at risk of failing before they fail. This is the feature that the operations head said genuinely changed how she sleeps at night.
Why hardware-agnostic mattered: The operator had ₹1.4 crore worth of working hardware. Our implementation cost a fraction of what a rip-and-replace from another vendor would have, and went live in 11 days instead of the 90+ days a full hardware swap would have required.
The first 90 days
Three numbers moved the most:
22% fuel cost reduction
Across the 240 vehicles, fuel costs dropped by 22% versus the trailing 90-day baseline. The bulk of this came from idle-time elimination and route compliance, with secondary contributions from coaching three drivers whose individual fuel consumption was significantly above peer.
31% reduction in idle time
The single biggest behavioural shift. Once drivers received a daily summary of their idle minutes versus the fleet median, idle time normalised within four weeks. No conversations from operations were needed for the bottom 80% of drivers — visibility alone changed the behaviour.
11 days from contract to go-live
By keeping the existing hardware and overlaying the platform, the deployment took just over a week of integration work plus a four-day driver onboarding window. The operator had expected a quarter; they got a fortnight.
What surprised us
Two things, mostly:
The drivers didn't hate it. Going in, we expected pushback on monitoring. The opposite happened. The drivers liked seeing their own scores and many started gaming the system in a healthy way — competing on fuel efficiency, sharing tips. Three months in, the operator's top-performing driver has voluntarily started running an internal coaching session for newer drivers. That outcome wasn't in our brief.
The predictive temperature alerts paid for the platform on a single incident. Six weeks in, the system flagged a compressor on Vehicle 187 as drawing 14% more current than its peer group. The operations team scheduled a service. The compressor was found to have a slowly leaking refrigerant line that would have failed within days. The cargo on that route was a pharmaceutical shipment worth more than the operator's annual ViaLoop spend. They have not stopped telling that story.
Where they are now
Six months in, the operator has expanded ViaLoop Fleet to a second fleet of 80 dry-goods vehicles in Saudi Arabia. They're currently piloting our driver-facing app in their Dubai hub, focused on a smoother handoff between operations and drivers. Their CEO has agreed to a named case study in 2026 once the second region is fully running.
Until then, the numbers above stand on their own.
Editor's note: The customer in this case study has approved publication on an anonymised basis pending wider rollout. Specific numbers have been verified by the customer's operations team and are accurate as of Q2 2026.