Logistics and last-mile delivery
Know which van charged where, on whose account, in which shift
Delivery fleets share vans between drivers and run to shift patterns, from Harare and Bulawayo depots to stops along the routes between them. Getz EMP ties every session to the driver, the card and the vehicle, allows company charging only at your depots and route stops in the hours you set. Finance gets one statement per corporate account; agree how depots map to accounts during setup.
The operations problem
What makes delivery-fleet charging hard to control
Shared vans, rotating drivers
A fuel-card statement says which card paid, not which driver charged which van at which depot.
Charging outside shifts
Without hour rules, company-paid charging at weekends or after hours shows up only at month end.
Top-ups on the route
Drivers need public chargers on the route, but only the ones you approve, and only for company vans.
How Getz EMP handles it
Your operation, mapped to settings
An example configuration for a multi-depot delivery fleet. Every setting is optional.
| Capability | Getz EMP setting |
|---|---|
| Separate spend and managers per depot | One fleet per depot; each fleet manager sees only their own depot’s drivers, vans and sessions |
| Company charging only in shifts | Charging windows per fleet, in your time zone, including overnight (for example 22:00–05:00) |
| Only at depots and approved route stops | Allowed sites or whole networks; any other site is refused at the start |
| No session runs past a van’s battery | A kWh cap per session; the platform stops the session when it is reached |
| Shared vans | An RFID card per van or per driver, blocked from the back office when lost |
| Take-home vans | Measured home sessions reimbursed after approval; the home charger itself is managed through its own platform |
| Events in your dispatch or telematics tool | Signed webhooks per event type, optionally per fleet |
Evidence
The rules your drivers see are the rules the platform enforces
The driver app shows each driver the fleet’s rules in plain words: which account pays, how many sites are approved, the charging hours and the energy cap. A start outside them is refused with the reason before anything begins.
Depot chargers are run by their charge point operator, which decides who may use the depot and looks after power, connectivity and faults. When the depot is published through Getz Hub, it sits on the fleet’s allowed list next to the public sites on your routes, and both land on the same statement.
If a depot loses its connection to the platform, new starts there cannot be authorised until it is back, because every start is checked in real time. Agree with dispatch which approved public sites drivers use instead, so a refused start has a planned next stop. Bay bookings depend on the charger’s operator offering them.
- Policy summary in the app, generated from the enforced policy
- Depot and public sites through Getz Hub
Every driver session in progress, across the charging networks the eMSP roams on.
- What you see: who is charging where, right now
- Why it matters: support can see and stop a session in one place
Questions from logistics operators
Can we see charging per vehicle, not just per driver?
Yes. Fleet vehicles are linked to the fleet, and sessions carry the driver, the token used and, where linked, the vehicle. An RFID card per van makes the vehicle the unit you track.
Can each depot have its own budget?
Yes. Give each depot its own fleet and, where budgets are held separately, its own corporate account and credit limit. Cost centres inside one account are coming soon.
What happens if a depot loses its connection?
Every start is authorised in real time, so depots need a steady connection to the platform. We review connectivity at your depots with you during set-up.
Map your depots and shifts to a fleet policy
Bring your depot list and shift pattern. We configure a demo fleet with them and run a company-paid start inside and outside the rules.