Returns
Courier Returns and Refusals in Pakistan: RTO, Send-Backs, and Restock
Cutting COD return *rates* is one job. Processing the parcels that still come back is another. Pakistani stores lose hours—and stock accuracy—when refusals, RTO (return to origin), reverse pickups, and “customer not available” sit in five courier portals with no restock rule. This guide is the ops playbook: what a refusal is, how send-backs work, who owns the reverse CN, and how to close the loop so finance is not guessing which SKU is still in a hub.
If you have not yet tightened confirmation and NDR follow-up, start with the guide on reducing COD return rates. Come here when the packing bench is already staring at a pile of inbound bags and nobody knows which orders they belong to.
Refusal, RTO, NDR, send-back: use the words ops can act on
- NDR / failed attempt: the rider tried; the buyer was away, unreachable, or asked for a later time. The parcel is often still with the courier.
- Refusal: the buyer (or someone at the door) declined to take the parcel or pay COD.
- RTO: the network is sending the parcel back to your pickup or return address. Freight and return fees apply per your rate card.
- Send-back / reverse pickup: you or the courier initiate a return from the buyer’s location (wrong size, damaged, after-delivery return).
Mixing these in one spreadsheet column called “return” is how you double-refund, restock air, or keep advertising a SKU that is still in transit back from Multan. Tag the *reason* and the *physical location* separately.
A close-the-loop queue, not a graveyard of CN numbers
- Pull exceptions daily: NDR aging, refused, in-return, received-at-origin, missing.
- Act on NDR while the parcel is still out for delivery—call or WhatsApp before it auto-RTO.
- When RTO is inevitable, record expected return fee and the SKU so inventory is not sold twice.
- On physical receipt, scan or tick received; only then restock or write off.
- If the buyer already paid prepaid or you collected COD by mistake, queue the refund against the same order ID.
What usually breaks in Pakistani reverse logistics
Courier return bags arrive without a packing list your intern understands. CNs are faded. The buyer’s “return” WhatsApp has no order number. Staff restock by product photo. Two weeks later finance asks why return freight was billed for a CN you already marked delivered. The fix is boring: one order record that holds forward CN, return CN, reason, and warehouse received-yes/no. If that record lives only in a courier portal, you do not have a process.
Forward shipment versus return / refusal handling.
| Stage | Forward COD order | Return or refusal |
|---|---|---|
| Trigger | Confirmed order, label printed | NDR exhausted, door refusal, or buyer-requested return |
| Document | Outbound CN / tracking | Same CN in RTO, or a new reverse CN—know which |
| Cash | Collect at door | No collect, or refund if prepaid / wrong collect |
| Stock | Leave warehouse | Do not sell again until scanned back in |
| Finance | Expect remittance if delivered | Expect return fee; no COD credit for refused |
Bulk refusals after a sale: do not treat them as one-off chats
A flash sale can dump a hundred NDRs in 48 hours. Answering them one by one in Instagram DMs will miss the parcels that could still be reattempted. Filter by city and courier, batch the “call before RTO” list, and let auto-RTO happen only after a written rule (for example: two failed attempts plus no WhatsApp reply). Document the rule so support and warehouse argue less.
Send-backs after delivery
After-delivery returns (wrong size, damaged) are not the same as COD refusal. You may owe a reverse pickup, a QC check, and a refund timeline you announced on the product page. Book the reverse shipment on the same order, attach photos if you require them, and do not refund until the parcel is in your QC bin—unless your policy says otherwise and you can afford the leakage.
How this ties to COD payouts
Refused parcels should not appear as COD collected. If a remittance file credits a CN you marked refused, that is a reconciliation item—not a warehouse mystery. Pair this playbook with COD remittance versus courier invoice matching so ops and finance share one CN truth. Returns that never get a received stamp are how “missing inventory” and “courier stole cash” stories start; most of the time the bag is still in a hub.
Returns and refusals on WeShip
WeShip at weship.pk is built so exceptions sit next to the original order: refusals, failed attempts, send-backs, and bulk actions instead of five portal exports. Use it with confirmation so fewer parcels enter this queue—and use it when they do, so restock and refunds are not folklore. The returns and refusals feature page is the product view of this same workflow.
Pilot for two weeks: every inbound return bag scanned against the order list before anyone restocks. Count how many CNs were “returned” in the courier app but not on your shelf. That gap is your real reverse-logistics problem.
FAQ
What is RTO in Pakistani courier shipping?
Return to origin: the network sends the parcel back to your pickup or return address after failed attempts or refusal. Return freight rules depend on the courier contract.
Is a COD refusal the same as a customer return?
No. Refusal happens at delivery before or instead of payment. A customer return is usually after they accepted the parcel. Different cash and reverse-CN steps.
When should I restock a returned SKU?
After you physically receive and QC it. Restocking on a courier “RTO initiated” status sells stock you do not have.
How do I stop the same buyer from cycling refusals?
Flag repeat refusers before the next label. Confirmation and courier choice help; a returns queue that never closes does not.
Where are returns tools on WeShip?
See returns and refusals on weship.pk. Use it with the COD returns-rate guide so you both prevent and process exceptions.
Close returns in the same queue as the original order
See how WeShip handles refusals, RTO, and send-backs so warehouse and finance are not working from five courier portals.