For your fleet
Choose your setup path
Check tracker compatibility and the plan before you activate vehicles.
Buyer file fit
Clinic route sheets keep SZL billing contact, dashboard ownership, and first vehicles separate from device questions.
Account
- Name the buyer file owner, export recipient, approval currency, and first vehicle group.
- Keep plan cost separate from GPS unit model, SIM state, and field-service questions.
GPS-unit proof
Lobamba service vans, sugar estate mileage, and Manzini depot loops give support enough context to review model fit and SIM status.
Tracker
- Attach odometer photo, current provider, GPS unit protocol, and employee-notice language.
- Use Eswatini finance approver to avoid mixing dashboard labels with legal or HR advice.
Exports to inspect
Mbabane hill returns, siSwati label checks, and estate gate queues should become journeys, geofences, export labels, or exception notes after activation.
Reports
- Review trip history, geo-zone alerts, and activity exports before expanding the fleet.
- Use border post errands and royal compound access to spot recurring stops, delays, and exceptions.
Before you connect
Before you connect, note school term pickups and valley rain detours so you can compare them with trip history once your trackers report.
Checklist
- Have each tracker's IMEI and SIM ready. Traxelio checks the model from the IMEI.
- If you already own trackers, connect them before you compare the software plan.
Operating context
Common Challenges
-
Buyer file scope
Eswatini buyers should name the billing contact, dashboard language, and first vehicle group before plan cost review starts.
-
Lobamba records
Keep sugar estate mileage, Eswatini finance approver, and border post errands attached to vehicle records so support can read the operating pattern.
-
Support limit
Traxelio can review software fit and existing GPS-unit proof; local stock, install path, and carrier network availability remain unconfirmed.
Traxelio Solutions
-
SZL buyer-file check
Use clinic route sheets and royal compound access to decide who owns billing, who receives exports, and which vehicles should appear first.
-
GPS-unit proof
Send GPS unit model, SIM state, odometer photo, and current provider beside Lobamba service vans, sugar estate mileage, and Manzini depot loops before activation.
-
Exports to inspect
Map Mbabane hill returns, siSwati label checks, and estate gate queues to trip history, geofences, and activity exports after the buyer file is configured.
Cities
GPS Tracking in the cities of Eswatini
Find GPS tracking services in the major cities of Eswatini.
FAQ
Frequently asked questions
Start with Lobamba service vans, Mbabane hill returns, and siSwati label checks. Those records make the buyer file question concrete before device stock or install path is discussed.
Connect each tracker by IMEI; Traxelio checks the model, then you check the SIM. Plan employee notice before your trackers start reporting.
Compare plan cost after clinic route sheets confirms the buyer, approval currency, export recipient, and first vehicle group.
Keep royal compound access, school term pickups, and valley rain detours as notes for naming zones and reading trip history. They do not confirm network availability or emergency service.
Use sugar estate mileage for route exceptions, border post errands for service windows, and estate gate queues for recurring stops before reading activity exports.
Name geofences from real operating labels such as Manzini depot loops, school term pickups, and valley rain detours, then keep alert thresholds separate from payroll or discipline decisions.
Traxelio can review buyer file activation, GPS unit compatibility, trip history, geo-zone alerts, and export recipients once your trackers are connected.
For Eswatini, connecting first shows whether Traxelio recognizes the tracker you already own: enter its IMEI, Traxelio checks the model, then you check the SIM.
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 activation conversation 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.
Each local detail here names your own records; none of them is a service promise. siSwati label checks and Eswatini finance approver help name the dashboard and notice language, but they do not create legal advice. Clinic route sheets and royal compound access help name billing contact and export owners, but they do not promise local support. Manzini depot loops, estate gate queues, school term pickups, and valley rain detours help you read routes once your trackers are connected.
Tracking employee vehicles? See if GPS tracking is legal for employee vehicles
Ready to track your fleet in Eswatini?
Connect the GPS tracker you already own, or check GPS tracker availability.