Item Not Received Claim? Prove Delivery and Win

The two very different battles behind a 'parcel never arrived' claim — and the proof of delivery that actually holds up in each.

AI-assisted content notice. This article was drafted with AI assistance and reviewed by a human editor at Hail Pilot before publishing.

Why an Item Not Received Claim Is the Friendly-Fraud Sweet Spot

Of all the ways a buyer can take goods and their money back, the item not received claim is the cleanest, because it puts the burden of proof on you and hands the buyer a story that is hard to disprove without records. A buyer who claims the item was faulty has to describe the fault. A buyer who says the parcel never arrived only has to say it did not come.

That asymmetry is why item not received (INR) is the most abused claim type across marketplaces and card networks alike. The honest version is real: parcels do go missing, couriers do misdeliver, porch theft happens. The dishonest version rides on the honest one. A false not received claim looks identical to a genuine one at the moment it lands, and the seller who cannot produce delivery evidence loses both outcomes the same way.

Here is the mechanic that costs you money. On most marketplaces, if you cannot show a delivered-status scan tied to the order, the platform sides with the buyer and the refund is automatic. On a card chargeback, if you do not respond with evidence inside the window, the reversal stands by default. Silence is a loss. The buyer keeps the goods, keeps the money, and you eat the cost of goods plus the shipping plus, on the card side, a chargeback fee.

The defensible sellers are not the ones who argue best. They are the ones who kept the delivery trail before the claim ever existed. Everything below is about building that trail and using it in the right forum.

Two Different Fights: Marketplace Dispute vs Card Chargeback

The single most expensive mistake is treating a marketplace INR dispute and an INR chargeback as the same problem — they have different judges, accept different evidence, and run on different clocks. A buyer can even try both: open a not received case on Shopee or Lazada, lose it, then call the bank and file a chargeback on the same order. You defend each in its own forum.

A marketplace dispute is decided by the platform's resolution team. It reads courier tracking, in-app chat, and any photos you upload, and it moves fast, often a few days from a short response window. The evidence that wins is native to the platform: the tracking number already attached to the order, the delivered scan, and the chat thread where the buyer discussed delivery.

A card or bank chargeback is decided by the card scheme through the buyer's issuing bank. You respond through your payment processor or acquirer with a formal representment: a written rebuttal plus proof of delivery documents. The clock is set by the card network, not the marketplace, and the acceptable proof is stricter. The scheme usually wants a delivery confirmation showing the address, and for higher-value goods, often signature or a recipient identity match.

	Marketplace INR dispute	INR card chargeback
Who decides	Platform resolution team (Shopee, Lazada, Amazon.sg)	Card scheme, via the buyer's issuing bank
You respond through	The Seller Centre dispute panel	Your payment processor / acquirer (representment)
Evidence it accepts	Courier tracking, delivered scan, in-app chat, photos	Formal proof of delivery: tracking + address, often signature / recipient match
Timeline	Short review window, decided in days	Scheme-defined window; check your processor's exact deadline
Default if you stay silent	Refund to buyer	Reversal stands, plus a chargeback fee
Where abuse tends to land	Marketplace-native purchases	Card-on-file, off-platform, or high-value orders

Card-scheme windows and exact documentation rules differ by network and by processor, and they change. Treat the timeline as "check your processor's current representment deadline for this reason code," never as a fixed number you memorised once. The point that does not change: on both sides, no evidence means an automatic loss.

Proof of Delivery That Actually Holds Up

Weak proof of delivery says a parcel was delivered somewhere; strong proof of delivery ties a delivered scan to this buyer, this address, and this order — and that difference decides the case. A raw "Delivered" status with no address and no recipient is the most common reason a defensible order still loses. The buyer says "delivered where? Not to me," and a bare status line cannot answer.

Build the chain. Every link you can add moves the case from arguable to closed.

Courier tracking to a delivered status. The baseline. A tracking number that reaches "Delivered," with the timestamp, on the courier's own portal, not a screenshot you could have typed.
POD with signature, photo, or geotag. A proof of delivery capture at the doorstep: a signature, a photo of the parcel at the address, or a GPS geotag of the drop. Higher-value orders should carry signature-required POD by policy, not by luck.
Recipient name and address match. The delivery record should show the same name and address as the order. A match closes the "not to me" argument; a mismatch is your early warning that something is genuinely wrong.
Locker or collection-point pickup log. If the parcel went to a parcel locker or a pickup point, the collection log (the timestamp and the code or account that opened the locker) is often the strongest single record you have, because the buyer's own action retrieved it.
Correlating chat. In-app messages where the buyer asked "where is my order," gave revised delivery instructions, or acknowledged receipt. Chat that places the buyer in the delivery conversation undercuts a later "it never came."

The strong version of a case reads as one story: order placed, dispatched on this date, courier scan to Delivered at this address on this timestamp, POD photo at the door, buyer's own chat message two days earlier confirming the address. The weak version is a lone status line and a hope.

Consider an illustrative order: a buyer files a not received claim eleven days after a locker pickup. You pull the collection-point log showing the parcel code was scanned out at 7:14pm on the delivery date, alongside a chat message where the same buyer had asked you to route it to that exact locker. The claim does not survive contact with that record. That is what "holds up" means — not volume of documents, but a chain no reasonable reviewer can break.

For the marketplace side, our Shopee dispute evidence guide walks the exact upload steps and what the resolution team weighs first.

Prevention: Lower Your INR Rate Before the Claim

You cannot stop a buyer from filing a false not received claim, but you can decide in advance whether you will have the proof to win it — and that decision is made at ship time, not at dispute time. Prevention is cheaper than every representment you will ever write.

