BLOG

How to track RTO reasons so you can fix your process

A plain sheet with three columns, order, reason and fix, can show you where your parcels keep failing. Here is how to set it up and read it without needing any benchmark.

A parcel moving through an order, packing and delivery workflow
From order to doorstep · Editorial illustration

You cannot fix what you have not written down

Sellers often feel that returns are random. A parcel here, a refusal there. But when you list them in one place, patterns appear that memory hides. Maybe half your failed parcels share the same cause. Maybe one product keeps coming back. You only discover this if you keep a record.

You do not need software. A spreadsheet or even a notebook works. What matters is that you fill it in every time, the same way.

The simple sheet

Start with three main columns and a few helpers.

  • Order. The order number, so you can look it up.
  • Reason. Why the parcel came back, in a few words.
  • Fix. What you could change, or what you did.

Add these helpers if you want a little more power.

  • Date it came back.
  • Product name.
  • Payment type, COD or prepaid.
  • City or pincode area.
  • Cost of the failed delivery, using your own estimate.

Keep it small. A sheet that takes two minutes to update will actually be updated.

Use fixed reason labels

Free text is hard to count. Pick a short list of labels and stick to them. Examples:

  • Customer unreachable
  • Address incomplete or wrong
  • Customer refused
  • Customer not available
  • Changed mind before delivery
  • Product damaged in transit
  • Wrong item sent
  • Other, with a note

When you learn the real reason, choose the closest label. If something does not fit, write a note and later add a new label if it happens again.

Where the reasons come from

Use whatever you can find: the courier status, your tracking page, a message from the customer, your own inspection of the returned item. Do not guess if you have no answer. "Unknown" is an honest label, and a high count of unknowns tells you to ask more questions.

Review once a month

At the end of the month, count how many returns fall under each label. Then ask three questions.

  • Which reason is the biggest for us?
  • Is it linked to a product, a payment type or an area?
  • What one change could reduce it next month?

Match the fix to the cause. Unreachable customers point to confirmation routines, as in how to confirm a COD order before you ship it. Address issues point to better data collection, as in delivery tips for apartments, villages and rural addresses. Damage points to packing, which you can improve using the packing guides for your category.

Do not compare with random benchmarks

I will not give you any "good" return rate to aim for, because it depends so much on your product and customers. Compare yourself with yourself. If your numbers improve month over month, your process is working. Break-even RTO rate for COD shows how to find the level your own margins can afford.

Make one change at a time

If you change confirmation, packaging and policy all together, you will not know what helped. Pick one fix, run it for a few weeks, and look again.

Make it a team habit

If a family member or helper packs orders, show them the sheet. When everyone logs the same way, your records stay clean. Over time the sheet becomes one of the most valuable things in your business, because it holds what you have learned the hard way. The bigger picture is in returns and RTO, the numbers nobody tells you.

How to track RTO reasons so you can fix your process — varchas.store