Shipping
Not every high-risk order needs to be cancelled. Learn how RTO risk scoring helps identify potentially avoidable returns.

Delhivery Research
5 min read

Key insights
RTO risk scores use customer, address, payment and regional delivery data to identify orders that are more likely to return before dispatch.
A high-risk score is a signal to verify an order, not automatically cancel it. Contact verification and COD-to-prepaid conversion can help prevent avoidable returns.
Integrating risk checks into a time-bound manifest process helps businesses prioritise high-risk orders without slowing down dispatch operations.
The cheapest return is the one that never gets dispatched. Risk scoring is an attempt to identify those orders while you can still do something about them - at manifest, not at the doorstep. It is not a certainty machine, and treating it as one costs you good revenue. Used properly, it tells you where to spend the twenty minutes of attention you actually have before the pickup.
What the Score is Built From
Delhivery's RTO Predictor assigns each order a score between 0.0 and 1.0, where a higher number means the order is more likely to come back, and classifies it as High, Medium or Low risk. The score is drawn from four kinds of input.
โ Consignee contact and address details. Whether the address is complete and traceable, and whether the phone number looks reachable.
โ Product information and value. Category and order value both carry signal; a high-value cash order behaves differently from a Rs. 499 one.
โ Payment method. Cash and prepaid orders return at different rates, and the model treats them differently.
โ Historical delivery patterns in that region. How orders to that area have actually behaved, which is information you cannot derive from your own order book alone.

What Does a Score Mean
A 0.8 does not mean the order will come back. It means orders that look like this one come back materially more often than orders that look like a 0.2. That distinction decides how you use it.
If you cancel every order above 0.7, you will cancel a large number of orders that would have delivered perfectly well, and you will have no way of knowing how many, because you will never see the outcome. The score is a prioritisation tool. It tells you which orders deserve a verification call, not which orders deserve to be refused.
The score also reflects the order as you submitted it. An order with a two-line address and an unverified phone number will score worse than the same purchase captured properly. Some of what the model is reading back to you is the quality of your own checkout.
The 4 Actions and When Each is Right
There are four things you can do with a scored order.
1. Contact verification. Reach the customer and confirm the order, the address and the amount payable. This is the default action on a high-risk order and it resolves most of them.
2. Mark as verified. Once you have confirmed it - by call, by WhatsApp reply, or because it is a repeat customer you know - record that, so the order moves on and nobody looks at it twice.
3. Convert COD to prepaid. Send a payment link. A customer who pays before dispatch has removed the largest single driver of return risk. Offer a small incentive if you need one; it is cheaper than the return.
4. Cancel. Reserve this for orders where the score is high and you have a second, independent reason - a buyer who has refused before, an address that has already failed, or a value well above what you are willing to send on cash to an unverified customer. Never cancel on the score alone.
Fitting the Check Into Dispatch Without Slowing it Down
The failure mode here is a team that stops packing to investigate scores. Avoid it with three rules as explained in the graphic below:

Pricing is per predicted cash order: Rs. 2.49 plus GST for each COD order scored, billed every 15 days. Do the arithmetic on your volume. Two thousand cash orders a month is a little under Rs. 5,000 plus GST. Against a per-return cost in the region of Rs. 200, that is covered by preventing roughly 25 returns in the month. Whether it clears that bar depends on your cash share and your category, so measure it rather than assume it.
Learn From Orders You Shipped
The most useful data comes from the high-band orders you dispatched without acting on them. Track what actually happened to those. Over a couple of months you will see where the real threshold sits for your business, and you can set your touch list there instead of at a round number.
What You Can Do
1. Pull your cash orders from last month and calculate what scoring them would have cost at Rs. 2.49 plus GST.
2. Set your value threshold: the order value above which a cash order always gets a verification call.
3. Write the four actions and your rule for each into your dispatch checklist.
4. Fix a 20-minute slot before pickup cut-off and give it to one named person.
5. Start a simple log of high-band orders you shipped anyway, and review the outcomes in six weeks.
โโโ
Explore DelhiveryOne: Digital shipping & logistics platform for D2C brands, SMEs & e-commerce sellers.

Shipping
Surface, Express or Next-Day? Match Service Level to the Order
Learn how to match shipping speed to product margins, customer expectations and order economics to make every upgrade count.

Delhivery Research

Shipping
Your COD Money is on its Way. Can Your Business Wait?
Understand COD remittance cycles, manage cash flow and plan working capital as your ecommerce business grows.

Delhivery Research

Shipping
Before You Sign: 6 Checks for Your Logistics Partner
Look beyond shipping rates. Evaluate delivery performance, hidden costs, technology, support and real-world results before committing.

Delhivery Research
These are the popular topics you might want to check out
Ship with the largest integrated logistics company
Create your business account now
SERVICES
Delhivery One
Explore Now
Information Security Policy
Delhivery is committed to safeguarding the confidentiality, integrity and availability of all physical and electronic information assets of the organization. We ensure that the regulatory, operational and contractual requirements are fulfilled.
Disclaimer
Operational metrics listed are as of August 04, 2023