Delivered But Not Received Chargebacks on Shopify: What Actually Wins

Tracking Says Delivered — That's Not What the Issuer Is Asking

When a customer files a 'delivered but not received' chargeback, the dispute isn't about whether the carrier dropped the package. It's about whether the cardholder received it. Issuers draw that line deliberately, and most merchants lose because they submit tracking confirmation and AVS as if those two data points close the case. They don't.

Before you build a response, open Shopify Admin and work through the order systematically. Under Orders > Fulfillment, confirm the fulfillment status and pull the tracking number. Under Orders > Customer Details, compare the shipping address against the billing address — document any match or mismatch explicitly. Under Orders > Tracking Information, note the exact delivery timestamp and location description the carrier logged. Under Orders > Customer Communication, pull every message thread: contact attempts, replies, any acknowledgment from the customer. Then check Shopify Protect status on the order — if it shows PROTECTED, that changes your calculus before you spend time building a response package.

Visa and Mastercard may weight evidence differently depending on processor routing, and Shopify Payments handles evidence submission differently than third-party gateways like Stripe — confirm your exact deadline and submission format with your processor before you do anything else. Missing the response window is an automatic loss regardless of how strong the evidence is.

What Each Piece of Evidence Actually Proves — and Where It Stops

Three evidence types dominate these disputes, and all three have a ceiling issuers know how to exploit.

Tracking marked delivered confirms the package reached the delivery address. A carrier log reading "Delivered on 10/05/2023 at 2:45 PM, left at front door" is useful — but issuers routinely argue that delivery to an address is not delivery to the cardholder, particularly in apartment buildings or shared-access properties. Tracking alone rarely closes a dispute at the issuer level.

AVS Y tells you the billing address matched at authorization. It supports transaction legitimacy, but issuers will note that AVS says nothing about whether the cardholder physically received a shipment. Use it as corroborating context, not as your lead argument.

Carrier delivery photos are the strongest single piece of evidence in this dispute type — a timestamped photo of the package at the delivery location is harder to dismiss than a status update. But even photos have a ceiling: if the cardholder claims the package was stolen post-delivery or left at the wrong unit, the photo shows placement, not receipt. Pair photos with GPS delivery coordinates if your carrier provides them, or a signed delivery confirmation if the order value justified requiring one at shipping.

The honest read: no single piece of evidence wins these disputes. The issuer is looking for a package of proof — tracking plus photo plus communication log plus address verification — that makes the non-receipt claim implausible, not just unproven.

The $300 Fashion Order That Lost With Full AVS and a Delivery Photo

A fashion merchant with a $150 average order value processed a $300 order on October 1. Full AVS match at authorization. Shipped October 2 with tracking. Carrier marked it delivered October 5 — front porch, timestamped. The customer filed a chargeback on October 10 claiming non-receipt.

The merchant pulled the tracking confirmation and the AVS result and submitted both as the response. They also had a carrier delivery photo — package visible on the porch, timestamp matching the carrier log — but treated it as redundant given the tracking data. They did not include it. They had a customer email from October 8, two days before the chargeback, where the customer asked about the order status. That email was not included either.

The issuer ruled for the cardholder. The tracking showed delivery to an address. The AVS showed a billing match. Neither proved the cardholder received the package. The merchant had the two pieces of evidence that might have shifted the outcome — the photo and the communication log — and left both out of the submission.

The photo would have shown the package at the specific delivery location, making a misdelivery claim harder to sustain. The October 8 email, depending on its content, could have established that the customer was aware of the delivery timeline and did not immediately dispute it — a behavioral signal issuers sometimes weigh. Neither piece is a guaranteed win, but both materially strengthen the case. Submitting tracking and AVS without them was an operational loss, not an evidence loss.

Decision lesson: A case is fightable when tracking, delivery photo, GPS data, and communication logs are submitted together as a package. It's weak when the merchant stops at tracking and AVS — not because the evidence doesn't exist, but because it wasn't pulled and included. Check every evidence source before you submit, not after you lose.

Before You Submit: What to Verify

Work through this before the response goes out. Confirm the dispute status and deadline inside Shopify Admin — the clock is real and processor deadlines vary, so verify the exact date with your processor rather than assuming. Check Shopify Protect status on the order; if it's PROTECTED and ACTIVE, understand what coverage applies before deciding whether to fight or accept. Confirm the dispute reason code and make sure your evidence package addresses what that code actually requires — 'item not received' has specific issuer criteria that differ from fraud codes.

Pull the carrier delivery photo if one exists; do not assume tracking data makes it unnecessary. Pull every customer communication from the order — pre-dispute contact attempts matter to issuers. Document the address comparison between billing and shipping explicitly; don't leave the issuer to infer a match. If the order value was high enough that signature confirmation should have been required at shipping, note whether it was or wasn't — that affects how you frame the response. Regional delivery service differences can affect what constitutes acceptable proof, particularly for international orders, so confirm with your carrier what documentation they can provide beyond the standard tracking log.

DisputeDesk handles evidence assembly and deadline tracking automatically from your Shopify order data — merchants still own the accuracy check and the final submission decision. Once the package is built, the fight-or-accept math is straightforward: if you have tracking plus photo plus communication log, fight. If you have tracking and AVS only, the case is weak regardless of what the carrier log says.