Logistics: knowing where it is, what it cost, and who owes whom

The foundation is a consignment record that carries the full lifecycle: booking with agreed rate and terms, vehicle and driver allocation, loading with weight and item detail, LR generation, transit events, delivery with proof, and invoicing. Every state change is timestamped and attributed.

Position comes from telematics where vehicles are fitted, and from driver app check-ins where they are not. Both feed the same timeline, so a customer-facing status is available regardless of vehicle type — which matters for operators running a mix of owned and market vehicles.

Geofencing at loading points, delivery points and key transit locations gives automatic arrival and departure timestamps. That is what makes detention claims defensible: not an argument about when the vehicle arrived, but a record.

Most operators pay market-vehicle freight bills and bill customers on rate cards that have accumulated exceptions, seasonal variations and negotiated deviations. Reconciling every consignment against the correct rate manually is impossible at volume, so it is done by sampling or not at all.

We automate it. The applicable rate is determined by route, vehicle type, weight, customer and date from the rate card structure, and every bill — inbound and outbound — is compared against it automatically. Exceptions are presented for review with the difference quantified.

The findings are consistently substantial. Across recent engagements, automated reconciliation has surfaced between 0.8 and 3.1 per cent of freight spend as discrepancy, most of it small individual variances that were invisible at transaction level and material in aggregate.

The driver app is the most operationally sensitive piece of software in a logistics business, because the users are mobile, often working in poor connectivity, sometimes not comfortable with English, and under time pressure. An app they will not use produces no data.

We build for that reality: available in Hindi and Bengali as well as English, offline-capable so a delivery in a basement or a rural area still records, minimal typing with photographs doing most of the evidence work, and a workflow that follows the physical sequence of the job.

ePOD capture — signature, photographs of the delivered goods and any damage, receiver name and time, geotagged — replaces the paper POD that takes a week to return to the office and is frequently lost. That single change typically accelerates invoicing by five to nine days, which for a business running on working capital is worth more than the labour saved.

For 3PLs and distribution operations, the warehouse layer matters as much as transport. We build inbound receipt with quality and quantity verification, putaway with location management, picking with wave or order-based strategies, packing, and dispatch — with barcode or RFID scanning at each step.

The design priority is picking efficiency, because it dominates warehouse labour cost. Location assignment based on velocity, pick paths that minimise travel, and batch picking where order profiles allow it typically reduce picking time by twenty-five to forty per cent against a manual list-based process.

For multi-client 3PL operations we handle the billing complexity properly: storage charges by volume and duration, handling charges by transaction type, value-added service charges, and per-client reporting that stands up to a client audit.

A significant proportion of a logistics operator's customer service time is spent answering one question: where is my consignment. It is a question a system can answer perfectly and a person answers slowly.

We build customer portals and WhatsApp-based status where customers see their consignments, current position, expected delivery, POD documents and their account ledger. Adoption is typically high because the alternative is a phone call, and the effect on support load is immediate — clients routinely report over ninety per cent of status queries moving to self-service within two months.

The same channel handles proactive communication: dispatch notification, delay alerts with revised ETA, and delivery confirmation with the POD attached. Proactive notification reduces inbound queries further and materially improves the customer relationship, because a customer who is told about a delay is far less annoyed than one who discovers it.

Empty running is the single largest controllable inefficiency in most fleet operations. Reducing it requires knowing where vehicles will become available and what loads are coming, early enough to match them.

We build the visibility that makes matching possible: forward view of vehicle availability by location and time, inbound load requirements, and a matching interface for the planner. As with manufacturing planning, we support the planner's judgement rather than replacing it — the algorithm does not know that a particular driver refuses a particular route, and the planner does.

For operators running both owned and market vehicles, the same view supports the hire decision: whether to use an owned vehicle that is available or hire in, with the cost comparison computed rather than estimated.