Used Sold As New Complaint On Amazon: The Fastest Way To Fix It

One order ID. That is often the entire body of evidence attached to a Used Sold as New notification, and it is the part sellers find hardest to accept, because one buyer describing one unit is enough to take a listing off sale while the rest of the catalogue carries on as though nothing happened.

We understand how that feels, because the ASIN was selling this morning, the inventory behind it keeps accruing storage fees whether the page is live or not, and the notification explains almost nothing.

The useful thing to know early is that most of these complaints are not about a used product. They are about a product that arrived looking used, and that is a different problem with a different fix.

What Amazon is actually measuring

A Used Sold as New complaint is a product condition complaint. It sits under policy compliance in Account Health, and the trigger is a customer statement rather than an inspection. A buyer picks a return reason, leaves feedback or files a claim saying the item arrived used, and that goes on the record against the ASIN.

The standard is Amazon's own definition of New, worth reading literally: "For a product to be considered New, it should be as if you walked into a store and bought it right off the shelf in its factory packaging." Source: Amazon condition guidelines, Amazon primary.

The test is not whether the item works. It is whether opening the parcel felt like opening a new product, and a crushed carton, a lifted seal or a box taped twice fails that on its own. Plenty of these complaints involve units nobody ever used.

Where the used units actually come from

There are only a handful of real causes, and separating them matters, because Amazon reads an appeal as credible when it names one and treats the rest as noise.

The first column is where most cases genuinely sit. Riverbend Consulting, third party, updated 2024, lists the same pattern our team sees most often: unsellable returns mixed back into sellable inventory, with inspection too light to catch it. Nobody decides to do that. It happens because a returned unit that looks fine from the outside costs money to write off.

What changed on 31 March 2026

For years the honest answer in some of these cases was that the unit was never yours, because stickerless commingled inventory let Amazon pool identical products from different sellers.

That ended. Amazon's announcement states the new requirements "will go into effect for inventory shipped on or after March 31, 2026", with brand owners holding the Brand Representative role no longer needing Amazon barcode stickers on products that already carry a manufacturer barcode.

Resellers not enrolled that way "will now be required to use Amazon barcode stickers for products even if they have a manufacturer barcode". Source: Amazon Seller Central, Amazon primary, 2026.

So "it was commingled stock" has stopped being an available explanation after that date. That cuts both ways, because a clean process is now genuinely provable.

How to tell whether this is your problem or the network's

Five checks, worth running before the appeal is written, because it is only as good as the cause it names.

1. The complaint window comes first. The notification carries dates and order IDs, and everything after that is a question about what your inventory was doing then, not now.
2. Returns on the ASIN over that window tell you most of it. The path is Reports then Fulfilment then Customer Returns. Disposition matters more than the rate, because units marked sellable and put back into stock are the most common origin of these complaints.
3. Clustering separates a process fault from a one-off. Several complaints on one SKU points at packaging or prep. Complaints across unrelated SKUs points at returns handling.
4. Fulfilment channel narrows it further. Merchant-fulfilled complaints are almost always your packing bench. FBA complaints can be either, which is why the returns data comes first.
5. Stock shipped before and after 31 March 2026 behaves differently. Older units may still reflect the shared inventory arrangement, so the receipt date changes what you can reasonably claim.

What to gather before you write anything

There is a strong pull to reply immediately, and it is worth resisting for a day, because a fast appeal naming the wrong cause comes back rejected, and the second attempt argues against your own first version.

The appeal that addresses root cause rather than apologising

The appeals that fail almost always fail the same way, by leading with regret and a promise to be more careful. Reviewers are looking for a cause, a correction and a control, and an apology is none of those.

1. The opening states the cause in one sentence. Returned units restocked without a condition check, packaging not rated for the network, or a supplier run that varied. One cause, named plainly, with evidence referenced.
2. The corrective action covers units that already exist. Removal orders, disposal records or a fresh inspection of remaining stock, because a cause with no cleanup reads as a cause still running.
3. The preventive action has to be a mechanism, not an intention. A named person, a written check, a quarantine location, a packaging change. Amazon can believe a process, and can do nothing with a commitment to be careful.
4. Attachments get referenced by name in the text. Reviewers work quickly, and a document nobody is pointed at tends to be a document nobody reads.
5. The submission route is the violation itself. In Account Health the affected listing carries its own appeal option, which keeps everything attached to the right record instead of opening a general case.
6. Follow-up is the unglamorous half. Template replies happen, and they often have little to do with what was sent. Going again with the same evidence works better than softening it.

We cannot promise a listing comes back, because the outcome depends on the complaint history behind the ASIN and on which reviewer picks it up, and we would be careful with anyone who promises otherwise. What we can say is that appeals naming a specific cause with evidence behind it move very differently.

On a toy brand in the US facing a false pesticide flag, a different policy category but the same shape of work, our team had 22 ASINs reinstated within 7 days and Account Health restored from 200 to 1000. Our account health management page covers the policy side.

Keeping the complaint from coming back

Amazon treats condition complaints cumulatively, so the second on an ASIN is a harder conversation than the first. Prevention is boring, which is why it gets skipped.

1. Returns get a physical location that is not sellable stock. One shelf, one label, one person deciding. Writing off a returned unit is cheaper than a deactivated ASIN.
2. Outer packaging is tested against the network rather than your warehouse. A carton that survives a pallet does not always survive a conveyor and a van, and that failure arrives as a condition complaint.
3. Seals are treated as part of the product. Anything opened for prep needs a plan for how it looks resealed, because buyers read tape as evidence.
4. Return reasons get read monthly. Buyers usually say what happened before they say it to Amazon, and that wording is the earliest warning available.
5. New supplier runs get sampled before they go in. Production variation arrives silently, and stock already in a fulfilment centre is expensive to correct. Our inventory management work starts here.

What we would do first if this were our account

Pull the returns data for the complaint window before anything else, because that report usually decides which cause you are dealing with, and the appeal gets written from there rather than from a template.

Then check whether the same wording is appearing on other ASINs, since a pattern across the catalogue is a returns-handling problem and a cluster on one SKU is a packaging problem. If the notification has already been appealed and rejected, the second attempt matters more, and a rejected appeal does narrow the room available. That is the kind of case our team works through regularly, alongside the wider policy warning side of an account.

We will not give you a timeline, because these move at Amazon's pace and the first reply is sometimes a template that does not engage with what was sent. What we can tell you, before you spend anything, is which cause your data supports and whether your draft names it. That is what the free, no-obligation audit covers, and if your process is sound and this was one unreasonable buyer, we will say that too.

Related guides

• FNSKU versus manufacturer barcodes
• The ODR, LSR and VTR metrics behind most warnings
• Appealing a false Restricted Product flag

Common questions about Used Sold as New complaints