Plan of Action for a Used-Sold-as-New Complaint on Amazon

What triggers this specific complaint

Used-sold-as-new complaints have a narrower, more diagnosable set of causes than they first appear to. For FBA sellers, the most common cause is a customer return that gets restocked into sellable inventory without adequate inspection — Amazon's own reprocessing isn't infallible, and a returned item with subtle wear can end up back in the sellable pool. For sellers using commingled inventory (stickerless, commingled FBA), a genuinely used unit from a different seller's stock can occasionally ship against your listing, which is a distinct failure mode from your own fulfillment. For self-fulfilled or FBM sellers, the cause is more often internal — inventory that sat open, was returned to your own warehouse and reshipped, or packaging that degrades in storage or transit and reads as "used" to a customer even though the product itself wasn't previously owned.

Knowing which of these three mechanisms is even plausible for your specific fulfillment setup narrows the diagnosis considerably before you look at a single order — a pure FBM seller with no commingled inventory can rule that cause out immediately, for instance, and focus the investigation on returns handling or upstream packaging instead.

Knowing this in advance saves real time.

Diagnosing which cause actually applies

Before writing anything, pull the specific order history for the flagged ASIN and look for a pattern: is this a single complaint or several, and if several, do they cluster around a specific time window or fulfillment method? A single isolated complaint, especially on commingled FBA inventory, points toward the commingling explanation. A cluster of complaints all citing similar signs of prior use — resealed packaging, missing accessories, wear patterns — points toward a returns-reprocessing gap, either Amazon's or your own. Complaints correlating with a specific shipment or manufacturing batch point toward a packaging or handling issue upstream of Amazon entirely. Each diagnosis leads to a different, specific plan.

A worked example of the correct plan for each cause

For a commingled-inventory case: "Reviewing the flagged order, our inventory for this ASIN is enrolled in commingled FBA. We have opted out of commingled inventory for this ASIN as of [date], and confirmed our own remaining stock, verified [method], shows no signs of prior use." For a returns-reprocessing case on FBM: "We identified that the flagged unit was a customer return, restocked on [date] without a condition check beyond visual packaging inspection. As of [date], we require a functional and cosmetic inspection checklist, completed and logged by [role], before any returned unit re-enters sellable inventory." Each plan names the actual mechanism and a specific, checkable fix — neither one is a generic "we take quality seriously" statement.

Both examples share a structural feature worth noticing: the fix in each case is a specific, checkable change to a specific process, not a general statement about caring more about quality. That specificity is what separates a plan a reviewer can verify from one they simply have to trust.

The evidence that actually strengthens this kind of case

Beyond the plan itself, evidence that helps includes: your own inventory and returns-processing records for the relevant date range, documentation of any commingled-inventory opt-out (a screenshot of the current setting, dated), and where relevant, correspondence with your supplier about packaging or handling standards if the cause traces upstream. If the complaint is a single instance on high-volume commingled inventory, framing the case around the specific mechanism of commingling — and the opt-out as the fix — is considerably stronger than a broad process description that doesn't address why this specific unit reached the customer.

Photograph or otherwise document your current sellable inventory's condition periodically, even without an active complaint — a dated record showing your stock in new condition well before any complaint arose is far more persuasive than a claim made only after the fact with nothing to back it.

What to do when the complaint feels genuinely unfair

Some used-sold-as-new complaints are ambiguous — a customer's definition of "used" (a slightly creased box, a stray fingerprint) doesn't always match a seller's, and not every complaint reflects an actual condition problem. The plan of action still isn't the place to argue the customer was wrong; it's the place to show the process that governs how inventory reaches customers, and where relevant, that the specific customer's item was refunded or replaced regardless of the dispute over condition, since resolving the customer's experience is itself part of what a reviewer is checking for.

A brief, factual note about the ambiguity is fine; a lengthy argument about the customer's definition of "used" is not.

The common mistake: treating every instance as a sourcing problem

The recurring error is assuming every used-sold-as-new complaint traces back to where the product was purchased, and building a plan entirely around supplier documentation — which addresses authenticity, not condition. A genuine new product from a legitimate supplier can still reach a customer in used-looking condition through mishandling, a returns gap, or commingling, and a plan focused on proving the product's origin doesn't address any of those actual mechanisms. Diagnosing which failure mode actually applies, before writing the plan, is what separates a case that clears from one that gets rejected for not addressing the real issue.

This mistake is compounded when the supplier invoice submitted in response genuinely does prove the product is authentic — which it does, and which was never actually in question. Authenticity and condition are different claims, and proving one doesn't address the other.

Why this diagnosis discipline matters at scale

Full Circle has managed more than $500M in Amazon spend across 100+ brands, and used-sold-as-new complaints across that book split fairly evenly between commingling issues and internal returns-processing gaps — rarely a genuine sourcing problem, which is why plans built around supplier invoices alone tend to underperform on this specific case type. Dr. Shield diagnoses the specific mechanism before drafting a plan for this violation type — first 30 days free, priced on the call — because the wrong diagnosis here produces a technically well-written plan that still doesn't answer the actual complaint.

None of this guarantees reinstatement on any individual case — Amazon reviews each complaint against its own specific facts. What correct diagnosis buys is a plan that actually answers the mechanism behind the complaint, rather than one that technically addresses a different, unrelated concern.

Diagnosis first remains the rule, even here.