Not as described (SNAD) claim

What a SNAD claim means in fraud and returns governance

A Not as described claim is a buyer dispute that says the delivered item materially differed from what was advertised, promised, or expected. In payments, marketplace, and returns operations, it sits at the boundary between legitimate consumer protection and abuse of refund or chargeback processes.

The practical issue is that the same claim type can reflect three different realities: a true product mismatch, a mistaken buyer expectation, or a deliberate attempt to retain the item while reversing the payment. That makes SNAD handling less about the label itself and more about evidence, policy consistency, and dispute resolution quality.

How SNAD claims are evaluated

SNAD review usually compares the listing, order data, delivery condition, seller disclosures, photos, messages, and any applicable return policy. The core question is whether the item received was materially different from the item represented at purchase, not whether the buyer is simply unhappy after receipt.

Because the standard is about description and condition, small cosmetic variation, subjective disappointment, or post-delivery misuse does not automatically establish a valid claim. Conversely, missing parts, counterfeit goods, incorrect model numbers, and materially damaged items are classic fact patterns that can support SNAD when documented well.

Platforms and payment providers often treat SNAD as a governed dispute path rather than a simple customer-service complaint, so the decision usually depends on what can be shown at the time of sale and delivery, not on later assertions alone.

Why SNAD matters to sellers, marketplaces, and fraud teams

SNAD matters because it can shift loss from the buyer to the seller or platform even when the underlying problem is not fraud. It also creates a control problem: weak documentation, vague listings, and inconsistent evidence handling can make legitimate claims harder to separate from opportunistic ones.

For fraud governance, SNAD is useful because it highlights first-party abuse patterns as well as genuine service failures. A high volume of claims can indicate listing quality problems, fulfilment defects, misleading merchandising, or deliberate exploitation of buyer protections.

What good SNAD handling looks like

Good handling starts with clear item descriptions, accurate condition statements, and preserved evidence at listing, packing, shipment, and delivery. When those records are strong, SNAD decisions are easier to defend and less likely to become ad hoc reversals driven by incomplete facts.

Teams should also separate product-quality issues from dispute-qualification issues. A customer can be dissatisfied for many reasons, but SNAD only applies when the mismatch is material enough to change the transaction expectation in a meaningful way.

Where SNAD is common, the strongest operational response is to reduce ambiguity upstream, then standardise evidence review downstream so that valid claims are handled quickly while unsupported claims are rejected consistently.

Risk and Threat Considerations

snad claim create both financial and control risk because they can be used to reverse transactions after goods have been received, especially when sellers lack strong proof of description, packaging, or delivery condition. They also expose marketplaces to policy gaming when the dispute process rewards incomplete evidence or inconsistent adjudication.

Failure mechanism: Weak listing accuracy, missing item-state evidence, and poor claim triage let genuine defects and first-party abuse look the same, which can drive avoidable refunds, chargebacks, and seller distrust.

Impact: The result can be direct loss, higher dispute rates, degraded marketplace trust, and a feedback loop where honest sellers absorb more friction than abusive claimants.

Practitioner Guidance

What to watch for: Repeated SNAD filings against the same buyer, category, or seller often signal either a product-quality problem or a dispute-abuse pattern, and the review process should distinguish between those two. The most useful operational question is whether the evidence at listing and delivery is strong enough to make the claim objectively testable.

Governance implication: Treat SNAD as a policy and evidence standard, not just a customer-service label. Clear thresholds for material mismatch, consistent documentation requirements, and repeat-pattern review help keep the process fair without making it easy to game.

Related resources from NHI Mgmt Group

• What should merchants do when they receive a false SNAD or INR claim?
• SNAD Claim
• What do security teams get wrong about the aud claim in JWTs?
• Who is accountable when privileged access failures affect a cyber insurance claim?