Logistics Platform Development

Every logistics platform we have been asked to rescue failed in one of four places. Not in the tracking map — the tracking map always works. It failed in the money, the network, the driver's phone, or the paperwork.

COD reconciliation is where logistics companies actually lose money

Cash on delivery is still a large share of Indian ecommerce parcels, and every one of those rupees passes through a delivery executive, a hub cashier, a bank deposit slip and a remittance file before it reaches the merchant. Each handoff is a place where the number can change.

The systems that fail here treat COD as a status flag on a shipment. The systems that work model it as a ledger: a cash liability is created the moment the executive marks delivered, it sits against that executive until it is deposited, the deposit is matched against a bank statement line, and the merchant remittance draws from settled cash only. Every entry is double-sided and immutable — a correction is a new reversing entry, never an update. That is what lets you answer, at 4pm on a Tuesday, exactly how much cash is in the field, whose hands it is in and how long it has been there. Without that, shrinkage is invisible until the quarterly audit, and by then the trail is cold.

Hub-and-spoke is a graph problem, and most software pretends it is a list

A parcel does not go from A to B. It goes from a pickup to a first-mile hub, onto a line-haul trip to a regional sortation centre, to a destination hub, into a delivery route with sixty other parcels, and possibly back again on an RTO. Software that models a shipment as having "an origin and a destination" collapses the moment you ask it a real question: which bags are on this trip, what is the bag seal number, which parcels missed the connection and what is the new ETA for each of them.

We model the bag, the trip, the leg and the scan as first-class entities. A scan is an immutable event with a location, a timestamp, a device and a person. The shipment's state is derived from its scans, never stored and updated in place. This costs slightly more to build, and it is what makes exception handling — which is the entire job of a logistics control tower — actually possible.

The driver app is offline-first or it is a liability

The delivery executive's phone will lose signal in a basement warehouse, a lift, a gated society and most of rural India. If the app requires connectivity to record a delivery, the executive will record it later from memory, or not at all, and your data is now fiction.

So: a local database as the source of truth on the handset, every action queued as an immutable mutation, and a sync that reconciles on reconnection with an explicit conflict policy. The electronic proof of delivery — signature, photo, OTP, geotag — is captured and stored locally, then uploaded when there is bandwidth, with the timestamp of capture rather than the timestamp of upload. That distinction has decided more than one payment dispute in our clients' favour.

The paperwork is not optional and it is not simple

An e-way bill is required for most consignments above ₹50,000, it has a validity tied to distance, it must be extended before it lapses, and a vehicle stopped with an expired one is a detention with a penalty attached. Part-B updates on a vehicle change. FASTag transactions have to be reconciled against trip cost or the fuel and toll budget is a guess. We build these as integrations with retry, idempotency and an alert when a bill is approaching expiry — not as a screen where somebody in operations is expected to remember.