Shopify Chargeback Evidence for Product Not Received: Assemble the Case Before the Deadline Hits

When an INR dispute lands, pull these four things before you open the order

Open Shopify Admin → Orders → Disputes. The reason code reads something like Visa 13.1, Mastercard 4853-INR, or Mastercard 4855. Before you screenshot anything, confirm the response deadline — Visa gives 20 days from dispute creation; Mastercard timelines vary by acquirer, so confirm with your processor. Set your internal cutoff two days earlier. That buffer is where most merchants lose winnable cases.

Then pull four things in this order:

1. The full carrier tracking record — not the Shopify shipping summary, the carrier's own tracking page with every scan event
2. The customer contact history — every email, chat, or support ticket before the dispute was filed
3. The order-level signals in Shopify Admin: billing address, shipping address, IP, fulfillment timestamps
4. Your shipping confirmation email — the one sent to the customer with the tracking number and estimated delivery window

That's your working set. Everything else is supplemental.

What the issuer is actually evaluating

For INR, the issuer is asking one question: did the merchant demonstrate that the goods were delivered to the address the cardholder authorized? Not shipped. Not in transit. Delivered.

Tracking confirmation alone answers about 60% of that question. The rest comes from contextual signals — address match, prior contact, delivery scan specificity. Merchants who submit only a tracking screenshot are submitting an incomplete answer.

Delivery scans matter more than delivery status. A scan showing "Delivered, Front Door, 2:14 PM" at the correct ZIP code is stronger than a status line reading "Delivered." If your carrier provides GPS-anchored delivery confirmation (UPS, FedEx, and some USPS services do), include that. It's harder to dismiss than a status flag.

Signature confirmation is the strongest single piece of delivery evidence for high-value orders. If the order was over $200 and you didn't require signature, that's an operational gap — not an evidence gap. You can't fix it retroactively, but you can note it internally for future policy.

Step 1: Pull the carrier record — the right way

Go to the carrier's tracking portal directly. Copy the full tracking detail page — every scan event, timestamp, and location. Do not rely on Shopify's shipping summary or the email confirmation screenshot alone. Issuers have seen merchants submit the shipping confirmation email as "proof of delivery" — it proves shipment, not delivery.

What to capture:

• Every scan event from label creation through final delivery
• The delivery timestamp and location descriptor ("Front Door," "Mailroom," "Left with Resident")
• The ZIP code or city shown in the final scan — confirm it matches the order's shipping address
• If available: GPS coordinates or delivery photo (UPS My Choice, FedEx Delivery Manager, USPS Informed Delivery)

If the tracking shows a delivery exception — attempted delivery, held at facility, returned to sender — stop. That's a different scenario and a much harder fight. An exception record submitted as delivery proof will lose immediately.

Step 2: Pull the contact history — and read it carefully

This is where most merchants underinvest. The contact history before the dispute was filed is often the most decisive evidence in an INR case.

If the customer never contacted you before filing the dispute, that's a signal worth noting in your response narrative. Cardholders with genuine non-receipt almost always reach out first. Cardholders committing friendly fraud often skip that step and go straight to the issuer.

If the customer did contact you, read the thread carefully. Look for:

• Did they ask where the package was, or did they immediately demand a refund?
• Did they reference a specific delivery problem (wrong address, stolen from porch) or give a vague complaint?
• Did they accept a replacement offer and then still file a dispute?
• Did they contact you after the dispute was already filed?

A customer who emailed "where is my order?" three days before filing a chargeback looks different to an issuer than one who filed with zero prior contact. Include the email thread — full headers if possible, not a screenshot of your inbox.

Step 3: Check the order signals in Shopify Admin

In Shopify Admin, open the order and review the fraud analysis panel. Look at the risk indicators Shopify surfaces: AVS result, CVV result, IP geolocation match, billing/shipping address relationship.

For INR disputes, these signals don't prove delivery — but they contextualize the transaction. An order with AVS Y, CVV match, billing address matching shipping address, and IP consistent with the cardholder's region looks different from an order with mismatched addresses and a flagged IP. The former is a harder dispute for the cardholder to sustain.

Note the fulfillment timestamp relative to the order date. If you shipped within your stated handling window, include that. If you shipped late, don't hide it — but don't lead with it either.

The $215 apparel order that had tracking and still lost

A merchant shipped a $215 jacket via USPS Priority Mail. Tracking showed delivered. The customer had emailed once, three weeks after the order, saying "I think my package might be lost" — then filed a chargeback two days later without waiting for a response.

The merchant submitted the tracking screenshot and the order confirmation. That was the entire response.

The issuer sided with the cardholder. Why: the tracking showed "Delivered" but with no location descriptor — just a status flag. The merchant submitted no contact history. The response narrative was a single sentence: "Order was delivered per tracking."

The merchant had the email thread. They had the order-level signals showing AVS Y and matching addresses. They didn't pull them. The loss was operational, not evidentiary.

