Container Tracking Software for the Road Leg of the Box
A container is not simply cargo with a number stencilled on it. It is a box with an owner, a seal, a size, a direction and a clock running against it. KO Fleetz records the container as part of the booking that moves it, joined to the vehicle, the LR and the trip that ran the leg.
Everything about the box is in someone's WhatsApp
Container work runs on messages. The container number comes from the CHA. The seal number is a photo. Pickup is confirmed on a call, the gate-in gets acknowledged with a thumbs-up, and the empty return depot changes at four in the afternoon because the line said so. None of this is written down anywhere that survives the week, and the person holding all of it is the one operator who does not take leave.
The vocabulary alone defeats a generic fleet system. A 40 ft and a 20 ft are not merely two vehicle types; they are different bookings, different rates, different chassis and different problems. Import and export legs run in opposite directions with opposite paperwork. The box you deliver full is the box you collect empty, and it is the same asset in both cases even though nothing in your system says so.
So the office keeps two records of one job. The transport system knows a truck went from a port to an industrial estate. The container details — number, size, seal, line, direction — live in a spreadsheet the CHA coordinator maintains. When a customer asks which vehicle carried a specific box last Tuesday, someone has to join those two by hand, and the join is done from a recollection of who was driving.
The box becomes a field, not a message
A container in KO Fleetz is a record on the booking that moves it. Container number, size, type, seal and the direction of the leg sit as data, joined to the LR raised against the consignment and the vehicle that carried it. The customer's question about which truck ran which box last Tuesday becomes a search, and the CHA coordinator's spreadsheet stops being load-bearing.
Size and direction stop being footnotes. Bookings carry vehicle type, so 40 ft and 20 ft movements are countable as what they are, and an import-heavy month reads as an import-heavy month on the booking analysis rather than as an impression. That matters, because the two directions consume your fleet differently and a mix that is drifting is worth knowing about before the chassis are wrong for the work.
Now the honest part, and please read it before the demo. This is not a terminal operating system. KO Fleetz does not talk to the port. There is no integration pulling gate-in and gate-out events, no berth schedule, no line-level EDI, no automatic free-day countdown from the shipping line. The container is tracked as part of your booking and your trip, which is the road leg — the part you actually control. Where the box sits inside the terminal is the terminal's system to answer, and any vendor claiming otherwise should be asked to show it working.
Capabilities
What KO Fleetz container management gives your team
Container as a booking record
Number, size, type and seal are held against the booking that moves the box, so the details survive the chat thread they arrived in.
20 ft and 40 ft as real distinctions
Booking by vehicle type separates the two, so your mix of box sizes is a figure on the dashboard instead of something the yard supervisor senses.
Import and export legs
Booking type records which direction the box is running, because the paperwork, the rate and the pain points differ sharply between the two.
Seal number on record
The seal is captured against the container rather than living as a photo in a chat, which is what a tamper dispute at the consignee's gate turns on.
Box joined to vehicle and trip
Which truck carried which container on which day is a query against the record, not a reconstruction from the roster and somebody's memory.
Laden and empty movements
The full delivery and the empty return are recorded as the movements they are, so the leg that earns nothing is at least visible as work done.
Container LR and manifest
The consignment note and the loading document are raised the same way as any other freight, so container work is not a parallel process running on the side.
Detention exposure on the road leg
Waiting at the factory gate and at the depot shows against the trip, which is the portion of the free-day clock your own operation is responsible for.
How it works
How KO Fleetz does it
Step 1: Book the movement with the box
Container number, size, type, seal and direction go on the booking at the point it is raised, from whatever the CHA sent, typed once.
Step 2: Raise the LR and allot the vehicle
The consignment note and the truck are put against it like any other load. Container work stops being a special case with its own private process.
Step 3: Run the leg
The trip carries the movement — pickup, delivery, empty return. Waiting time and route sit on the trip record, not in the coordinator's recollection.
Step 4: Close and bill
The delivered leg closes the LR and the freight bill is raised against it, per container or per trip, at the rate held for that customer and lane.
Outcomes
What changes
- Number, size and seal held as data, not as messages
- Written down
- Which vehicle ran which box, answered from the record
- Searchable
- Import against export, 40 ft against 20 ft, as figures
- Countable
- The part of the container journey you actually control
- Road leg
Frequently asked questions
No, and we would rather lose the deal than let you discover it afterwards. There is no connection to a terminal operating system, no gate-in or gate-out feed, no line EDI and no automatic free-day counter. What KO Fleetz records is the road leg: the booking, the box on it, the truck that carried it and the trip that ran it. If your requirement is terminal visibility, you need a system that has actually built those connections, and you should ask any vendor claiming it to demonstrate a live feed rather than a screenshot.
It means the container is a field on your booking rather than a message in a chat. Number, size, type, seal and direction are recorded and joined to the LR, the vehicle and the trip. If the truck carries a tracker, you also get position on the leg from the tracking module. Put plainly: you can answer where your truck is and which box is on it. You cannot answer where the box is once it is inside the terminal, because nothing tells us.
As a movement in its own right, because that is what it is. The box is delivered laden, the container is destuffed, and the empty goes back to the depot the line nominated — often a different depot from the one everyone assumed on Monday. That return consumes a truck, a driver and a day, and it earns whatever your rate structure says it earns, which is frequently very little. Recording it as a trip at least means the cost of the empty leg is not invisible when you price the laden one.
Not as a countdown from the line, no. Demurrage and detention clocks are set by the shipping line and the terminal against dates we have no feed for, so any counter we showed would be a number typed in by your own staff and then trusted like a fact. What you do get is the road-leg timing: when your vehicle reached the factory, how long it waited, when it left. That is the portion of the clock your operation controls, and it is the portion you can actually argue about with a customer.
In the system it is booking data, and operationally it is most of the conversation. The two sizes take different chassis, price differently, load differently and behave differently on a lane. Because bookings carry the type, the split is a number you can look at rather than a feel for the yard. What KO Fleetz does not do is plan around it. It will not tell you to buy more skeletal trailers or which chassis to allot tomorrow morning. It shows you the mix and leaves the call with you.
It is the same Bookings module and deliberately so. A container movement raises a booking, an LR and a manifest exactly like a general cargo consignment; it simply carries container fields as well. That matters because most Indian transporters do both, often with the same trucks and certainly with the same office, and a fleet system that forks into two parallel processes for the two kinds of work gets abandoned on one of them within a quarter.
See container work on the same record as everything else
Bring your CHA coordinator's spreadsheet and a week of box movements. We will show you the same jobs as bookings, with the road leg attached.