Operations systems for logistics businesses in India and the UAE: trip and consignment tracking, vehicle and driver management, COD reconciliation, fuel and expense control, and client billing that matches what actually moved.
Where does a logistics company’s truth actually live?
Scattered across a diesel receipt in a driver’s pocket, a POD photo on someone’s personal phone, a rate chart from 2023, and a billing clerk reconstructing trips at month-end from memory and WhatsApp scrollback. The trucks are real, the work is real — the record of the work is folklore. And in a trade running single-digit margins, folklore is expensive: revenue leaks through undercharged detention, unbilled extra points, COD that surfaces slowly, and fuel jugaad nobody can prove or disprove. The leaks are individually chhota; annually they’re the difference between profit and “kya karein, market slow hai.”
The market isn’t slow. The paperwork is leaking — and unlike the market, the paperwork is fixable.
What does the logistics build include?
- Trip lifecycle, end to end. Booking to loading to POD, every consignment’s status real rather than remembered. The trip is the unit of truth; everything else — billing, fuel, COD, driver settlement — hangs off it.
- The driver app, built for the actual road. Offline-first, because highways don’t do 5G — the field-operations platform underneath assumes disconnection as the default. POD capture with photo and signature, expense entry with receipts photographed, COD collection logging at the doorstep. Three buttons, big targets, Hindi and regional labels; if a driver uses WhatsApp, this is easier.
- The COD ledger. Collected versus deposited versus settled — per driver, per client, reconciled daily with an ageing clock on cash-in-pocket. The reconciliation discipline applied to the trade’s most trust-dependent flow; the awkward conversations get replaced by a report.
- Billing that clients can’t dispute. Rate cards with slabs, detention computed from timestamps, extra points charged from the trip record, POD attached to the invoice. Undercharging ends because the bill is generated from what happened, not reconstructed from what’s remembered — and disputes shrink when evidence travels with the invoice.
- Fuel and maintenance control. Consumption against norms per vehicle per route, outliers flagged without accusations — the numbers ask the questions, which keeps the workshop honest and the conversations civil. Maintenance schedules tracked so breakdowns become rarer than excuses.
- Client and vehicle P&L. Which clients, which routes and which vehicles actually make money — computed from real trips, so the next rate negotiation starts from arithmetic instead of instinct.
Why offline-first is non-negotiable here
Because the network dies exactly where the work happens — the highway stretch, the warehouse basement, the border queue. A logistics app that needs connectivity is a demo, not a tool. Everything in the driver app captures locally and syncs when the network returns, with conflicts resolved by rule; the DR Congo field-ops education built this instinct — systems that must survive infrastructure that fights back — and Indian highways keep it honest. The office console shows live-enough truth with exception queues, and the evening settlement closes each driver’s day: trips, expenses, COD, done. Ekdum barobar, every night, without a single “network nahi tha” excuse mattering.
What does the first quarter recover?
The leak audit’s findings, systematically. Detention and extra points billed because timestamps exist. The COD ageing gap shrinking as the deposit clock ticks visibly. Fuel outliers regressing to norms once measurement exists — the mere presence of the report does half the work. And the month-end billing scramble replaced by invoices generated the day trips close, which improves cash flow before it improves anything else. Diesel bachao, margin badhao — but the deeper change is calm: the owner stops carrying the whole operation’s truth in their head, because the system carries it in writing.
Related reading
/products/field-operations — the platform underneath · /blog/reconciliation-at-scale — the COD discipline · /industries/marketplaces — the settlement sibling · /products/company-os — the owner’s one screen
The one-truck test
Pick one truck, one month — I’ll run the leak audit on the first engagement and show you the rupee figures line by line. /contact; the audit usually pays for the system before the rollout finishes.
Questions I actually get
Can you integrate the GPS trackers we already have?
Yes, where trackers exist their feeds join the trip record; where they do not, the driver app's check-ins cover the gap. The system is deliberately tracker-agnostic — the operational truth comes from the trip lifecycle and the documents, with location data as corroboration rather than the foundation.
We run India-UAE corridor operations. Does one system handle both?
Yes — per-entity books with GST on the Indian side and FTA VAT on the UAE side, consignments crossing between them with the paperwork trail intact. Corridor operators are a natural fit; the two-tax-brain pattern is the same one the retail ERP runs for cross-border chains.
Our drivers will not use an app. Honestly, will this work?
They use WhatsApp, which means they use exactly this level of complexity: three buttons, camera, works offline, Hindi and regional labels. The app is built to that standard and field-tested against it — and drivers adopt fastest once they realise the POD photo ends the damage-claim arguments that used to land on them.
How does COD reconciliation actually close the loop?
Collection logged at delivery with amount and mode, deposits matched against collections per driver per day, and client settlements drawn from the same chain — so cash in a driver's pocket is a tracked state with an ageing clock, not a mystery. The gap between collected and deposited is the report owners check first and soonest.
Can clients see their own consignments?
Yes — a client view with consignment status, PODs and invoice-ready data, which quietly kills the where-is-my-shipment call volume and turns billing disputes into drill-downs. Transparency you can prove is a retention feature in logistics exactly as it is in marketplaces.
What is the fastest first win?
The leak audit: one month of one vehicle's trips reconstructed in the system — fuel against norms, billed versus billable charges, COD chain, detention uncharged. It takes days, names rupee figures, and decides the rollout order better than any demo. Most operators find the system's annual cost hiding in that one month.