Mixed Fleets — how KIRA manages mile and kilometer cars together, with total accuracy

The problem: when your fleet is mixed between miles and kilometers

Not every car in your fleet measures distance the same way. Cars imported from the American market — a common part of the used and imported car market across the Gulf — come with an odometer that reads in miles by default, while the rest of your fleet (Gulf-spec, European, or Asian-spec cars) reads in kilometers. In practice, that means one fleet speaking two different distance languages, with no way to change it — a car's physical odometer doesn't switch from miles to kilometers at the press of a button.

Most car rental management systems assume everything is in kilometers. For a company with even a single mile-based car, that means one of two things: either staff enter the odometer number as-is (in miles) and the system treats it as kilometers — producing completely wrong figures everywhere that reading feeds into — or staff manually convert the number every single time they log a reading, a process that's prone to human error and inconsistent from one employee to the next.

Why "unifying the unit" isn't a real solution

The obvious fix that comes to mind is "let's just standardize everything to kilometers" — but that isn't actually possible. A mile-based imported car's odometer is a physical instrument on the dashboard, not a number you can flip in software. Every option available to a company trying to "unify" the unit is a bad one:

• Ignore the difference and enter the mile figure as if it were kilometers — this understates the real distance by roughly 38% (1 mile = 1.609 km), so the accuracy of every downstream calculation collapses.
• Manually convert with an outside calculator every single time — slow, error-prone, and leaves no documented record of when or why the conversion happened.
• Drop these cars from the fleet entirely — an unjustified financial loss over a software limitation.

The real problem isn't "how do we convert the numbers" — it's "how do we make the system understand that each car might speak a different language, and handle each one correctly in its own language automatically."

KIRA's solution: every car keeps its own unit forever

In KIRA, the odometer unit is set per car — kilometers or miles — and there's no "unify the fleet" action anywhere. A mile-based car stays in miles forever, and shows in its native unit everywhere in the system:

• The car profile and its details: the reading and its unit are shown exactly as they are — no conversion, no hidden rounding.
• The contract and the deliver/receive screens: every odometer reading is entered and displayed in that car's own native unit.
• Maintenance requests and reports: the current reading, last service, and remaining distance to the next service are all in the car's own unit — never a misleading default of kilometers.
• The KIRA Partners app: the exact same principle on mobile — the car list, handover, and maintenance screens all show the correct unit for each car.

Billing accuracy: automatic conversion only in the extra-mileage calculation

A contract's daily mileage limit is always in kilometers — that's the standard convention in rental agreements. So what happens when a customer picks up a mile-based car, then returns it having driven beyond the allowed limit? KIRA automatically converts the pickup and return readings from miles to kilometers only at the moment of calculation, then computes the real difference precisely to bill for the excess mileage — with zero manual staff involvement and no rounding that could introduce an error into the invoice.

In PDF contracts and the detailed view, the original reading still shows in miles, alongside a clear note of its approximate kilometer equivalent — so both the customer and staff understand both numbers without any ambiguity.

Live tracking integration: accurate maintenance alerts and correct distance readings

This is where systems without real mile support cause the most serious damage: KIRA's GPS tracking system reads the distance driven live from the tracking device installed in the car, to calculate when that car's next maintenance is due. The problem with tracking that only assumes kilometers is that — before this update — it would read a mile-based car's distance and treat it as if it were kilometers, meaning a maintenance alert would fire dramatically later than its real due date (a car that had actually driven 5,000 real miles — about 8,047 kilometers — was being read in maintenance calculations as if it had only driven 5,000 kilometers). That gap means delaying necessary maintenance by thousands of extra kilometers, with the real mechanical risk and safety risk that carries.

Now, KIRA converts the live reading from the tracking system into the car's native unit on every sync, so a mile-based car's distance stays correct and consistent in every maintenance calculation that depends on it — exactly as precisely as an ordinary kilometer-based car's would be. The result: maintenance alerts arrive at their true real-world timing regardless of a car's odometer unit, and the distance-traveled reading reflects reality with no approximation.

Who this is for, and how to get started

This feature is built specifically for any rental company that owns — or is planning to own — mile-odometer imported cars within a fleet that's otherwise kilometer-based: there's no longer any reason to exclude these cars from the fleet, or to carry the risk of manual conversion and wrong figures. Every car is handled in its correct language from day one — on web and mobile, across the contract, billing, maintenance, and live tracking alike. Learn more about fleet tracking at KIRA or the KIRA Partners app.