The product
One inventory.
Every moving cost in it.
QuamBase is not a tracking screen bolted onto a spreadsheet. It is a single record of what your fleet did, priced as it happens, and closed against what you billed.
Capture
Trips, diesel, advances, tolls and tyres enter once, at the moment they happen.
Price
Every candidate route carries a resistance score in rupees before a wheel turns.
Commit
One line reaches the driver, with the arithmetic that justifies it attached.
Reconcile
Kilometres run and kilometres billed close on the same figure, every day.
Route resistance
The shortest road is rarely the cheapest one.
Maps optimise for distance and time because those are the only two things a map knows. A fleet pays in tolls, diesel, idle hours and driver batta. Resistance scoring prices all four before dispatch, so the decision is arithmetic rather than habit.
What goes into a score
Five inputs, one number
| Input | Weight | Source |
|---|---|---|
| Toll cost | 0.28 | FASTag ledger |
| Fuel burn at grade & load | 0.26 | Your own mileage history |
| Expected idle hours | 0.21 | Time-of-day congestion |
| Detour distance | 0.15 | Road network |
| Driver batta for the time | 0.10 | Your batta policy |
Why it holds up
It learns from your trucks, not a model fleet.
Fuel burn is drawn from the mileage your vehicles actually returned on that corridor, at that load, in that season — not a manufacturer figure. A 2016 tipper and a 2023 tractor-trailer get different numbers on the same road, because they earn different numbers on the same road.
Every committed route keeps the arithmetic that chose it. When a customer disputes a detour six weeks later, the answer is a record, not a recollection.
Reconciliation
Carried, posted, lost.
Most fleets discover the gap between what moved and what was billed at month end, when the trail has gone cold. QuamBase closes that gap daily, because the trip sheet the driver completes is the same record the invoice is raised from.
01
One record, not three
The dispatch note, the trip sheet and the invoice are three views of one row. There is no re-keying step in which a figure can change.
02
Daily close, not monthly
Unmatched legs surface the same evening, while the driver still remembers the halt and the slip is still in the cab.
03
Exceptions, not reports
You are shown the twelve rows that disagree, not the two thousand that agree. Reconciliation becomes a short list, not an audit.
Modules
What you get on day one.
Dispatch & trip sheets
Indent → allocation → committed route → POD, in one thread. The driver receives the route on WhatsApp and closes the leg with a photo. The office never types a trip sheet again.
Diesel & mileage
Every fill matched to a trip, a tank and a card. Mileage drift flagged per vehicle, per driver and per route, with the comparison held against that vehicle’s own history.
Driver advances & batta
A running ledger per driver covering advances, batta, deductions and settlements. Month-end becomes a confirmation rather than a reconstruction.
Tyres & maintenance
Tyre life tracked by position and axle, rotation and retread history, service due by kilometre rather than by calendar month.
Billing, GST & e-way
Invoices raised off the closed trip record with GST and e-way bill fields already populated. Exports to Tally and Zoho Books on your schedule.
P&L by vehicle
Profit by vehicle, route, customer and driver — computed from the same numbers that ran dispatch, so there is no second version of the truth.
See it on your own routes