Delivered not received (DNR) describes an order the carrier marked as delivered that the customer says never arrived. Every DNR claim starts the same way: tracking shows a completed delivery, and a customer insists the package is not there. Some of those claims are porch piracy or misdelivery. Some are fraud. The merchant has to decide which, usually within a single support ticket.
DNR sits at the sharpest ambiguity in post purchase operations because both sides can be telling the truth. The carrier’s scan is real, the empty doorstep may be real too, and the cost of the decision lands on the merchant either way: refund a false claim and fund the fraud, deny an honest one and lose the customer.
Wyllo classifies false delivered not received claims as a post purchase claims pattern inside first-party fraud: a real customer, a real payment, and a dishonest claim. It overlaps with item not received (INR) claims, friendly fraud disputes coded as merchandise not received, and refund abuse.
By the numbers: The theft behind honest claims is real and large: an estimated 104 million US packages were stolen in 2025, worth about $15 billion, and 31% of Americans had a package stolen within a year. The claims that exploit that reality are concentrated: roughly 1% of customers are marked as risky returners, and they are 85 times more likely to be flagged than the general population. Read the Happy Returns and Wyllo return fraud report
Ecosystem Overview
A DNR claim travels through systems that each confirm one thing and assume the rest:
- Carrier tracking that records a scan at a time and place, not who took possession
- Claims and returns platforms that approve or deny by policy rules, not by the customer in front of them
- Customer support tools where “where is my order” pressure pushes agents toward fast refunds
- Card networks whose merchandise not received reason codes convert every unresolved claim into a chargeback
The weak point is that the delivery scan gets treated as proof in both directions. Merchants who deny every claim because “tracking says delivered” push genuine theft victims into disputes the merchant then loses, since a scan alone rarely wins a merchandise not received chargeback. Merchants who refund every claim to protect the experience train bad actors to come back, and to share the policy in fraud communities when they do.
Within the Wyllo platform, Return Fraud and Abuse Prevention scores the claim before the refund, using the customer’s full history of orders, deliveries, claims, and refunds. CX Support puts that signal in front of the agent handling the ticket, so the trusted customer gets an instant resolution and the serial claimant gets verification.
Common Delivered Not Received Scenarios
Porch piracy. The package was delivered and then stolen. The customer is honest, the scan is accurate, and the loss is real. Theft clusters by neighborhood and spikes around peak delivery weeks, which gives merchants corroborating context.
The misdelivery. The carrier scanned the package at the wrong address. GPS coordinates on the delivery scan that sit away from the shipping address are the tell, and the package often surfaces a door or a street over.
The household mix-up. A family member, neighbor, roommate, or mailroom accepted the delivery. Many of these claims resolve themselves within a day, which is a reason to acknowledge fast but refund deliberately.
The false claim. The customer has the package and claims otherwise, through support for a refund or replacement, or through their card issuer as a merchandise not received dispute. The order was legitimate and the identity was real, which is why checkout screening never sees it coming.
The organized version. Coordinated abuse groups file DNR claims at scale, with playbooks that name which merchants refund on the first ticket and what order value stays under review thresholds. One bad actor can run the scheme across dozens of accounts and addresses.
Delivered Not Received vs. Item Not Received
Item not received is the broader claim that an order never arrived. Delivered not received is the specific case where tracking says it did. The distinction matters operationally: an INR claim with no delivery scan points at the carrier and is usually settled with a trace or a reship, while a DNR claim puts the carrier’s record against the customer’s word and leaves the merchant to arbitrate. Card networks group both under merchandise not received reason codes, so in the dispute queue the difference shows up only in the evidence available to fight with.
Supporting Insight
Treating all DNR claims the same fails in both directions, and the outcome data shows how messy the middle is. In 27% of package theft cases the victim received a replacement from the seller and 19% received a refund, while 25% never received any refund at all. Honest victims routinely absorb the loss, and they remember who made them absorb it.
The dispute path is just as noisy: Mastercard and Datos Insights research finds 48% of consumers admit to having mistakenly disputed a legitimate charge. A household mix-up that reaches the bank before it reaches the merchant becomes a chargeback the merchant pays to fight. The claim channel, the timing, and the customer’s history carry more signal than the claim itself.
How Merchants Mitigate Delivered Not Received Claims
Evidence controls raise the quality of what a delivery scan proves: photo on delivery, GPS coordinates captured at the scan, signature for high value orders, and device and session data tying the delivery address to the account. That stack resolves honest claims faster and wins representment cases when a false claim becomes a dispute.
Workflow controls make the response fit the customer instead of the policy: instant reship or refund for customers whose history has earned trust, verification steps for claim patterns, and a dispute-ready evidence file for the small population that files merchandise not received claims as a habit.
Behavioral intelligence connects the claim to everything the merchant already knows: prior DNR and INR claims, refund ratio, linked accounts and addresses, and delivery outcomes across the customer’s lifetime. A false DNR claim is rarely a first offense, and the pattern is visible at the moment the ticket is opened.
Summary
Delivered not received claims force merchants to arbitrate between a carrier’s scan and a customer’s word, with real theft on one side and concentrated, repeatable fraud on the other. Blanket policies lose either way.
The durable fix is intent aware decisioning on the claim itself: strong delivery evidence, a response tiered by the customer’s own history, and friction only where it is earned.
Frequently Asked Questions
Is a carrier delivery scan proof of delivery?
No. A scan proves the carrier recorded a delivery event at a time and place, not that the customer took possession. Photo on delivery, GPS coordinates, and signatures turn the scan into evidence strong enough to resolve claims and win disputes. A bare scan does neither reliably.
Who pays when a package is marked delivered but never received?
Usually the merchant, through a refund, a replacement, or a lost dispute. Carriers reimburse only narrow cases, and only 8.5% of package theft victims report receiving a carrier refund. That asymmetry is why claim decisions deserve the same rigor merchants apply to payment fraud.
How can merchants tell porch piracy from a false claim?
By the pattern, not the ticket. A first claim from a longtime customer in a neighborhood with theft reports reads honest. Repeat claims across orders, addresses, or linked accounts, clustered on high value or easily resold items, mark the serial claimant. The customer’s history decides, because the package cannot.
Can merchants win delivered not received chargebacks?
Yes, when the evidence stack exists. Merchandise not received disputes are winnable through representment with photo and GPS delivery confirmation, signature where captured, and device and session data connecting the order to the cardholder. Merchants who build that file at delivery time, not dispute time, win far more of them.
