02 / 06 · Delivery exception map

Find the pattern behind the return.

Look beyond an overall return rate. Follow failed deliveries back to the courier, payment mode, location and order context that shaped them.

Dispatched 0Returned 0
01 · Orders dispatched

What was shipped, where, and with which courier?

Shipment and order identifiers

02 · Delivery exceptions

Which deliveries failed or came back?

Delivery events, NDR and return status

03 · Patterns to review

Where do repeated exceptions deserve a closer look?

Courier, pincode and payment-mode cohorts

Dive in

Three pincodes, eleven percent of margin.

02The evidence chain

The example on this page, unwound to the records behind it — the way every insight in SeerFlow can be.

  1. 1Order#SF-5170 · COD · pincode 4410xx
  2. 2PayoutNothing collected · ₹0 remitted
  3. 3ReturnRTO · ₹142 freight paid both ways
  4. Illustrative example · not a customer result
03Why it matters

~26%

of COD orders returned to origin.

Shipway’s ShipNotes analysis shows the cost risk behind COD. An undelivered order can leave you paying delivery and return charges without collecting the sale.

Shipway · ShipNotes findings

Recommendations support your team’s decisions; savings depend on the delivery outcome.

All research
04Start here

Patterns help prioritise investigation. They do not prove a courier or customer caused an outcome; event coverage and cohort size matter.

Start free
Next questionSettlement reconciliation