What does the tachograph obligation actually require?
Driver cards and vehicle unit data must be downloaded at defined intervals and retained for the period set by the regulation, and drivers hours must be monitored against the limits in Regulation 561/2006 on driving time, breaks and rest periods.
Remote download is what makes this practical at scale: without it, cards are physically collected on a schedule, and a vehicle that stays on the road is a compliance gap. Every platform on this list that claims tachograph support should be asked to demonstrate remote download specifically.
Infringement reporting matters too — knowing that a driver is approaching a limit is more useful than learning afterwards that they exceeded one.
Why do American fleet platforms not cover this?
Because they were built for a different regime. The US ELD mandate and hours-of-service rules have their own definitions, thresholds and record formats, and a platform architected around them does not incidentally satisfy European requirements.
Some US vendors offer European modules. The question to ask is whether remote tachograph download is included, whether drivers hours analysis follows 561/2006 rather than a translation of the US rules, and how long the archive is retained.
The consequence of getting this wrong is not a poor user experience; it is a failed inspection, which is a different category of problem.
What else should be in the contract?
Contract length and exit terms, because this category sells multi-year deals with hardware bundled. Establish what happens to the devices at the end and what the data export looks like.
Installation: who fits the hardware, in which countries, and what CAN bus work is needed for fuel and engine data. This is physical work across a dispersed fleet and it is routinely underestimated.
And the works council position, which in Germany, Austria and the Netherlands should be agreed before installation rather than after. Purpose, retention and who can see live positions are the points that matter.