GPS tracking in Lobamba

Start with Lobamba service vans, Mbabane hill returns, and siSwati label checks, then connect each tracker by its IMEI, followed by the model check and the SIM.

sugar estate mileage, Eswatini finance approver, and valley rain detours are review inputs; they do not promise install path, stock, or network availability.

Plan cost comes after clinic route sheets, when payment contact and priority vehicles are known.

Review royal compound access, useful geofences, and abnormal journeys before adding more vehicles.

Document the normal day in plain operational language: Lobamba service vans starts the shift, Mbabane hill returns explains the planned movement, siSwati label checks names the vehicle group, and sugar estate mileage shows where timing breaks down. Add Eswatini finance approver for employee notice, border post errands for the service window, clinic route sheets for billing ownership, and royal compound access for the first export recipient. Keep Manzini depot loops, estate gate queues, school term pickups, and valley rain detours as supporting notes so the first dashboard stays about real vehicles, not a broad market assumption.

Read the first export against the buyer's own labels. Lobamba service vans should show start time and return time; sugar estate mileage should show delay reason; border post errands should show whether the stop was planned; Manzini depot loops should show the zone name; estate gate queues should show recurring movement; school term pickups should show who approved the exception; valley rain detours should show whether the same issue repeats. If those fields are missing, collect them before adding more vehicles.