Commerce Graph · Research Note · Guide

First Mile vs Last Mile

Understanding where your shipment breaks — at pickup, in transit, or at the buyer's door — is the first step to cutting returns and protecting margins.

AS OF 11 JUL 2026 · SOURCE: COMMERCE GRAPH — SHIPROCKET COMMERCE INTELLIGENCE
Key takeaways

In Indian e-commerce, the conversation about delivery performance almost always starts and ends with the last mile — the moment a delivery agent knocks on a customer's door. That focus is understandable but incomplete. Delivery failures are rarely born at the doorstep; they are conceived much earlier, at the point of pickup or somewhere deep inside a hub network that most sellers never see.

First mile, middle mile, and last mile are not interchangeable terms for 'shipping.' Each leg has distinct failure modes, distinct cost drivers, and distinct levers that a seller can actually control. Confusing them leads to misdiagnosed problems — chasing delivery agent accountability when the real breakdown was a missed pickup scan three days earlier. This guide separates the three legs clearly, maps where Indian e-commerce shipments most commonly break, and gives sellers a practical framework to diagnose and fix failures at the right point in the chain.

Defining the Three Legs: First Mile, Middle Mile, and Last Mile

First mile is the movement of a shipment from its origin — typically a seller's warehouse, dark store, or retail back office — to the courier partner's first processing facility, often called a pickup hub or origin hub. This leg is triggered the moment a seller generates a manifest and a pickup agent collects the consignment. It sounds simple, but it involves manifest creation, physical handover, scanning at pickup, and induction into the courier's network.

Middle mile covers the trunk movement between hubs — from an origin hub to a regional sorting centre, and from there to a destination city hub. This is the invisible backbone of logistics. Sellers rarely track it because most courier portals show only a 'in transit' status across this entire leg. But middle mile is where transit time is either preserved or destroyed, depending on load consolidation schedules, line-haul frequency, and sorting accuracy.

Last mile is the delivery leg from the destination hub to the buyer's address. It is the most labour-intensive, most variable, and most customer-visible segment. It involves route planning, delivery agent allocation, customer communication, and physical handover or safe-drop. In Indian e-commerce, cash-on-delivery orders add a payment collection step that introduces further complexity.

Understanding each leg as a distinct operational domain — with its own SLAs, its own data signals, and its own failure taxonomy — is the foundation of serious logistics management.

Why Last Mile Gets All the Attention — and Why That Is a Problem

Last mile failures are visible and immediate. A customer who did not receive their order raises a complaint, leaves a negative review, or initiates a return. The feedback loop is fast and loud. This visibility has led most Indian e-commerce sellers to concentrate their logistics energy — dispute escalations, courier scorecards, NDR management — almost entirely on the last mile.

The problem is that last mile performance is heavily upstream-determined. A shipment that was picked up late, entered the network with an incorrect weight or dimension, or was mis-sorted at a regional hub will arrive at the destination hub already outside its promised delivery window. The delivery agent is then blamed for a delay that was structurally inevitable.

More specifically, address and pincode errors introduced at the order stage — which should be caught at first mile induction — travel silently through the middle mile and explode as undeliverable exceptions at the last mile. By that point, the cost of correction is highest: the shipment must be held, a customer call must be made, and delivery reattempted. Each reattempt has a cost.

Sellers who treat last mile in isolation also miss a structural insight: reducing Return-to-Origin rates requires working backwards. Most RTO in India is addressable, not structural — it traces to fixable first mile data errors, poor NDR communication, and COD friction, none of which are last mile problems in origin.

First Mile Failures: The Silent Killers of Delivery Performance

First mile failures are underreported because they are hard to see. A pickup that is marked as 'collected' but not scanned into the network is a ghost shipment — it exists on the seller's manifest but has not formally entered the courier's system. These are among the most damaging exceptions in Indian e-commerce because they create a window of complete tracking opacity.

The most common first mile failure modes for Indian sellers are: missed pickups due to agent no-shows or capacity constraints at the courier's end; manifest mismatches where the number of bags handed over does not match the system record; incorrect weight or dimension capture that triggers billing disputes and, in some courier systems, automatic holds; and mis-tagging where a shipment is assigned to the wrong route at origin hub sorting.

Manifest hygiene is the single highest-leverage first mile control. Every shipment should have a clean, verified manifest with accurate product descriptions, correct pincode, and verified buyer phone number before the pickup agent arrives. Handing a poorly prepared manifest to a pickup agent is handing a time-bomb to your last mile team.