Rebuilt correctly, that response would have included: the full USPS tracking detail (which did show a ZIP-level delivery scan), the customer email showing they waited three weeks before complaining, the AVS match, and a two-paragraph narrative explaining the timeline. Winnable. Not won.

Decision point: fight the dispute or issue a replacement first

Before you submit evidence, make one call: is this a customer worth retaining, and is the dispute amount below your threshold for direct resolution?

Path A — Fight the dispute. Submit evidence through Shopify Admin → Orders → Disputes → Respond. You keep the funds if you win. You lose the customer relationship almost certainly. If you lose, you're out the merchandise and the chargeback fee. Use this path when: the order value is high, the delivery evidence is strong, the contact history is thin or suspicious, and the customer has no prior purchase history with you.

Path B — Resolve directly and withdraw. Issue a replacement or refund, contact the customer, and if the dispute is still open, submit documentation of the resolution. Some processors allow you to note a resolution and request the dispute be withdrawn — confirm this with your processor, as the mechanics vary. Use this path when: the order value is low, the delivery evidence is weak (exception scans, no location descriptor), or the customer has a legitimate complaint history. A $40 loss is cheaper than a $40 loss plus a chargeback fee plus a dispute on your ratio.

Do not try to do both simultaneously. Issuing a refund while also submitting a dispute response creates a contradictory record that issuers notice.

Step 4: Build the response narrative — write this before you attach anything

The narrative is one to two paragraphs. It goes at the top of your response. It does not summarize the attachments — it tells the issuer what happened and why the evidence supports your position.

Write it in this structure:

1. What was ordered, when it shipped, and when it was delivered (with carrier and tracking number inline)
2. What the delivery record shows specifically
3. What the customer contact history shows (or doesn't show)
4. Why the evidence supports that delivery occurred to the authorized address

Sample narrative line (adapt to your order):

"Order #4821 was placed on March 3 and shipped via UPS on March 4 (tracking 1Z8F3E4A0312345678). UPS records show delivery on March 7 at 2:41 PM to the front door at the ZIP code matching the cardholder's shipping address. The cardholder did not contact us prior to filing this dispute. We have attached the full UPS tracking detail, the order confirmation, and our complete email history with this customer."

That's it. Don't editorialize. Don't call the cardholder a fraudster. Don't speculate about porch theft. State what the evidence shows and let the attachments carry the rest.

Where weak proof actually loses INR disputes

These are the failure modes that appear repeatedly in lost INR cases:

Tracking screenshot instead of tracking record. A screenshot of the Shopify shipping summary or the carrier's status page shows "Delivered" with no scan detail. Issuers can dismiss this as insufficient. Pull the full event log.

No contact history submitted. If the customer never reached out and you don't document that absence, the issuer has no behavioral context. A note in your narrative — "the cardholder did not contact us prior to filing" — is evidence. Silence about it is a missed opportunity.

Mismatched addresses not explained. If the shipping address differs from the billing address (gift orders, reshippers, freight forwarders), explain it in the narrative. An unexplained address mismatch in an INR dispute looks like a red flag to the issuer, even if it's legitimate.

Late submission. Submitting on day 19 of a 20-day window with a disorganized evidence packet is worse than submitting on day 10 with a clean one. Issuers review hundreds of responses. A clear, organized submission with a readable narrative gets more attention than a 14-attachment dump with no context.

Signature not required on high-value orders. If the order was over $200 and no signature was required, the delivery evidence is structurally weaker. You can still win — but the narrative has to work harder. Acknowledge your shipping policy and lean on the scan specificity and contact history.

Internal note to log after every INR response

After submitting, log this internally (adapt to your ticketing system or ops doc):

"INR dispute — Order #[X] — [Date submitted] — Evidence: full carrier tracking (scan-level), customer email thread ([X] messages, [first contact date]), AVS result, order fraud signals. Narrative submitted. Deadline was [date]; submitted [date]. Outcome pending. Flag for postmortem if lost."

That log becomes your pattern data. After 10 INR disputes, you'll see whether you're losing on evidence type, submission timing, or order profile. Without it, every loss is a one-off.

Shopify Payments vs. third-party gateways

If you're on Shopify Payments, disputes surface directly in Admin → Payments → Disputes with a built-in response interface. The deadline is visible in the dashboard. Evidence uploads are capped — confirm current file size and format limits in your Shopify Admin, as these change.

If you're on a third-party gateway (Stripe, Braintree, PayPal, others), the dispute may not surface in Shopify Admin at all, or may appear with limited detail. You'll respond through the gateway's own portal. The evidence requirements are the same; the submission mechanics differ. Confirm response deadlines directly with your gateway — do not assume the Shopify Admin deadline display is accurate for third-party processors.

DisputeDesk organizes evidence across both surfaces, but the merchant still owns the decision on what to submit and when. Automation improves consistency; it doesn't replace the judgment call on whether a specific INR case is worth fighting.