Freight Management Software That Follows the Consignment, Not the Vehicle
A booking is a promise made to a customer: this much cargo, from here to there, at this rate. KO Fleetz keeps that promise as a record of its own, carries it through the lorry receipt and the manifest, and closes it with a freight bill that nobody had to reconstruct from memory.
The booking register and the vehicle register never meet
Somebody in the office takes the call and writes the consignment into a register. A rate is agreed, sometimes on the phone, sometimes in a way that will be argued about later. The LR book comes out and a number is written by hand. The manifest is a sheet the loader fills in at the gate. Four artefacts, four handwritings, and the only thing linking them is the memory of whoever was on duty.
The gap opens at billing. The customer queries a rate, and answering the query means finding the booking slip, the LR carbon copy and whatever the loader wrote, then assembling a version of events that everyone can live with. Some of those bills go out weeks late because nobody could locate the paper. Some never go out at all, and the fleet only notices when the year is being closed.
Underneath sits a confusion the trade lives with: the consignment and the vehicle movement get treated as the same thing. They are not. One vehicle can carry several part-load consignments, each booked separately at a different rate for a different customer. One large booking can take three vehicles across two weeks. Force them into a single record and one of them is always being distorted to fit the other.
The booking is the promise. The trip is the vehicle keeping it.
In KO Fleetz a booking exists from the moment it is taken, in draft, before anyone has decided which vehicle will run it. It holds the customer, the load type, the vehicle type the cargo needs, the container where there is one, and the pricing that was agreed. It moves to confirmed when the commercial side is settled, and stays visible in progress until every consignment inside it has actually been delivered.
The lorry receipt is what the booking turns into once the cargo has a vehicle behind it. KO Fleetz gives each LR its own state — confirmed, assigned, in transit, delivered — because a single booking's consignments do not all move at once and pretending they do is how part-load operators end up billing wrong. The manifest then answers the other question: not what did the customer ask for, but what is on this vehicle right now.
The border with trip management is deliberate and worth stating plainly. This module never dispatches anything, never plans a route and never tells you where a truck is. KO Fleetz owns the commercial object and its paperwork; the trip module owns the vehicle, the driver, the stops and the running. They reference each other, which is precisely why a freight bill can be raised without anybody retyping what was delivered.
Capabilities
What KO Fleetz Freight Booking Software does
The booking as a first-class record
A consignment is captured before a vehicle is chosen, and carries its customer, cargo, agreed rate and current state from draft through to completion.
Lorry receipt with its own lifecycle
KO Fleetz tracks each LR separately as confirmed, assigned, in transit or delivered, so consignments inside one booking are never forced to move on the same clock.
Manifest per vehicle
What is physically loaded on this vehicle for this run, assembled from the LRs riding on it rather than written out again at the gate.
Full load and part load handled differently
A part-load vehicle carries several customers at several rates. Load type is a property of the booking, so billing does not have to guess afterwards.
Container and equipment detail
Twenty-foot and forty-foot equipment is recorded against the consignment it carries, which is what makes container-level history possible later.
Pricing held where it was agreed
In KO Fleetz the rate lives on the booking from the day it was quoted, so the freight bill reflects what was promised rather than what someone recalls promising.
Freight bill raised from the LR
KO Fleetz raises the freight bill from the consignment record and its delivery state, which is how a bill stops depending on paper arriving back from a cab.
Import and general cargo streams
Import movements carry different documentation expectations from general cargo, and the booking type keeps them separable instead of blended into one list.
How it works
How KO Fleetz does it
Step 1: Take the booking before you have a vehicle
Customer, cargo, load type, equipment and rate are captured in draft. Nothing about the vehicle is required yet, because none of it has been decided.
Step 2: Raise the lorry receipt
Once the consignment has a vehicle behind it, the LR is issued against the booking and starts its own lifecycle rather than inheriting the booking's.
Step 3: Build the manifest for the run
The LRs travelling on one vehicle are assembled into a manifest, which is the document the gate, the driver and the receiving end actually need.
Step 4: Bill against what was delivered
The freight bill is raised from the LR's delivery state and the booking's agreed pricing. The dispute, if there is one, has records behind it.
Outcomes
What changes
- The rate is recorded the day it is agreed
- Booked, not guessed
- Each LR moves on its own clock
- Per consignment
- Part-load customers stop sharing one record
- Separable
- The freight bill has paper behind it
- Billable
Explore in detail
Every freight booking software capability
Each of these is a capability page in its own right, with the workflow, the limits and the awkward questions answered.
What sits either side of a booking
Upstream, orders arrive from customer portals, shipper TMS platforms, email and the phone, and the phone is not going away — so manual capture is treated as a first-class path rather than a fallback nobody designed. Downstream, freight bills hand off to accounting and GST filing systems, and the e-way bill module reads the consignment rather than asking for it again. Container and import movements touch shipping line schedules, CFS and port systems where those expose anything readable, which in Indian ports varies by terminal and by year. Customer-side, delivery status can be published back to a shipper portal so the LR state answers the where-is-my-cargo call without a person doing it. The honest constraint is upstream, not downstream: many Indian shippers still send an order as a WhatsApp message, and no integration fixes that.
Explore integrationsFrequently asked questions
A booking is what a customer asked for and agreed to pay. A trip is a vehicle going somewhere. They diverge constantly. Three part-load bookings ride one trip, each billed to a different party. One heavy booking takes four trips over a fortnight. Keep them as one record and you must either bill the trip, which is wrong for part load, or dispatch the booking, which is wrong for anything large. In KO Fleetz they are separate objects that reference each other.
No on both counts, and it is worth being blunt. There is no general ledger here, no GST return filing, no rating engine that prices a lane from a tariff matrix. The freight bill this module produces is a transport document that hands off to your accounting system. What it does own is the stretch nobody else covers properly: the consignment from the day it was booked to the day it was billed, with the LR and the manifest in between.
Yes, and most operators should for at least the first year. An LR number is referenced by customers, by consignees and sometimes by people at a check post, and changing the series mid-year creates confusion that has nothing to do with software. The module can carry an existing series, and it can run a new one alongside. What it will not do is let two consignments claim the same number, which is a failure the paper book permits quite easily.
That is the case the design is built around. KO Fleetz makes each consignment its own LR with its own rate, its own consignee and its own delivery state, and the manifest simply records which of them are on the vehicle. Delivering the third drop closes the third LR and nothing else. Full-load work is the easier case and is handled as one booking, one LR, one bill.
Rates change. A detention charge appears, a customer renegotiates, a route turns out longer than quoted. The booking's pricing can be amended, and the amendment is a recorded change rather than an overwrite, so the bill and the original quote can both be produced when the query arrives. The module does not decide whether a change is justified. It makes sure the version history exists when two people remember the call differently.
Only as a status, not as a position. An LR marked in transit means the consignment has left and has not been recorded as delivered. That is a document state somebody set, not a satellite fix. Actual location comes from the tracking module, and delivery evidence from proof of delivery. If a vehicle has no tracker fitted, the LR state is all you get, and the platform will not dress that up as visibility.
See your booking register as one record
Bring a week of LR books and one customer's disputed bill. We will show you in KO Fleetz where the paper trail breaks and what closing it looks like.