Odometer checks
Axlerun refuses a reading that goes backwards or further than the vehicle could have travelled. Turn that check off per role when your fleet legitimately needs to record one anyway.
Odometer readings are the backbone of a logbook, so Axlerun checks a new one against the vehicle's history and refuses anything implausible: a reading that goes backwards, or one further than the vehicle could have travelled since the last.
That is right almost always, and wrong often enough to matter.
When the check gets in the way
Back-entry — catching up a month of readings out of order, so each one looks like it goes backwards.
Corrections — a reading was typed wrong, and the right one is now lower than the mistake.
A replacement cluster — the instrument cluster was swapped and the odometer genuinely starts again from a different number.
Turning it off, per role
Go to Modules and find Odometer checks in the General area. It sits outside the modules because it belongs to no single one.
Untick a role — Business Owner, Business Admin or Driver — to let those people record a reading the check would otherwise refuse.
All three are ticked by default, which is the setting most fleets should keep.
A reading let through this way is stored flagged, so it is visible as one that bypassed the check rather than disappearing into the history as though it were ordinary. Turning the check off does not hide anything; it records that you chose to override.
Who should have it off
Usually nobody, or an admin only. Leaving it on for drivers is the point of the check: a driver typing 100,000 instead of 10,000 at the pump is exactly the mistake it exists to catch, and the person best placed to spot a wrong reading later is not the person who entered it in a hurry.
If you are doing a one-off catch-up, untick the role, do the work, and tick it back on.
Last updated Tue Sep 15