When a parcel is marked RTO (return to origin), it is travelling back to the seller, and in many cases your refund depends on the seller receiving it and processing it. So the refund rarely lands on the day the status changes. Keep a short record of the dates, the status messages and the amount debited, and set one follow-up date, so that you chase with facts instead of memory.
What does RTO mean on your order?
RTO is shorthand for return to origin. The courier could not complete delivery, perhaps because of an incomplete address, nobody home for the attempts allowed, a refused parcel or a phone number that did not connect. The parcel then goes back to the seller's warehouse. Your order page may call this 'undelivered', 'returned to seller' or something similar. The wording differs from one shopping app to another, so copy it exactly as shown.
If you paid online, your money sits with the seller or the payment provider while the parcel is on its way back. If you chose cash on delivery, nothing was debited and there is no refund to chase. You only need a note of the failed attempt, in case you want to reorder.
What should you write down the day the status changes?
- Order number, item, amount debited and how you paid (UPI, card or wallet).
- Date and time of each delivery attempt, as the tracking page shows them.
- The exact status message at each step, such as 'delivery attempted', 'return initiated' and 'returned to seller'.
- Courier name and tracking number, in case the seller asks for them.
- The refund timeline stated on the seller's help page, copied word for word, with a screenshot of the page.
- Your follow-up date, which is the day after that stated timeline ends.
Take a screenshot at every status change. Tracking pages are often overwritten, so the 'returned to seller' message you saw on Tuesday may not be visible on Friday.
A worked example with made-up dates
Say you ordered a ₹1,499 kurta set on 4 March and paid by UPI. Delivery failed on 8 March, the app showed 'return initiated' on 9 March, and 'returned to seller' on 14 March. Suppose the seller's help page says refunds are processed within seven days of the parcel reaching them. Seven days after 14 March is 21 March, so that is your follow-up date.
| Date | What happened | Money | What you note |
|---|---|---|---|
| 4 Mar | Order paid by UPI | ₹1,499 debited | Order number saved |
| 8 Mar | Delivery attempt failed | None | Screenshot of status |
| 9 Mar | Return initiated | None | Exact wording copied |
| 14 Mar | Returned to seller | None | Follow-up set for 21 Mar |
| 21 Mar | Check statement and order page | ₹1,499 credit expected | Contact seller if missing |
When should you chase, and what do you say?
Wait until your follow-up date, then look at your bank or card statement and at the order page. If the credit is not there, write to the seller with the order number, the date the parcel went back to them, the amount and how you paid. A refund often goes back to the account or card you paid from, so check that one first. Write down any reference number you are given, with the date and the name of the person.
Where does this sit in your expense tracker?
Until the refund arrives, the order is spending. In a sheet, enter ₹1,499 as a Shopping line with the note 'RTO, refund awaited', and when the credit lands add a matching refund line dated that day, so the month nets to zero for this order. In SpendixAI you can add the expense by hand, or import the statement that carries the debit and review the row before saving it, then record the refund the same way once it shows up.
A short checklist for any returned parcel
- Screenshot each status page and save the tracking number.
- Copy the seller's stated refund timeline.
- Enter the purchase and mark it 'refund awaited'.
- Set a follow-up date one day after the timeline ends.
- On that date, check the statement, then contact the seller if needed.
- Add the refund as its own line and clear the 'awaited' mark.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

