How to Win an "Item Not as Described" Chargeback on Shopify

This is the hardest of the three common dispute types to win, and the reason is structural. A merchandise-not-received dispute turns on a fact a third party can verify: did the carrier deliver the package? A 10.4 unauthorized transaction turns on verification signals — AVS, CVV, device, IP. A not-as-described dispute turns on a judgment call about whether the thing in the box matched the thing on the page.

That doesn't make it unwinnable. It means the evidence that wins looks nothing like the evidence that wins the other two, and merchants who submit their usual package — tracking number, delivery confirmation, order details — lose these almost by default. Delivery proof is irrelevant here. The customer agrees the package arrived. That's the whole premise of their claim.

What Counts as "Not as Described"

A not-as-described dispute (Visa reason code 13.3) is filed when a customer says the product they received didn't match what was advertised, or arrived damaged or defective. Mastercard doesn't break this out into its own code — it lives under 4853, the broad cardholder-dispute code that also covers not-received claims, so the specific complaint arrives in the dispute narrative rather than the code itself.

In practice these claims cluster into a few recognizable shapes:

• Genuine mismatch. Wrong color, wrong size, wrong variant, wrong item entirely. A fulfillment error.
• Damaged or defective on arrival. The right product, but broken, faulty, or unusable.
• Expectation gap. The product is exactly what you sold, but the listing oversold it — a flattering photo, a vague material description, an omitted dimension.
• Buyer's remorse dressed as a defect. The customer changed their mind, missed the return window or didn't want to pay return shipping, and reframed it as a product problem to get their money back through the bank instead.

Only the last two are worth fighting hard. If you genuinely shipped the wrong item or a broken one, the dispute is legitimate and your effort is better spent on the refund and the fulfillment process that caused it. Representment is for the cases where you delivered what you promised.

Why the Usual Evidence Package Fails

The reviewer handling a 13.3 is asking one question: was the product materially different from how it was represented at the point of sale?

Tracking data doesn't answer that. Neither does AVS, CVV, IP address, or device fingerprint — all of which establish that the right person bought the item, which nobody is contesting. Submitting them signals that you either didn't read the reason code or don't have anything better, and it buries whatever relevant evidence you did include.

This is the reason-code discipline that separates a good response from a generic one. Each code has its own question. Evidence that wins one code is noise in another, and reviewers work through these quickly. A focused three-paragraph response beats a twelve-item evidence dump that never addresses the actual claim.

The Evidence That Wins

For a not-as-described case, your product listing is the primary evidence. Everything below exists to show that what you promised and what you shipped were the same thing.

• The full product description as it appeared at purchase. Not today's version — the version live on the date of the order. This is the single most important item, and the one most merchants can't produce.
• Product photographs from the listing. The images the customer actually saw before buying.
• Specifications, dimensions, materials, and sizing charts. Anything that pins the product down objectively and can be checked against what shipped.
• The specific variant ordered. Size, color, and configuration as selected at checkout, matched against the fulfillment record and SKU shipped.
• Fulfillment records showing which SKU left your warehouse. This is what rebuts a wrong-item claim directly.
• Your return and refund policy, plus proof it was disclosed. Where it appeared, and that the customer had to pass it to complete checkout.
• The full customer service thread. Every message, with timestamps.
• Evidence the item was never returned. If the customer kept the product and also took the money back, say so plainly.

The Two Arguments That Actually Persuade

Strip a winning 13.3 response down and it usually rests on one of two things.

1. The product matched the listing

Put the description and the shipped item side by side and let the comparison do the work. "The listing specified a 40 cm × 30 cm cotton-canvas tote in navy. SKU TOTE-NVY-40 shipped on August 3, matching that specification." Where the customer's complaint names a specific attribute, address that attribute directly and quote the listing text that covers it.

This is why archived listing copy matters so much. If you can only show what the page says now, and the page has been edited since the order, you've lost the ability to prove what the customer was actually shown.

2. The customer didn't use the remedy you offered

A chargeback is meant to be a last resort, not a first move. If you have a clear, disclosed return policy and the customer never attempted a return, never requested an exchange, and in many cases never contacted you at all before going to their bank, that's a substantive argument — and it's the one that most often wins the expectation-gap and buyer's-remorse cases.

It only works if you can prove the policy was available and that no reasonable attempt was made to use it. A support thread where you offered a return or replacement and the customer stopped responding is close to ideal here.

The Argument That Loses Every Time

Do not argue that the product is good.

Merchants slip into defending quality — the sourcing, the reviews, the years in business, the other happy customers. None of it is responsive. The claim is not "this product is bad in general," it's "this product was not what was described to me." Quality testimonials don't touch that, and they read as deflection.

Nor should you argue that the customer is lying, however sure you are. Assertions about motive carry no weight without evidence, and a response written with visible irritation is easy to dismiss. Lay out what was promised, what was sent, and what remedy was available. Let the reviewer draw the conclusion.

Writing the Rebuttal

Order matters as much as content:

• Name the specific complaint. "The cardholder states the item arrived in the wrong color." Showing you understood the claim earns you the reviewer's attention.
• Quote the listing as it stood on the order date. The exact text describing the attribute in question.
• Show what shipped. SKU, variant, fulfillment record, and where possible a photograph of the item as packed.
• State the return policy and where it was disclosed. Include the timestamp of acceptance at checkout if you capture it.
• Show the support history. What the customer told you, what you offered, when they stopped engaging.
• Note that the item was not returned. One sentence, no editorializing.

Three or four tight paragraphs, each answering the description question. Nothing about tracking, nothing about fraud scoring, nothing about how long you've been in business.

What to Fix Before the Next One

More than any other reason code, 13.3 losses trace back to things you could have done months earlier:

• Archive your listings. Keep a dated snapshot of description text and images whenever a product page changes. Without it you cannot prove what a customer saw, and product pages get edited constantly.
• Describe products literally. Exact dimensions, materials, weights, and color names. Aspirational copy converts slightly better and disputes considerably worse.
• Photograph accurately. Include a scale reference, and shoot in neutral lighting so the color that arrives is the color that was shown.
• Make the return policy unmissable. On the product page, in the confirmation email, and in the package. "I didn't know I could return it" is a claim you want to be able to disprove.
• Answer support messages fast, in writing. A documented offer to fix the problem is among the strongest exhibits you can bring to a 13.3, and it often prevents the dispute entirely.
• Photograph outbound orders above a value threshold. A timestamped photo of the packed item ends wrong-item and damaged-on-arrival arguments quickly.

These disputes are won at the listing and the support desk, months before the chargeback arrives. By the time you're writing the rebuttal, the evidence either exists or it doesn't.