Amazon Strategy
Amazon Order Defect Rate (ODR): What Counts and How to Fix It
Amazon Order Defect Rate must stay below 1%. Learn what counts toward ODR, what doesn't, and how to appeal before Amazon suspends your seller account.
Amazon Order Defect Rate (ODR) is the percentage of your orders in the last 60 days that received negative feedback, an A-to-z Guarantee claim granted in the buyer’s favor, or a service credit card chargeback. Amazon sets the ceiling at 1%, and crossing it puts your selling privileges at risk. Most sellers misread which events actually count, which is why perfectly fixable ODR problems escalate into suspensions.
This post breaks down the exact formula, what Amazon counts and what it doesn’t, how to appeal defects that shouldn’t be on your record, and how to bring the number down before Seller Performance flags the account.
How does Amazon calculate Order Defect Rate?
ODR is a ratio, not a count. Amazon divides the number of orders that received a defect by the total number of orders shipped in a rolling 60-day window. According to Amazon Seller Central’s Order Defect Rate policy page, the target is under 1%.
The rolling window matters more than most sellers realize. A defect stays on the record for 60 days, then ages out. If you shipped 200 orders and one buyer left 1-star feedback, your ODR reads 0.5% for two months. If you shipped 50 orders with the same defect, it reads 2%, and you’re in suspension territory.
Volume is your friend here, but only if the incoming orders are clean. Pumping more orders through a broken listing just multiplies the defect count. The math only works when the underlying process is stable, which is why account health monitoring needs to sit alongside ODR tracking, not replace it.
Sellers with fewer than 50 orders in the window often see wild ODR swings from single events. Amazon still enforces the 1% ceiling, but Seller Performance tends to review low-volume flags with more context before acting.
What counts toward ODR and what doesn’t?
This is where most sellers get burned. Amazon counts three specific events, and everything else people worry about is noise as far as ODR math goes.
| Event | Counts toward ODR? | Notes |
|---|---|---|
| Negative feedback (1-2 stars) | Yes | Unless struck by Amazon for policy violation |
| A-to-z Guarantee claim granted | Yes | Only if decided in buyer’s favor |
| Service credit card chargeback | Yes | Payment disputes filed with the buyer’s card issuer |
| Refund (no other event) | No | A refund by itself is not a defect |
| Return (no other event) | No | Returns feed return rate, not ODR |
| Neutral feedback (3 stars) | No | Only 1-2 star ratings count |
| A-to-z claim withdrawn | No | If the buyer cancels or Amazon closes it in your favor |
| Late shipment | No | Feeds Late Shipment Rate, a separate metric |
| Cancellation | No | Feeds Pre-Fulfillment Cancel Rate, separate |
The confusion usually starts with returns. A high return rate hurts profit and signals a listing problem, but it doesn’t touch ODR directly. It only becomes an ODR issue when the buyer also leaves negative feedback or files an A-to-z claim. That’s why buyer feedback quality is worth managing even when returns are already trending up.
Chargebacks are the sneakiest of the three. A buyer can bypass Amazon and dispute the charge directly with their card issuer. You often find out through Seller Central weeks after the sale. Chargebacks count toward ODR regardless of whether the underlying complaint was valid, which is one reason conversion rate quality matters, buyers who feel the product matched the listing rarely go to their bank.
Why does Amazon suspend accounts for ODR issues?
Amazon treats the 1% threshold as a customer trust floor, not a soft target. Seller Central’s own Account Health documentation is explicit that persistent ODR above 1% can result in loss of selling privileges. Note that Amazon’s algorithms and enforcement thresholds are not publicly documented in full detail, so this reflects current public guidance and community observation, not a legal opinion.
The suspension pattern is usually staged. First you get a warning in Account Health. If the rate stays high, you get a formal notice asking for a Plan of Action. If that isn’t accepted, or if the rate keeps climbing, selling privileges are suspended pending review. Sellers who ignore the warning phase are the ones who wake up unable to ship.
Suspensions are worse than they look on paper. FBA inventory keeps generating storage fees while you can’t sell it. PPC campaigns pause. Any ranking momentum on your ASINs decays. If you were investing in listing optimization or paid traffic, the suspension window costs you both the sales and the compounding rank gains.
Reinstatement isn’t fast. Even a well-written appeal takes days to weeks to process, and complex cases can drag past a month. Preventing the suspension is roughly 20 times cheaper than reversing one, which is why proactive monitoring is the whole game.
How do you appeal a defect that shouldn’t count?
Not every defect on your record belongs there. Buyers regularly leave feedback complaining about FBA shipping (which is Amazon’s job), leave product reviews as feedback (against policy), or file A-to-z claims that get granted despite tracking showing delivery. Each of these has a specific appeal path.
For negative feedback, request removal through the Feedback Manager if the comment violates Amazon’s policies: it’s about FBA shipping or customer service, it’s a product review, it contains obscene language, or it includes personally identifiable information. Amazon strikes qualifying feedback, and struck feedback drops out of the ODR calculation. This is the fastest ODR win available.
For A-to-z claims, appeal within 30 days of the decision through the A-to-z Claims dashboard. Amazon reverses claims when tracking shows on-time delivery, when the buyer received a refund elsewhere, or when the complaint is factually wrong. A reversed claim is removed from ODR.
For chargebacks, respond through the Chargeback Claims section of Seller Central with proof of delivery, refund history, and buyer communication. Amazon defends the seller on chargebacks where the shipment tracking and communication record are clean. Won chargebacks come off ODR.
When you’re writing an actual Plan of Action for a broader ODR issue, structure the response around three components:
- Root cause. Name the specific process failure. “Our supplier changed the packaging material in April and we didn’t catch it, resulting in higher damage complaints.” Vague root causes get rejected.
- Corrective action. What you’ve already done. Removed the affected ASIN, contacted buyers, refunded proactively, changed suppliers. Concrete, past-tense actions.
- Preventive action. What systems you’ve put in place so it doesn’t recur. New QC checklist, weekly ODR review, revised listing copy, updated packaging spec.
Seller Performance reads hundreds of these. The ones that get approved are specific, factual, and free of blame-shifting toward buyers or Amazon.
The framing here matters. This is research and practitioner observation, not legal advice. If you’re in an active suspension, work with a specialist who handles Amazon appeals for a living.
How do you reduce Order Defect Rate systematically?
Appeals clean up the record you already have. Reducing ODR at the source is a different job, and it’s mostly about listing accuracy and expectation setting.
Listing accuracy is the biggest lever. If buyers report the product is different from the listing, that’s an ODR-generating gap between what the copy promised and what shipped. Anecdotally, a large share of defects on any given account cluster in a small number of listings, which is why targeted listing optimization beats blanket rewrites. Fix the ASINs generating the complaints first.
The three source-level drivers to audit:
- Listing accuracy. If buyers report the product is different from the listing, the copy is over-promising. Rewrite titles, bullets, and A+ content to match reality, not to hit keyword density.
- Packaging failures. Damaged-on-arrival complaints trace back to inadequate packaging or fragile SKUs shipped in unreinforced mailers. A one-time packaging upgrade is cheaper than a suspension.
- Sizing and fit. Apparel, accessories, and home goods generate defect complaints when the size chart is missing or inaccurate. Adding a specific, measured size chart cuts fit complaints.
For example, you might write in a corrective-action document: “Between May 1 and June 15 we observed roughly a three percent damage complaint rate on ASIN B0XXXXXXX, which we traced to a change in outer carton spec. New spec effective June 20.” That illustrative framing is what Seller Performance reads well, specific numbers, dated events, named ASINs.
Keyword targeting is quieter but still relevant. Listings ranking for search terms they can’t actually satisfy generate mismatch complaints. Applying a disciplined keyword research methodology and pruning irrelevant backend keywords reduces the flow of buyers arriving with the wrong expectations. Tighter keyword targeting and listing accuracy can cut product-fit complaints within one or two replenishment cycles, based on what we see across managed accounts.
PPC is another underrated ODR lever. If you’re bidding on broad-match terms that pull unrelated intent, those buyers are more likely to return, complain, or leave 1-star feedback. Cleaner PPC campaign structure with disciplined negative keywords reduces low-quality traffic.
What monitoring cadence keeps ODR under control?
Weekly is the minimum. Daily is the standard for accounts doing meaningful volume or accounts with a history of Account Health warnings.
Log into Seller Central > Account Health at least once a week and review three numbers: current ODR, defects in the last 60 days by type, and any pending A-to-z claims. Pending claims are the highest-leverage item because you can still respond and prevent the defect from being granted.
Set up email alerts for negative feedback. Amazon sends these automatically, but many sellers filter them into a folder they never check. A 1-star feedback that you catch on day one can often be corrected with the buyer directly before it ages into an unrecoverable defect. Buyers can remove their own feedback within 60 days.
For accounts running paid traffic, monitor ODR alongside ACoS and TACoS. A spike in defects often correlates with a campaign expansion that pulled in mismatched buyers. Cross-referencing the two dashboards catches the pattern before Amazon’s does.
Sellers running larger catalogs benefit from segmenting ODR by ASIN, not just at the account level. The Blog hub covers the operational side of catalog management in more depth, and pairing ODR analysis with competitor analysis helps identify whether category-wide return norms are shifting or whether the problem is isolated to your listings.
If your account is already close to 1%, the fastest path down is a combination of feedback strikes on policy-violating comments and immediate corrective action on the top defect-generating ASIN. Volume alone won’t save you if the underlying process is still broken.
Frequently Asked Questions About Order Defect Rate
What is a good Amazon Order Defect Rate?
Amazon’s stated target is under 1% of orders in the rolling 60-day window. Anything at or above 1% risks account suspension. Well-managed accounts often sit under 0.5%, though the achievable benchmark varies by category and order volume.
How long does it take for ODR to recover after a defect?
ODR uses a rolling 60-day window, so a single defect ages out after 60 days. If you receive one defect on 100 orders, your ODR reads 1% for the next two months unless you generate additional clean orders to dilute the ratio. Higher volume shortens the practical recovery time.
Does a refund count against Order Defect Rate?
No. A straight refund with no negative feedback, no A-to-z claim, and no chargeback does not count toward ODR. The metric only counts three specific defect types, not refunds or returns by themselves.
Can I remove a negative feedback that’s hurting my ODR?
Amazon strikes feedback that violates their policies (product reviews left as feedback, comments about FBA shipping, profanity, or PII) if you request removal through Seller Central. Buyers can also remove their own feedback within 60 days. Struck feedback drops out of the ODR calculation.
What happens if my ODR goes above 1%?
Amazon typically issues a warning first, then may suspend selling privileges if the rate doesn’t come down. You’ll be asked to submit a Plan of Action covering root cause, corrective action, and preventive action for each defect category driving the number up.
Track the keywords driving mismatch traffic and clean up the listings generating defects before Amazon does. Start your free Keywords.am trial and get the ranking and listing data you need to keep ODR under 1% without guesswork.