RTO reduction: fix the cause before dispatch

RTO reduction starts before dispatch: confirm that the buyer wants the order, collect a usable address, show the full payable amount and promise a delivery window the selected courier can serve. After a failed attempt, verify the reason and send a specific reattempt instruction. Measure the result as money retained per acquired order.

Start with the largest loss in your own closed dispatch cohorts. An address correction, a clearer COD fee or a different service on a weak route needs a different owner. Choose the fix that addresses the recorded cause and compare its delivered contribution with the current process.

What is RTO in ecommerce?

Return to origin means an undelivered parcel returns to the shipper. Delhivery's Rate Card documentation, updated 20 Dec 2024, distinguishes RTO from a customer return after delivery, which it calls DTO. The guide was checked on 06 Nov 2026.

Keep cancellation before dispatch in a separate category. It consumes acquisition and support effort, but has not yet incurred the same outward journey. A customer return also needs its own record because a sale and a delivery happened before the reverse pickup.

Use the airway bill to connect the original dispatch, failed-attempt history and returned stock. If an order has several parcels, write down whether the report counts orders or shipments. Use that unit consistently when comparing couriers and dates.

Calculate RTO rate from a closed dispatch cohort

For an operations report, use this definition:

Final RTO rate = shipments returned to origin ÷ dispatched shipments in the cohort.

Choose the dispatch period first, then follow those parcels to final outcomes. Keep an initiated return separate from a parcel physically received back at the warehouse. Finance needs the received status and condition to reconcile stock; the delivery desk needs the initiated status to stop chasing a reattempt.

Split COD and prepaid within the same cohort. Also inspect product, acquisition source and courier service when there is enough volume to make a useful decision. A campaign that attracts refused orders calls for an offer check. A route with repeated transit failures calls for a service check.

Keep unresolved parcels visible alongside the rate. Comparing a fully settled cohort with newly dispatched orders rewards the newer cohort simply because its returns have not finished travelling. Set the review date from the actual service and return cycle, then compare cohorts at the same stage.

Read the reason before choosing an RTO reduction tactic

Use the courier reason and the buyer's verified response together. The following worksheet is a practical way to assign the fix.

Choose a recurring reason with a clear action. A broad instruction to reduce RTO gives the desk no decision rule. A change such as displaying the COD fee beside the payment choice is specific enough to inspect on a phone and measure in subsequent dispatches.

Check COD intent and address quality before shipping

Review the confirmation record before the parcel leaves. Make the payable amount visible, including any COD or shipping fee. Give the customer a way to correct a missing address detail or cancel an unwanted order before dispatch.

Use risk flags to prioritise verification. Delhivery's RTO Predictor guide, updated 03 Apr 2025 and checked 06 Nov 2026, describes a pre-shipping risk flag built from shipment and consignee inputs. Treat a flag as a queueing signal: check the order, record the response and route it to the appropriate action.

Record why an order was held or cancelled. If a new rule blocks genuine buyers, the shipped cohort alone will hide the lost demand. Keep the original placed-order count and acquisition spend beside the dispatch report so you can see whether better delivery performance paid for that trade-off.

Avoid blanket pincode exclusions as the first fix. Inspect the service, address and delivery promise on the affected route. A workable alternate courier or corrected promise retains demand that a broad block would discard.

Test COD to prepaid on contribution

A prepaid incentive changes both payment economics and buyer behaviour. Price the incentive, gateway fee and any checkout fee into the same order worksheet. Use our payment gateway charges comparison for the dated public fee schedules.

Track the complete funnel: placed orders, successful prepaid payments, dispatches and deliveries. Give refunds and customer returns time to settle. The COD charges guide explains how collection fees differ from the fee your shop charges the buyer.

Compare a similar order mix under the unchanged offer. Keep the products, destination mix and acquisition source visible. If a festival offer changes the basket or campaign mix during the test, separate that change in the report before assigning the result to prepaid adoption.

Resolve NDRs while a reattempt is actionable

Give every failed delivery an owner and a next action. Confirm what the buyer wants, then send the courier the missing detail: a usable contact number, an address correction or a supported dispute. Save the request and follow the next scan.

Delhivery's SmartNDR guide, updated 08 Jul 2026 and checked 06 Nov 2026, describes automated buyer follow-up and reattempt recommendations. Keep the buyer's response and final outcome in the same action history when comparing automated and manual handling.

Use the NDR management routine to organise shift handovers. Close a case when the parcel reaches the relevant outcome, and hand back a definite buyer refusal through the return process. That preserves desk time for orders with a useful delivery instruction.

Worked example: put a rupee value on fewer RTOs

Worked example with assumed inputs, excluding tax and fixed overhead: compare cohorts of 100 dispatched orders, with the same ₹10,000 acquisition spend. A delivered order retains ₹300 after product, packaging, payment and delivery costs. An RTO loses ₹150 in outward freight, return freight and used packaging, with stock recovered intact. The proposed verification routine costs ₹600 per cohort.

The test retains ₹1,650 more. Each recovered delivery replaces a ₹150 loss with ₹300 contribution, a ₹450 change. Recovering five deliveries adds ₹2,250 before the ₹600 verification bill. The required improvement to cover that bill is two additional deliveries, rounding ₹600 divided by ₹450 up to a whole order.

Shiprocket's forward and RTO charges guide, updated 13 Jul 2024 and checked 06 Nov 2026, separates outward freight from the return journey. Put both into the returned-order loss. Record damaged stock and additional service charges against the affected shipment when reconciling your real cohort.

Choose the next test and keep the warehouse handoff intact

Rank the verified causes by their total loss and the work required to fix them. Write the selected change beside its owner, start date and unchanged comparison process. Preserve the order and shipment references so the final invoice and return receipt can be joined later.

At the warehouse, record the parcel's arrival and condition before restoring saleable inventory. Keep damaged stock and incomplete packages in an exception queue. Join the inspection outcome to the same order worksheet used by growth and finance.

Review the test when both delivery outcomes and courier charges have settled. Compare retained contribution at the original acquired-order level, then inspect the reason mix to decide which operational change to keep.