Dispute reason responses

Responding to a Not-as-Described Chargeback on Shopify

Woman smiles and opens a box with white tissue paper.
Photo: Avelino Calvar Martinez / Burst

A not-as-described chargeback turns on the difference between what the customer was promised at purchase and what the merchant supplied. Build the response by listing each alleged mismatch, identifying the relevant purchase-time claim, and comparing it with transaction-specific fulfillment records.

Do not begin with today’s improved product page or a general statement that the merchant sells quality goods. Neither establishes what this customer accepted or received. If the comparison reveals a material error, acknowledge it and choose the appropriate case route instead of trying to make the current description stand in for the original promise.

Identify the exact alleged discrepancy

Read the claim and the prior support exchange. Determine whether the customer challenges dimensions, material, color, compatibility, included components, service scope, or another specific representation. If the complaint is vague, use available issuer details and appropriate provider clarification to narrow it.

Shopify groups significant description differences within product-unacceptable disputes. Shopify dispute reasons.

Write each allegation as a separate factual question. “The item is not as described” may contain several issues, such as a missing accessory and an unsupported compatibility claim. Combining them into one broad denial can leave part of the customer’s case unanswered.

Check the disputed amount and item scope. If only one line is challenged, do not defend unrelated products merely because they share an order. The response should show what the merchant is asking the reviewer to assess, including any previous credit relevant to that scope.

Compare the purchase-time promise with the supplied item

Locate the product or service description version applicable to the purchase. Include the selected variant and relevant images or offer wording. If the historical version is unavailable, disclose the gap and use other legitimate records without pretending a current page is historical evidence.

Visa’s dispute conditions depend on the actual allegation. Visa public rules.

Then identify what was supplied. Use item identifiers, packing records, delivery records, service completion records, or dated photographs where they actually connect to the disputed purchase. A generic supplier catalog does not prove which variant went into the parcel.

Avoid using subjective language to resolve an objective mismatch. If the claimed difference concerns a measurement, show the relevant measurement and units. If it concerns an accessory, identify the contents promised and supplied. If it concerns a condition-dependent performance claim, state the relevant condition and whether it was disclosed.

Distinguish a description dispute from a defect diagnosis. An item can match its specification and still fail. If the actual complaint is malfunction rather than a mismatch, route the reasoning accordingly instead of using a correct SKU as proof that the product worked.

Use an allegation-by-allegation comparison

This reusable matrix gives the reviewer a readable map of the contested facts.

Customer allegation Purchase-time promise Supplied-item record Merchant conclusion
Wrong dimension Relevant dated specification Order-linked measurement or item specification Match, mismatch, or uncertain
Missing component Included-contents statement Packing or return record Component supplied, omitted, or unverified
Unsupported compatibility Relevant compatibility wording Exact supplied model and verified support Claim supported, overstated, or uncertain
Wrong variant Selected order option Fulfilled SKU and identifiable item Variant match or error

In a hypothetical case, a customer says a shelf was narrower than advertised and lacked mounting hardware. The archived listing shows the advertised width, while the fulfillment record identifies the correct shelf model. However, the packing record does not confirm the hardware, and a prior support message acknowledges it was omitted.

The merchant can address the width allegation with relevant records but should not deny the missing hardware. The response needs to explain the acknowledged omission and any completed remedy, with accurate dates and scope. Defending one point does not erase another supported complaint.

Present the comparison and resolution history fairly

Lead with the issue and the merchant’s supported position. Attach only the relevant description excerpt, item record, and communications necessary to explain the comparison. Preserve enough context that a limitation or exclusion is not separated from a headline promising the opposite.

Include the actual resolution history where relevant. A replacement offer is not a completed replacement. A customer declining an unsuitable alternative is not necessarily refusing a valid remedy. Describe what was offered, accepted, shipped, returned, or credited without expanding the meaning of those events.

Check any procedural condition with the actual provider and network reason. Do not make a blanket argument that lack of prior contact automatically defeats the dispute. The case’s requirements need to be verified for its specific route.

If a response is available and supported, submit it through Shopify or the provider by the live merchant deadline and confirm status. If the merchant’s records establish the mismatch and no permitted defense applies, use the appropriate resolution path. A useful response makes the promise-to-product comparison transparent rather than asking the reviewer to trust the merchant’s general reputation.

Keep the dispute reason, amount and response deadline visible in Lower Chargeback while you prepare your response in Shopify or with your provider.

Monitor Your Disputes

Related reading in this collection: