What leaves the building
The hardware is the cheap part and the least interesting part. What matters is where the data lands and what raises a phone call.
The same tracker does two different jobs depending on which vehicle it is in, and operators who conflate them buy the wrong thing.
In a delivery van it is an operations tool. Live position on the same map as the run, with idle, hard braking and speeding raised to the office while the morning is still running.
In a cart, an LSV, a scooter, a car or a trailer that leaves with a customer, it is asset protection. A boundary drawn around where that rental is allowed to go, and an alert when it crosses.
Same hardware, same integration, different question being answered. Delivery vehicle tracking and vehicle tracking are separate pages here for that reason.
An OBD unit runs around $20 to buy and about $70 a year to keep reporting. Against the value of a plated low speed vehicle or a cart, that is small enough that the arithmetic is rarely the blocker.
What decides it is where the data lands. A tracker reporting into its own portal means somebody has to keep a second tab open and correlate it by hand against the run and the reservation, which is work nobody does on a busy Saturday.
Reporting into the same system that holds the unit record and the booking is what makes it operational rather than forensic.
Draw the boundary around where a rental is allowed: a plantation gate, an island, a county line, or the streets an LSV is plated for. Set it per unit or across a fleet.
A crossing raises an out-of-zone alert to the office with the vehicle, the renter and the time on it. That alert is the whole window in which a problem is still cheap. A vehicle heading somewhere it was never rented to go is recoverable at the moment it crosses the line and expensive by the evening.
The measure worth watching is out-of-zone events caught while the vehicle is still easy to reach, and the hours between the alert and the recovery.
Out on hire
Alerts
Three carts are out on hire, each one reporting into the record that holds the reservation it went out on. All three are inside the zone.
Position on the same map as the stops means completed stops leave the screen as they close. Anything still showing behind the vehicle is a stop the driver has gone past without closing it.
The office can screenshot that and text the driver while the van is still on the road, which is the difference between a five-minute detour and a refund. Nobody knows where the van is covers what that changes on a Saturday.
Open stops 6
Alerts
Van 1 leaves the depot with six stops in the order the run was built. Everything on the map is open work.
It does not stop a vehicle. There is no remote immobiliser and no engine cut-off, and nothing in the platform can bring a vehicle back on its own.
It is a fixed integration rather than an open device list. One supported unit, chosen so the data arriving is the same shape every time, in the same way card processing runs through one processor. Trackers you already own will not report into it.
It is not a driver scorecard, a payroll timeclock or an hours-of-service compliance system, and it makes no claim to be one.
And telling renters that a vehicle is tracked, and meeting whatever your jurisdiction requires about disclosure and consent, sits with you. The platform stores the data and gives no legal advice.
The guest-facing view, where a customer watches how many stops away the van is, does not exist yet and has no published date.
It is the strongest thing on this subject for a last-minute booking, which is exactly why it is worth building rather than claiming early. Treat it as absent from what you would be buying today.
Around $20 to buy an OBD unit and about $70 a year to keep it reporting. The cost is rarely the deciding factor against the value of a cart or a plated low speed vehicle; what decides it is whether the data lands in the same system as the unit record and the booking, or in a separate portal somebody has to correlate by hand.
In a delivery van it gives live position on the same map as the run with idle, braking and speeding alerts. In a vehicle that leaves with a customer it gives a boundary and an out-of-zone alert while recovery is still cheap. It cannot immobilise a vehicle, it works with one supported device rather than any tracker, and guest-facing delivery tracking has not shipped.
No. The integration is one supported unit rather than an open device list, so the data arriving is the same shape every time.
No. It reports position and raises boundary alerts. There is no remote immobiliser and no engine cut-off.
That depends on your jurisdiction and it sits with you. The platform stores the data and gives no legal advice about disclosure or consent.
A demo takes six fields and someone who understands rental operations calls you back. Where Bodhisys is the wrong fit you will hear it on that call rather than after three meetings.