Limited time BFCM offer for prevent 2.0
Limited time BFCM offer for prevent 2.0
Limited time BFCM offer for prevent 2.0
Limited time BFCM offer for prevent 2.0
Feb 8, 2026
Item Not As Described
Quality Dispute
Product Misrepresentation
Order Documentation

Why Do I Get So Many Item Not As Described Disputes?

In this article

Chargebacks?
No longer your problem.

Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.

600+ reviews
No credit card needed.

TL;DR:

  • Most item not as described disputes trace back to vague specs, wrong-variant photos, packing errors or supplier quality drift.
  • Rank products by disputes per 1,000 orders, not raw counts, so you fix the worst rate first.
  • Visa 13.3, 13.4, 13.5 and Mastercard 4853 each need proof of what you promised versus what shipped.
  • PayPal’s SNAD rule excludes items that matched an accurate listing, so disclose defects and wear up front.

You get many item not as described disputes when what customers receive doesn’t match what your listing promised. The usual causes are vague specs, photos of the wrong variant, packing errors, quality drift from a supplier, and slow returns. Fix the listing or product first, then fight only the claims your records can beat.

Written by Chargeflow Experts. Updated 12 November 2026.

Compare the Promise With the Delivered Item

AreaAudit QuestionEvidence to Preserve
DescriptionAre size, materials, fit and limits clear?The listing version the buyer saw.
ImagesDo photos show the real variant and what is in the box?Product photos and the option chosen.
FulfillmentDid the right item and quantity ship?SKU, packing, shipping and quality records.
ServiceDid you deliver what you agreed to?Scope, milestones and sign-off records.
RemedyDid you promise a return, repair or refund, and did it happen?The support and remedy timeline.

Stripe’s category guidance keeps quality complaints apart from non-receipt claims. Read the case details. A delivery scan proves the parcel arrived, not that the item matched its description.

Which Reason Codes Mean Not as Described?

Not-as-described claims come under a few chargeback reason codes. The code tells you what the bank thinks went wrong, so match your proof to it. This map follows Stripe’s reason code guide.

CodeWhat the customer saysProof that fits
Visa 13.3 Not as Described or DefectiveThe item was materially different, damaged or defective.The listing as it looked at purchase, fulfillment records and your support replies.
Visa 13.4 Counterfeit MerchandiseThe item is not genuine.Supplier invoices, authenticity certificates or distributor agreements.
Visa 13.5 MisrepresentationThe offer did not match the features or quality promised.Archived marketing pages, terms the buyer accepted and usage logs for digital goods.
Mastercard 4853 Defective or Not as DescribedThe goods or services were defective, damaged or not as described.Product description, delivery records and proof you offered a fix or return.

For Visa 13.4 and 13.5, Stripe notes the customer is expected to raise the problem with you before filing. If your records show no contact at all, say so in your response. See how to tailor evidence to each reason code.

What Does Significantly Not as Described Mean?

“Significantly not as described” (SNAD) is PayPal’s term for this claim type. PayPal’s Buyer Protection terms use clear examples, and card issuers apply similar logic.

Counts as SNADDoes not count
The item is materially different from the description.A defect the listing clearly described.
A completely different item arrived.The item matched the listing, but the buyer changed their mind.
The condition was misrepresented, it was damaged in shipping, or a fake was sold as authentic.The item matched the listing, but missed the buyer’s hopes.
Major parts were missing and not disclosed, or part of a multi-item order never came.Minor scratches on an item listed as “used.”

The lesson for your listings is simple. Disclose defects, wear and missing parts up front, and the claim usually fails. See how sellers win PayPal SNAD claims.

Prioritize the Repeated Complaint

More disputes does not always mean a worse rate

Pick the product fix from measured complaints

Comparable product cohorts

Group complaints by SKU, variant, supplier batch and issue. Divide by sales so your best seller isn’t flagged just for selling more. Add support tickets and return notes to the dispute count.

Verified purchase specifications

For example, swap “fits most laptops” for the real inside size and the models it fits. Measure before you publish. Never add a number just to sound exact.

Here is a sample case. SKU A had 12 not-as-described disputes on 4,000 orders: 3 per 1,000. SKU B had 6 disputes on 500 orders: 12 per 1,000. SKU B has half the disputes but four times the rate, so you fix it first. Use the same math as your chargeback rate calculation.

Make Purchase Information and Remedies Clear

Show key limits near the buy button and test how they look on mobile. Save each listing version so you can prove what the buyer saw. Give customers an easy way to report a wrong or broken item. A clear return policy helps, but a buyer accepting your terms does not prove you met them.

For course disputes, compare the original offer with what you delivered using the course not-as-described checklist. For software, the SaaS not-as-described guide ties features to the plan sold. For live packages, the coaching program guide tracks sessions, feedback and other promised work.

Use support and payments handoffs and refund-status controls to avoid conflicting promises. Reviews are an early warning too: turn negative reviews into dispute prevention.

