Proof of delivery, route planning and WhatsApp updates for logistics

What customers now expect

A customer who ordered a sofa online gets a WhatsApp message when it leaves the warehouse, a link to track the van and a photo of the delivery at their door. Your B2B customers have noticed. The dealer waiting for 40 cartons of tiles now wants the same, and so does their accounts team when they dispute a short delivery three weeks later.

For most transporters, distributors and 3PLs, the gap is rarely a missing platform. It usually comes down to three practical things: proof of delivery that is captured at the door, routes that are planned in the system, and messages that go out without a coordinator typing each one.

Our recommendation

• Give drivers a simple app that captures a photo, signature or OTP, location and time at each drop, and works offline.
• Plan routes in software using clean addresses, vehicle capacity and delivery windows, and let dispatchers adjust the result.
• Send WhatsApp updates through the WhatsApp Business Platform using approved templates, triggered by events in your system.
• Feed delivery data straight into billing, so invoices go out the day goods are delivered.

Electronic proof of delivery

Paper PODs are the reason many logistics businesses bill late. The signed copy travels back with the driver, sits in a tray, gets scanned at month end and is sometimes lost. Every lost POD is a potential dispute.

A good electronic POD app captures:

• Who received it. Name, and an OTP sent to the consignee's phone, or a signature on the screen.
• What was delivered. Quantity against the delivery note, with reasons for any shortage or damage.
• Evidence. One or two photos of the goods at the drop point.
• Where and when. GPS location and timestamp, recorded automatically.

Design for the driver. Large buttons, local language labels, a flow that takes under a minute, and offline use because signal drops in basements, godowns and highway stretches. If the app is slow, drivers will skip it and fill details later from memory, which defeats the point.

Once PODs are digital, connect them to billing. A delivery marked complete can trigger the invoice in Tally, Zoho Books or your ERP the same day. For a business that today bills a week after delivery, that alone can shorten collection time noticeably.

Route planning that dispatchers trust

Route optimisation software solves what is called the vehicle routing problem: which stops go on which vehicle, in what order, within capacity and time limits. The maths is mature. Results disappoint for other reasons.

• Bad addresses. "Near Hanuman temple, behind the petrol pump" cannot be geocoded reliably. Build a customer location master with pinned coordinates, captured once by a driver at the first delivery and reused.
• Missing constraints. Vehicle capacity by weight and volume, unloading time per stop, customer receiving hours, no entry times for trucks in city limits. Leave these out and the plan looks good on screen but fails on the road.
• No override. Dispatchers know things software does not, like which customer pays only if the driver collects a cheque. Let them move stops, and record why.

Start by planning routes for one depot for a month and compare planned against actual. Use the gaps to fix data before expanding.

For goods that need an e-way bill, connect your dispatch to the e-way bill system so the vehicle number is updated automatically when a load is assigned.

WhatsApp updates done properly

Most customers in India read WhatsApp faster than email or SMS. Doing it properly means using the WhatsApp Business Platform through Meta or an approved provider.

• Templates. Messages you start, such as "Your order has been dispatched", must use templates approved by Meta. Write them clearly and keep variables to what you need: order number, expected time, tracking link.
• Opt in. Customers must agree to receive messages. Capture this at order or onboarding and store it.
• Pricing. Meta charges for template messages, with rates that vary by category and country. Send what is useful, not every status change.
• Triggers. Tie messages to events: dispatched, out for delivery, delivered with POD photo, delivery failed with reason and a reschedule option.
• Replies. Customers will reply. Route replies to a shared inbox so a person answers within your service hours.

Under the DPDP Act 2023, phone numbers and delivery addresses are personal data. Use them for the purpose the customer gave them for, protect them, and delete them under a retention rule.

Failed deliveries deserve their own flow

A failed delivery costs you a second trip, so record why it failed. Customer not available, address not found, shop closed, payment not ready, goods refused. Give drivers these as buttons, ask for a photo of the closed shutter or the gate, and send the customer a WhatsApp message with a reschedule option straight away. After a month, the reasons tell you which customers need a call before dispatch and which areas need a different time slot.

What it costs and how long it takes

For a mid sized distributor or transporter, a first phase with a driver app, POD, basic route planning, WhatsApp updates and a link to accounting usually takes 5 to 8 weeks. The larger costs are integration with your existing systems and the training and follow up with drivers in the first month.

When an off the shelf tool is enough

If you run fewer than ten vehicles on fixed routes, a subscription delivery app with built in WhatsApp messages will probably serve you well. Custom software makes sense when you need tight links to your own ERP, multiple depots, mixed fleets including hired vehicles, or customer specific rules that a standard product handles poorly.