Choosing a System
The questions that separate products in this market, which are all about what the device reads and what the platform lets you export.
Buying · Procedure
Every telematics product shows vehicles on a map. They differ in what else they can read and what you can do with it afterwards.
The data questions
Which parameters does the device read from this vehicle model, by name? Ask for the field list, not a category.
Is fuel consumption read from the engine or estimated from distance?
Are manufacturer-specific fault codes available, or generic only?
Is the odometer read from the vehicle or calculated?
Does it read state of charge and battery health on electric vehicles?
A vendor who cannot answer these per model is selling a map.
The platform questions
Can raw data be exported, in a documented format, on a schedule?
Is there an API, with a specification rather than a mention?
Can it integrate with a maintenance system, a fuel card provider, a finance system?
What is the data retention, and does it meet your compliance obligations — which are frequently longer than the default.
The configuration questions
Can alerts be tuned per vehicle type, or is there one threshold for the fleet?
Can driver-related features be switched off entirely? Which matters if your deployment is asset-focused and you want it to stay that way.
Can reports be produced per vehicle, per model and per site without exporting to a spreadsheet every time?
The trial
On your worst vehicles, not your newest.
An old van, a mixed-brand pair, and an electric vehicle if you have one.
Compare the reported odometer against the dashboard, by hand, weekly.
Compare reported consumption against a full tank.
Raise a fault deliberately if you safely can, and see what arrives and when.
Red flags
A field list that is the same for every vehicle model, which means it is a specification rather than a measurement.
Driver scoring as the headline feature in an asset-focused purchase.
No export, or export only as a report.
Retention shorter than your compliance obligation, with no answer about extending it.
The contract
Data ownership and export on termination, specified now.
Notification before firmware changes that alter what is read.
Device replacement terms, because failures are a routine cost and who bears them is a real number over a fleet.
Trial on the worst vehicles
Not the newest.
An old van, a mixed-brand pair, and an electric vehicle if you have one.
A product that works on your newest vehicle tells you nothing; one that works on the ten-year-old tells you what the rollout will actually be like.
And that is where the field list differences show up, which no demonstration will surface.
Follow the difficult record
Use workforce software pricing options to frame one representative case. The useful evidence is the record created when a value is corrected, approved and exported.