Retail payment terminal — chargebacks and card payments context
Article

Delivered But Not Received Chargebacks on Shopify: Building Evidence That Survives Issuer Skepticism

Carrier tracking marked delivered is the starting point, not the finish line. Here's how to pair delivery proof with contact history and contextual signals to build a response issuers can't easily dismiss.

DE

DisputeDesk Editorial

Jun 1, 2026
9 min read
English

The tracking says delivered. The cardholder says it never arrived. Do this first.

Open Shopify Admin → Orders → Disputes. Before you pull a single screenshot, check two things: the reason code and the response deadline. Most delivered-but-not-received (DNR) disputes land under Visa 13.1 (Item Not Received) or Mastercard 4853-INR. A small share arrive coded as unauthorized (Visa 10.4, Mastercard 4837) — which means the cardholder is claiming they didn't make the purchase at all, not just that the package didn't arrive. Those are different fights. Confirm the code before you build anything.

Deadline: Visa gives merchants 20 days from dispute notification. Mastercard timelines vary — confirm with your processor. Set an internal cutoff two days earlier. Carrier signature delays, screenshot exports, and email thread compilation routinely eat that buffer.

What delivery proof actually proves — and where it stops

A carrier scan marked "Delivered" proves the carrier reported a delivery event at a location. It does not prove the cardholder received the package. Issuers know this. Porch theft is real. Misdelivery is real. Carrier scan errors exist. Submitting a tracking screenshot alone and expecting a win is the most common operational failure in DNR disputes.

What delivery proof does well: it establishes that the merchant fulfilled the order, that the package left the warehouse, and that the carrier reported a successful drop. That's a foundation. It's not a case.

What breaks the case open is pairing delivery proof with signals that make the non-receipt claim implausible — or at minimum, inconsistent with the cardholder's own behavior before the dispute was filed.

Step 1: Pull the full delivery record, not just the tracking number

From the order in Shopify Admin, export or screenshot the following before you do anything else:

  • Full carrier tracking history — every scan event, not just the final "Delivered" status. Include the city/state of each scan. If the package traveled from your warehouse to a regional hub to a local facility to the delivery address, that chain matters.
  • Delivery timestamp — exact date and time of the delivery scan, not just the date.
  • Delivery location detail — "Front Door," "Mailbox," "Left with Resident," "Delivered to Agent" — whatever the carrier logged. This matters if the cardholder later claims they were home all day.
  • Signature confirmation record — if you required it. If you didn't require it on a high-value order, note that for your post-dispute policy review.

For UPS and FedEx, delivery photos ("Proof of Delivery" images) are available for most residential deliveries. Pull them. A timestamped photo of your package at the cardholder's front door is the single strongest piece of evidence in a DNR dispute. USPS does not consistently provide delivery photos — confirm availability for your specific shipment with the USPS tracking portal.

Step 2: Pull the customer contact history before the dispute was filed

This is where most merchants lose winnable cases. They submit delivery proof and nothing else. The issuer sees a tracking screenshot and a cardholder saying the package never arrived — and has no reason to favor one over the other.

Customer contact history changes that calculus. Specifically:

  • Did the cardholder contact you about the missing package before filing the dispute? If yes, pull every message — email, chat, SMS, Shopify order notes. Timestamp everything.
  • Did you respond? What did you say? Did you offer a replacement, a refund, or a carrier investigation?
  • Did the cardholder accept a replacement and then file a chargeback anyway? That's a different dispute — document it explicitly.
  • Did the cardholder never contact you at all before the dispute landed? That's also relevant. Note it.

A cardholder who filed a chargeback without ever contacting the merchant is a weaker claimant in the issuer's eyes than one who genuinely tried to resolve it. Not dispositive — but it shifts the narrative.

Step 3: Check the order-level signals in Shopify Admin

Pull the order record from Shopify Admin → Orders → [Order Number]. Review:

  • Shipping address vs. billing address match — a mismatch doesn't mean fraud, but it's context. A match strengthens your position that the package went to the cardholder's own address.
  • AVS and CVV result — visible in the order's payment detail section. Document both.
  • IP address at checkout — Shopify logs this. If the IP resolves to the same city as the shipping address, include it. If it resolves to a VPN or a location inconsistent with the shipping address, that's a flag — but it cuts against you, not for you. Don't include it if it weakens your case.
  • Order history for this customer — has this email or card filed disputes before? Has this address received multiple orders without prior issues? Pattern matters.
  • Fulfillment timeline — how long between order placement and shipment? A same-day or next-day fulfillment with a clean tracking chain is stronger than a delayed fulfillment with gaps.

