The Questions Worth Asking a Fleet Tracking Vendor

A per-vehicle monthly rate is the number every vendor leads with, and it is the least useful one for comparing two proposals. Multiply it by the term, add the hardware if it is billed separately, add installation if that is extra, and compare those totals instead. Two quotes a dollar apart per vehicle can be thousands apart over three years once the hardware line is in.

Then ask the question most buyers skip: what happens if we end early. Some contracts pro-rate the remainder. Others make the full term payable regardless of when you leave, which is the trade for hardware and installation being included rather than invoiced. Neither is wrong, but you should know which one you are signing, and you should be told before the paperwork rather than in it.

This is the question that catches vendors out on cross-border fleets. In the United States, ELD manufacturers self-certify their devices with FMCSA. In Canada, a device must be certified by an accredited third-party body against the CCMTA Technical Standard. They are different bars, and a device legal on one side of the border is not automatically legal on the other.

If any of your vehicles cross, ask for the certification specifically rather than a reassurance that the device is compliant. Compliant where is the actual question, and a vendor who answers it precisely is telling you something useful about the rest of their answers.

Most telematics agreements renew automatically at the end of the term unless something else is agreed. That is normal and not sinister, but it means the moment to renegotiate is before the term ends, not after, and the notice required is set out in the agreement rather than assumed.

Ask how much notice, ask whether the rate changes on renewal, and ask what happens to the hardware if you leave. A vendor who has thought about the end of the relationship is usually one who expects to still be there for it.

Fleet software stops being a standalone purchase the moment it needs to talk to fuel cards, dispatch software, payroll or a maintenance system. Ask whether there is a documented API, whether the vendor charges for access to it, and whether the data you generate can be exported in a usable form if you leave.

The answer tells you how much of a decision this really is. A closed platform makes the second decision, three years from now, considerably more expensive than the first one.

Most light and medium-duty vehicles with a standard diagnostic port are genuinely plug-and-play: the device seats in the port and starts reporting, no technician required. Fleets rarely consist only of those vehicles. Heavy trucks, older equipment, trailers with no power and machines with no diagnostic port at all need a different answer.

So ask specifically about the awkward ones, and ask whether that work is included or quoted separately. A vendor who says every install is simple has either not seen your fleet or is not telling you the part you will find out about later.

Every vendor is attentive during a sale. The question is what the relationship looks like once the fleet is live and the account is no longer new: who answers the phone, whether they know your account, whether they are in a time zone that overlaps your working day, and what happens when a device fails.

If hardware is included in the rate rather than sold to you, a failure should be a support call and not a warranty claim on equipment you own. That difference is worth confirming in advance, because it decides how a bad day actually goes.

Case studies are written by the vendor. A phone call with a fleet of roughly your size, running roughly your duty cycle, is not. Ask for one, and treat reluctance as information.

The useful questions for that call are the unglamorous ones: what broke, how long support took to fix it, and whether the rollout took as long as they were told it would.