Tracking Says Delivered, Customer Says Not Received: A Seller’s Playbook

The tracking says “Delivered.” Your customer says nothing arrived. When tracking says delivered but the customer says not received, do not refund or refuse on instinct. Spend five minutes checking the carrier scans, the GPS pin, and the customer’s order history, then decide based on order value and risk signals. That one habit protects both your margin and your good customers.

Here is the frustrating part. Usually nobody is lying. The driver really did scan the package. The customer really did check the mailroom and knock on a neighbor’s door. Something went wrong in the gap between those two moments.

These claims are called item not received claims, or INR claims for short. They hurt twice. You lose the product. If the buyer skips you and disputes the charge with their bank, you lose the payment too. Add a dispute fee and a mark against your merchant account, and one $80 order can cost you well over $150.

This guide walks through the full workflow. How to triage a claim, when to refund, when to fight, what evidence actually wins, and how to write the policy before the next claim lands.

Why “Delivered” Does Not End the Conversation

Many sellers treat a delivered scan as the finish line. Tracking closed, order closed. That works most of the time. It does not work every time.

A tracking status is built from scans, and scans can mislead. A driver may scan a package the moment it leaves the truck, before it is placed anywhere. A GPS ping can register the truck on the street rather than the doorstep. Packages land at the wrong unit in apartment buildings, at the wrong house in gated communities, and at look-alike addresses on the same street.

Then there is the human layer. Some claims are genuine porch theft, where the package arrived and someone walked off with it. Some are friendly fraud, where the buyer knows it arrived and disputes anyway. Some are simply a spouse who brought the box inside and forgot to mention it.

So treat a delivered scan as a data point, not a verdict. Close every claim on the scan alone and you hand free products to the small group gaming you. Refund every claim on reflex and you invite more of them. A consistent process is what separates the two.

How to Triage an INR Claim in Five Minutes

Before you refund, reship, or push back, gather the same facts a bank would look at. This is not an interrogation. It is a short evidence check so your decision is informed rather than emotional.

Read the full carrier scan history, not just the last line

Open the complete tracking history and read it as a timeline. Does the sequence make sense? A package that jumps between distant facilities in an hour usually points to a scanning glitch or a mislabeled parcel. A delivery scan that lands hours outside the normal route window is worth a second look too.

Some carriers attach a delivery photo. Look at it closely. A visible house number, a distinctive door, or a recognizable porch tells you a lot. A photo of a generic brick wall tells you almost nothing.

Check the GPS pin against the shipping address

If your shipping platform shows GPS coordinates for the delivery scan, compare the pin to the address on the label. A pin sitting on the building is meaningful support. A pin a block away, or on a different building, points toward carrier error and changes your whole response.

Compare the address the customer actually uses

Pull the buyer’s past orders. Did they just move? Is this a brand new address? Is the apartment number missing or mistyped? A label and address mismatch is the most common, least dramatic explanation for a missing package, and it is usually fixable without any conflict.

Review the buyer’s order and claim history

A first claim from a customer on their fifteenth order is a different situation from a $400 first order on a three-day-old account. Neither pattern proves anything alone. Together with the scan data, they usually point clearly in one direction.

Refund, Reship, or Fight: Making the Call

After triage you have three options. Refund, reship, or contest. Order value and buyer history decide which one fits.

Low order value with a clean customer history

Refund or reship, quickly. A dispute fee plus your time can easily exceed the value of a $20 product. Beyond the math, speed here is cheap marketing. A customer who gets an instant replacement tells a friend. A customer forced to file a bank dispute tells everyone.

High order value with a clean customer history

Take the middle path. Offer a reship with signature confirmation this time, or a partial resolution while you file a claim with the carrier. Many carriers reimburse sellers for high-value lost parcels, so the loss is not always yours to absorb. Do not open with suspicion just because the number is bigger. That is how you lose good customers to bad luck.

Any order value when red flags are present

Push back when the pattern is clear. Multiple INR claims from one account. A brand new account placing a large first order. A shipping address that does not match billing. Or several different customer names all shipping to the same address. In those cases, decline the request, and if it becomes a chargeback, submit your evidence rather than eating the loss by default.

One important distinction. If the buyer never contacted you and went straight to their bank, you are no longer in customer service. You are in a dispute, on the card network’s clock, and the evidence you can produce in the next few days is the whole game.

What Proof Actually Wins an INR Chargeback

Not all evidence carries the same weight. Banks and card networks want proof that ties the delivery to the customer, not merely to a street address. Here is the hierarchy, strongest first.

Signature confirmation

A signature, physical or electronic, matched to the recipient is the strongest evidence you can hold. It answers the question the bank actually cares about: did someone at this address take possession of this package? Very few INR disputes survive it.

Delivery photo showing the correct address

A clear photo of the parcel at a doorstep that matches the shipping address carries real weight, especially when a house number or another identifying detail is in frame. It is not as airtight as a signature, because a photo proves placement rather than receipt.

