Architecture · 11 min read
Multi-base fleet architecture reference
Architecture reference for multi-base UK + Ireland taxi fleets — operator-licence structure, per-base configuration, cross-base transfers, compliance reporting.
Multi-base fleet operations differ structurally from single-base in operator-licence handling, per-base configuration, cross-base booking transfers, and compliance reporting. This architecture reference covers the design patterns multi-base UK + Ireland operators typically deploy on TaxiCloud, with specific notes on cross-jurisdiction operating (London + South East, North West M62 corridor, NI + Republic of Ireland).
Step 1
Operator-licence structure
Multi-base operators typically hold one operator licence per jurisdiction (Glasgow City Council + Edinburgh + Aberdeen, for example). Some councils issue combined regional licences; most issue per-council. Coordinate licence renewal cycles to avoid expiry-cluster compliance gaps.
Step 2
Per-base pricing configuration
Each base gets its own pricing rules, fare classes, surcharge structures. Common pattern: shared fare-class definitions across bases with per-base surcharge overrides. TaxiCloud surfaces per-base configuration as first-class objects.
Step 3
Per-base dispatcher seats
Dispatchers typically operate within their assigned base for ownership clarity. Cross-base bookings hand off to receiving-base dispatcher. Some operators run a centralised 'super-dispatcher' role for after-hours coordination.
Step 4
Cross-base booking transfer rules
Bookings crossing base boundaries trigger transfer logic — pricing reconciles per-base rules, settlement splits commission per agreed percentage, dispatcher console flags ownership transition.
Step 5
Compliance reporting per area
Each operating area generates separate quarterly returns automatically. Cross-base bookings preserve under the originating operator licence area for regulator reporting clarity.
Step 6
Cross-jurisdiction patterns
London + South East: TfL + council coordination. North West M62: Manchester + Liverpool + Warrington under coordinated councils. Cross-border NI + Republic: DVA + NTA dual-jurisdiction with currency handling.
Frequently asked
Questions, answered.
How many bases can a TaxiCloud Pro Max tenant run?
Pro Max covers up to 5 bases in standard configuration. Pro Ultra is custom for operators running 5+ bases or cross-jurisdiction multi-currency operations.
How do cross-base bookings split commission?
Configurable per operator. Common patterns: 60/40 originating-base / receiving-base, 50/50 split for cross-border bookings, dispatcher-discretion override for VIP corporate accounts.
Can multi-base operators run different brands per base?
Yes. Pro Max white-label supports per-base brand configuration — different domain, logo, colours per operating area.
Other guides
Strategy
Electric vehicle fleet transition guide
Reference for UK + Ireland taxi operators transitioning to electric or hybrid fleets — vehicle selection, charging infrastructure, range-aware dispatch, payback economics.
ReadEvaluation
How to choose taxi dispatch software in 2026
A 2026 procurement-grade reference for selecting a taxi dispatch platform — buying criteria, cost structures, compliance fit, and the questions to ask every vendor before you sign.
ReadPricing
Dynamic pricing for taxi fleets — design and operations
How UK and Ireland taxi fleets design dynamic pricing in 2026 — surge bands, time-of-day overlays, demand signals, regulator constraints, and the operating disciplines that prevent rider backlash.
Read
Share this article
Pronti quando lo sei tu
Dispatch in modalità autopilota.
Prova gratuita di 14 giorni. Cancel anytime.