Deliveries and distribution
Delivery fleets, and the record of what happened
We have been fitting and running tracking on Maltese delivery fleets since 2010, first as DP:Tracking and now as Yipii. Over that time the questions have stayed much the same. Where is the van, how long did it sit at that stop, who was driving it, and can we show a customer the record when they say the delivery never arrived.
Prefer the main Yipii pages?
Who this is for
- Distribution businesses running multi-drop routes
- Wholesalers delivering to trade customers
- Courier and last-mile operators
- Groups running deliveries alongside other vehicle work
Stops and the time spent at them
Every trip breaks into stops with arrival time, departure time and duration. On a multi-drop round, that record is what tells you whether a route is genuinely full or simply slow. Where a customer disputes a delivery, the arrival and departure times at their address settle it without an argument.
- Arrival, departure and dwell time per stop
- Full trip breakdown per vehicle per day
- Route playback for any date within the retention period
- Position history retained for the contracted period
Geofences at customer sites
A geofence around a depot, a customer site or a delivery zone records entry and exit automatically. Over a period, that produces a time-at-customer record that is useful for route planning and for the conversations that follow a service complaint.
- Geofence per depot, customer site or zone
- Automatic entry and exit logging
- Alerts on departure from the depot and arrival at key accounts
Who was driving
Where several drivers share a vehicle across shifts, driver identification attributes each trip correctly. Drivers identify by RFID card, iButton, BLE tag or the app. Reports then break down by driver rather than only by vehicle, which is what makes driver behaviour figures worth anything.
- RFID, iButton, BLE tag or app identification
- Trips and behaviour reported per driver
- Shift-based reporting for shared vehicles
The running costs underneath
On hardwired installs with a CAN connection, fuel consumption, fault codes and engine temperatures come through alongside position. Combined with idle time, that is where the recoverable cost in a delivery operation usually sits. Maintenance scheduling against distance or engine hours keeps vehicles out of unplanned downtime, which on a delivery round costs more than the repair.
- Fuel and engine data on CAN bus installs
- Idle time against working time per vehicle and per driver
- Maintenance scheduling by distance, engine hours or date
- Work orders and service history per vehicle
When Yipii is not the right fit
Cases where you should look at something else, or budget for a second system alongside this one.
- A route optimisation engine is what you need. Yipii records what the route did and exposes it by API. It does not plan or sequence drops for you.
- Electronic proof of delivery with signatures and photographs is required. That is a separate class of product, though trip and geofence records do evidence vehicle presence and timing.
- You want customer-facing delivery ETAs sent automatically. Public link sharing gives live vehicle visibility through a shared link, but it is not an automated ETA notification service.
Questions
- Can we see how long a van spent at each delivery stop?
- Yes. Every trip breaks into stops with arrival time, departure time and dwell duration, and the full route can be played back for any date within your retention period.
- Can trips be attributed to the driver rather than the vehicle?
- Yes, where driver identification is fitted. Drivers identify by RFID card, iButton, BLE tag or the app, and reporting then breaks down per driver across shared vehicles.
- Does Yipii provide proof of delivery?
- Not as signatures or photographs. What the platform provides is the vehicle record: arrival and departure times at a geofenced customer site, and full route playback. That evidences vehicle presence and timing, which resolves most delivery disputes.
- We already run tracking from another provider. How hard is it to move?
- We handle the changeover. Plug-and-play devices arrive configured and can be live the same day. Hardwired fleets are scheduled with our own auto-electricians, so the timeline depends on fleet size and install type. We have been carrying out migrations in Malta since 2010.
Talk to us about your delivery fleet
Yipii Ltd has provided vehicle tracking and fleet telematics in Malta since 2010, previously as Dazzle Panel and DP:Tracking. The platform, alerts and tracking run 24/7. Human support is available during business hours.
Written and maintained by the Yipii team, Malta.