New Shopify Store Chargeback Checklist: What to Lock Down Before You Get Hit

You can lose a dispute before the issuer ever evaluates your evidence

Most chargebacks on new Shopify stores aren't lost on evidence — they're lost on setup. Policies that weren't visible at checkout. Fraud signals that were there but never reviewed. Shipping confirmations that proved dispatch but not delivery. The issuer doesn't see the effort behind your store; they see the paper trail you left. If that trail has gaps, the cardholder wins by default.

Before a dispute lands, five areas inside Shopify Admin determine whether you'll have anything worth submitting. Go to Settings > Policies and confirm your refund, return, and shipping policies are published and surfaced on product pages and at checkout — not buried in a footer link. Issuers will ask whether the cardholder was informed of your terms before purchase. A policy that exists but isn't visible at the point of sale is operationally the same as no policy. Next, check Orders > Fraud Analysis. Shopify's built-in fraud scoring is active by default for Shopify Payments, but fraud analysis capabilities differ between Shopify Payments and third-party gateways — if you're running a third-party processor, confirm what signals you're actually capturing. Then review Settings > Checkout > Customer Contact: missing or unvalidated address fields create delivery disputes that are nearly impossible to win. Finally, confirm that shipping confirmation emails are automated under Orders > Order Details > Shipping Confirmation, and that your payment provider settings under Settings > Payments are correctly configured for your transaction type. A misconfigured payment provider is one of the cleaner ways to generate an unauthorized-transaction dispute on an otherwise legitimate order.

What the evidence actually proves — and where it stops

Three pieces of evidence show up in almost every new-store dispute response. None of them is as strong as merchants assume.

Policy visibility is the most commonly over-relied on. Showing that your refund and return policies were published and linked at checkout demonstrates that you communicated your terms — and that's worth including in a response. But issuers can and do argue that visibility doesn't confirm comprehension, particularly when a cardholder claims they never saw or understood the terms. The stronger framing isn't "our policy was posted" — it's showing exactly where the policy appeared in the customer's purchase flow, with screenshots of the checkout page and a copy of the confirmation email that included the policy link.

Fraud analysis flags carry a similar limitation. A partial AVS mismatch or a Shopify fraud warning is a risk indicator, not proof of fraudulent intent. Issuers typically require a pattern — multiple verification failures, behavioral signals, prior dispute history — before they'll treat a fraud flag as dispositive. AVS response codes also vary by payment processor, so confirm with your processor what a "partial match" actually means in your setup before citing it as evidence. Include fraud analysis results as part of a broader evidence set, not as a standalone argument.

Shipping confirmations are the most misunderstood. A confirmation email proves you shipped. A carrier tracking number showing a delivered status proves the carrier marked it delivered. Neither proves the cardholder received the package at their address. For "item not received" disputes, issuers want delivery confirmation to the cardholder's address — ideally a signature or a carrier photo confirmation. If you don't have that, your tracking number is supporting context, not a winning argument on its own.

A $150 fashion order, a partial AVS match, and a loss that was preventable

A new Shopify fashion retailer, average order value around $75, takes a $150 order on January 10th. The card returns a partial AVS match — billing zip matches, but the billing street doesn't. The merchant reviews the order, sees the fraud flag, decides to ship anyway, and sends a shipping confirmation email on January 12th. The carrier marks the order delivered on January 15th.

On January 20th, the customer files a chargeback: "Item not received." The merchant pulls the shipping confirmation email, the carrier tracking number showing delivery on the 15th, and the original order confirmation. They submit the response before the deadline. The issuer rules for the cardholder.

Here's why the case was weak before the response was written. The partial AVS match was a documented signal that the billing address on the card didn't fully match — and the merchant shipped anyway without additional verification. The carrier tracking showed "delivered" but there was no signature, no photo confirmation, no delivery to a specific person. The customer communication log showed a shipping confirmation email but no follow-up contact, no delivery inquiry, no attempt to resolve before the dispute was filed. The issuer had a cardholder saying they didn't receive a package, a merchant with a tracking number that proved carrier delivery (not cardholder receipt), and a fraud flag that the merchant had already seen and ignored.

A better response would have required two things that weren't present: a carrier delivery confirmation with address-level detail, and documentation of any customer contact between January 15th and January 20th. If the merchant had required signature confirmation on a $150 order — above their own AOV — the case would have been fightable. If they had emailed the customer after the delivery scan and gotten no response, that communication log would have shifted the narrative. Neither happened.

Decision lesson: A tracking number showing "delivered" is not delivery proof for dispute purposes — it's carrier proof. On orders above your AOV, or on any order with a fraud flag, require signature or photo confirmation at dispatch. That's the evidence gap that made this case unwinnable, not the response itself.

Before you submit a response, work through this

When a dispute appears in Shopify Admin under Finances > Disputes, the response deadline is shown on the dispute detail page. That deadline is set by your payment processor and the card network — chargeback response requirements vary by network and issuer, so confirm the exact window with your processor rather than assuming a standard number of days. Missing the deadline forfeits the dispute regardless of your evidence.

Check whether Shopify Protect is active on the order. If the order shows PROTECTED status under Shopify Payments, Shopify covers the dispute cost and you don't need to submit a response. If it shows ACTIVE or NONE, you're responsible. Don't submit a response on a PROTECTED order — it's unnecessary and can create confusion.

Confirm the dispute reason code. "Item not received" requires delivery proof to the cardholder's address. "Item not as described" requires product documentation and communication logs showing the item matched its listing. "Unauthorized transaction" requires fraud signals, AVS/CVV results, and device/IP data where available. Submitting shipping confirmation for an unauthorized dispute, or fraud flags for a non-receipt dispute, doesn't move the issuer.

Match your evidence to the reason code, verify that your delivery proof actually proves cardholder receipt (not just carrier delivery), and pull any customer communication from the order timeline in Shopify Admin. Then decide whether the case is worth fighting: if your delivery proof is carrier-only with no signature on a disputed amount under $50, the math on response time versus recovery probability may not favor submission. DisputeDesk's response assembly handles evidence packaging and deadline tracking; the judgment call on whether to fight is still yours, and it should be made before you start building the response.