Item Not as Described Chargebacks on Shopify: What to Check Before You Submit
Color disputes, vague specs, ambiguous images — 'item not as described' chargebacks are won or lost before the customer ever files. Here's what to check in Shopify Admin.
DisputeDesk Editorial
Why these disputes are decided before the chargeback is filed
An "item not as described" chargeback lands when a cardholder claims the product they received differs from what your Shopify store advertised. The issuer's job is simple: compare what you said the product was against what the customer says they got. If your product listing is vague, your images are ambiguous, or your pre-shipment communication is thin, you can lose before the issuer evaluates a single piece of evidence.
Start in Shopify Admin > Products. Pull the live listing for the disputed item and read the description as if you've never seen the product. Is the material, size, color, and spec stated explicitly — or does it leave room for interpretation? Issuers side with cardholders when descriptions are ambiguous. Then check the images: are they high-resolution, multi-angle, and accurate to the unit you actually shipped? Low-quality or stylized images that don't reflect the physical product are a liability in any dispute response. Next, go to Admin > Orders > Order Details and pull the customer communication thread. Document every interaction about product details before and after the sale. Issuers favor merchants who can show transparent, timestamped communication — not just a tracking number.
Also confirm the fulfillment details in Admin > Orders > Fulfillment. Verify that the item shipped matches the order specifications exactly. A mismatch between the SKU ordered and the SKU shipped turns a subjective dispute into an objective one — and not in your favor. Finally, check Admin > Orders > Refunds. If you offered a return or exchange and the customer filed anyway, that offer needs to be documented and timestamped in your response. Delayed or partial refund offers give issuers a reason to side with the cardholder regardless of description accuracy.
What evidence actually moves the needle — and what doesn't
Three evidence tensions come up repeatedly in "item not as described" disputes, and they don't all carry equal weight.
The strongest position is a detailed product description that maps directly to the item specifications at the time of purchase — not a revised version, the live listing at checkout. If the description is specific (dimensions, material, exact color name, model number), highlight those elements explicitly in your response and show they match the unit shipped. Ambiguous language like "vibrant blue" or "approximately 12 inches" gives issuers room to rule against you even when you believe the product is accurate.
Images are useful but conditional. If your product photos clearly show all angles and features, they support your case. But color disputes are a known trap: customers frequently perceive color differently based on screen calibration, and issuers know this. A product page that includes a disclaimer about color variation due to screen settings is a stronger position than one that doesn't — both for prevention and for dispute response. Submitting photos alone without that context rarely closes a color dispute.
The third tension is the most counterintuitive: a customer who acknowledges receipt of the correct item but still claims it's not as described. Delivery confirmation and a customer email confirming receipt support your position, but issuers may still question whether your description was clear enough to set accurate expectations. In that scenario, your response needs to lead with the specific description elements, not just the delivery proof. Delivery proof establishes the item arrived — it doesn't establish the item matched the listing.
The color dispute that looked winnable and wasn't
A fashion merchant sells a dress listed as "royal blue" at $75. The customer orders on March 1st. The merchant ships with tracking on March 2nd. The dress arrives March 5th, and the customer contacts support the same day — the color looks different than expected. The merchant responds on March 6th with an offer to exchange or refund. The customer files a chargeback on March 10th.
On paper, the merchant has a reasonable evidence package: a product description naming the color, high-resolution images of the dress, a customer email confirming receipt, and documented support logs showing the exchange offer. That looks like a fightable case. It isn't — not reliably.
The vulnerability is the word "royal blue." Color perception is subjective, and the customer's screen may have rendered the dress differently than the merchant's product photography. The issuer reviewing this dispute doesn't have the physical dress. They have a description, some images, and a cardholder saying the color didn't match. If the product page has no disclaimer about color variation due to screen settings, the merchant has no anchor for that argument. The exchange offer, while good customer service, doesn't resolve the description ambiguity — it may actually signal the merchant acknowledged a problem.
A better response would have included additional images of the dress under different lighting conditions, a screenshot of the product page at the time of purchase showing the color name and any variation disclaimer, and a direct statement in the response tying the specific color name to the item shipped. Without that, the evidence package is complete but not persuasive on the actual dispute point.
The decision lesson: delivery proof and a documented exchange offer are table stakes, not winning arguments. In a color or appearance dispute, the case turns on whether your product listing set a specific, defensible expectation — not on whether the item arrived. If the listing is ambiguous, the dispute is weak regardless of what else you submit.
Before you submit: what to verify
Check the dispute status and response deadline in Shopify Admin > Payments > Disputes. Missing the deadline is an automatic loss — confirm the exact cutoff with your processor, since Shopify's displayed deadline and your acquirer's internal deadline can differ. Pull the Shopify Protect status on the order: if the order shows PROTECTED, Shopify may cover the dispute cost, but verify the coverage scope before deciding whether to fight or accept.
Confirm the dispute reason code. "Item not as described" requires evidence that the product matched the listing — not just that it was delivered. Match your evidence package to that specific requirement. Delivery confirmation alone doesn't close this dispute type. Pull the product listing as it appeared at checkout (use Shopify's order confirmation email or a cached version if the listing has since been updated), and compare it line by line against the item shipped. If there's a gap, your response needs to address it directly or the issuer will.
Decide whether to fight. If the product description is genuinely ambiguous, the images are stylized rather than accurate, and you have no color-variation disclaimer, the case is weak even if you believe the product was correct. Accepting the dispute and updating the listing costs less than a lost chargeback plus a dispute fee. Visa and Mastercard may weigh description specificity differently depending on processor routing — confirm with your processor what documentation standard applies to your account. DisputeDesk's pack assembly handles evidence compilation and flags description gaps flagged during review; merchants still own the decision on whether the listing is defensible.
Key Takeaways
FAQ
Disclaimer
This content is for informational purposes only and does not constitute legal advice.
Automate Your Chargeback Responses
DisputeDesk automatically tracks deadlines, collects evidence, and generates winning responses so you never miss a deadline again.



