Custom Taxi Booking Apps for Taxi Ranks and VTC Fleets

The phone rings, the operator picks the nearest car by guesswork, and the passenger has no idea how long the wait will be. Then a hotel asks for an itemised monthly report to sign a contract, and all you have is a paper logbook. Your own booking app brings passengers, drivers and corporate clients into a single system, and gives you a channel of your own with no commission to pay.

How many separate apps does this need?

  • 01

    Passenger app (iOS + Android)

    Book from the map, enter pickup and destination, see the estimated fare, the vehicle's arrival time and the driver's plate number, share the trip in progress, and pay by saved card or cash on arrival.

  • 02

    Driver app (iOS + Android)

    Accept/decline screen for incoming jobs, background location broadcasting, rank and queue management, fare display based on the taximeter or distance, shift start/stop, and a daily earnings summary.

  • 03

    Fleet and call centre panel (web)

    Live vehicle map, manual assignment of phone bookings, driver and vehicle document tracking, tariff management by zone and time of day, cancellation and complaint records, and driver earnings reports.

  • 04

    Corporate client portal (web)

    Separate access so companies can open accounts for their employees, set spending limits, view a single consolidated monthly invoice and pull trip breakdowns by department.

What the app includes

  • Rank queue rights and turn-passing management
  • Flight-number tracking for landing time and meet-and-greet
  • Advance bookings with driver departure reminders
  • Number-masked calling between passenger and driver
  • Live trip-sharing link with plate and driver details
  • Corporate trip code and cost-center selection at booking
  • Expiry alerts for driver and vehicle documents (licence, inspection, insurance)
  • End-of-shift earnings with rank share and commission deductions
  • Zone and time-based tariffs: night, out-of-city, return leg
  • Fixed route price list for airport-to-hotel transfers
  • Waiting timer and no-show fee when the passenger never boards
  • Vehicle filters for luggage space, child seat and wheelchair access

State of the sector

For a taxi rank or a newly founded VTC/transfer company, competitive pressure comes from two directions. Passengers no longer want to call and wait; they want to see on screen how many minutes away the car is. Hotels, hospitals and factories, meanwhile, expect itemised monthly invoices and trip reports on contract work. A rank without an app loses that corporate business to the competitor who can produce the paperwork. On top of that, every trip coming through a platform carries a commission and leaves the customer relationship with the platform; an operator who builds its own channel keeps repeat customers on its own side.

Metrics that matter here

  • Booking fulfilment rate and average vehicle arrival time — How many bookings found a car and how many minutes it took to reach the passenger; these two numbers measure both the dispatch engine and driver supply.
  • Driver acceptance rate — The share of offered jobs that drivers accept; if it is low, either the notification flow or the fairness of dispatch is broken, and passengers wait.
  • Empty mileage ratio — The share of total distance driven without a passenger; smart dispatch and return-trip matching bring this down directly.
  • Corporate account share of trips and collection time — How much of revenue comes from contract customers and how many days it takes to collect an invoice; the portal and automated invoicing speed this up.

Common mistakes in this sector

  • Designing the driver app as a copy of the passenger app The driver uses it at the wheel, one-handed, in direct sunlight. Multi-step screens and small buttons cause missed jobs. The driver side needs its own design: a large accept button, an audible alert and the fewest possible taps.
  • Leaving phone bookings outside the system Digitising only app bookings while phone bookings go into a notebook creates two separate queues and starts arguments among drivers about how work is shared out. The operator panel belongs in the first release, not in a later phase.
  • Setting fares independently of the taximeter When the amount the app calculates does not match the taximeter, arguments break out at the end of the trip and complaints pile up. In a licensed taxi the app shows an estimate while the taximeter governs; that distinction has to be designed in from the start.
  • Showing passenger and driver phone numbers in the clear Once numbers are exchanged openly, drivers pull customers off the app and the business loses both the trip and the record of it, leaving no audit trail when a complaint comes in. Use masked calling or in-app messaging instead.

Regulation and compliance

Commercial passenger transport in Turkey is carried out under the Road Transport Regulation with an operating licence and the required driver credentials; taxi tariffs are set by provincial traffic commission and municipal decisions, and the app cannot operate outside that tariff. Depending on how drivers are engaged, SGK (Turkish social security) registration is required. Passenger and driver location, route and contact data are personal data under KVKK (Turkey's data protection law, aligned with GDPR): a privacy notice, a retention period and role-based access must be in place, and location must not be tracked outside shift hours. Corporate and card payments trigger an obligation to issue e-Arşiv invoices (part of Turkey's mandatory e-invoicing system).

The real challenges in this sector

  • Dispatch: the nearest car is not always the right car

    Assigning by straight-line distance picks the driver stuck on the opposite carriageway or at the mouth of a bridge. The dispatch engine has to work from estimated arrival time over the actual road network, and factor the driver's recent accept/decline behaviour, vehicle density in the area and queue position at the rank into the score. Otherwise drivers conclude the system is dealing jobs unfairly and simply close the app.

  • Keeping the driver's phone alive through a full shift

    A driver keeps the app open for twelve hours. Continuous high-accuracy GPS plus an always-on screen will kill the handset by mid-afternoon. You need different location sampling rates when a trip is in progress versus when the car is idle, batched uploads while idle, and an onboarding flow that explicitly asks for background location permission on iOS and battery optimisation exemption on Android.

  • A silent job alert is a lost trip

    If the driver misses the notification at the wheel, the job goes unanswered and the passenger waits. Push alone is not enough: the job has to arrive over a persistent socket connection and be shown full screen with sound and vibration, on a channel that works regardless of silent mode, and it must be handed off automatically to the next vehicle if no answer comes within a set number of seconds.

  • Fares: the taximeter or the app's own calculation?

    For licensed taxis the fare is tied to the municipally set taximeter tariff; the app cannot impose its own pricing. The system should show an estimate built from the flag-fall, per-kilometre and waiting-time units, then settle on the taximeter reading at the end of the trip. On the VTC/transfer side, fixed route pricing, meet-and-greet and waiting charges are modelled separately.

  • Losing the signal in tunnels, car parks and covered areas

    In an airport car park or a tunnel the GPS signal drops, the car jumps around the map and distance accumulates incorrectly. Location data has to be buffered on the device and sent in order once the connection returns, absurd points filtered out using speed and accuracy values, and the trip route snapped to the road network. Otherwise the passenger watches their car drive into the sea.

