A large FMCG distributor in an Indian metro runs a complex daily logistics operation. 300–600 retail orders arrive via WhatsApp by 10pm. Load plans must be ready by 4am. Vehicles depart between 5am and 8am. Deliveries run until mid-afternoon. Each stage of this operation has inefficiency. In most distributors, these stages run independently — order capture on WhatsApp managed by one team, load planning on spreadsheets by another, routing by the most experienced driver. The distributor who fixes only one stage recovers a fraction of the available improvement. The distributor who connects all four stages recovers most of it. --- The Four-Stage FMCG Distributor Logistics Chain Stage Inputs Outputs What Breaks When Manual WhatsApp order capture Retailer WhatsApp messages Confirmed ERP sales orders with pricing and credit validation Orders delayed 4–6 hours, credit breaches at month end, 12–18% entry error rate Load building Confirmed orders, vehicle fleet specs, SKU constraints Vehicle load plans with weight, volume, temperature zone, and load sequence 70–80% vehicle utilisation, temperature violations, load sequence ignored Route optimisation Load plans, retailer addresses, time windows, driver shift times Sequenced delivery routes minimising total cost 15–25% excess distance, missed time windows, driver overtime Proof of delivery Driver delivery completion, customer signature, exceptions Digital POD records, real-time exception alerts Paper POD, exceptions discovered at end of day, disputes unresolved Fixing each stage independently delivers partial improvement. Connecting them delivers the full improvement — because the output of each stage is the input to the next. --- The Order Capture Foundation For an FMCG distributor, the logistics chain starts at order capture — not at the depot. The load plan cannot be built until orders are confirmed. The route cannot be optimised until the load plan is finalised. Every hour of delay in order capture compresses the optimisation window. Distributors running manual WhatsApp processing typically finalise order entry by midnight. Load planning runs overnight. Route planning happens at 4am. The margin for error is minimal. Automating WhatsApp order capture means orders enter ERP within 2 minutes of receipt — giving the load planning system 6 hours instead of 1 hour before vehicles depart. --- Load Building for FMCG Distributor Fleets FMCG distributor loads are complex. A single vehicle may carry ambient dry goods, chilled dairy, beverages, and personal care products — each with different storage requirements and each for multiple retailers along the route. SKU Category Storage Requirement Load Constraint Ambient dry goods (biscuits, snacks) Room temperature Stacking limit — fragile products on top Chilled dairy (milk, yoghurt, paneer) 2–8°C refrigerated compartment Temperature zone — cannot mix with ambient Beverages (soft drinks, juices) Cool or ambient depending on SKU Weight — heavy per unit, load-off sequence critical Frozen products -18°C freezer compartment Strict temperature zone — dedicated compartment only A load plan that ignores these constraints produces delivery rejections. A chilled product in the ambient section arrives warm. A fragile product at the bottom of a heavy load arrives damaged. Automated load building matches each order's SKU list against the vehicle's compartment specifications — by design, not by chance. --- Route Optimisation for Indian FMCG Distribution Route optimisation for FMCG distributors in Indian metros must account for three India-specific constraints that generic routing tools often miss. Market area traffic patterns. Wholesale market areas — Khari Baoli in Delhi, Masjid Bunder in Mumbai, KR Market in Bengaluru — are accessible early morning and heavily congested from 9am. Distributors routing without time-of-day constraints send vehicles into these markets at 10am and lose 45–90 minutes in congestion. Routing these stops for 6am–8am recovers that time at zero additional cost. Retailer receiving windows. Kirana stores receive in the morning. Modern trade has fixed receiving slots. A route that ignores these windows produces rejected deliveries — which cost the original delivery cost plus a return trip. Mixed vehicle types. A distributor fleet may include 2-tonne tempos, 5-tonne trucks, and refrigerated vehicles. The optimisation must match each load to the appropriate vehicle type — not just any vehicle with sufficient total capacity. --- Connecting Real-Time Tracking and Proof of Delivery Most distributors use paper proof of delivery. The driver gets a signature at each stop. Exceptions — rejected deliveries, partial deliveries — are discovered when the driver returns at end of day. By that point, the retail account has not received their order. The dispute over whether the item was delivered is resolved through conversation rather than evidence. Digital proof of delivery — a timestamped, geotagged confirmation on the driver's mobile device — creates the record that resolves disputes immediately. When a delivery exception occurs, the dispatch team sees it within minutes. A same-day resolution is possible. For FMCG distributors running 300–600 deliveries per day, reducing rejected delivery incidents from 5–8% to below 1% through connected logistics optimisation — from order capture through proof of delivery — saves ₹15–30 lakh annually in return delivery cost, credit notes, and dispute resolution overhead.