Telematics is the most commoditised part of the fleet software stack and the most heavily contracted. Devices are cheap, the data is broadly similar between vendors, and the differentiation is in depth, integration and the terms you sign.
Decide what you are buying it for
Telematics is bought for four different reasons, and they lead to different products:
| Purpose | What matters | What does not |
|---|---|---|
| Vehicle location and dispatch | Update frequency, map quality, geofencing | Engine data depth |
| Maintenance and utilisation | Odometer accuracy, engine hours, fault codes | Second-by-second tracking |
| Driver safety | Behaviour events, video, coaching workflow | Deep diagnostics |
| Cost control and compliance | Fuel data, idling, hours records, reporting | Real-time visibility |
Buying a safety-focused platform when your problem is maintenance scheduling produces an expensive system that does not solve your problem. Write down your top two purposes before you take a demo.
'We support all vehicles' means the device fits. It does not mean you get engine data.
Device types
OBD-II plug-in. Fits the diagnostic port on light vehicles. Self-install in seconds, easy to move between vehicles, and easy to unplug — which is either a feature or a control problem depending on your view. Limited data depth on some vehicles.
Hardwired. Professionally installed, tamper-resistant, more reliable power, access to more vehicle data. Standard for commercial vehicles and for anything where unplugging matters.
Heavy-vehicle bus connection (J1939/J1708). For trucks and buses, giving access to a much richer data set: fuel consumption, engine load, fault codes, PTO usage.
Camera-integrated units. Combine tracking with road-facing and optionally driver-facing video. See video telematics.
Battery-powered asset trackers. For trailers, plant and containers with no power source. Reporting frequency is traded against battery life, typically measured in years.
Smartphone-only telematics. No hardware, uses the driver's phone. Cheap and easy to start, but data quality depends on the phone being on, charged and carried, so it suits light-duty and grey-fleet use rather than core operations.
See OBD versus hardwired for the detailed comparison.
The data hierarchy
Ask vendors precisely which of these they provide for your vehicle makes and models, not in general:
- Position, speed, heading — every product has this.
- Trip start and end, idling — nearly all.
- Odometer from the vehicle rather than derived from GPS distance. Materially more accurate, and the basis of good maintenance scheduling.
- Engine hours — essential for plant and for hour-based servicing.
- Fuel level and consumption from the vehicle bus — much better than fuel card inference.
- Fault codes (DTCs) with descriptions.
- Seat belt, harsh events, cornering for behaviour programmes.
- PTO, tail lift, door sensors, temperature via inputs or CAN.
- EV-specific data — state of charge, charging sessions, regenerative braking.
Vehicle coverage varies enormously by make, model year and market. Insist on a written coverage statement for your actual fleet composition before signing.
Contract traps
Telematics contracts are where fleets get caught, more than in any other fleet software category.
- Term length. 36–60 months is common, often with hardware bundled. Understand the early termination charge before signing.
- Per-device pricing after a rate change. Confirm whether adding vehicles mid-term is at the original rate.
- Hardware ownership. Do you own the devices at term end, or are they rented? If rented, what is the return condition and cost?
- Installation and de-installation costs, particularly when disposing of vehicles.
- Data ownership and export. Can you extract full historical data, in what format, at what cost, and does that right survive termination?
- SIM and connectivity charges, including roaming for cross-border operation.
- Auto-renewal clauses with short notice windows. Diarise the notice date the day you sign.
- Feature tier changes. Vendors reorganise packages; confirm your features are contractually fixed, not "current package contents".
Integration requirements
Telematics is rarely the end point; the data has value once it reaches your other systems.
- Fleet maintenance system — automatic odometer and engine hours are the single highest-value integration.
- Route and dispatch — actual arrival and departure times, feeding service time models.
- Payroll or HR — hours, where the operation uses telematics for time recording (and where employment law permits).
- Fuel card systems — cross-checking transactions against vehicle position, which detects both fraud and card misuse.
- Your own analytics — via API or data feed.
Confirm the API is documented and accessible, not "available on request via professional services".
Evaluating properly
- Pilot on 10–20 vehicles across your different vehicle types, for at least four weeks.
- Verify odometer accuracy against physical readings on a sample.
- Check reporting frequency in poor coverage areas of your operation.
- Test the integration you care about most, in the pilot, not as a promise.
- Assess the admin experience: adding a vehicle, moving a device, reassigning a driver.
- Involve drivers and be transparent about what is recorded. See driver privacy.
- Compute the three-year total cost, including installation, removal, SIMs and uplifts.
Frequently asked questions
How much does fleet telematics cost?
Entry-level tracking is typically in the low tens of dollars or euros per vehicle per month, with hardware sometimes bundled and sometimes charged separately. Video telematics, advanced safety features and heavy-vehicle diagnostics push costs substantially higher. Always compare on three-year total cost including hardware and installation.
What return should we expect?
The measurable returns usually come from idling reduction, fuel efficiency, better maintenance scheduling and reduced insurance claims. The size depends heavily on your starting point — a fleet with no visibility at all typically sees larger and faster gains than one already managing these areas.
Do drivers need to be told they are tracked?
Yes, and in many jurisdictions it is a legal requirement with specific transparency obligations, and sometimes formal consultation. Beyond legality, covert tracking destroys trust and reliably backfires. Publish a clear policy and explain the purposes.
Should we buy telematics from our fleet software vendor?
A native module removes integration risk, but bundled telematics is sometimes weaker than a specialist product. If a specialist wins on capability, confirm the integration with your fleet platform is a supported feature rather than a project you will own.
What happens when we change telematics providers?
Devices generally do not transfer between vendors, so migration means removal, installation and reconfiguration across the fleet, plus historical data extraction. This switching cost is precisely why contract terms and data export rights deserve attention at signature.
