Reduce Empty Miles Across a Logistics Fleet

From whichever signal your operation already generates, ranked by how much it can be trusted. Axle or body weight is best: the vehicle reports its own state and nobody has to remember anything. A delivery confirmation is next, since a completed drop with no subsequent collection implies an empty run onward. Dispatch status works where discipline is good. Where none of those exists for a leg it is reported as unknown rather than counted as empty, because inflating the deadhead figure would discredit the whole report.

From your own order book, yes. From the open market, no. If you have freight already booked that a vehicle going free could realistically collect, the match surfaces with position, remaining hours and equipment type all checked. What KO Fleetz is not is a load board or a brokerage. It will not source third-party freight, negotiate a rate, or connect you to a spot market. If your empty legs need external loads to fill them, this shows you which lanes to go looking on, and the looking is still yours.

Yes, and any tool implying otherwise is selling something. Freight flows are asymmetric. Regions consume more than they produce, or the reverse. Specialised equipment has nothing to carry on the return, and a tanker cannot pick up pallets. The useful work is separating deadhead that reflects a real market from deadhead that reflects a dispatcher not knowing where his vehicle was. The module labels the structural lanes explicitly, because a shortlist people believe beats a long list they ignore.

Route optimisation works within the jobs you already have: given these stops and these vehicles, what is the best sequence and path. This module questions the jobs themselves. It asks why a vehicle is running three hundred kilometres with nothing in it, and whether different work existed that would have changed the answer. Optimisation makes the empty leg shorter. Empty-mile reduction tries to stop it being empty. They complement each other, and optimising a badly balanced order book just produces efficient waste.

No, though they improve it. Without weight data the loaded flag comes from delivery confirmations and dispatch status, which is enough for corridor-level analysis and for spotting where deadhead concentrates. What weight adds is trust and coverage: it catches the part-load return that status alone records as loaded, and it fills in legs where nobody updated anything. If you already run axle sensors or a weighbridge feed for compliance, connecting them costs little and sharpens the classification considerably.

Empty running is usually the largest single reason a run loses money, so the two are read together. Trip profitability tells you a corridor returns less than it should. This module frequently explains why: the outbound rate is carrying a return leg nobody pays for. Fix the deadhead and the lane's margin moves without touching the rate. If it cannot be fixed, the return leg is a genuine cost of serving that corridor and belongs in the price, which is a far better-informed conversation to walk into.