Ask most fleet operators how they know when a specific tyre was last rotated, or which trailer was coupled to which truck three months ago, and the honest answer is usually: a logbook, a workshop receipt, or someone's memory. That gap is where breakdowns turn expensive — not because the maintenance didn't happen, but because nobody can prove when, where, or on which vehicle.
We built the fleet side of our Transport Management System to close that gap at the asset level, not the fleet level.
The problem with "fleet management" as a category
Most fleet software tracks the vehicle. Ours tracks the vehicle, the trailer, and the tyre as three separate histories that stay linked even as the physical combination changes on the road — because in cross-border haulage, it does change. A tractor unit doesn't keep the same trailer for its whole life, and a trailer doesn't keep the same tyres.
So the system logs:
- Trailer coupling history — which trailer was on which tractor, and when the pairing changed.
- Tyre operational profiles — per-tyre history, independent of whichever vehicle it's currently mounted on.
- Spare parts tracking — logged against the vehicle record, not a separate inventory sheet disconnected from the fleet.
None of this is exotic. What matters is that it's queryable later when a tyre fails early, you can actually look at its history instead of guessing.
Incidents become workshop orders automatically
The part of this we're most glad we built early: when a breakdown or incident is logged against a vehicle with its own cost lines it automatically generates a Workshop Order. That sounds small. In practice it means the person who reports "the trailer brakes failed near Kasumbalesa" isn't also the person who has to remember to open a maintenance ticket, assign it, and track the cost separately. The system does that step.
Preventive Maintenance Plans sit alongside this — scheduled by distance or date, so servicing isn't purely reactive.
What the axle-by-axle view actually solves
The tyre configuration screen — the one we've been showing above — maps every tyre to its exact axle position (A1 OL, A1 IL, A1 IR, A1 OR, and so on down the chassis). It's a small interface decision with a real consequence: when a tyre needs replacing, nobody has to physically walk out to the yard to figure out which one. The record already says where it sits.
Why we're writing this down
We're not describing this because it's a novel idea — matching maintenance records to physical assets isn't new. We're describing it because in fleet operations, the gap between "the data exists" and "the data is usable" is where most systems quietly fail. A maintenance history nobody can search is barely better than no history at all.
If your fleet's maintenance records currently live across a mix of logbooks, WhatsApp messages, and someone's memory, that's exactly the gap this was built to close. Get in touch — happy to walk you through it.
Chesify Labs builds Odoo-based operational systems for logistics, freight, and fleet-heavy businesses across East and Southern Africa.