Sellers operating at volume should also negotiate pickup SLA commitments with their courier partners — not just delivery SLAs — and track pickup attempt rate, first-scan rate, and origin hub induction time as KPIs. These metrics are available in most courier APIs and in platforms like Shiprocket, but many sellers simply do not look at them.

Middle Mile Bottlenecks: The Leg Nobody Watches

Middle mile is logistics infrastructure in its most industrial form: line-haul trucks, sorting conveyor belts, hub-to-hub handoffs, and load consolidation schedules that run on fixed departure windows. For sellers, it is largely a black box — and that invisibility is itself a risk.

The primary middle mile failure mode is hub delay, which occurs when a shipment misses a line-haul cut-off at a regional sorting centre. This can happen because the shipment arrived late from the origin hub (a first mile cascade), because the hub was running over capacity during a sale event, or because of route-level disruptions such as weather or state-border check delays. A single missed cut-off can add one to two transit days to a shipment, which in a same-day or next-day promise context is catastrophic.

A second failure mode is mis-sort: a shipment tagged to Delhi NCR ends up on a Jaipur line-haul because of a label scan error at the sorting centre. Mis-sorts are rare but extremely expensive — they require reverse-hauling the shipment and rescheduling delivery, often pushing the order past cancellation windows.

Sellers cannot control middle mile operations directly, but they can select courier partners based on hub network density and line-haul frequency for their specific origin-destination corridors. A courier with strong trunk routes between Mumbai and Bengaluru may be significantly weaker on a Lucknow-to-Guwahati corridor. Route-level performance data, available through multi-carrier platforms, should drive partner allocation decisions — not headline delivery percentages.

Common Mistakes Sellers Make Across All Three Legs

The most widespread mistake is treating logistics as a single-vendor accountability problem. When deliveries break, sellers escalate to their courier partner and wait for resolution, rather than diagnosing which leg failed and whether the root cause was within the seller's control. This reactive posture is expensive and slow.

A second common mistake is over-relying on customer-facing tracking updates to monitor network health. Tracking status strings like 'in transit' or 'out for delivery' are consumer-facing simplifications. They do not reveal whether a shipment missed a hub cut-off, was held for address verification, or is on its third delivery attempt. Sellers need raw event-log data from courier APIs to see the actual journey.

Ignoring COD as a last mile variable is another systematic mistake. Cash-on-delivery orders have materially different delivery dynamics than prepaid orders — higher buyer unavailability, higher RTO propensity, and longer dwell time at the delivery agent level because payment collection adds a step. Sellers who manage COD and prepaid shipments identically are misreading their own data.

Finally, many sellers neglect the feedback loop from last mile back to first mile. If a high proportion of undeliverable exceptions cite 'address not found,' the correct fix is upstream: improving address capture at checkout, enforcing pincode verification, and adding buyer phone confirmation at order stage — not simply issuing more delivery reattempts. Building this cross-leg diagnostic habit is what separates operationally mature sellers from those perpetually fighting fires.

A Practical Framework for Indian Sellers: Diagnosing and Fixing Delivery Breaks

Start with leg-level exception mapping. Pull shipment event data for a rolling period and categorise every failed or delayed shipment by the leg where the first exception occurred — first mile (pickup miss, no-scan), middle mile (hub delay, mis-sort), or last mile (undeliverable, RTO, false attempt). This single exercise will reveal where your network is actually breaking, which is almost always different from where you assume it is.

For first mile, establish non-negotiable pre-dispatch standards: verified buyer phone, clean pincode, accurate dead weight and volumetric weight, and a sealed, labelled package handed to the agent with a signed manifest receipt. Track your courier's pickup attempt rate and first-scan rate weekly.

For middle mile, build a corridor performance matrix. For your top ten origin-destination pairs by volume, score each courier partner on average transit time and exception rate. Allocate shipments to the strongest performer per corridor, not per overall brand reputation.

For last mile, implement a structured NDR (Non-Delivery Report) workflow: every undelivered shipment should trigger an automated buyer outreach within hours, with a re-delivery slot confirmation before the next attempt. Do not leave NDR resolution to the courier's default process. For COD, consider offering a prepaid conversion option on NDR to reduce friction at the door.

Finally, close the loop: tag every RTO with a root-cause leg and feed that data back into your product and ops teams. Address errors belong in checkout. Pickup misses belong in vendor management. Delivery failures belong in NDR logic. Keeping these streams separate is what makes improvement sustainable.

Methodology