The $310 order that had delivery proof and still lost

A merchant sold a $310 skincare bundle. USPS tracking showed delivered, front door, 2:14 PM on a Tuesday. The merchant submitted the tracking screenshot and the order confirmation. The cardholder disputed under Visa 13.1. The merchant lost.

What the merchant didn't submit: the email thread where the cardholder had contacted them three days after delivery asking about "the status" of the order — not reporting it missing, just asking. The merchant replied with the tracking link. The cardholder said "ok thanks" and went quiet. Two weeks later, the dispute landed.

That email thread was the case. "Ok thanks" after receiving a tracking link showing delivered is not the behavior of someone who never received a package. The merchant had it. They didn't submit it. The issuer saw a tracking screenshot and a cardholder claim and had no reason to rule for the merchant.

The operational failure wasn't evidence quality — it was evidence scope. The merchant thought delivery proof was the case. It was only the foundation.

Step 4: Build the response narrative — one paragraph, written before you attach anything

Before you compile attachments, write a single paragraph that tells the issuer what happened. This is the narrative line that frames every piece of evidence you submit. Issuers read this first. If it's vague or generic, the evidence gets evaluated without context.

Sample narrative line (adapt to your order):

"The order was placed on [date] and shipped via [carrier] on [date]. Carrier tracking confirms delivery on [date] at [time] to the address provided at checkout, which matches the cardholder's billing address. The cardholder contacted us on [date] — [X] days after the confirmed delivery — asking about the order status. We responded with the tracking confirmation and the cardholder acknowledged receipt of that information. No replacement or refund was requested prior to this dispute. We are submitting the full tracking history, the delivery confirmation, and the complete customer communication record."

That paragraph does three things: it establishes fulfillment, it surfaces the post-delivery contact behavior, and it tells the issuer exactly what evidence is coming. Write it first. Then attach the evidence in the order the narrative describes.

Decision point: fight the dispute or resolve directly with the customer

Before you submit anything, make this call explicitly.

Path A — Fight the dispute. You have delivery proof, a clean tracking chain, and ideally some form of post-delivery contact from the cardholder. The order value justifies the time cost. You submit the full evidence stack and let the issuer decide. Risk: you lose anyway, and the chargeback fee is non-recoverable. Visa and Mastercard dispute fees typically run $15–$25 per dispute, confirm exact amounts with your processor. Win rate on well-evidenced DNR disputes with delivery photos and contact history is meaningfully higher than tracking-only submissions — but not guaranteed.

Path B — Resolve directly and withdraw. The order value is low (under $50 is a common threshold merchants use, but set your own), you have no delivery photo, and the cardholder has no prior dispute history with you. Issue a refund, contact the cardholder directly, and document the resolution. In Shopify Payments, you can submit evidence or accept the dispute — accepting closes it without a fight. If you refund before the dispute closes, confirm with your processor whether the dispute still needs to be formally accepted or whether the refund satisfies it automatically. Processor behavior varies here.

The consequence of fighting without strong evidence isn't just losing — it's losing and paying the dispute fee. The consequence of always conceding is training a segment of your customer base that disputes work. Neither extreme is right. Make the call per order, not per policy.

Step 5: Assemble and sequence the evidence package

Submit in this order — issuers read top to bottom:

  1. Response narrative (the paragraph you wrote in Step 4)
  2. Full carrier tracking history — every scan, not just the final status
  3. Delivery photo if available (UPS, FedEx — pull from carrier portal before it expires; some carriers purge photos after 30–90 days)
  4. Signature confirmation record if applicable
  5. Order confirmation showing shipping address, billing address, and fulfillment date
  6. Customer communication history — every message, in chronological order, with timestamps
  7. AVS/CVV match confirmation from the Shopify order payment detail
  8. Any prior order history showing successful deliveries to the same address

Do not submit everything you have. Submit what supports the narrative. A 40-page evidence packet with irrelevant screenshots reads as desperation, not thoroughness. Issuers have limited review time per dispute.

When the address is a reshipper or freight forwarder

If the shipping address resolves to a known freight forwarder or reshipper — common in international orders routed through a US address — the DNR claim pattern changes. The cardholder may genuinely not have received it because the forwarder lost it, or the dispute may be coordinated fraud using a forwarder as a buffer.

