Flipkart Marketplace Platform  ·  View 18 of 25  ·  5 · Runtime

Fulfilment and Last Mile

Three supply models, one delivery promise, and the cash that has to come back.

Editable source SVG draw.io All views
Allocate Pick and pack First mile Line haul Last mile Proof Platform fulfilled Node selection OR-Tools Wave and pick WMS Sortation Own line haul Delivery hub route plan OTP or QR Seller fulfilled Seller node pincode serviceability Label and manifest Carrier pickup Carrier network 8 partners Carrier last mile Scan webhook signed Reverse Return authorised abuse score Reverse pickup slot Rider collects Return centre Grade and restock Refund trigger saga Promise and money Delivery promise ML ETA SLA clock starts Breach alerting Track and trace COD collection cash or UPI Remittance match T+2 Fulfilment — Three Supply Models, One Promise Application we own Security / platform Interface / broker External / third party Decision point The promise shown at checkout is computed from the same node-selection model that later allocates the order, so the ETA a shopper sees and the ETA operations plans against are one number. v 1.0 · owner Supply Chain Engineering · date 2026-09

Decisions

  • The delivery promise shown at checkout comes from the same node-selection model that later allocates the order — one number, not two
  • Seller-fulfilled and platform-fulfilled orders share the order and event model; only the execution lane differs
  • Reverse logistics runs on the forward network in the opposite direction rather than as a separate system

Numbers and constraints

  • Eight carrier integrations, so no single partner failure removes a serviceable pincode
  • COD remittance matched T+2 against rider-level collections
  • Node selection is a constrained optimisation over cost, promise and stock — solved with OR-Tools, refreshed per wave

Risks

  • Carrier scan feeds arrive late and out of order; tracking state is therefore derived, never authoritative
  • Serviceability data drifts at pincode level and is the usual cause of an undeliverable promise
  • Sale-event volume hits sortation capacity before it hits software capacity — the constraint is physical
◀  Discovery Pipeline All views Deployment Topology  ▶
Solution Architecture v1.0 · Open source on Microsoft Azure · Enterprise Architecture · 2026-0918-fulfilment-and-last-mile