GPS pin data and plain tracking status

GPS supports your case but rarely carries it. It records where the driver’s device was, not whether the package reached the customer’s hands. Pair it with a photo or a signature. A bare delivered status with no photo, pin, or signature is the weakest submission you can make and usually loses.

Where to Set Your Signature Confirmation Threshold

Signature confirmation is your best defense, but it costs money and adds friction. You do not need it on every order. The smart move is to pick a dollar figure and require a signature above it.

There is no universal number. The right threshold depends on your margins, your average order value, and what a missing package truly costs you once you add the product, the dispute fee, and the staff time.

A worked example you can copy

Say you sell a $95 item that costs you $38 to make and $9 to ship. A chargeback on that order pulls back the full $95. Your processor generally keeps the fee it already took on the original sale. It then adds a separate per-dispute fee, usually whether you win or lose. Finally, add the 40 minutes someone spends assembling evidence. The all-in loss sits far above the $38 of product.

There is a second cost most sellers miss. You have to earn the money back. At a 40% net margin, a $600 run of losses needs $1,500 of new sales just to return to level. That is why prevention beats recovery, and why a few dollars of signature confirmation pays for itself after a small number of prevented claims.

Run the same arithmetic on your own figures with the chargeback cost calculator. It adds the four pieces above, subtracts the share you expect to win back, and shows your dispute ratio, which card networks monitor. Confirm your actual per-dispute fee on your processor’s live fee schedule first, and use the payment processor fee calculator if you are comparing Stripe, PayPal, Square, and ACH. Then look at where your INR claims cluster by order value. Your threshold belongs at the point where a single loss stops being annoying and starts being painful.

For many small and midsize sellers that point sits somewhere between $75 and $150. Thin-margin businesses should set it lower. Strong-margin businesses can set it higher and accept a few losses in exchange for a smoother checkout. Whatever you pick, publish it at checkout. Customers accept a signature requirement they knew about in advance, and legitimate buyers almost never object.

Porch Piracy vs. Friendly Fraud vs. Carrier Error

Almost every INR claim traces back to one of three causes. Naming the right one keeps your tone and your decision aligned.

Porch piracy means someone took the package after a legitimate delivery. Your customer is the victim, even though you carry the loss unless a carrier claim or shipping insurance covers it. Handle these gently.

Friendly fraud means the buyer received the order and claims otherwise. Sometimes the intent is a free item. Sometimes they genuinely misplaced the box and honestly believe it never came. The evidence pattern, not the tone of the email, tells you which.

Carrier error means the delivery company made a mistake. Wrong address, wrong label, or a scan recorded before the drop. These resolve quickly once you spot them, and they are far more common than most sellers assume.

Writing the Policy Before You Need It

The best time to build your INR process is before a wave of claims arrives. A written policy does two jobs. It keeps your team consistent, and it tells customers what to expect when a package goes missing.

Your policy should answer these points in plain language:

• The order value at which signature confirmation becomes mandatory.
• How many days a customer has to report a missing package, aligned with your carrier’s own claim deadline.
• How you treat a first claim versus a repeat claim from the same account.
• What happens when the shipping address does not match the customer’s records.

Write two versions. A short, friendly one for the customer-facing shipping page, and a longer internal one your team follows step by step. That internal document matters more than it looks. If a dispute reaches a card network review, being able to show that you apply the same review process to every claim is a genuine strength, not paperwork.

While you are documenting things, tighten the money side too. Clear terms and deadlines stop small problems from becoming write-offs, and our invoicing and payments guide covers the same discipline for the invoices you send. If a run of losses would dent your cash position, the emergency runway calculator shows how many months your reserves actually buy you.

Merchant Services Direct

Some cases are not simple missing packages at all. Triangulation fraud, where stolen card details fund orders that look perfectly legitimate on the surface, needs a different evidence approach, including material that meets the Compelling Evidence 3.0 framework. If your claims look like an organized pattern rather than scattered bad luck, Merchant Services Direct covers that territory in more depth.

Conclusion

When tracking says delivered but the customer says not received, the outcome depends far more on your process than on any single claim. Triage first. Read the whole scan history, check the pin, compare the address, and look at the buyer’s record. Then decide by value and risk, refunding small orders quickly, reshipping larger ones with a signature, and contesting only when a real pattern shows up.

Collect stronger proof as a habit, not as a reaction. Set a signature threshold that matches your margins, publish it, and write the policy down before the next claim arrives. Do that and INR claims stop being a monthly emergency. They become a routine you handle in five minutes.

If you want more plain-English guidance on protecting the money side of a small operation, start with our contracts and money guide, then subscribe to the Freelance Treasury newsletter for one practical breakdown a week.

FAQs

This article is educational and does not constitute legal, tax, or financial advice for your specific situation. Card network rules, carrier claim windows, and processor dispute fees change; verify current terms with your processor and carrier before setting policy.