At a glance
Returns on ‘Good / Like New’ Items counts buyers who returned an item you graded New, Like New, or Good and cited a condition mismatch. A rising count is the clearest early warning that your intake grading has drifted optimistic.
| What it counts | Returns where the listing’s Mercari condition grade was Good or better and the buyer’s return reason was condition or item-not-as-described. |
| Sample type | Backend API data from Mercari, refreshed on the standard data refresh. |
| Why it matters | Condition mismatch returns cost return shipping, refunds, and seller rating points. Repeated mismatches on high grades signal your grading bar is too generous and needs tightening at the next intake. |
| Reading the value | A raw count over the window. Lower is better. Read the trend, not a single day; a steady climb matters more than one bad week. |
| Currency | number |
| Time window | 30D |
| Alert trigger | >5 returns on Good/LikeNew |
| Sentiment key | mer_grading_drift_signal |
| Roles | owner, operations |
Calculation
Vortex IQ matches each return in the window to the originating listing and reads the condition grade that was assigned at listing time. Returns are kept only when that grade was Good, Like New, or New and the buyer’s stated return reason relates to condition or the item not matching its description. The result is a simple count over the trailing 30 days. Returns on items graded Fair or Poor, and returns for unrelated reasons such as wrong size, are excluded so the signal stays specific to grading accuracy.Worked example
A representative reading of Returns on ‘Good / Like New’ Items for a typical Mercari reseller. Say a clothing reseller normally sees one or two of these returns a month. This month the card reads 7, which trips the>5 returns on Good/LikeNew alert. Drilling in, six of the seven were items graded Like New that buyers reported with visible wear or pilling. That pattern points to one intake batch graded too generously rather than random bad luck. The action is to re-grade your current Like New inventory one notch stricter and add a wear-check step to intake. Cross-reference mer_dispute_rate to confirm whether these returns are escalating into disputes, and mer_avg_review_rating to see if your seller rating is taking damage. Vortex Mind traces the upstream cause, for example linking the spike to a single sourcing lot, and Ask Viq answers plain-English questions like “which items drove this month’s condition returns?”
Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
mer_dispute_rate | Confirms whether condition returns are escalating into formal disputes. |
mer_return_rate | Sets these grading returns in the context of your overall return volume. |
mer_avg_review_rating | Shows whether mismatched grading is dragging your seller rating down. |
mer_listing_quality_score | Flags whether photos and descriptions are reinforcing optimistic grades. |
mer_marketplace_health_score | Rolls return and dispute behaviour into overall account standing. |
Reconciling against Mercari
Where to look in Mercari’s own dashboard: In the Mercari seller app, open your sales history and filter to returned or refunded orders, then read each order’s return reason. The listing’s condition grade is visible on the original listing. There is no single native report that joins grade to return reason, which is the gap this card closes. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Period boundary. Mercari attributes a return to the date it was opened, which may straddle the 30-day window edge. | Variable | Match the period range. |
| Time zone. Return timestamps may be recorded in a different time zone than your reporting view. | Marginal | Confirm time zone match. |
| Filter scope. This card counts only condition-reason returns on Good-or-better grades, not all returns. | Variable | Match filter settings. |