The white-label platform market is full of options that look very similar on the sales slide. They all claim real-time tracking, geofences, reports and a mobile app. The difference shows up later, once you have migrated your base.
First: what “white label” actually means
The term is used very loosely. It is worth separating three levels, because the price and the implications are very different.
| Level | What you can change | What your customer sees |
|---|---|---|
| Reselling | Nothing, or a logo in a corner | The provider's brand |
| Customisation | Logo, colours and a provider subdomain | Your brand, but the domain gives the provider away |
| Real white label | Own domain, full identity, apps and emails | Only your company, at every touchpoint |
If the password-reset email arrives from the provider's domain, it is not white label. If the app in the store is named after the provider, it is not either. Those are the two places where the illusion breaks most often.
The questions that actually discriminate
On hardware
- How many models are certified, and which of the ones you sell are on the list?
- Does certifying a new device cost anything? How long does it take and who decides?
- When they certify a device for another customer, does it become available to everyone?
- Do they support the full protocol or only basic position? Inputs, outputs, CAN, fuel probes and temperature are where the difference lies.
On data
- Can you export your full database, history included, and in what format?
- How long is history retained and what does extending it cost?
- Does the provider use your data for anything other than providing the service?
- If you end the contract, is there a retention period or a penalty?
On the business
- Is billing per reporting asset or per licence purchased?
- Is there an implementation, training or app-publishing fee?
- Is there a minimum term? What happens if your base shrinks?
- Can you create sub-distributors with their own brand?
On engineering
- Is there a documented API and a sandbox, or only “we have an API”?
- Are there per-event webhooks or do you have to poll in a loop?
- Do they publish service status and an incident history?
How to test instead of believe
A guided demo always goes well: the salesperson knows the happy path. To find out how the platform really behaves, ask for a trial environment and do these five things yourself.
- Connect a real device. Not the one the provider lends you: one of the ones you sell, with your SIM, installed the way you install it.
- Generate a thousand positions and request a report. See how long it takes and whether the result matches the real trip.
- Create a customer and restrict their permissions. Then log in as that user and try to see what you should not. It is the cheapest isolation test.
- Call support with a real problem. Response time during the sale is the best you will ever get.
- Ask for a full export of your trial. If it is awkward with ten assets, imagine ten thousand.
The red flags
Some answers should be enough to end the conversation:
- “We run the export for you if you need it” — your data is not yours.
- “The API is under development” — you will key everything twice for years.
- “Your own domain is charged separately” — white label is an add-on, not the product.
- “We certify your device for a one-off fee of…” — the catalogue will not grow with you.
- “We have every device on the market” — nobody does. Ask for the list.
The cost that is not in the proposal
Price per asset is easy to compare. What is hard to compare is what does not appear: your team's hours keying what the API should do on its own, the field visits for devices that report badly, the calls from customers who do not understand a badly worded alert.
A platform two dollars cheaper per asset can end up far more expensive if it forces you to keep a person doing data entry.
In short
Choose by thinking about what your operation looks like with ten times the assets you have today, not this week's. The right platform is the one that still works once you have grown; the wrong one makes you repeat the migration just as the business starts to work.
