How to choose fleet software: a checklist
May 30, 2026 · Suso Merino · CEO
Most fleet software comparisons floating around online are sponsored listings or generic reviews. They’re of little use when you have to sign a three-year contract for 80 vehicles. This checklist is what we’d ask a provider if we were buying for our own fleet: concrete questions, verifiable answers and red flags that expose the salesperson who’s making it up as they go.
It’s designed for fleet managers at midsize SMBs (10-200 vehicles) and operations directors who have already seen two or three demos and need to tell the providers apart before signing.
Section 1. Hardware: proprietary or standard
The first question is what hardware goes in the vehicle. There are two paths:
- Proprietary hardware: the provider designs its own device, usually manufactured by a third party with the provider’s brand on it. If you switch providers, you throw all the hardware away.
- Standard hardware from a recognized manufacturer (Teltonika, Queclink, Concox): the device is the same one used by dozens of platforms. If you switch providers, in many cases the hardware keeps working.
Questions to ask the sales rep:
- The exact device manufacturer and model. If they hesitate or say “it’s our own,” that’s a red flag.
- Who controls the device firmware: you, the integrator or the manufacturer? It matters for updates and for portability.
- If I cancel after 18 months, can the hardware be used with another provider, or is it useless?
- Does installation require a workshop (concealed wiring), or is it plug-and-play OBD? The difference is 5 minutes vs. 90 minutes per vehicle, and €0 vs. €60 in installation.
For context, we use standard Teltonika hardware (FMM003, FMC003, Eye Beacon, Eye Sensor) precisely so the customer isn’t held hostage by the provider.
Section 2. Real AI vs. AI marketing
“AI” has appeared on every landing page since 2023. The filtering question is: give me a concrete case with metrics. If the answer is generic (“we optimize routes with AI,” “we predict breakdowns with machine learning”) with no numbers and no time horizon, there’s no real AI. It’s probably a rules-based system with a marketing label.
Questions that separate AI from a label:
- What does the model predict, and with what horizon? A valid answer: “battery alert 14-28 days in advance, 78% accuracy.”
- What data was the model trained on? How many vehicles, how many miles/kilometers, how much history?
- How many false-positive alerts does it generate per month in a fleet my size?
- Can you show me a real customer case with concrete savings metrics? (Even if anonymized.)
- Does the AI run on your servers, or do you use third-party APIs (OpenAI, Google)? It matters for cost, latency and data privacy.
There’s a common pattern: “ML” used for if-then rules with adaptive thresholds. It isn’t a lie, but it isn’t what customers understand when they hear AI either. In AI for fleets: real use cases with ROI you’ll find examples of the kind of answer you should expect.
Section 3. Contract: minimum term, cancellation and data ownership
The contract is where lawsuits are lost. The clauses to review with your advisor before signing:
| Aspect | Concrete question | Red flag |
|---|---|---|
| Minimum term | How many months at minimum? | More than 36 months without an aggressive discount |
| Renewal | Automatic or express? Notice period? | Automatic, with 90 days’ notice |
| Early exit | Penalty? What percentage? | 100% of the remaining amount |
| Historical data | When I cancel, do I get a full export? In what format? | “That’s not possible” or “PDF only” |
| Hardware | Do I buy it, lease it, or does it belong to the provider? | Mandatory lease with no purchase option |
| Price increases | How much can it go up per year? | Unlimited CPI-linked increases or “according to the market” |
Exporting your data when you cancel is the most overlooked point and the most painful one later. Any serious provider delivers a full CSV or JSON with the history of positions, events and maintenance. If they say no or charge extra, they’re locking the customer in with the customer’s own data.
Section 4. Support: Spanish, phone, SLA
Support is tested before signing, not after. A technique that works: during the demo phase, call the support line on a Friday at 6:30 p.m. without telling the sales rep. What they answer (or don’t) is what they’ll answer when you lose tracking on 40 vans on a Saturday morning.
Questions:
- Is support available in Spanish? Or in Spanish through an outsourced tier 1 that escalates in English?
- What hours? Ideally Monday to Friday 8 a.m.-8 p.m., with 24/7 on-call coverage for critical incidents.
- Is there a written SLA? A response-time commitment? Compensation if it isn’t met?
- Does support know my industry (refrigerated transport, public works, urban delivery)? A technician who understands your business solves in 10 minutes what takes another two hours.
- Is there a named account manager, or do you go into a shared inbox?
For fleets of more than 50 vehicles, it’s reasonable to require a named account manager in the contract.
Section 5. Integrations: API, webhooks and connectors
A fleet platform cut off from the rest of the company’s software duplicates work and limits ROI. The key questions:
- Is there a public, documented REST API? Ask for access to the documentation during the demo. If they won’t show it, be suspicious.
- Are there webhooks for key events (geofence entry/exit, maintenance alert, end of route)?
- Are there native connectors for the ERPs I use (SAP, Microsoft Dynamics, Odoo, Sage, A3)?
- Is there a TMS connector if I work in logistics?
- If I need a custom integration, does the provider build it, a partner, or do I have to hire a third party?
Ask for examples of customers who have integrated what you want to integrate. If all their customers use the system in isolation, get ready to do the same.
Section 6. Compliance: GDPR, EU servers, ENS if applicable
Any serious provider in Spain has this covered, but it’s worth confirming in writing before signing:
- A signed GDPR data processing agreement between your company and the provider. It’s mandatory when the provider processes personal data (driver location, identification by card or beacon).
- Servers in the European Union. Ideally in Spain or in a certified European data center (Frankfurt, Dublin, Madrid, Barcelona).
- ISO 27001 certification for the provider or for the cloud provider it uses.
- If you sell to the public sector, Spain’s National Security Framework (ENS, Esquema Nacional de Seguridad) at medium or high category. Without it, you can’t bid in public tenders. More on this in the context of the public sector.
- A clear data retention policy: how long do they keep historical positions? Can you export and delete them on demand?
Section 7. The demo: with your real case, not a canned one
The most common trap. The sales rep brings a slick demo with perfect data on a big screen and everything runs smoothly. Your fleet’s reality is different. How to avoid the trap:
- Ask for a demo with two or three of your real vehicles for 7-15 days. Any serious provider will agree. If not, be suspicious.
- Define three concrete scenarios you need to validate before the demo. For example: “I want to see a geofence exit alert reaching the manager’s phone,” “I want to see a weekly scoring report by driver,” “I want to see a real OBD fuel reading compared with the refueling invoice.”
- Ask for access to the real dashboard, not just screenshots. Let your team log in and poke around.
- Measure the latency of the mobile app and the web dashboard when loaded with your data. If it takes more than 4 seconds to open the fleet map, double that for when you have 80 vehicles.
- Ask how long it takes to export a monthly report for the whole fleet. If it takes more than 30 seconds, there’s an architecture problem.
Summary table of deal-breakers
These are the criteria that rule out a provider without having to move the negotiation forward:
| Filter | If the answer is… | Rule out |
|---|---|---|
| Proprietary hardware with no alternative | “Only our device; it can’t be changed” | Yes |
| Minimum term + automatic renewal + long notice | “36 months, automatic annual renewal, 90 days’ notice” | Yes |
| No data export on cancellation | “The history stays on our platform” | Yes |
| Email-only support | “Tickets via the portal, no phone” | Yes, for critical fleets |
| No EU servers | “AWS US-East,” with no further nuance | Yes, in regulated industries |
| No documented API | “We build the integration ourselves, on a quote basis” | Yes, if you need to integrate |
Related comparisons
If you’re evaluating specific providers, we’ve published dedicated analyses:
Both follow the same methodology as this checklist and go into detail on pricing and real, measured functionality.
Conclusion
Choosing fleet software is a 3- to 5-year decision. The right questions during the evaluation phase save you from abusive contracts, locked-in hardware and support that doesn’t answer later on. The checklist doesn’t guarantee you’ll get it right, but it does eliminate the 60% of options that don’t pass the basic filter.
If you’d like a Trackia demo with real vehicles from your fleet for 15 days, with no commitment and full access to the dashboard, request it here and we’ll activate it within 48 hours. And if you’re clear on the model and want to go straight to a quote, our price ranges are published on the pricing page.