Fitting ten vehicles with a GPS tracker is a purchase. Equipping fifty, a hundred or several hundred vehicles spread across several cities is a project: it involves management, fleet managers, finance, IT and drivers. This guide helps you ask the right questions before you sign.
In short: for a large fleet in Morocco, choose fleet management software that handles multiple sites and access levels, a supplier able to install with its own team in all your cities, exportable data hosted under a clear framework, a possible link to your ERP or TMS, and a budget based on the full cost rather than the price of the device.
What criteria matter for a large fleet?
Beyond a few dozen vehicles, needs change. The live map is still useful, but it is no longer what makes the difference. What matters:
- Organisation by site and group. Management needs to see the whole fleet; each branch manager only their own vehicles. Check how access rights are assigned and how easy they are to change.
- Reports. With a hundred vehicles, nobody looks at the map one vehicle at a time. You need clear summaries: kilometres, idle time, fuel, alerts, by site and period, exportable to PDF or Excel.
- Sensors. Depending on your business: fuel probe, temperature for refrigerated transport, door sensors, CAN bus reading for vehicle data. Choose hardware that can take them from day one.
- Ease of use in the field. A tool that only two people at head office know how to use will not be used. Test it with your fleet managers, not just with management.
- Support. At this size, there will always be a vehicle down, a device to move, a user to create. Response and on-site intervention times count as much as the software.
What questions should you ask the supplier?
The table below works as a comparison grid. Ask every supplier the same questions and request written answers.
| Criterion | Why it matters | Question to ask |
|---|---|---|
| Installation | Poor fitting means wrong data or breakdowns | Who installs: your own technicians or a subcontractor? How many vehicles per day? |
| Geographic coverage | Your depots are in several cities | Which cities do you cover, and how quickly? |
| Access rights | Each site should see only its own vehicles | How are groups and roles organised? How many users are included? |
| Sensors | Fuel, temperature or CAN bus depending on the business | Which sensors are compatible with the proposed tracker? |
| Reports | Nobody tracks a hundred vehicles on a map | Can we get reports by site and period, in PDF and Excel? |
| Data | Vehicle positions are sensitive data | Where is the data hosted? How long is it kept? |
| Reversibility | You must be able to switch suppliers | How do we get our data back at the end of the contract? |
| Integration | Avoid double data entry | Can you send the data to our ERP or TMS, and how? |
| Support | Breakdowns happen | What is the response time? Is there a dedicated contact? |
| Contract | Compare like with like | What is included: hardware, SIM, installation, platform, support? |
Be wary of vague answers. If a supplier cannot tell you exactly who installs or where your data is stored, that is already an answer.
How does a multi-site rollout work?
A rollout across several cities is planned like a site project. The usual steps:
- Inventory. A list of vehicles per site, with make, model, year, tank type and special needs (fuel, cold chain, machinery). This is the basis for the quote and the schedule.
- A pilot site. Start with one depot and a few vehicles. You check installation quality, data reporting and team buy-in before scaling up.
- Installation schedule. Site by site, agreed with your managers. The aim is to keep vehicles off the road as little as possible: fitting at the depot and, if needed, outside working hours.
- Vehicle-by-vehicle checks. Each vehicle should be tested before going back on the road: position, ignition, sensors. A fuel probe must be calibrated to the tank.
- Configuration. Groups, users, zones (depots, customers, sites), alerts and automatic reports, set to your rules.
- Onboarding. Short training for each profile: management, fleet managers, operations.
The total duration depends on the number of vehicles, the number of sites and the supplier’s installation capacity. Ask for a detailed schedule for your fleet.
How do you connect GPS to your ERP/TMS?
If you already use an ERP, a TMS or a fleet maintenance tool, GPS data becomes more valuable when it flows straight into it: kilometres for maintenance, engine hours for billing machinery, trips for proof of delivery, fuel for cost control.
Before raising it with the supplier, clarify on your side:
- Which data you want (positions, kilometres, fuel, alerts, temperatures);
- How often (continuously, daily, monthly);
- Into which tool, and in what form your IT team can receive it.
A serious integration starts with a feasibility study. Be cautious of an “everything is possible” given without looking at your system. Conversely, a regular Excel export is sometimes enough to get started.
How do you get drivers to accept tracking (Law 09-08)?
This is often the most sensitive part of a project. Poorly explained tracking feels like surveillance; well presented, it becomes a tool that also protects the driver.
In Morocco, the processing of personal data is governed by Law 09-08. The position of a vehicle driven by an employee can fall within its scope. A few principles to follow, to be confirmed with your legal adviser:
- Inform drivers before go-live: what is tracked, why, and who has access.
- Define clear purposes: vehicle security, route planning, fuel control, maintenance.
- Restrict access to those who need it and set a retention period.
- Set usage rules for vehicles outside working hours.
- Complete the required formalities with the CNDP, depending on your situation.
Also explain what drivers gain: evidence in a dispute over timing, an accident or a theft, and conversations based on facts rather than suspicion.
What budget should you plan: what makes up the cost?
There is no single price: the cost depends on fleet size, equipment, sensors and service level. To compare offers, break them down:
- Hardware: tracker, probes, sensors, wiring. Is it sold, rented or included?
- Installation: fitting, calibration, travel to your cities.
- Subscription: platform, app, SIM card and data transmission.
- Support and maintenance: call-outs, replacement of a faulty device, warranty.
- Options: ERP/TMS integration, custom development, additional users.
- Internal costs: your teams’ time for the pilot, training and follow-up.
Then set this cost against your own stakes: fuel spend, incidents, administrative hours. Actual savings depend on your fleet and the actions you take; run the numbers with your own figures rather than generic promises.
Frequently asked questions
What is the difference between a GPS tracker and fleet management software?
The tracker is the device installed in the vehicle; it sends data. Fleet management software turns that data into useful information: map, history, alerts, reports, fuel, maintenance. For a large fleet, the software and the service are what make the difference.
Do we need to equip the whole fleet at once?
No. A pilot site lets you validate the installation, the platform and how teams receive it. The rollout then continues site by site, on an agreed schedule.
Can cars, trucks and machinery share the same platform?
Yes, and that is the most common case. Each vehicle type can have its own sensors and alerts while staying in a shared view.
How long does it take to equip 100 vehicles?
It depends on the number of sites, the sensors to fit and the installation team’s capacity. Ask the supplier for a precise schedule for your fleet.
At MINTA, our own technicians install and check every vehicle, and the MINTA TRACKER platform includes an AI assistant: a written message, even in Darija, is enough to get a report (voice notes are coming soon). The assistant consults your data; it does not change anything. Want to see how it applies to your fleet? Request a demo.