Required integrations

  • Saved cards and 3D Secure payments via iyzico or PayTR (Turkish payment providers)
  • Corporate client collections through a bank virtual POS
  • e-Arşiv invoicing integration with GİB (Turkish Revenue Administration) and consolidated monthly corporate billing
  • Mapping, routing and ETA service (arrival times calculated over the road network)
  • Job alerts and an audible channel via Firebase Cloud Messaging and APNs
  • Bulk SMS provider for trip codes, plate numbers and cancellation notices

Who this page is for

  • An urban taxi rank or drivers' cooperative

    The priority is pulling phone bookings into the panel, dispatching without breaking rank order, and showing an estimate that matches the regulated meter tariff. Cards and the corporate portal can wait for a later phase.

  • A newly founded VTC or airport transfer company

    Here the business is reservations: fixed route pricing, flight-tracked meet-and-greet, advance driver assignment and prepayment by saved card. On-demand volume is low, so the dispatch engine can stay simple.

  • A small fleet running contracted staff and patient transport

    The corporate side dominates: cost centres, spend limits, recurring route schedules, departmental breakdowns and consolidated monthly invoices. The passenger app can stay minimal while the panel and reporting carry the weight.

A phased plan that splits the budget

  1. 1

    Phase 1 — Booking, dispatch and a core that runs one rank 7-9 hafta

    Passenger app, driver app and operator panel go live: map booking, road-network based assignment to the best vehicle, audible ride alerts, live vehicle tracking, cash payment and end-of-shift earnings. Phone-in bookings enter the same panel from day one, because a second parallel queue makes drivers abandon the system.

  2. 2

    Phase 2 — Payments, corporate accounts and invoicing 4-6 hafta

    Saved-card and 3D Secure payments, the corporate portal with spend limits and cost centres, monthly consolidated invoices and e-Arşiv (Turkey's mandatory electronic invoicing system) go live. It comes second because hotel and hospital contracts only produce documents once trips are already being recorded reliably.

  3. 3

    Phase 3 — Transfers, reservations and fleet depth 5-7 hafta

    Fixed-route transfers, flight-tracked meet-and-greet, advance reservations, hourly hire, rank queue rules, document expiry alerts and reports on empty kilometres and acceptance rates are added. These only pay off once a steady daily booking volume exists.

Typical scope and timeline

The passenger app, the driver app and the fleet/call centre panel are built together. Scope covers map-based booking and the dispatch engine, live location broadcasting, tariff and service type management, card and cash payment, corporate account invoicing, driver earnings reports, notification infrastructure, publishing to the iOS and Android stores, and support through the pilot period. Scope and budget are agreed after a scoping call.

Estimated timeline: 12-18 weeks

Off-the-shelf or custom build?

Topic Off-the-shelf Custom build
Time to launch and cost A ready-made dispatch package can be running within days; with a handful of vehicles it is genuinely a good way to test whether the demand is real. Custom development takes weeks and a one-off investment; in return there is no per-vehicle monthly fee piling up as the fleet grows.
Taximeter and local tariff compliance Foreign-built packages usually impose their own pricing model; matching a locally regulated meter tariff, waiting units and estimate-versus-final logic is often a workaround. The meter stays authoritative for licensed taxis while the app shows an estimate, and VTC fixed routes plus meet-and-greet fees are modelled as separate service types.
Corporate accounts and invoicing flow Even when a ready product has a corporate module, cost centres, spend limits and Turkish e-invoice output usually end up as manual exports stitched together. The departmental breakdown, monthly consolidated invoice and accounting integration that hotel, hospital and factory contracts demand are built directly into the system.
Data ownership and customer relationship On a subscription, trip history, the passenger list and corporate accounts live on the vendor's infrastructure; export and migration terms decide what happens if you leave. Data stays on your own servers, retention and privacy-notice rules under Turkey's KVKK data protection law are yours to set, and the corporate relationship stays with the business.

Sector glossary

Rank queue right
The order in which vehicles waiting at a rank receive work. If dispatch only picks the nearest car and ignores whose turn it is, disputes start at the rank, so turn-passing rules are defined in the system.
Meet and greet
The driver waiting inside the terminal with a name sign instead of at the kerb. It is priced separately, and parking time plus flight delays feed straight into the fare.
No-show
The car arrives but the passenger never appears. Once the waiting timer expires the driver closes the job as a no-show, generating a waiting fee and a cancellation record so the trip is not simply written off.
Trip voucher code
A code the hotel desk or a company manager hands the guest that charges the ride to a corporate account. The driver takes no cash; the trip lands on that company's monthly invoice.
Geofence
A virtual boundary drawn on the map for an airport, a hotel forecourt or a city limit; a car entering it joins that zone's queue automatically, and trips crossing it switch to the out-of-city tariff.

Frequently asked questions

Let us talk about your project

A free 30-minute call to scope it out, then an itemised quote within 48 hours.

Get a Free Quote

This page explains the problems an app must solve in this sector. We share references and comparable projects during the call.

Other sectors

All sectors →