IoT Telematics for Last-Mile EV Delivery Fleets
Route compliance, SOC-aware dispatch, multi-shift duty tracking, and overheating protection for E2W and E3W fleets that run hard and cannot afford to stop.
Last-mile delivery is the hardest duty an EV can face. A single E2W or E3W might run three shifts a day, change riders at every handover, carry heavy loads through stop-and-go traffic, and get fast-charged in whatever minutes exist between dispatch waves. Every one of those behaviours abuses the battery and the vehicle.
For the fleet operator the problem is that the abuse is invisible. Is the vehicle actually on its assigned route or parked for personal errands? Is the battery about to die mid-trip because it was dispatched too low? Is that pack overheating under the third shift of the day? Without telemetry, the operator only finds out when a trip strands a rider and a customer waits.
VoltZIQ connects the delivery vehicle end to end. Our 4G LTE Cat-1 telematics device reads the BMS over CAN and RS485, reporting SOC, SOH, cell temperatures, and faults, and streams GPS position and duty data to the cloud, where each vehicle's route compliance, battery state, and maintenance needs are visible live.
Why last-mile EV fleets strand trips and burn through batteries
The first problem is hard, multi-shift duty. Delivery E2Ws and E3Ws are pushed far beyond commuter duty, with several riders per vehicle in a single day and little time between shifts. Each rider treats the battery differently, and the combined abuse — fast acceleration, heavy loads, rapid charging — takes a toll no single operator can see from a logbook.
The second problem is route and usage verification. Operators cannot tell whether a vehicle is on its assigned route, sitting idle, or being used for something else entirely. Without GPS-based route compliance, a dispatched vehicle doing personal trips looks the same as one doing its job, and operational planning is built on assumptions.
The third problem is SOC and cold-start failure. Range is the single point of failure in last-mile EV delivery, and dispatching a vehicle with too little state of charge, or one that cold-starts poorly in the morning, strands a rider mid-trip exactly when delivery deadlines are tightest. The operator learns about it from an angry customer, not from the data.
The fourth problem is battery overheating. Aggressive multi-shift duty with repeated fast charging drives pack temperatures up, and chronic heat is the fastest killer of lithium cells. Without cell-temperature telemetry, a pack cooks silently until capacity collapse or a protective shutdown happens mid-route.
And finally, there is no way to bill utilization or plan maintenance per vehicle. One vehicle in the fleet may be doing triple the real work of another, but a flat maintenance and billing model treats them identically. Without per-vehicle utilization and health data, the operator under-bills the heavy units and under-serviced the tired ones.
The VoltZIQ approach to last-mile EV delivery
It starts with the vehicle under continuous watch. The VoltZIQ telematics device reads the BMS over CAN 2.0B and RS485, reporting SOC, SOH, cell voltages, temperatures, and fault codes, alongside GPS position, on 4G LTE Cat-1 with NB-IoT fallback across the delivery area.
Route compliance becomes objective. Each vehicle reports its live position against the planned dispatch, with up to 50 geofence zones per device flagging vehicles that leave their route, idle beyond thresholds, or stop at unauthorized locations. Operators see the whole fleet on the fleet tracker dashboard in real time.
Dispatch becomes SOC-aware. With SOC, temperature, and health streams from the platform, the operator can hold a vehicle back from a long route when its state of charge is too low or its pack is cold-starting poorly, and route delivery demand to the vehicles that can actually complete the trip.
Overheating is caught before it cooks the pack. Cell-temperature telemetry and configurable alert thresholds flag packs running hot under multi-shift duty, so the operator can rotate a vehicle to charging, reduce its load, or take it for maintenance before thermal degrades the cells and strands a shift.
Finally, utilization and maintenance get per-vehicle. Alert types cover over-temp, over-voltage, geofence, tamper, and low SOC, and the alerts center plus battery health dashboards support triage, while the REST API and webhooks feed usage and health records into billing and maintenance planning for each vehicle in the fleet.
What You Get in the Build
Live Fleet Tracking
Every E2W and E3W sits on the fleet tracker dashboard with real-time position, route, and duty status streamed over 4G LTE Cat-1 with NB-IoT fallback.
Route Compliance Geo-Fencing
Up to 50 geofence zones per vehicle flag vehicles that leave assigned routes, idle too long, or stop at unauthorized locations, in real time.
SOC & Battery Monitoring
CAN 2.0B and RS485 BMS readout of SOC, SOH, cell voltages, and temperatures, so every dispatch decision is backed by real pack state.
Overheat Detection & Alerts
Cell-temperature telemetry trips configurable alarms under aggressive multi-shift duty, catching thermal abuse before it cooks the pack.
Utilization & Duty Tracking
Per-vehicle usage, idle time, and route data quantify how hard each unit works, so you can bill utilization and plan maintenance accurately.
Smart Alerting
Over-temp, over-voltage, geofence, tamper, and low-SOC alerts are evaluated on-device and pushed within seconds to dashboard and webhooks.
API / Webhooks Integration
REST, MQTT, and WebSocket APIs over TLS 1.3 plus webhooks feed vehicle and battery data straight into dispatch and billing systems.
OTA Updates with Rollback
Firmware updates reach every vehicle over the air with rollback safety, keeping dispatch and protection logic current without downtime.
The Bottom-Line Benefits
Fewer Stranded Trips
SOC-aware dispatch and cold-start visibility keep riders from leaving on battery state that will not finish the route.
Less Downtime Per Vehicle
Faults and battery alarms surface early, so maintenance happens on a schedule, not after a mid-route failure.
Longer Battery Service Life
Overheat and deep-discharge protection slow thermal and cycle degradation across hard multi-shift duty.
Accurate Utilization Billing
Per-vehicle usage and route records let you bill delivery demand fairly and plan fleet size from evidence.
Verified Route Compliance
Objective geofence and position data confirm vehicles stay on route, cutting misuse and improving SLA reporting.
Faster Maintenance Triage
Multi-role dashboards route each fault to the right team, shortening diagnosis and keeping vehicles in dispatch.
Questions We Get From Engineers
The device uses 4G LTE Cat-1 with NB-IoT fallback, giving better low-signal and indoor reach than older 3G trackers. It carries both eSIM and a physical nano-SIM, and even where data drops inside a depot, GPS still reports and telemetry is buffered and uploaded when the link returns.
The platform streams live SOC and temperature for every vehicle, and your dispatch team can gate route assignment on that state. Route planners can hold a low-SOC or cold-starting vehicle from a long route, and webhooks push SOC into your dispatch system so decisions happen automatically.
Yes. The platform exposes REST, MQTT, and WebSocket APIs over TLS 1.3 plus webhooks, so utilization, route, SOC, and battery events can feed into your dispatch queue and billing engine. We can also self-host the backend for operators with strict data policies.
The telematics device reads the vehicle and BMS over CAN 2.0B and RS485. We map the CAN IDs and register layouts of your specific BMS and controller, then report SOC, SOH, cell voltages, temperatures, and faults, without forcing you to replace existing electronics.
Reporting intervals are configurable from 1 to 60 seconds, and alert conditions like over-temp, low SOC, geofence, and tamper are evaluated on-device and pushed over 4G. Critical events typically reach the dashboard and webhooks within seconds of happening.
Yes. Most operators start with a single depot or route and a handful of vehicles to validate coverage, dispatch integration, and alerting before scaling. Send an RFQ with your vehicle type, BMS vendor, and fleet size, and our team will respond with a pilot plan within 24 business hours.
Run Every Delivery Shift With Data
Send us your vehicle type, BMS vendor, and dispatch setup — our engineering team will respond with a pilot plan and pricing within 24 business hours, so your last-mile fleet runs on telemetry, not guesswork.