Figures reflect orders on the Shiprocket network over the trailing 30 days unless a period is stated. Order-volume figures are indexed to the leading city within each tier (= 100), not absolute counts. AOV, RTO and prepaid share are tier averages. Any current, incomplete month is excluded from trend charts. Data via the Commerce Graph over Shiprocket’s Sense APIs.

Frequently asked questions

What is the difference between first mile and last mile in logistics?

First mile logistics is the movement of goods from the seller's origin point to the courier's first processing hub, covering pickup and initial network induction. Last mile logistics is the final leg from the courier's local delivery hub to the end customer's address. The two legs have entirely different failure modes: first mile breaks on manifest errors and missed pickups, while last mile breaks on buyer unavailability, address issues, and delivery agent execution. Conflating them leads to misdiagnosed problems and wasted escalation effort.

What is middle mile logistics and why does it matter for Indian e-commerce?

Middle mile logistics is the trunk movement of shipments between a courier's regional sorting hubs — the leg between origin hub and destination city hub that most sellers never track directly. It matters because a missed line-haul cut-off in the middle mile can add one to two transit days to a shipment, making a promised fast delivery impossible before the delivery agent even tries. Sellers should evaluate courier partners on middle mile hub density and line-haul frequency for their specific shipping corridors, not just on headline delivery rates.

Why is last mile the most expensive part of logistics?

Last mile is the most expensive leg because it is the most labour-intensive and least scalable: each delivery requires a human agent to travel to a unique address, attempt handover, collect payment on COD orders, and handle exceptions in real time. Unlike middle mile trunk routes where one truck moves hundreds of shipments efficiently, last mile routes fragment that load into individual stops. Failed delivery attempts compound the cost because each reattempt repeats the full per-stop expense without generating a completed delivery.

What causes high RTO rates in Indian e-commerce and which leg is responsible?

High return-to-origin rates in Indian e-commerce are driven by failures across multiple legs, but the root causes are often first mile in origin. Incorrect addresses and unverified phone numbers entered at the order stage travel through the network undetected and surface as undeliverable exceptions at last mile. COD friction — buyers who refuse payment on delivery — is a last mile variable but is addressable through prepaid conversion nudges at NDR stage. Sellers who audit their RTO by root-cause leg consistently find that a majority of returns are preventable through upstream data quality fixes.

How does Amazon handle first mile, middle mile, and last mile logistics?

Amazon manages all three legs with proprietary infrastructure: seller-facing pickup through its carrier network feeds into regional fulfilment centres as the first mile, inter-FC and sortation centre transfers form the middle mile, and Amazon Logistics handles last mile delivery to buyers. The integration allows Amazon to hold SLA accountability across all legs internally. Independent Indian e-commerce sellers working with third-party couriers lack this vertical control, which makes explicit leg-level SLA agreements and multi-carrier strategies especially important for matching reliability.

What is the best way to reduce first mile failures for an Indian e-commerce seller?

The highest-leverage first mile controls are manifest hygiene and pickup SLA monitoring. Every shipment should be dispatched with a verified buyer phone number, correct pincode, accurate weight, and a properly sealed and labelled package. Sellers should track pickup attempt rate and first-scan rate — the share of collected shipments scanned into the courier network on the same day — as weekly KPIs. Platforms like Shiprocket surface these metrics through courier API integrations, making it possible to flag underperforming pickup routes before they cascade into delivery delays.

How should sellers manage NDR and last mile delivery failures?

Sellers should operate a structured NDR workflow rather than relying on the courier's default reattempt logic. Every undelivered shipment should trigger automated buyer outreach within a few hours of the failed attempt, offering a specific re-delivery slot and, for COD orders, a prepaid conversion option to reduce payment friction. Each NDR should be tagged with a failure reason — buyer unavailable, address not found, refused — and those reasons should feed back into first mile data quality improvements and order-stage checkout optimisations to prevent repeat failures.

Is first mile or last mile more important to optimise first?

For most Indian e-commerce sellers, first mile optimisation delivers faster and more structural returns because errors introduced at pickup propagate through the entire chain. Fixing manifest data quality, securing pickup SLA commitments, and tracking first-scan rates prevents a class of last mile failures before they occur. However, last mile NDR management is the higher-urgency problem for sellers with elevated RTO rates, because it directly reduces revenue leakage on shipments already in the network. The practical answer is to run both workstreams in parallel rather than sequencing them.

People also search for
First mile vs last mile vs middle mileFirst mile vs last mile redditFirst mile, middle mile last mile logisticsFirst mile vs last mile in supply chainFirst mile vs last mile logisticsFirst mile vs last mile shippingFirst mile last mile transportationFirst mile middle mile last mile amazon