Proving the courier never knocked.
“Customer unavailable.” “Premises closed.” Sometimes nobody ever came — and that fake attempt manufactures an avoidable RTO you pay for. Here is how to spot the pattern, gather the evidence, and dispute it.
- A fake delivery attempt is a failed-delivery scan logged for a delivery that never really happened.
- Enough failed attempts push a parcel to RTO — so a fake attempt manufactures an avoidable loss.
- The tell is a mismatch: the buyer was reachable, no knock or call came, or the timing is implausible.
- Evidence is the courier's own log contradicted by the buyer's confirmation and the scan's implausibility.
- Robnu flags clustered and suspicious attempts and helps prepare the dispute. Free while we figure out pricing.
Most sellers treat a “customer unavailable” scan as final — the customer was out, bad luck, move on. Sometimes that is exactly what happened. But a meaningful share of failed-attempt scans describe a delivery that was never genuinely tried, and each one that ripens into an RTO is a loss you did nothing to cause. This guide is about telling the two apart and doing something about the fake ones.
There is a specific, quietly infuriating way to lose a sale: the tracking says the courier tried to deliver and the customer was not available, the customer swears nobody came, and after a couple of these the parcel turns around and heads back to you as an RTO. You paid to ship it out, you will pay in lost margin, and the failure was never real. This is the fake delivery attempt, and it is more common than most sellers realise.
What a fake delivery attempt actually is
A fake delivery attempt is a scan the courier logs — typically “customer unavailable,” “premises closed,” or “customer refused” — for a delivery that was never genuinely attempted. Nobody knocked, nobody called, but the tracking timeline now records a failed attempt as if they had. On its own, one scan is just data. The damage comes from what it triggers.
Couriers move a parcel to return to origin after a set number of failed delivery attempts. So each fake attempt is not a neutral event — it is a step toward a manufactured RTO. Stack up enough of them and a parcel that a real attempt would have delivered instead comes back to you, carrying the full cost of a failure the customer never caused and you could not have prevented. That is the mechanism, and understanding it is what turns a shrug into a claim.
How to tell a fake attempt from a real one
Not every failed attempt is fake, and crying foul on genuine ones wastes everyone’s time. The signal you are looking for is a mismatch between the scan and reality. The customer was demonstrably at home and reachable. No call or knock happened — the buyer will tell you this directly if you ask. The “attempt” is timestamped at an implausible hour, or several attempts are logged suspiciously close together, faster than a real delivery route would allow.
One failed attempt is normal life. A pattern — failed attempts the buyer confirms never happened, or attempts that cluster on a particular lane or courier — is the thing worth investigating. And the pattern is the more valuable discovery, because a single disputed attempt saves one order, while a spotted pattern lets you fix a source of recurring loss. This is closely related to fake deliveries, where a parcel is marked delivered but never arrives — see building return and delivery evidence.
The evidence that builds a case
A fake-attempt dispute is won by contradicting the courier’s own log with reality. The strongest package combines three things. First, the tracking log itself — the scans, with their timestamps, screenshotted. Second, the customer’s written confirmation that no attempt was made and that they were available. Third, the internal implausibility of the scan: odd timing, or a cluster of attempts too tight to be genuine.
None of these alone is decisive, but together they tell a coherent story: a specific attempt logged as failed did not really happen. As with every dispute, it also has to be raised inside the window, because a strong case filed late is a lost case. The discipline of assembling evidence quickly and completely is the same one that governs RTO recovery and payment reconciliation.
From single disputes to fixing the source
Winning back one order is satisfying; stopping the leak is transformative. Because fake attempts tend to cluster on specific couriers or lanes, the real prize is detection at the pattern level. When you can show that failed attempts concentrate on a particular route or partner, you have something concrete to raise with the marketplace and the logistics provider — a basis to push for genuine delivery attempts where they are not happening.
You cannot fix what you cannot see, and seeing it means treating delivery events as data to be watched rather than fate to be accepted. That is a job for a system that ties every delivery timeline to its order and surfaces the anomalies — an agentic OMS — rather than for a human scrolling tracking pages one parcel at a time. Our courier RTO rates guide covers how to read that lane-level picture.
Sources & further reading
Delivery-status definitions and dispute processes vary by courier and marketplace and are updated over time, so confirm the current terms against the official documentation and your own tracking records:
Four signals an attempt was fake
No single signal proves it, but together they build a case worth raising. Watch for the combination, not just one.
Buyer was reachable
The customer confirms they were home and available, and no call or knock came. Their written word against the “unavailable” scan is the heart of the case.
Implausible timing
The attempt is stamped at an odd hour, or one when the buyer knows nobody came to the door. Timing that does not fit reality is a red flag.
Clustered attempts
Several failed attempts logged too close together to be genuine separate visits. Real routes take time; a tight cluster suggests the scans, not the deliveries, were batched.
Lane or courier pattern
Failed attempts concentrate on one route or partner. The single most valuable signal, because it points to a fixable source rather than a one-off.
Building the dispute package
You are contradicting the courier’s own record with reality. The package that does that reliably has three parts, filed inside the window.
- The tracking log. Screenshots of the scans and their timestamps — the courier’s own account.
- Buyer confirmation. Written word from the customer that no attempt was made and they were available.
- The implausibility. The odd timing or the tight cluster that shows the scan cannot be genuine.
- A same-day filing. Raised inside the window, because a strong case filed late is still a lost one.
The recovery side of this lives in RTO recovery.
Seeing the attempts you would otherwise miss
Nobody has time to scroll every parcel’s tracking timeline hunting for an implausible scan. So the fake attempts stay invisible, the manufactured RTOs pile up, and the loss is written off as bad luck. That is the gap.
Robnu is an agentic OMS: it ties every delivery event to its order and watches for the patterns a human would miss — clustered failed attempts, implausible timing, RTOs triggered by questionable attempts — then flags them and helps assemble the dispute. It files the claim where one applies (a rare approval click while fully-autonomous filing rolls out), and surfaces the lane and courier patterns worth raising at the source.
That is the spine of the whole product: you sell, Robnu runs the rest, and makes sure every rupee is paid correctly.
Fake delivery attempts, answered
A fake delivery attempt is a scan the courier logs — commonly 'customer unavailable', 'premises closed', or 'customer refused' — for a delivery that was never genuinely attempted. Nobody knocked, nobody called, but the tracking now shows a failed attempt. It matters because enough failed attempts push a parcel into return to origin, so a fake attempt manufactures an avoidable RTO that costs you the sale and the freight.
The tell is usually a mismatch between the scan and reality. The customer was demonstrably home and reachable, no call or knock happened, the 'attempt' is timestamped at an implausible hour, or several attempts are logged suspiciously close together. A single failed attempt is normal; a pattern of failed attempts where the buyer confirms nobody came is the signal worth investigating and disputing.
Usually it is not malice but pressure — a delivery executive running behind, a difficult lane, or an address that is genuinely hard to reach, where logging a failed attempt is faster than completing the delivery. The cause does not really matter to you. What matters is that a delivery that could have completed instead becomes an RTO, and you carry the cost of a failure that was not the customer's doing.
The strongest evidence combines the courier's own tracking log with a contradiction of it: the customer confirming in writing that no attempt was made, records showing they were reachable, and the implausibility of the scan itself — odd timing, or clustered attempts. Screenshots of the tracking timeline alongside the buyer's confirmation build a case that a specific attempt did not really happen.
Yes. If a parcel went to RTO because of delivery attempts that did not genuinely happen, that is grounds to raise a dispute rather than silently absorb the loss. You are challenging the premise that delivery was properly attempted. As with any claim, it lives or dies on evidence and on being raised inside the window, so speed and documentation are everything.
Each one that turns into an RTO costs the forward freight you already spent, the margin on a sale that should have completed, and roughly a week of stock tied up coming back. Individually modest, but fake attempts often cluster on specific lanes or couriers, so a persistent pattern quietly inflates your RTO rate and drains margin across many orders. That is why spotting the pattern matters more than winning any single dispute.
Detection is the lever. When you can see that failed attempts cluster on a particular courier or lane, you have something concrete to raise with the marketplace and the logistics partner, and a basis to push for genuine delivery attempts on those routes. You cannot fix what you cannot see, so the first step is systematically flagging suspicious attempts rather than treating each failed delivery as a one-off.
They are related but different. A fake delivery attempt logs a failed attempt that did not happen, pushing the parcel toward RTO. A fake delivery marks a parcel as delivered when it never reached the customer, which is a different and equally costly problem. Both are cases where the courier's scan contradicts reality, and both are disputable with the right evidence.
Robnu watches your order and delivery events, so patterns like clustered failed attempts, implausible timing, and RTOs triggered by questionable attempts surface instead of hiding in the noise. It ties the delivery timeline to the order and flags what looks wrong, then helps assemble and prepare the dispute. Autonomous filing is rolling out, so a rare approval click may still be needed before a claim goes out.
Related seller guides
More on the operations, money and claims that decide whether a marketplace catalogue actually makes money.
Fake delivery attempts: when the scan says attempted but nobody came
Why false delivery-attempt scans happen, the forced RTO and freight they push onto sellers, and the evidence trail — buyer statements, scan times, AWB events — that wins the dispute.
Courier Weight Certificates That Win Weight-Discrepancy Claims
When a courier charges you for a heavier parcel than you shipped, a weight certificate is the evidence that overturns it. What a weight certificate is, why it wins, and how to build the record before you need it.
RTO vs customer return: different problems, different fixes
One is a delivery problem, the other a listing problem. They need opposite remedies and different claim routes — yet most sellers track them as a single number.
Tampered package returns: evidence that wins the claim
Broken seals, re-taped flaps, a parcel lighter than it shipped — the receive-bench routine, courier tamper annotations, and where the claim actually gets filed.
RTO OFD meaning: out for delivery, then back to you
"RTO OFD" means your returned parcel is out for delivery back to your own pickup address. What the status means, the timeline to expect, and what to watch so you are not charged for a parcel that never arrives.
Meesho QC Fail on a Return: Your Claim Window and How to Use It
When a returned Meesho parcel fails quality check, the outcome and your money are decided in a short window. What QC-fail means, the evidence that holds, and the claim path that recovers a wrongly-failed return.
Amazon India SAFE-T claims: when and how to file
SAFE-T reimburses seller-fulfilled losses on returns Amazon's standard policy passed to you. What qualifies, the evidence that wins, and why most of the money is simply never claimed.
RTO vs RTV vs DTO: three returns, three different losses
They look identical on a dashboard and cost completely different amounts. One question separates them, and each needs a different claim route and different evidence.