Skip to content

Returnable Asset Tracking That Turns Lost Crates Into a Visible Balance

Every crate, can, cage and pallet that leaves on a delivery is meant to come back, and a fair share of them quietly does not. KO Fleetz records what went out with each trip and customer, what returned, and what is still outstanding — so the slow bleed of missing containers becomes a balance you can chase, not a number you discover at stocktake.

The crates go out counted and come back guessed

A milk round leaves the depot with two hundred crates and forty cans stacked on the deck. Everyone knows the truck went out full. What nobody can tell you at the end of the week is how many of those units are still sitting in a shop's back room, a housing society's gate, or the footwell of a vehicle that has since been reassigned. The load-out is counted because the warehouse insists on it. The return is eyeballed by a tired driver reversing onto the dock at nine at night.

So the loss is real but never attributed. Crates walk off one route at a time — two here, five there, a stack a shopkeeper swears he already gave back. No single day looks like a problem, which is exactly why the problem never gets owned. The crate is worth a couple of hundred rupees and the can rather more, and multiplied across a season of daily rounds the unreturned pile is a genuine line of lost capital that shows up only when procurement is asked to buy replacements again.

By the time it surfaces it is a write-off, not an investigation. The annual count comes in short, someone approves a fresh purchase order, and the shortfall is booked as breakage and shrinkage because there is no record granular enough to argue otherwise. The one customer who is quietly hoarding forty cages and the one route that leaks every week are hidden inside a single fleet-wide number that nobody can break apart.

Give every returnable a balance, per customer and per route

KO Fleetz treats a returnable unit the way a ledger treats money. What leaves on a trip is a debit against the customers on that route; what comes back is a credit; and the difference is an outstanding balance that carries forward day after day instead of resetting to zero every morning. Crates, cans, cages, pallets, trays, kegs, gas cylinders and milk cans are each their own asset type with their own count, because a shortage of forty trays is a different conversation from a shortage of forty gas cylinders.

The balance is held where you can act on it: against the customer and against the route. When a distributor's account shows sixty crates outstanding and climbing, that is a number the sales person can raise on the next visit while it is still six weeks old rather than six months. When one route consistently returns fewer cages than it carried out, that is a pattern the depot supervisor can see before it becomes a purchase order.

Two honest limits, stated up front. This is not container management — that feature handles shipping containers on the freight leg, the numbered forty-foot and twenty-foot boxes with seals and a port at one end. Returnable asset tracking is the opposite scale: the many small reusable units that cycle with everyday deliveries and are counted, not scanned as unique boxes. And it does not manufacture certainty from nothing. If a driver records a return count that is wrong, the balance is wrong until it is reconciled — the platform makes the disagreement visible and dated, which is more than a spreadsheet at month end can do.

Capabilities

What KO Fleetz returnable asset tracking gives your team

  • Load-out and return counts per trip

    What left the depot and what came back is recorded against the specific trip that carried it, so a route's crate movement is a paired figure instead of a load-out with no matching return.

  • Outstanding balance per customer

    Each customer carries a running count of what they still hold, by asset type, so a distributor sitting on sixty crates is a number on their account rather than a suspicion the delivery driver mentions occasionally.

  • Asset types counted separately

    Crates, cans, cages, pallets, trays, kegs, cylinders and milk cans each keep their own tally, because a returnable steel can and a plastic tray have very different replacement costs and very different return rates.

  • Per-route leakage view

    Return rates roll up by route and round, surfacing the corridor that consistently brings back fewer units than it carried out before the shortfall reaches the annual count.

  • Return against proof of delivery

    The returned-empties count is captured at the same doorstep event as the delivery, so the crates handed back are recorded when and where the drop happened, not reconstructed at the dock hours later.

  • Where the pool is sitting

    The platform shows how much of your returnable pool is in circulation versus outstanding at customers, so a fleet buying new crates can first see how many it already owns but cannot find.

  • Ageing on outstanding units

    An outstanding balance carries the date it went out, so a crate held two weeks reads differently from one held four months, and the follow-up can be prioritised by how stale and how large the debt is.

  • Recirculation, not annual write-off

    Because every unit is expected back and its absence is visible daily, the returnable pool is managed as an asset that cycles rather than an inventory that quietly depletes and is topped up once a year.

