What Is a Used-Sold-as-New Violation?
Amazon's condition standards are strict: a product listed as "New" must arrive sealed, undamaged, and indistinguishable from a manufacturer-direct purchase. When a buyer reports otherwise, or when Amazon's own returns-monitoring data flags a pattern, Seller Central issues a condition-mismatch complaint that can remove a listing, suppress an ASIN, or trigger account-level review under the Account Health performance metrics.
The violation stings hardest when the seller never intentionally listed used inventory as new. One of the most common scenarios is an automatic SKU condition change, a system-level event where a third-party repricing tool, a bulk inventory upload, or a warehouse workflow silently overwrites a product's condition from "Used" to "New." The seller ships the item, the buyer opens it expecting a factory-sealed product, and a complaint lands before anyone realizes what happened.
Understanding why this happens and how to appeal it correctly is the difference between a reinstated listing and a permanent ASIN ban. For sellers who want a deeper look at condition-related suspensions, the used sold as new guide covers the full range of violation subtypes.
"The most common mistake sellers make in these appeals is treating a system-caused condition change as an intentional policy breach. Amazon's investigators are looking for evidence that proves the root cause was technical, not behavioral, and that framing has to be crystal clear in the Plan of Action." — Renata Osei-Mensah, Senior Appeals Strategist, Clearpath Marketplace Advisory
How SKUs Automatically Change from Used to New
This scenario is far more common than most sellers realize. Several technical pathways can silently flip a product's condition field.
Flat-file upload overwrites. When a seller re-uploads an inventory feed to adjust pricing or replenish quantity, a missing or blank "condition" column can cause Seller Central to default to "New." If the original listing was "Used - Like New," that label disappears without any warning.
Third-party repricing tools. Some repricing integrations push updates through the Products API. Depending on how the feed is structured, a condition attribute that isn't explicitly passed can revert to a system default. The Amazon Seller Code of Conduct holds sellers responsible for all content posted under their account, regardless of whether a tool caused it.
FBA condition changes after a return. Amazon occasionally processes a customer return and routes the item back into active inventory without downgrading the condition. The item ships again as "New" even though it was an open return.
Multi-channel fulfillment mismatches. Sellers managing inventory across multiple warehouses sometimes see condition labels sync incorrectly when stock is transferred between fulfillment channels.
Each of these scenarios produces the same compliance outcome: a buyer receives a used item sold as new, and Amazon logs a defect against the seller's account.
Why This Violation Is Especially Dangerous
If you have gotten the email, you have already lost sleep over it. Here is why fast action matters.
A single condition-mismatch complaint can cascade quickly. Amazon's automated systems frequently suppress the ASIN at the first complaint, and a pattern of complaints can trigger account-level review within days. Sellers who dismiss a warning notice without responding often discover their account is deactivated by the time they act.
The violation appears prominently in Account Health under "Product Condition Customer Complaints." Multiple complaints within a rolling period can push the Account Health Rating into the "At Risk" zone, which limits access to certain selling programs and surfaces the account to Amazon's Trust and Safety reviews.
Loss of a high-BSR ASIN during peak season can translate into tens of thousands of dollars in missed revenue. That real cost makes fast, accurate appeals worth far more than their face value. Sellers managing multiple categories should also review the account deactivation knowledge base to understand how one violation category can influence a broader account review.
How to Appeal a Used-Sold-as-New Violation Caused by an Automatic SKU Change
The appeal for a system-caused condition change requires a different structure than a behavioral violation appeal. The root cause is technical, the corrective action is procedural, and the evidence must prove both.
- Decode the notice and isolate the affected ASIN. Log into Seller Central's Account Health dashboard and identify the exact order number and ASIN listed in the complaint. Use AppealsPro.ai's Suspension Notice Decoder to extract the violation subtype, required evidence categories, and the specific policy section Amazon cited so you know exactly what the appeal must address.
- Reconstruct the condition-change event. Pull the flat-file upload history, repricing tool logs, or FBA returns report for the date range covering the flagged order. You need a timestamped record showing when the condition field changed and what system action caused it. This is your root-cause evidence.
- Gather supporting documentation using a violation-specific checklist. For a condition-mismatch appeal, you typically need the original product listing showing the correct condition, the upload or API log showing the overwrite, supplier invoices confirming you sourced genuine new inventory, and any FBA returns data. AppealsPro.ai's Document Checklists generate a violation-specific evidence list so nothing critical is missing before you draft the letter.
- Draft a Plan of Action with a clear three-part structure. Write a root-cause section covering the system event that changed the condition, a corrective-action section covering what you did immediately such as removing the listing and auditing all SKUs, and a preventive-action section covering the controls you have implemented such as mandatory condition-field validation before any upload. The Appeal Letter Generator produces a policy-matched draft aligned to Amazon's used-sold-as-new standards, which you then customize with your specific evidence.
- Review before submitting. Read the appeal from Amazon's perspective: does every claim have a corresponding piece of evidence? Is the preventive action section specific enough to be credible? Vague promises like "we will be more careful" are the single most common reason appeals are rejected. Confirm all evidence files are attached and properly labeled.
- Submit through Account Health and track the response window. Upload through Seller Central's Account Health interface, not via generic Seller Support. Note the timestamp and monitor for a response. If Amazon sends a follow-up request for additional information, that reply needs to be addressed within the response window or the case may close unfavorably.