How to fight a product not received chargeback on Shopify
The tracking said delivered. The customer told their bank nothing arrived. You screenshotted the carrier page, pasted it into the Shopify response, and lost anyway.
That outcome confuses people, because the screenshot looked conclusive. It usually is not.
What the issuer is actually asking you to prove
Shopify files this one under Product Not Received, which its help centre describes as the customer believing goods or services were not delivered.
The issuer is not asking whether you shipped something. It is asking whether the cardholder received what they paid for, at the address on the order, by the date you told them to expect it.
Three different complaints hide under that one label. Nothing arrived at all. Something arrived, but after the date promised. Something arrived, but not where the cardholder lives.
A delivered scan speaks to the first partially, and to the other two not at all.
Why "delivered" on its own is thin
A carrier tracking page proves a parcel moved through a network and got marked delivered. By itself it does not establish which address it reached, that the address belonged to the cardholder, or that the contents matched the order.
Reviewers see a green "Delivered" badge and nothing else constantly. It carries roughly the weight you would expect from something that common.
What turns the screenshot into evidence is the join. The carrier record needs to name a delivery address, or at minimum a city and postal code, that matches the shipping address on the Shopify order. Where the carrier captures a signature, a delivery photo, or delivery geolocation, that is the strongest single artifact available to you, and most merchants never pull it, because it sits one click deeper than the tracking summary.
The evidence, mapped to the version of the claim
Work out which of the three complaints you are answering, then assemble for that one.
| Version of the claim | Core evidence |
|---|---|
| Nothing arrived | Full carrier event history, delivery address match, signature or photo, customer messages referencing the item |
| Arrived late | Delivery estimate shown at checkout, actual delivery date, any delay notice sent |
| Wrong address | Address as the customer entered it, any post-purchase address change, carrier's delivered-to address |
| Only part arrived | Packing list, separate tracking for every parcel |
| Digital product or service | Access or download logs, session IP, accepted terms |
- Nothing arrived. The full carrier event history from acceptance through to the delivery scan, not just the final status. The delivery address as the carrier recorded it. Signature, delivery photo, or geolocation where the carrier captures it. Any message where the customer referenced the item, a colour, a size, or a fault with it, because that is an acknowledgement of receipt in their own words.
- It arrived late. The delivery estimate the customer actually saw, meaning the checkout shipping option or the confirmation email, not your generic shipping policy page. The real delivery date beside it. Any delay notification you sent. If you sent none, do not paper over it.
- It went to the wrong address. The address exactly as the customer entered it, any post-purchase address change with a timestamp and a requester, and the carrier's delivered-to address. Address edits cause more of these than porch theft does, and they are the easiest version to document.
- Only part of it arrived. The packing list, and separate tracking for every parcel in a split shipment. One tracking number against a four-item order invites the reviewer to assume the rest never shipped.
- A digital product or service. Access or download logs with timestamps, the session IP, and the terms the customer accepted at purchase.
What Shopify does for you, and where it stops
If you use Shopify Payments, Shopify's documentation says it automatically collects available data and sends the response to the card company on the due date, and that you can choose to submit immediately instead. For product not received disputes specifically, Shopify says AI-generated insights are included in what it submits.
Treat that as a floor. The auto-collected set covers order, fulfillment, and address data Shopify already holds. It does not include the carrier's event history, the delivery estimate the customer saw, the signature capture, or your support thread. Those are the parts that answer the allegation, and they are the parts you have to go and get.
Shopify puts the response window at usually 7 to 21 days, and it varies. Read the real due date on the dispute in your admin rather than assuming. Shopify also recommends screenshots of tracking pages and customer communications over external links, labelled clearly and legible in high contrast, because plenty of this material still reaches issuers by fax.
Assembling one packet properly runs 20 to 45 minutes, and most of that is hunting rather than deciding. Reclaim pulls the order, fulfillment, carrier, and conversation records together and files before the due date. It costs nothing to run: no install fee, no success fee, and you keep 100% of whatever comes back.
The honest part, including when not to fight
Sometimes the parcel really was taken off a porch, or the carrier really did misdeliver it. Fighting those is a poor use of 40 minutes and it irritates a customer who did nothing wrong.
One constraint shapes that call. Shopify's documentation says you cannot issue a refund once a cardholder has initiated a chargeback, while during an inquiry, where no funds have moved yet, a refund can end it. The window where refunding is still your choice closes earlier than most operators assume, which is a good argument for reading inquiry notifications the day they land.
The other thing worth being blunt about: the dispute counts toward your ratio with the card networks whether you win the representment or not. Winning gets the money back. It does not remove the dispute from the count, which is why a strong win rate and an acquirer warning letter can arrive in the same month.
Good evidence improves the odds of a fair review. Nobody can promise you an outcome, and a vendor who does is telling you something they cannot know.
Frequently asked questions
Does a 'delivered' tracking scan win a product not received chargeback on its own?
Rarely. A carrier tracking page proves a parcel moved through a network and got marked delivered. On its own it does not establish which address it reached, that the address belonged to the cardholder, or that the contents matched the order. It has to be joined to a delivery address that matches the shipping address on the order, ideally with a signature, photo, or geolocation.
Can I refund a customer after a chargeback has already been filed?
No. Shopify's documentation says you cannot issue a refund once a cardholder has initiated a chargeback. During an inquiry, before a chargeback is formally filed and while no funds have moved, a refund can still end it, which is why reading inquiry notifications the day they arrive matters.
What if only part of a multi-item order arrived?
Provide the packing list and separate tracking for every parcel in the shipment. One tracking number against a four-item order invites the reviewer to assume the rest never shipped, so each parcel needs its own trail.
Does Shopify automatically submit evidence for product not received disputes?
If you use Shopify Payments, Shopify says it automatically collects available data and submits on the due date unless you submit sooner, and includes AI-generated insights for this reason code. That auto-collected set covers order, fulfillment, and address data Shopify already holds. It does not include the carrier's full event history, the delivery estimate the customer saw, or your support thread.
The check to run this week
Take your last ten product not received disputes and answer one question for each: does the carrier record name a delivery address that matches the shipping address on the order?
If you cannot answer that in under two minutes per order, your problem is not evidence quality. It is that your carrier data is not reachable from your order data. Fix that join before you write another response.