On this page
What "white-label" actually means
A white-label taxi app is a booking app built once by a software supplier and then dressed in your brand: your name, logo, colours and app store listing. Passengers see your company. Behind the scenes, the same core software runs for several operators, which is why it usually costs much less than building an app from scratch.
The alternative is a fully custom build, where a developer writes an app just for you. That gives you total control, but you pay for every feature, every fix and every update to keep up with Apple and Google. For most independent and regional operators, white-label is the realistic route to an app of their own. If you’re still deciding whether you need one at all, start with why your taxi firm needs its own booking app.
White-label isn’t a single thing, though. Two products sold under the same label can differ hugely in what you own, how they connect to your dispatch system and what happens when you want to leave. This guide covers what you should expect to get, and the questions worth asking before you sign.
What you should expect to get
The passenger app
The basics any white-label taxi app should cover:
- Account sign-up and saved addresses
- Booking now or for later, with a price or estimate before confirming
- Live tracking of the car and a real arrival time
- Card, wallet and cash payment options
- Trip history and receipts
- Notifications when the driver is assigned, arriving and outside
Extras that make a real difference include loyalty points, account or business bookings, and the ability to change offers and messages without waiting for an app store update.
A connection to your dispatch system
This is the part that matters most and is easiest to gloss over in a demo. App bookings should land in your dispatch system like any other job, with the trip status flowing back to the passenger. If controllers have to retype app bookings, or the app runs a separate fleet view, you’ve bought a second system to manage rather than a booking channel.
Your app store listings
You should end up with your own listing on the App Store and Google Play, in your company name. This has practical consequences:
- Apple’s App Review Guidelines (guideline 4.2.6) say apps built from a commercial template or app generation service will be rejected unless they are submitted directly by the provider of the app’s content. In practice that usually means the app sits in a developer account belonging to your company.
- Apple asks organisations enrolling in its developer programme for a D-U-N-S Number registered to their legal entity, and Google said in 2023 that new Play Console accounts for organisations need one too. Get that sorted early, because it can hold up launch.
Admin and reporting
Expect a back office where you can see app bookings, manage promotions, set up loyalty rewards and view basic numbers such as downloads, active users and repeat bookings.
Ten questions to ask before you buy
1. Whose developer account will the app live in?
If the app is in the supplier’s account and you part ways, you may lose the listing, the reviews and every install. Ask for the app to be published under your company, or for a clear written process to transfer it.
2. Who owns the passenger data?
Under UK GDPR, the organisation that decides why and how personal data is used is the controller. For your own booking app, that should be you, with the supplier acting as your processor. The ICO says a controller using a processor needs a written contract covering things such as acting only on your documented instructions, security and the use of sub-processors. Ask to see it.
3. Can I export my data if I leave?
Passenger accounts, booking history and marketing consents are valuable. Ask what format you’d get them in and how quickly.
4. Which dispatch systems does it work with, and how?
Ask which dispatch systems are supported today, not on a roadmap, and whether bookings arrive in your queue as normal jobs. If you might change dispatch system one day, ask whether you keep the app, your passengers and your data when you do.
5. How is it secured?
A good answer covers where your dispatch credentials are stored, whether the app talks to your dispatch system directly or through a server the supplier runs, and what gets logged. Dispatch keys shouldn’t be shipped inside the app itself.
6. How do payments work, and where does the money go?
Apple’s guidelines (3.1.3(e)) say apps selling physical goods or services consumed outside the app, such as a taxi journey, must use payment methods other than in-app purchase, like Apple Pay or card entry. Ask which payment provider the app uses, whether fares are paid into your own merchant account, when cards are charged and how refunds and disputes are handled. Our guide to how passengers want to pay for taxis covers the options.
7. Who keeps it up to date?
Apple and Google update their requirements regularly. Google Play, for example, sets a target API level requirement that new apps and updates must meet, and older apps can stop appearing to new users on newer Android devices. Make sure the supplier commits to keeping your app compliant, and ask how often they release updates.
8. Does it meet accessibility standards?
The Department for Transport’s best practice guidance says operators’ digital booking apps should comply with WCAG 2.1 Level AA. Ask how the app has been tested against it.
9. What does it cost, all in?
Pricing models vary: set-up fees, monthly licences, per-booking charges or a mix. Get the full picture, including app store developer fees, payment processing, text message costs and any charges for changes to branding or features.
10. What’s the contract length and exit process?
Look for a reasonable notice period and a written exit plan covering the app listing, your data and any domain or brand assets.
Red flags
- The demo can’t show a real booking reaching a dispatch system
- Vague answers about data ownership or "we’ll sort that later"
- The app sits only in the supplier’s account, with no transfer route
- No named contact for support during your busy hours
- Fees that depend on things you can’t predict, without a cap
Getting the launch right
A white-label app is quick to stand up, but launch still takes planning:
- Prepare your listing. Screenshots, a description written for passengers in your area, and your privacy policy.
- Test with real trips. Book through the app from your own phones, at quiet and busy times, before telling anyone.
- Brief your team. Controllers and drivers should know app jobs look like any other, and how to answer passengers’ questions about the app.
- Promote it to current passengers first. QR codes in cars, links in booking texts and a line on your hold message.
- Review after a month. Look at downloads, repeat bookings and any support issues.
How Moova’s Passenger App fits
Our Passenger App is a white-label booking app in your name: your logo, colours and company name, published to the App Store and Google Play, so passengers see your company, not ours. Passengers book, follow their car live and pay by card or cash, and card payments are held at booking and taken when the trip is done. It books straight into the dispatch system you already run, starting with iCabbi, and shows a live arrival time even while the driver finishes a nearby trip.
You own your passengers, bookings and marketing results, and if you ever change dispatch system you keep your app, your passengers and your data. On security, the app only talks to your own backend, never straight to dispatch, and no dispatch keys ship in the app; keys are encrypted and every dispatch request is logged with credentials redacted. Loyalty points are built in, and offers and settings change without an app update.
If you need something more bespoke, our custom software service builds apps and integrations around how your business works.
Frequently asked questions
Is a white-label app as good as a custom-built one?
For most operators, yes. A well-maintained white-label app benefits from improvements made for every customer, and you avoid paying for each update alone. A custom build makes sense when you need features no product offers.
How long does it take to launch?
It depends on the supplier, your dispatch integration and app store review. Getting your company’s developer accounts and D-U-N-S Number in place early is one of the simplest ways to avoid delays.
Will passengers know it’s a white-label app?
They shouldn’t. The app, listing and messages should all carry your name.
Can I keep taking phone bookings?
Yes. The app is another way to book, alongside your phone line and website, and all of them should arrive in the same dispatch system.
Talk to us
If you’re comparing white-label taxi apps and want to see one running on your own brand, talk to Moova. We’ll show you the Passenger App and answer every question on this list.