Set your shipping policy by order value, not by habit. Low-value orders can run on standard trackable shipping. For higher-value orders, require signature or photo POD, because those are the orders a chargeback will target and the orders where a bare scan will not carry the day. The extra courier cost on a high-value parcel is small next to losing the goods and the money together.

Use trackable shipping on everything you can. An untracked parcel is an INR claim you have already lost, with no delivered scan to point at. Capture handover proof at the point the parcel leaves you: the pickup booking confirmation, the drop-off receipt, the weight slip. That handover record is what separates "we shipped it" from "we can prove we shipped it."

Then watch for the repeat pattern. A buyer who files not received on order after order, across time, is a signal — but a first-time buyer with no history is not. This is where risk scoring earns its place, and where the framing matters: a buyer with no record is treated as unknown, neutral, and not guilty by default. You are not blacklisting anyone. You are noticing when the same behaviour repeats against your own orders, which is exactly what a delivery dispute pattern looks like before it becomes a habit.

Hail Pilot scores buyer and return risk across your own orders and flags repeat behaviour, so a serial not received filer surfaces before you refund them for the third time. Cross-merchant signals, where they exist, use HMAC-hashed tokens and never raw personal data — the pattern travels, the identity does not. For the wider abuse picture, see detecting serial refund abusers and our breakdown of return and refund fraud on Shopee and Lazada.

Responding Step by Step: Marketplace Dispute and Chargeback Representment

Both fights follow the same shape (assemble the delivery chain, write a factual rebuttal, submit inside the window, escalate if needed), but the forum and the wording differ, so run them as two separate playbooks. Do not send the marketplace narrative to the card scheme, and do not send scheme paperwork into a Seller Centre chat.

Assemble the proof of delivery pack. Pull the courier tracking to delivered status, the POD (signature, photo, or geotag), the recipient name and address match, any locker or pickup-point log, and the correlating chat. Put them in delivery order so the record reads as a timeline.
Write a factual rebuttal. State what was ordered, that it was delivered, and the evidence that proves it — in that order. Cite the delivered scan timestamp, the address match, and the pickup log. No emotion, no "please kindly reconsider." A reviewer quotes facts, not feelings.
Submit inside the window. For a marketplace dispute, respond in the Seller Centre panel before the review window closes. For a chargeback, submit representment through your processor before the scheme deadline. A missed window is a default loss on both sides, regardless of how strong your evidence was.
Escalate with new evidence only. If a marketplace dispute is rejected and you have net-new proof, use the platform's escalation path. If a chargeback representment fails, arbitration exists but carries its own cost and risk — weigh it against the order value before you push further.

For the marketplace playbook applied to a specific platform, winning a Lazada dispute in Singapore covers the panel steps and the evidence order the resolution team expects.

The Hail Pilot evidence engine builds step 1 for you: it pulls order data, chat logs, tracking, and photos into one dispute case file per order, so when a not received claim lands, the delivery chain is already assembled instead of scattered across four tabs. The dispute copilot then drafts the factual rebuttal for a human to approve before it goes out. You still decide; the assembly is done.

Frequently Asked Questions

What is an item not received claim? It is a buyer claiming that an order they paid for never arrived. It can be filed as a marketplace dispute inside the platform, or as an INR chargeback through the buyer's bank or card scheme. Both reverse the payment unless the seller proves delivery.

How do I prove a parcel was delivered? With a chain, not a single line. Courier tracking to a delivered status, a proof of delivery capture (signature, photo, or geotag), a recipient name and address that match the order, and any locker or pickup-point log. Correlating chat where the buyer discussed the delivery strengthens it further.

Is a marketplace dispute the same as a chargeback? No. A marketplace dispute is decided by the platform against tracking and chat on a short timeline. A chargeback is decided by the card scheme through the buyer's bank, needs formal proof of delivery submitted as representment, and runs on the scheme's own deadline. A buyer can attempt both on the same order.

What is chargeback representment? It is the seller's formal response to a chargeback: a written rebuttal plus proof of delivery documents, submitted through your payment processor or acquirer. If you do not submit it inside the scheme window, the reversal stands and a chargeback fee is usually added.

Can a buyer really keep the item and get a refund? On a false not received claim, yes — if you cannot prove delivery. That is why it is the friendly-fraud sweet spot. The defence is evidence you captured at ship time, not an argument you make after the claim.

How do I spot a false not received claim? Look for the pattern against your own orders: the same buyer filing not received repeatedly over time. A first-time buyer is treated as neutral and not guilty by default. Risk scoring flags the repeat filer without blacklisting anyone on a single claim.

Does signature on delivery help against chargebacks? Yes, especially on higher-value orders. Card schemes weigh formal proof of delivery, and signature or a recipient identity match is stronger than a bare delivered scan. Requiring signature POD on high-value orders by policy is one of the cheapest ways to lower your INR loss rate.

What happens if I ignore an INR chargeback? You lose by default. The reversal stands, the buyer keeps the goods and the money, and your processor adds a chargeback fee. Even a weak representment submitted on time beats silence.

Stop Eating Refunds for Goods You Delivered

You did the hard part — you shipped the order and it arrived. Losing it to a not received claim comes down to whether the delivery proof is assembled and used in the right forum before the window closes. Hail Pilot pulls tracking, chat, order data, and photos into one case file per dispute, scores repeat not received behaviour across your own orders, and drafts the rebuttal for you to approve. See how the evidence engine and dispute copilot work together across your connected channels.

Prove delivery once, win the claim, and keep the money you earned. Start free.

By Charlie Lee — Founder, Hail Pilot. Reviewed 2026-07-07.

'Item Not Received' Claims: Prove Delivery, Win