The return that was picked up and never scanned
This is the return failure with the worst shape: the buyer has their refund, the courier has the parcel, and your system shows nothing arriving. The window to act is short.
A pickup that is collected and never scanned sits between the buyer and the network, so neither party shows it as yours. Raise it as soon as the scan is overdue rather than waiting for the parcel, because claim windows run from the event and not from when you noticed. The tracking record, not your inventory, is the evidence.
- Collected and not scanned is a real state, not a delay you should wait out.
- Claim windows run from the event, so waiting is the costliest response.
- Your evidence is the tracking record, not your own stock count.
- A missing scan and a wrong-item return are different claims with different routes.
- This clusters by courier and route, so the pattern is worth tracking.
Most return problems resolve themselves if you wait. This one does not, and waiting is specifically what turns a recoverable loss into a permanent one, because the windows that let you claim are already running.
What the state actually means
The courier has collected from the buyer, so from the buyer's side the return is complete and the refund is justified. The parcel has not been scanned into the return network, so from the network's side it does not yet exist as a shipment in transit. In that gap nobody is accountable by default.
That is why it does not resolve on its own the way an in-transit delay does. An in-transit parcel has a record moving through a system. This one has a pickup confirmation and then silence.
Why waiting is the expensive choice
Claim windows run from the event, not from the day you noticed. A seller who waits two weeks to see whether the parcel turns up has spent a large share of the window on hope, and arrives at the claim with less time and no more evidence.
The correct response is to raise it as soon as the scan is overdue relative to your normal pattern. If the parcel then arrives, you withdraw it, which costs nothing. If it does not, you are inside the window instead of outside it.
What counts as evidence
The tracking record. Specifically, the pickup confirmation, the absence of a subsequent scan, and the date range between them. That is a record Amazon and the courier both hold, which is exactly what makes it usable.
Your own inventory count is not evidence. Saying the item never arrived in your warehouse is a statement about your records, and a claim rests on the other party's records. This distinction decides more claims than any amount of explanation.
Keep it separate from a wrong-item return
A parcel that arrives containing the wrong item, or nothing, is a different claim: there the goods arrived and the contents are the issue, and the evidence is photographs taken at the moment of opening. A parcel that never arrived has no contents to photograph.
Filing one as the other is a common reason a legitimate claim is refused, because the evidence requested does not match the evidence available and the case stalls while the window closes.
Look for the pattern
These failures are rarely uniform. They cluster by courier, by route and sometimes by the pickup process in a particular area. One or two routes producing most of your missing scans is a fact worth knowing, because it changes a series of individual claims into one operational conversation.
Keeping a simple log of pickup date, route and scan date costs almost nothing and turns a vague sense that returns go missing into something you can act on.
The process worth having
Check expected returns against actual scans on a schedule rather than when something feels wrong. Any return collected and not scanned within your normal window gets raised that day. Record the tracking reference, the pickup confirmation and the dates at the moment you raise it.
This takes minutes a week and is the difference between recovering these and absorbing them. The cost of absorbing them is invisible, which is exactly why it is usually chosen by default rather than on purpose.
Where it connects
Every one of these is also a stock discrepancy, because a unit you were refunded for and never received is missing from a count that believes it is coming back. That is why return tracking and reconciliation are the same job rather than two.
Robnu is read-only on Amazon today: orders, returns, payouts and inventory sync so you can see and reconcile them. It cannot accept Amazon orders or make their labels. Order processing is live for AJIO and Meesho.
Where this sits in the rest of your Amazon operation
Robnu is read-only on Amazon today: orders, returns, payouts and inventory sync so you can see and reconcile them, and it cannot accept Amazon orders or make their labels. Order processing is live for AJIO and Meesho. Related reading:
Sources & further reading
- Amazon India, how to list your products the one publicly readable Amazon.in page that states listing figures: title 200 characters, images 500x500 or 1,000x1,000. Read 23 October 2026.
- Amazon India seller forums where the failure shapes described here are reported by sellers. Read 23 October 2026.
- Amazon listing and image style guides login-gated. It redirects to Amazon sign-in, so the detailed rules it holds are not quoted here and are described as market convention instead. Read 23 October 2026.
Not legal or tax advice. Amazon changes fees, windows and policies without notice, and the detailed style guides and account-health thresholds sit behind a Seller Central login, so any figure quoted here as convention is not Amazon-published. Check anything you plan to act on against your own Seller Central account first.
Questions sellers ask
The courier collected from the buyer, so the return looks complete from their side and the refund is justified, but the parcel was never scanned into the return network, so it does not exist as a shipment in transit. In that gap nobody is accountable by default, which is why it does not resolve itself.
No, and waiting is the costliest response. Claim windows run from the event rather than from when you noticed, so two weeks of hope spends the window without adding evidence. Raise it as soon as the scan is overdue; if the parcel then arrives you withdraw the claim, which costs nothing.
The tracking record: the pickup confirmation, the absence of a later scan, and the dates between them, because Amazon and the courier both hold that record. Your own inventory count is not evidence, since it is a statement about your records and a claim rests on theirs.
No. Those arrived, and the issue is the contents, so the evidence is photographs taken at the moment of opening. A parcel that never arrived has no contents to photograph. Filing one as the other commonly stalls a legitimate claim, because the evidence requested cannot exist.
Look for the pattern. These cluster by courier, by route and sometimes by a particular area's pickup process, so a simple log of pickup date, route and scan date turns a series of individual claims into one operational conversation worth having.
On a schedule rather than when something feels wrong. Compare expected returns against actual scans, and raise anything collected and not scanned within your normal window that day. It takes minutes a week and is the difference between recovering these losses and absorbing them unnoticed.
Related seller guides
More on the operations, money and claims that decide whether a marketplace catalogue actually makes money.
Bulk Label Cropping on Meesho: Save Hours a Day (2026)
Bulk label cropping on Meesho turns a full download of shipping labels into clean, print-ready slips in one pass. Learn how it works, how barcodes stay intact at scale, and how to keep buyer data private.
Meesho Label Cropper Tools: Which to Use and Why (2026)
How a Meesho seller turns the downloaded A4 label sheet into a clean thermal-size label without exposing buyer details on unknown websites.
Bulk order processing on Amazon without the mistakes
Processing Amazon orders in batches is where throughput comes from and where the expensive mistakes happen. What batches safely, what never should, and the checks that catch a bad batch early.
Finding the keywords an Indian Amazon buyer actually types
Keyword research for Amazon India without a paid tool, using the sources that reflect Indian search language rather than American, and the vocabulary trap that costs most catalogues their traffic.
Amazon listing uploaded with no error and showing nowhere
A clean processing report does not mean a live listing. The six states an uploaded listing sits in while buyers cannot see it, and how to tell them apart.
How to Hide the Address on a Meesho Label (2026)
How to hide the buyer address on a Meesho label safely: why it matters for privacy and reuse, which courier fields you must never cover, safe masking methods, and the compliance line you should not cross.
Meesho Return Fraud: Dispute a Wrong or Damaged Return (2026)
Buyer returned a wrong, used or damaged item on Meesho? Here is how the return-fraud dispute works, unboxing-video evidence, the 48 to 72 hour claim window, and exactly how to file so you get paid back.
Amazon order processing steps, start to handover
Every Amazon order moves through the same seven states from payment to handover. What each one means, where it stalls, and which metric each stall feeds.