RTO (Return to Origin) is the shipment that goes out, fails delivery, and comes back to you. You pay forward freight, reverse freight, and you still have no sale.
Why RTO happens
- Address quality. Missing landmarks, wrong pincodes, and half-typed flat numbers are the single biggest cause.
- Unreachable buyers. The delivery agent calls once, gets no answer, and marks the attempt failed.
- Buyer regret on COD. With nothing paid upfront, cancelling costs the buyer nothing.
- Slow delivery. The longer a parcel takes, the more likely the buyer has moved on.
A practical checklist
- Validate the address at checkout. Pincode lookup, mandatory landmark field, and a 10-digit phone check catch most bad data before it becomes a shipment.
- Confirm high-risk COD orders. A WhatsApp confirmation on orders above your average order value pays for itself very quickly.
- Act on NDR the same day. An NDR (Non-Delivery Report) is a second chance, not a verdict. Reach the buyer, reschedule, and push the reattempt.
- Nudge prepaid. A small discount on prepaid orders is usually cheaper than one RTO.
- Pick the courier by lane, not by habit. Delivery performance varies a lot by pincode cluster.
- Measure RTO by product, city, and courier. You will almost always find that a handful of SKUs and a handful of pincodes cause most of the damage.
What good looks like
Most Indian D2C brands see COD RTO in the 15-30% range. Getting it under 12% is realistic with disciplined address capture, same-day NDR handling, and courier selection by lane.
RoutikQ surfaces NDR alerts and courier-wise performance in one panel, so you can act on returns while they are still recoverable.