In these cases, your delivery proof shows the package arrived at the forwarder, not at the cardholder. Issuers generally do not hold merchants liable for what happens after confirmed delivery to a customer-designated address — but this varies by network and issuer. Visa's rules under 13.1 typically protect merchants who can show delivery to the address provided at checkout. Mastercard's 4853-INR has similar protections. Document that the address was customer-provided at checkout, that delivery to that address is confirmed, and that you had no visibility into the downstream logistics. Include a screenshot of the checkout address field from the Shopify order.

Internal note before you close the workflow

After submitting, log this in your internal system or in the Shopify order notes field:

"DNR dispute submitted [date]. Evidence: tracking history, delivery photo [yes/no], customer contact thread [yes/no], AVS match [yes/no]. Narrative framing: post-delivery contact behavior. Decision: fought. Follow up on outcome by [deadline + 5 days]."

This note exists for two reasons. First, if the dispute escalates to arbitration, you need a clean record of what was submitted and when. Second, if you lose, the note tells you exactly which evidence was missing — so the next DNR dispute from a similar order profile gets a stronger response.

What to fix before the next DNR dispute lands

Signature confirmation on orders above your average order value is the single highest-leverage operational change for DNR disputes. It doesn't eliminate them — cardholders can still claim the signature wasn't theirs — but it raises the evidentiary bar significantly. Set the threshold based on your product category and average dispute rate, not a generic dollar amount.

Delivery photo availability is carrier-dependent. If you're shipping primarily via USPS and losing DNR disputes, consider adding UPS or FedEx for high-value orders specifically because of photo availability. That's an operational cost decision, but it's a real one.

Post-purchase confirmation emails with tracking links, sent automatically via Shopify's order notification settings, create a paper trail showing the cardholder was informed of the shipment. They're not evidence of receipt — but they're evidence of notification, which matters when a cardholder claims they had no idea the order was coming.

Key Takeaways

Carrier tracking marked 'Delivered' is a foundation, not a case — pair it with post-delivery customer contact history to make the non-receipt claim implausible.
Delivery photos from UPS and FedEx are the strongest single piece of evidence in a DNR dispute; pull them before they expire (some carriers purge after 30–90 days).
A cardholder who contacted you after delivery and acknowledged the tracking confirmation — then filed a dispute weeks later — is a weaker claimant. That email thread is your case.
Write the response narrative before you attach a single file. Issuers read it first; it frames everything that follows.
Decide explicitly whether to fight or concede per order — fighting without delivery photos and contact history on a low-value order often costs more in fees than the dispute itself.

FAQ

Does a Shopify tracking number marked 'Delivered' automatically win a delivered-but-not-received chargeback?
No. Carrier delivery confirmation establishes that a delivery event was reported — not that the cardholder received the package. Issuers weigh it alongside other signals. Without supporting evidence like delivery photos or customer contact history, a tracking screenshot alone frequently loses.
What's the difference between a Visa 13.1 and a Visa 10.4 dispute for a missing package claim?
Visa 13.1 is Item Not Received — the cardholder acknowledges making the purchase but says the item didn't arrive. Visa 10.4 is unauthorized — the cardholder claims they didn't make the purchase at all. The evidence strategy is different for each. Confirm the reason code in Shopify Admin → Orders → Disputes before building your response.
Should I refund the customer before the dispute deadline to avoid the chargeback fee?
It depends on your processor. Some processors will close the dispute automatically if a refund is issued before the deadline; others require you to formally accept the dispute separately. Confirm with your processor. Issuing a refund without formally accepting the dispute can result in both the refund and the chargeback fee being applied.
How long do I have to respond to a delivered-but-not-received chargeback on Shopify?
Visa gives merchants 20 days from dispute notification. Mastercard timelines vary by reason code — confirm with your processor. Set an internal deadline two days earlier to account for evidence compilation time.
What if the shipping address was a freight forwarder and the package was delivered there?
Visa 13.1 and Mastercard 4853-INR generally protect merchants who can show delivery to the address provided at checkout, regardless of what happens downstream. Document that the address was customer-provided, confirm delivery to that address, and include a screenshot of the checkout address field from the Shopify order. Issuer interpretation can vary — confirm with your processor for high-value orders.

Disclaimer

This content is for informational purposes only and does not constitute legal advice.

Automate Your Chargeback Responses

DisputeDesk automatically tracks deadlines, collects evidence, and generates winning responses so you never miss a deadline again.