Shopify Chargeback Evidence: What to Submit by Reason

Quick answer for Shopify merchants

Match Shopify chargeback evidence to the dispute reason: use fulfillment and delivery proof for an item-not-received claim, transaction and customer records for an unauthorized-payment claim, and product, policy, and communication records for a not-as-described claim. The bank or issuer reviews the evidence and decides the outcome, so the goal is to make the answer to the claim easy to find and verify, not to overwhelm the reviewer with every record your store holds.

Start with the dispute reason

Open the disputed order in Shopify admin and read the reason code before collecting anything. A “product not received” response needs delivery and fulfillment proof. A “fraudulent” response needs information that connects the cardholder to the order, such as billing details, IP address and country, fulfillment dates, and any prior undisputed order history. A “product unacceptable” response needs the product page, order details, customer communications, and return-policy history.

Do not send the same evidence bundle for every reason. Irrelevant attachments make the response harder to review and can hide the one record that answers the claim. Shopify’s chargeback process guidance explains where the case and response requirements appear, and the deadline shown on the individual dispute is the one to follow.

Shopify dispute evidence by reason

Shopify groups the reasons cardholders give into eight categories. Each calls for different records. Use the table below to find the reason, the records that answer it, and what to leave out.

The eight categories above follow Shopify’s own dispute-reason list. When the claim is fraudulent or unrecognized, contact the customer first if you can. A forgotten purchase or a family member’s order explains many of these disputes, and a written confirmation that the charge was valid is stronger evidence than an argument. For a duplicate or credit-not-processed claim, check your own records honestly: if you did charge twice or failed to refund, accepting the dispute is usually the right call.

How to choose relevant records and what to leave out

Filter every record against the stated claim before including it. Ask one question: does this document answer the reason code? A delivery confirmation answers “product not received.” A product photo does not. A refund record answers “credit not processed.” A customer-service chat about sizing does not.

A large folder of unrelated screenshots can hide the one delivery record or refund entry that matters. If a document does not help the reviewer verify the claim, leave it out. That includes internal notes, generic policy pages from today’s website, and screenshots of conversations that do not involve the disputed order. When a record is borderline, ask whether it would help someone who has never seen the order understand the timeline; if not, it belongs outside the packet.

Build a chronological order timeline

The reviewer should be able to follow the order without guessing. Include:

• Checkout and payment date
• Billing and shipping details that are appropriate to disclose
• Fraud or risk checks performed
• Fulfillment date and carrier
• Tracking and delivery confirmation
• Customer communications, especially dated messages
• Refund, cancellation, or return-policy actions

Use dates and order identifiers consistently throughout. As a hypothetical example, a $300 order disputed as “product not received” would be answered with the carrier tracking number and delivery confirmation showing the item arrived at the order address, not a copy of the customer’s support chat about a different order. Describe observable facts in the timeline. Avoid conclusions such as “the customer is definitely fraudulent”; instead state what the records show and when each event happened.

Preserve policy evidence

If your store relies on a cancellation, refund, shipping, or return policy, include the policy version that was available at checkout. A generic link to the current website may not prove what the customer saw when the order was placed, because policies can change over time.

Save a dated capture of the relevant policy page, or keep a versioned policy record you can attach to a dispute. This matters most for subscription-canceled, product-unacceptable, and credit-not-processed claims, where the customer’s expectation is measured against what was promised at the time of purchase.

Choose review or automatic submission deliberately

Some merchants want every response prepared for review before it goes out. Others prefer automatic submission when the evidence meets their policy. Choose the submission option deliberately and keep a record showing whether the response was reviewed, submitted manually, or submitted automatically. If you submit early, confirm the attachments are final, because the response locks. If you wait until the deadline, leave enough time to verify the packet. Either way, the visible deadline on the individual dispute in admin is the one to follow; see our guide to Shopify chargeback deadlines for a full response procedure.

Make the response easy to review

Before you submit, read the response as if you have never seen the order. Lead with the answer to the claim, then support it with dated facts. If the customer says the item was not received, begin with the fulfillment and delivery record rather than a general description of your business. If the customer says the payment was unauthorized, explain the relevant order and transaction facts without claiming that a risk signal proves who placed the order.

Check that attachments open, that screenshots are readable, and that dates and order identifiers agree across the response. Put the timeline before the attachments so the reviewer can follow the sequence, and label each attachment so its connection to the claim is clear. If a teammate reviews the case, ask them to identify the claim, the supporting record, and any unresolved gap in under a minute.

Keep contact conversations in writing when you can. A phone call is useful to a reviewer only when it is documented in writing, such as a follow-up email summarizing what was discussed and dated before the dispute existed. A call that exists only in phone records is invisible to the reviewer.

What to do when a record is missing

Do not fill a gap with an assumption. Say what the available records show and identify what you could not confirm. Then look for an appropriate source in a logical order: the carrier portal, fulfillment system, customer-service history, refund record, or the policy version shown at checkout. Keep the search focused on the order and the dispute reason.

Missing evidence is also a prevention lesson. If delivery scans are consistently difficult to find, improve the fulfillment record before the next dispute. If customer messages are split across inboxes, create a clearer support handoff. A response process is strongest when it improves the store’s everyday records instead of being rebuilt from scratch every time a case opens.

Connect prevention to response

Fraud prevention and dispute response are connected but not identical. You can review completed orders against rules you set, hold fulfillment according to your policy, and still receive a dispute later. The evidence response should show what your store actually did, when it happened, and which order records support it. For example, if you held an order for manual review and then released it after checking the billing address and contacting the customer, include that decision in the timeline. Prevention reduces the number of disputes you face; evidence preparation decides how well you answer the ones that still arrive.

An individual dispute response vs. a chargeback report

The evidence you submit to answer a dispute is not the same as a chargeback report. An individual dispute response addresses one case, its reason code, and the specific claim the cardholder raised. A chargeback report summarizes dispute activity and trends across cases, including how many disputes you received, by reason, over a period. The distinction matters because each serves a different job. The response answers the bank’s question about a single order. The report helps you spot patterns, such as a rising number of product-not-received claims from one carrier region, so you can decide whether to change fulfillment or checkout settings. If your goal is reporting and trend analysis, see our guide to the Shopify chargeback report rather than rebuilding that scope here.

A practical checklist

• Match the evidence to the dispute reason.
• Use one order identifier throughout.
• Put the timeline before the attachments.
• Include delivery or fulfillment proof when relevant.
• Preserve the policy shown at checkout.
• Remove unnecessary personal data.
• Verify the submission mode before the deadline.
• Have the evidence workflow ready before the dispute deadline.

The strongest response is the one you can produce consistently, not the one you assemble from scratch at 11 p.m. on the due date. If a record is hard to find this time, fix the underlying process so it is easy to find next time.