The Return Reason Code Breakdown: What Buyers Actually Mean When They Claim 'Not As Described'

When a buyer selects "Item not as described" on an eBay return, it usually means one of three things: the item genuinely doesn't match your listing, the buyer changed their mind and picked the reason that skips return shipping costs, or something happened in transit that got blamed on condition. In our reconciliation work with resellers moving 200+ items a month, roughly half of NAD claims on clothing turn out to be buyer's remorse wearing a condition costume — because the reason code, not the truth, determines who pays for the return label.

That single fact changes how you should read every return request that lands in your inbox. eBay gives buyers a dropdown, not a lie detector. Your job is to read past the code to the intent underneath, because the code determines your dispute rights, your seller performance metrics, and whether you're about to eat a $22 loss on a shirt that was exactly as photographed.

The Return Reason Codes and What They Actually Cover

eBay's return flow gives buyers a short list of reasons. For clothing, five show up constantly:

• Doesn't fit — a remorse reason. Buyer pays return shipping unless you offer free returns.
• Changed my mind / No longer needed / Bought by mistake — remorse reasons. Same shipping rule.
• Item doesn't match description or photos — this is Not As Described (NAD). Seller pays return shipping and the case counts against your INAD rate.
• Item defective or doesn't work — rare for clothing but shows up on items with functional elements: zippers, buttons, elastic waistbands, drawstrings.
• Item damaged during shipping — a shipping claim, not a condition claim, though it often gets miscoded as NAD by buyers who don't know the difference.

Here's the part that matters for your P&L: eBay tracks your Item Not As Described return rate as part of seller performance standards, and a pattern of NAD claims — even disputed ones — can push you toward below-standard status. That's why the code a buyer picks matters more than what actually happened. A buyer who simply doesn't like the fit but selects "doesn't match description" costs you the same seller-metric hit as a genuine condition miss, unless you catch it and push back.

Not As Described vs. Buyer's Remorse: How to Tell the Difference

The dropdown reason and the real reason are frequently different animals. Use this comparison when a return request comes in:

None of these signals are proof on their own. Together, three or more pointing the same direction is enough to build a response — or decide it's not worth fighting a $15 item and move on.

How to Decode Buyer Intent From a Return Reason

Run every NAD claim through this sequence before you respond. It takes under five minutes once it's a habit.

1. Pull your original listing photos and condition notes side by side with the buyer's return photos.
2. Compare the specific defect claimed against your graded condition tier — if the item was graded Excellent, Very Good, Good, Fair, or Poor at intake, check which of the five factors (Fabric Condition, Structural Integrity, Cosmetic Appearance, Functional Elements, Odor & Cleanliness) the claim actually falls under.
3. Check the timestamp on the claim against your delivery confirmation. A claim filed 24 hours after delivery reads differently than one filed on day 28.
4. Read the buyer's message for specificity. "There's a stain on the collar" is a claim you can verify. "Not as described" with no detail is a flag, not evidence.
5. Check the buyer's return history if you can see it, or note whether they've messaged you before purchase with sizing questions — a sign the return may be fit-driven, not condition-driven.
6. Decide your response: accept, offer a partial refund, or escalate to eBay for review with your documentation attached.
7. Log the outcome and reason code in your returns tracker regardless of resolution — this is the data you'll use for pattern analysis later.

Which Return Reasons You Can Actually Dispute as a Seller

Not every NAD claim is worth fighting, but some are winnable if you have the paperwork. Here's where you stand a real chance:

• You have timestamped intake photos showing the item's actual condition before it shipped, matching your listing description and grade. This is your strongest card — eBay's Money Back Guarantee process weighs seller evidence heavily when it's dated and specific.
• The claimed defect isn't visible in either your photos or the buyer's return photos. A vague claim with no supporting image is disputable.
• The item was disclosed with the exact flaw the buyer is citing. If your listing said "small mark near hem, see photo 6" and that's the return reason, you have grounds to push back or offer a partial refund instead of a full return.
• The reason code doesn't match the buyer's actual message. If they selected NAD but wrote "it just didn't fit right," you can request eBay reclassify the case, which shifts return shipping cost back to the buyer.

Where you generally can't win: functional defects you didn't test before shipping, damage that plausibly happened in transit with no packaging documentation on your end, and any case where your own listing photos are worse than the buyer's return photos at showing the flaw. If your evidence is weaker than theirs, take the partial refund and move on — a case escalation you lose still counts against your metrics.

Pattern Analysis: What Your Return Reasons Are Telling You Over Time

A single return is a data point. Twenty returns over a quarter are a diagnostic. Once you're logging reason codes consistently, look for these patterns:

• Repeated "doesn't match photos" on one category — usually a photography or grading gap, not bad luck. If denim keeps coming back for fading not shown in photos, your intake photo angles need work.
• Clusters of "doesn't fit" on one brand — a sizing note problem. Add brand-specific fit callouts to your item specifics and description.
• NAD claims concentrated in one grading tier — if items graded Good are generating more disputes than items graded Very Good or Excellent, your Good-tier threshold may be too generous. Recheck how you're applying the five condition factors at that tier.
• Odor-related claims — these fall under Odor & Cleanliness and are almost always preventable with a consistent pre-ship check, since smell doesn't show up in photos at all.

This is the return-reason equivalent of running a fee audit: the value isn't in any one case, it's in what a quarter of cases tells you about a systemic gap in your listing or grading process.

Where Condition Grading Fits Into This

Every NAD dispute ultimately comes down to one question: did the item match what you said it was? A standardized grade with a documented condition report — the kind that scores Fabric Condition, Structural Integrity, Cosmetic Appearance, Functional Elements, and Odor & Cleanliness individually rather than one seller adjective — gives you a paper trail that's specific enough to win disputes and, more usefully, specific enough that fewer buyers file them in the first place. Vague listing language ("good condition, some wear") invites vague disputes. A precise grade invites precise agreement.

You don't need to overhaul your whole workflow to test this. Grade your next ten listings with a documented, factor-by-factor condition report instead of a one-line adjective, and watch what happens to your return reason codes over the next 60 days. If you're already logging returns in FlipDesk's reconciliation module, tag each case with its reason code and revisit this pattern analysis in a month — the gaps usually show up fast.