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).

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Ready when you are

Dispatch on autopilot.

14-day free trial. No card. Cancel anytime.

47 fleets joined this month · Talk to sales