How it works

How KO Fleetz does it

  1. Step 1: Count what goes out

    At load-out, the returnable units on the trip are recorded by type and quantity against the route and its customers. This is the debit side of the ledger, and it reuses the count the warehouse already does rather than adding a new one.

  2. Step 2: Record what comes back at the drop

    As each delivery is completed, the empties handed back are entered against that customer, at that stop. Returns are captured where they happen so the credit lands on the right account instead of being averaged across the round.

  3. Step 3: Carry the balance forward

    Whatever did not return stays as an outstanding balance on the customer and the route, ageing from the day it went out. It does not reset overnight — a crate is owed until it comes back or is written off deliberately.

  4. Step 4: Chase and reconcile

    Sales and depot staff work the outstanding list, collecting empties, correcting miscounts and settling disputes against dated records. Every reconciliation is logged, so an adjusted balance shows why it changed.

Outcomes

What changes

Outstanding empties owed, not a fleet-wide shortfall
Per customer
Visibility of the balance, instead of an annual stocktake
Daily
Crates, cans and cages counted as separate pools
By asset type
Every outstanding unit ages from the day it left
Dated

Frequently asked questions

Plain counts are the default and are enough for most dairy and FMCG fleets. You record quantities by asset type — two hundred crates out, one hundred and ninety back — and the balance is kept at the customer and route level rather than for each individual unit. Barcodes or RFID become worth it only when you need to know which specific crate is where, which is rarely the question with low-value units that cycle daily. Tagging thousands of two-hundred-rupee crates usually costs more than the leakage it prevents, so KO Fleetz is built to work honestly from counts and to use unique IDs where you genuinely have them.

They operate at opposite ends of the scale. Container Management handles shipping containers on the freight leg — the individually numbered twenty- and forty-foot boxes with seals, a size, a direction and a port at one end, where each box is a booking in its own right. Returnable asset tracking is about the many small reusable units — crates, cans, cages, pallets, trays, kegs, cylinders, milk cans — that go out with ordinary deliveries and are counted in bulk, not tracked as unique sealed boxes. If you are moving containers to and from a port, that is Container Management. If you are bleeding crates on a milk round, this is the feature.

Every unit that goes out on a trip is debited to the customers on that route, and every unit handed back is credited to the customer it came from. The difference is an outstanding balance that carries forward day after day rather than resetting each morning. So a distributor who keeps taking delivery and returning slightly fewer empties than they received accumulates a visible, dated debt — sixty crates outstanding, the oldest of them three weeks old — which the sales person can raise on the next visit instead of discovering it at the annual count.

No, and keeping them separate is the point. A unit that comes back broken has returned; it is a maintenance or disposal question, and it should clear the customer's outstanding balance and move to a damaged count rather than stay recorded as owed. A unit that never comes back is a genuine loss and stays on the balance until it is collected or written off. Merging the two would let real losses hide behind breakage, which is exactly how the shortfall becomes an unarguable write-off today. The platform records a return as returned-good or returned-damaged so the two never blur.

It replaces an argument about memory with a dated record. Every load-out and every return is logged against a specific trip, customer and day, so a dispute is worked against entries rather than impressions — you can see the drop where the counts disagree instead of debating a season's total. It does not make the customer's claim automatically wrong, and it does not make yours automatically right; a miscount at the doorstep is still a miscount. What it gives you is a specific date and quantity to reconcile, and every correction is logged with why the balance changed, so the settled figure has a trail behind it.

No. Returns are captured as counts entered at the delivery, typically on the same device and at the same doorstep event as proof of delivery, so a driver enters how many empties came back rather than scanning anything. Where you already run handhelds or scanners you can use them, and where a unit does carry a barcode it can be scanned, but the feature does not assume any of that. It is designed to work from the count a driver can do with a mobile phone at the gate, because a system that demands scanning hardware for a two-hundred-rupee crate is a system that quietly stops being used.

Find out how many crates you actually own

Give us one route's load-outs and returns for a month, and KO Fleetz will show you the outstanding balance building up per customer — and how much of your pool is unaccounted for.