Fight, Refund or Fix? A Decision Rule

  • Fight when your saved listing matches what shipped, and the customer never contacted you or refused a return.
  • Refund when the item really was wrong, damaged or fake. Losing costs you the sale plus a dispute fee, such as Stripe’s $15 in the US.
  • Fix the listing when the same complaint repeats on one SKU. Each new sale with the same gap is another likely dispute.
  • Watch for abuse when one customer claims “not as described” across many orders. That pattern can be friendly fraud.

Build a Response Around the Claimed Difference

Find what the customer says was wrong. Then link each record to that exact issue. Explain any defect honestly. If the complaint is true, offer a fair remedy instead of defending a wrong listing.

See Item Not as Described chargebacks, evidence-review guidance and consistent performance reporting. You can explore Chargeflow’s chargeback recovery workflow for case preparation.

Compare the Purchase Promise With the Supplied Product

Illustrative productPurchase-time promiseSupplied record and next check
Physical jacketBlue, size M, waterproof. Listing version saved with the order.Warehouse record shows black, size M. Check the variant mix-up and offer a remedy.
Digital softwareVersion 3 for macOS, including export feature.The license unlocks version 2 with no export. Check the build delivered against the offer.

Keep three cases apart: a defective item, the wrong variant, and a description gap. Tracking proves shipment, but it can’t settle a spec dispute. Compare complaints for one listing version with its own sales, and don’t call a bigger count a higher rate. The chargeback evidence source map helps you find old listings and packing evidence.

Frequently Asked Questions

What Does Significantly Not as Described Mean in Payment Disputes?

Significantly not as described means the item a buyer received is materially different from its listing, such as a different item, an undisclosed defect, missing parts or a counterfeit. It does not cover an item that matched an accurate description but did not meet the buyer’s hopes.

Which Reason Codes Cover Item Not as Described Disputes?

Item not as described disputes usually arrive as Visa 13.3, Visa 13.4 for counterfeit goods, Visa 13.5 for misrepresentation, or Mastercard 4853. Each code needs proof of what you promised and what you delivered.

Does Delivery Proof Defeat a Not-as-Described Claim?

Delivery proof does not by itself defeat a not-as-described claim. You also need to answer the claimed difference, defect or service failure.

Does Policy Acceptance Prove the Item Matched?

Policy acceptance does not prove the item matched the listing. Compare the actual purchase promise with the product or service you delivered.

Which Product Should I Audit First?

Audit the product with the highest not-as-described rate first, measured as disputes per 1,000 orders, not the raw count. Then check its variants and supplier batches.

SHARE THIS ARTICLE

Chargebacks?
No longer your problem.

Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.

600+ reviews
No credit card needed.
subscribe

The latest chargebacks, fraud, and ecommerce content, in your inbox. Every week.

By providing your email you're agreeing to our Terms of Service and Privacy Notice
Diagram with dashed and curved lines forming segmented arcs highlighted by three blue diamond markers on the left side.Abstract circular grid design with blue diamond markers on a half-black, half-white background.

More articles.

June 4, 2026

How Do I Track Dispute Performance Across Multiple Accounts?

Track dispute performance across multiple accounts with clear rate definitions, a reconciled case register, weighted win rates, net recovery after fees, and a fixed report schedule.

Dispute Workflows
Processor Behavior
Dispute Decisioning
Representment Strategy
Chargeback Ratio
June 4, 2026

How Do I Standardize Evidence Across Dispute Types?

Standardize chargeback evidence with one core record set, a module for each dispute category, a fixed file format, and a check that each response was sent.

Proof of Delivery
Transaction Logs
Bank Requirements
Representment Strategy
June 4, 2026

How Do I Align Customer Support and Payments to Reduce Disputes?

Align customer support and payments with a shared case record, complaint-to-dispute playbook, refund and dispute overlap rules, and subscription habits that cut disputes.

Dispute Workflows
Poor Communication
Customer Confusion
Refund Timing Issues
Friendly Fraud
Frequently Asked Questions

Questions?
we’ve got answers.

What makes Chargeflow different from Stripe Disputes?

Chargeflow collects data from dozens of third party signals, not just transaction data like Stripe Dispute does. This allows for much more coverage and much better win rates because the evidence submitted is much more comprehensive and compelling..

How does Chargeflow fight chargebacks?

Chargeflow collects data like order info, customer messages, and payment details. It builds a full dispute case for you, so you don’t have to lift a finger.

Can Chargeflow handle chargebacks from multiple payment processors?

Yes! Chargeflow works with many processors — not just Stripe. That means one tool for all your chargebacks, no matter how you process payments.

How does Chargeflow Automation’s pricing work?

Chargeflow Automation uses success-based pricing on recovered chargebacks. Other Chargeflow products have separate pricing. Check the pricing page and your agreement for the applicable terms.

Is Chargeflow safe to use?

Chargeflow’s security documentation describes SOC 2 Type 2 compliance, GDPR compliance, encryption at rest and in transit, and access controls. Review the security page for details on its safeguards and data handling.

need more help?

Have a question? We’re here to help. Just hit the chat button to initiate a conversation with support.