London · Multi-base operators
London multi-base dispatch software — TfL multi-zone PHV operator platform
TfL-aware multi-base dispatch with per-zone pricing, cross-base booking transfers, multi-tenant isolation, and operator monthly returns generated per TfL operating area.
TaxiCloud is the modern multi-base taxi dispatch software for London PHV operators running more than one operating zone. Per-zone pricing rules, cross-base booking transfers, TfL operator monthly returns generated per operating area, ULEZ + Congestion Charge handling per zone, and AI Copilot routing across the combined fleet. Designed for the 2026 London PHV operator running North London + Central + South London zones under coordinated operator licences.
Why London
The local operating reality.
London is the largest multi-base PHV market in the UK by margin. The major London PHV operators almost universally run more than one operating zone — North London and Central London, City and Canary Wharf, South London and Heathrow corridor — to balance corporate-account density with airport feeder volumes. The 2026 TfL operator monthly return format requires per-operating-area reporting, which legacy multi-base dispatch platforms typically need a manual reconciliation step to produce. Modern dispatch like TaxiCloud generates per-area returns automatically, with cross-base booking transfers preserving driver and vehicle audit trails across zones.
How TaxiCloud runs multi-base operators in London
The operational impact.
Multi-base London operations on TaxiCloud separate per-zone configurations cleanly: each zone gets its own pricing rules, dispatcher seats, ULEZ surcharge configuration, Congestion Charge accruals, and TfL operator return generation. Cross-base booking transfers route automatically when a passenger booking originates in one zone but the route crosses into another — the dispatcher console flags ownership, the settlement reconciles cross-base commission splits, and the TfL return preserves the booking under the originating operator licence area.
Migration to multi-base TaxiCloud from iCabbi or Autocab takes 8-12 working days for a multi-zone London operator. The additional time over single-base migration covers per-zone configuration walkthrough, cross-base transfer rule setup, and per-area TfL return validation against existing reporting periods.
Frequently asked
London multi-base operators questions, answered.
How does TaxiCloud handle multi-base TfL operator monthly returns?
Each operating area generates a separate TfL operator monthly return automatically — driver licensing, vehicle PHV plate validity, dispatched bookings (PII redacted), and incident reports per area. Cross-base bookings preserve under the originating operator licence area.
Can multi-base London dispatchers transfer bookings between zones?
Yes. Cross-base booking transfers route automatically when routes cross zone boundaries; dispatcher console flags ownership; settlement reconciles cross-base commission splits per the operator's configured rules.
How does ULEZ work across multi-base London zones?
ULEZ-compliance is a per-vehicle attribute regardless of operating zone. The booking widget surcharges based on ULEZ entry; the dispatch board flags before non-compliant drivers cross the boundary; routes can be biased per-zone.
How long does multi-base London migration to TaxiCloud take?
Typically 8-12 working days for a multi-zone London operator. Cross-base configuration walkthrough adds 1-2 days over single-base migration.
Ready when you are
Dispatch on autopilot.
14-day free trial. No card. Cancel anytime.