Choosing a white-label GPS tracking platform is a decision you make once and live with for years. Migrating a fleet off a platform you regret is possible — we do it regularly — but it costs money, attention and a certain amount of credibility with the customers who notice. The demo is not where that decision should be made. Every platform in this market demos well, because a demo runs on clean data, a handful of devices and a salesperson who knows which screens to avoid.
What follows is the checklist we would use ourselves. Some of these questions we answer comfortably; a few of them are uncomfortable for every vendor in this industry, ours included. Ask them anyway.
Devices and protocols
1. Which exact device models are supported — not how many
"1,000+ devices supported" is the standard claim, and on its own it means very little. What matters is whether your hardware is supported, at the firmware version you actually have in the field. Ask for the list. Then pick the three models you deploy most and ask what happens with each one's less common messages: CAN bus data, driver ID via iButton or RFID, fuel probe readings, camera events.
Basic location decoding is easy and everybody has it. The long tail of a protocol — the sensor frames, the alarm codes, the manufacturer's proprietary extensions — is where platforms quietly differ, and it is exactly the part your customers pay extra for.
2. What happens when you need a device that is not supported
This will happen. A customer will standardise on hardware you have never seen, or a supplier will discontinue a model mid-contract. The answer you want is a concrete process and a timeline: who writes the protocol integration, how long it takes, and what it costs. The answer you do not want is "we will look into it" — that is how a signed deal turns into an apology six weeks later.
3. Can devices be re-pointed without touching them physically
Most trackers can be reconfigured remotely by SMS command or over-the-air, but only if the platform exposes that properly. If moving a thousand devices means sending a technician to each vehicle, the cost of ever leaving this vendor becomes the reason you never leave. Ask to see the bulk configuration screen, with real devices on it.
Data, ownership and exit
4. Who owns the data, in writing
The platform stores your customers' vehicle movements. Your contract should say plainly that this data belongs to you, that the vendor will not use it for any purpose beyond running your service, and that you can export it at any time. If the terms are vague here, assume the vague reading is the one that will be applied.
5. Can you export everything, in a format you can actually use
There is a meaningful difference between "you can export your data" and "you can export your data as a database dump with a documented schema". A vendor who will only give you CSV reports is offering you a filing cabinet, not your history. Ask for a sample export before you sign, not after you want to leave.
6. Where is the data physically stored
For operators selling into government and semi-government clients across the GCC, this is often the first question in a tender rather than a technical footnote. If your platform's data sits in a region you cannot name, you will lose those bids on the compliance annex without ever reaching a technical evaluation. Ask which country, and ask the same question about backups — where backups live is frequently a different answer.
7. What are the exit terms
Ask directly: if we give notice today, what happens? How long do we keep access? What does data extraction cost? Is there a penalty? A vendor confident in the product answers this without discomfort. A vendor whose retention depends on switching costs will change the subject. Notice which one you are talking to.
Commercials
8. How does pricing behave as you grow
Per-device pricing is simple to understand and simple to model, which is why most of this market uses it. The thing to check is the shape of the curve, not the headline number: where the volume breaks are, whether inactive devices still bill, what happens to a device that reports for three days a month on a seasonal fleet, and whether the price you agree today is fixed for the contract term.
Work out your cost per device at your realistic year-two volume, not your launch volume. A platform that is cheap at 200 devices and punishing at 2,000 is a platform you will outgrow at exactly the moment switching is hardest.
9. What is genuinely included, and what is a module
Fuel management, video telematics, driver behaviour scoring, maintenance scheduling, dispatch, billing — these are sold sometimes as core and sometimes as paid add-ons. Build the list of what you intend to sell to your customers, and price it properly before you compare vendors. We publish the full module list on our platform page for exactly this reason.
10. Is it genuinely white-label, all the way down
Check your logo and domain on the web application, then keep going. Check the mobile apps in the App Store and Play Store — whose developer account are they published under? Check the emails the system sends to your customers. Check the login screen, the API documentation your integrators will read, and the favicon in the browser tab. Partial white-labelling gets discovered by your customer, not by you, and usually at the worst moment.
Operations and support
11. What does the SLA actually commit to
Uptime percentages reward arithmetic. A 99.9% SLA allows roughly 43 minutes of downtime in a 30-day month; 99.5% — which reads almost identically — allows more than three and a half hours. Then read what the SLA covers: the web application only, or data ingestion too? A platform whose website is up while device data silently stops arriving is down, whatever the status page says.
Ask what the remedy is when the SLA is missed. If the answer is service credits against next month's invoice, that is normal. If there is no remedy at all, the SLA is marketing copy.
12. Who answers at 3am, and in which language
Fleet operations do not keep office hours, and neither do failures. Find out whether support is a ticket queue with a next-business-day target or a team with a phone number, whether there is Arabic support for your Gulf customers, and what the escalation path looks like when something is broken rather than merely confusing. Ask for the response-time commitment in writing.
A shorter version
If you only have one meeting, ask these three: show me my exact device models decoding sensor data, show me a full database export, and tell me what leaving costs me. A vendor who handles all three without hesitation has probably answered the other nine honestly too.
And a note on our own position: we build and host a white-label platform, so we are not a neutral party here. We publish this checklist because the operators who ask these questions tend to become good long-term partners, and because the ones who do not ask them tend to churn out of somebody's platform within two years — sometimes into ours, sometimes out of the industry entirely. Neither is good for anyone.
If you are weighing up building instead of buying, we have written that comparison separately in white-label versus a custom-built GPS platform. If you have already decided and want the go-to-market steps, start with how to start a GPS tracking business in the UAE.
Bring this checklist to us and we will answer all twelve in one call, including the uncomfortable ones. Book a technical review or message us on WhatsApp — send your device list in advance and we will test your exact models against the platform before we speak, so the answer you get is a demonstration rather than a claim.