What ODR level triggers suspension risk?

Amazon's target is under 1%. Once you cross 1%, your account enters at-risk status. At 1.5%+ you'll likely receive a warning. If you don't reduce it quickly, Amazon may suspend selling privileges. The fastest fix is identifying which orders are generating defects and addressing the root cause (product quality, shipping method, listing accuracy).

How quickly should I respond to policy warnings?

Within 24 hours, ideally within 12. Amazon gives you a limited window to respond. Faster responses demonstrate good faith, and your first response sets the tone. A well-written Plan of Action submitted within hours has a much higher approval rate than one submitted days later.

Does FBA protect me from account health issues?

Partially. FBA eliminates late shipment rate and pre-fulfillment cancel rate concerns since Amazon handles fulfillment. But ODR, policy violations, product authenticity complaints, and intellectual property issues still apply to FBA sellers. You're responsible for the product and listing — Amazon is only responsible for shipping.

How often should I check account health?

At minimum, check the Account Health Dashboard weekly. High-volume sellers (1,000+ orders/month) should check daily or set up automated monitoring. The risk isn't just suspension — even a small metric dip can reduce your Buy Box share and organic ranking before you notice.

Can I recover from an account suspension?

Yes, but it's much harder than preventing one. Recovery requires a detailed Plan of Action that identifies the root cause, explains what you've already done to fix it, and outlines systemic changes to prevent recurrence. Approval can take days to weeks. Prevention through weekly monitoring is always the better strategy.

What's the difference between a warning and a violation?

A warning is informational — Amazon is flagging a metric that's trending in the wrong direction. A violation means you've breached a specific policy. Warnings give you time to course-correct. Violations require immediate action and a formal response. Both should be treated seriously.

Amazon Account Health SOP: Weekly Monitoring Checklist

Account health is not a metric you check when things go wrong. It's the foundation that determines whether you can sell at all. A single metric crossing Amazon's threshold can trigger a warning, reduce your Buy Box share, or suspend your account entirely. The sellers who never face these crises are the ones who monitor systematically every week. This SOP gives you the exact checklist, the exact thresholds, and the exact response playbooks for every scenario.

Why You Need an Account Health SOP

Most sellers check their Account Health Dashboard reactively — after they receive a warning email. By then, the damage is already done. A systematic SOP catches problems while they're still small:

Early warning detection: A metric trending upward over 3 weeks is a problem you can fix quietly. That same metric hitting the threshold next week is a crisis that costs you sleep and revenue.
Delegation-ready: A written SOP means a VA or team member can handle weekly monitoring. You only get involved when something needs a decision. Without an SOP, account health monitoring lives in your head and dies when you take a week off.
Faster incident response: When a policy warning lands, you don't have time to research how to respond. A pre-written playbook means you submit your Plan of Action within hours, not days. Speed matters — Amazon's review team treats fast responses more favorably.
Audit trail: Documenting your weekly checks creates evidence that you're a diligent seller. If you ever need to appeal a suspension, showing a history of proactive monitoring strengthens your case significantly.

The Metrics That Matter

Amazon tracks dozens of metrics, but only a handful can actually shut you down. Focus your monitoring on these critical numbers:

Metric	Target	Danger zone	What it measures
Order Defect Rate (ODR)	< 1%	> 1%	A-to-Z claims + chargebacks + negative feedback
Late Shipment Rate	< 4%	> 4%	Orders shipped after expected ship date (FBM only)
Pre-fulfillment Cancel Rate	< 2.5%	> 2.5%	Orders cancelled by seller before shipment
Valid Tracking Rate	> 95%	< 95%	FBM orders with valid tracking uploaded on time
Voice of Customer	0 flags	Recurring flags	Customer complaints by type (not as described, defective, etc.)
Policy Violations	0 active	Any unresolved	Listing policy, product safety, IP complaints

ODR is the most dangerous metric. It's calculated on a 60-day rolling window, which means a bad week takes two months to fully clear. Prevention is vastly easier than recovery. Understanding what drives your Order Defect Rate is the single highest-leverage activity for account health.

Weekly Monitoring Checklist

Run this checklist every Monday morning. It takes 10 minutes manually, or 30 seconds with automated monitoring. The goal is to catch anything trending in the wrong direction before it hits a threshold.

1. Order Defect Rate (ODR)

Must stay under 1%. This is the metric that suspends accounts. It includes three components: A-to-Z Guarantee claims, credit card chargebacks, and negative seller feedback (1-2 star ratings). Check the trend line — a gradual rise from 0.3% to 0.7% over three weeks needs attention even though you're still "safe."

If trending up: Identify which component is driving the increase. Is it product quality (A-to-Z claims)? Shipping issues (late delivery complaints)? Communication (buyer frustrated they couldn't reach you)?

2. Late Shipment Rate

Must stay under 4%. Only applies to Merchant Fulfilled (FBM) orders — FBA sellers can skip this. Measured as orders where tracking shows shipment after the expected ship date. If you use FBM for any products, set your handling time conservatively. It's better to promise 3-day handling and ship in 2 than promise next-day and miss occasionally.

Quick fix: Increase your handling time in Seller Central. This gives you more buffer and reduces the metric immediately for future orders.

3. Pre-fulfillment Cancel Rate

Must stay under 2.5%. Triggered when you cancel an order before shipping — usually because the item is out of stock. The fix is inventory sync. If your inventory count in Seller Central doesn't match reality, you'll sell items you can't ship.

Pro tip: Set a safety stock buffer (e.g., show 5 fewer units than actual stock) to prevent overselling during high-traffic periods.

4. Policy Violations & A-to-Z Claims

Check for any new violations or claims since your last review. New violations should be addressed the same day — even if you disagree with the finding, a timely response demonstrates good faith. For A-to-Z claims, respond with order details, tracking information, and any communication history with the buyer.

Automate this with Jarvio; no coding required.

Start free trial

Monthly Deep Dive

The weekly checklist catches urgent problems. The monthly review catches systemic ones — patterns that don't trigger alarms individually but compound over time.

Performance Dashboard trends: Don't just check if metrics are within thresholds. Graph the last 90 days. Is ODR flat at 0.3% or has it crept from 0.2% to 0.5%? Flat is fine. Trending up means something changed — new product, new supplier batch, shipping carrier change.
Voice of Customer (VoC): This report groups customer complaints by type: "not as described," "defective," "arrived late," etc. Two or more complaints of the same type on the same ASIN is a pattern. Amazon may suppress listings with recurring VoC flags without warning. Fix the root cause before that happens.
Return reasons analysis: Download your return data and categorize by reason. If "not as described" is your top return reason, your listing images or bullet points are misleading customers. If "defective" is trending up, your supplier quality may be slipping. Each return costs you the product, return shipping, and restocking — plus it damages account health metrics.
Listing compliance scan: Review your active listings for potential policy issues: restricted keywords, unsubstantiated claims ("FDA approved," "clinically proven"), missing safety warnings, or incorrect category placement. A compliance issue that's been live for months can suddenly trigger a violation if Amazon's crawler catches it. Better to find and fix it yourself.
Intellectual property check: Search for any new IP complaints against your products. Also check if competitors are using your trademarks or copyrighted images. Brand protection is an ongoing process, not a one-time setup.

Immediate Action Playbooks

When something goes wrong, speed and quality of response both matter. Here are playbooks for the three most common incidents:

🚨 Policy Warning Received

Timeline: Respond within 24 hours. Ideally within 12.

Read the warning carefully — identify the exact policy cited and the specific ASIN or action flagged
Gather evidence: order details, product certificates, supplier documentation, listing screenshots
Write a Plan of Action (see below) that addresses root cause, corrective actions, and preventive measures
Submit through the Account Health Dashboard — not via email or Seller Support chat
Document the incident and response in your internal records for future reference

🚨 A-to-Z Claim Filed

Timeline: Respond same day.

Review the buyer's claim reason and your order details (tracking, delivery confirmation)
Check your Buyer-Seller Messaging for any communication history with this customer
If the claim is valid: refund proactively and note what you're doing to prevent recurrence
If the claim is invalid: provide tracking proof, delivery confirmation, photos, and communication records
Respond through the claim interface with a professional, factual tone — never emotional

🚨 Listing Suppressed

Timeline: Fix within hours. Every hour costs sales and ranking momentum.

Check the suppression reason in the "Fix Your Products" section of Seller Central
Common causes: missing product information, image policy violation, restricted keyword, safety claim without documentation
Fix the specific issue cited — don't rewrite the entire listing, just address what Amazon flagged
Re-submit and monitor for reactivation (usually 15 minutes to 24 hours)
If the listing doesn't reactivate within 24 hours, open a case with Seller Support referencing your fix

See our detailed guide on fixing suppressed listings.

How to Write a Plan of Action

A Plan of Action (POA) is your formal response to Amazon when they flag an issue. Most sellers write terrible POAs that get rejected because they're either too vague ("we'll do better") or too emotional ("this is unfair"). Here's the structure that gets approved:

Section 1: Root Cause

Identify exactly what went wrong and why. Be specific. "A batch of 500 units from Supplier X had dimensional variance of 2 inches due to a tooling change we were not notified about." Not "there was a product quality issue." Amazon wants to see that you understand the problem deeply enough to prevent it.

Section 2: Corrective Actions (Already Taken)

What have you already done? "Removed remaining 340 units from FBA inventory. Issued full refunds to 12 affected customers. Updated listing images with accurate measurements." Past tense, specific numbers, concrete actions. Amazon wants to see you've already acted, not that you're planning to.

Section 3: Preventive Measures

What systemic changes prevent recurrence? "Implemented incoming quality inspection: 5-unit sample measurement from every batch before sending to FBA. Added dimensional tolerance clause to supplier contract. Set up weekly VoC monitoring to catch complaints within 48 hours." These should be processes, not promises.

Keep it factual, professional, and under 500 words. Amazon's review team reads hundreds of these daily — they appreciate concise, structured responses over lengthy emotional appeals. For a more detailed guide, see how to write a suspension appeal.

Preventing Account Health Issues

The best account health SOP is one where the "Immediate Action" section never gets used. Here's how to stay out of trouble:

Accurate listings: The number one cause of "not as described" complaints — and therefore A-to-Z claims and ODR — is listings that don't match the product. Double-check dimensions, materials, color accuracy in photos, and included components. If your product changed, update the listing the same day.
Quality control on incoming inventory: Sample-check every batch from your supplier before sending to FBA. Check dimensions, weight, functionality, and packaging. One bad batch can generate dozens of returns and complaints that take months to clear from your metrics.
Conservative handling times: If you fulfil any orders yourself, set handling time 1 day longer than your actual capability. This gives you a buffer for unexpected delays. A "late" shipment that arrives on time is worse for your metrics than a "fast" shipment that arrives on time.
Proactive customer communication: When you know there's an issue (delayed shipment, quality problem), message the buyer before they complain. A proactive refund or replacement offer almost always prevents an A-to-Z claim. The claim costs you more than the refund would have.
Regular listing audits: Run a quarterly account audit that includes listing compliance review. Check for restricted keywords, unsubstantiated claims, and outdated information that could trigger policy violations.

Delegating Account Health to Your Team

Once your SOP is documented, a trained VA or team member can handle 90% of account health monitoring. Here's how to delegate effectively:

Give view-only access to the Performance Dashboard. Your VA needs to see the metrics but not make changes to listings or respond to violations without your approval.
Define escalation criteria clearly. "If any metric exceeds [threshold], notify me on Slack immediately. If a policy violation is received, notify me within 1 hour. Everything else goes in the weekly report."
Create a simple reporting template. A spreadsheet with this week's metrics, last week's metrics, the trend direction, and a notes column for anything unusual. Takes 10 minutes to fill, gives you everything you need at a glance.
Review their work for the first month. Check their weekly reports against the actual dashboard to ensure accuracy. After a month of accurate reporting, you can trust the delegated process and only step in when escalated.

See more SOPs ready for delegation on our Amazon SOPs hub. For hiring advice, read our guide on hiring a VA for Amazon.

Automating the Entire Process

Here's what automated account health monitoring looks like — the weekly check runs itself and only escalates when something needs your attention:

Jarvio

Run my weekly account health check.

Running weekly account health audit... Here's your report:

What are those Voice of Customer flags?

Pulling VoC details for the 2 flagged items... Both flags are on ASIN B09KX7 (Bamboo Cutting Board, Large): **Flag 1:** "Item not as described" — Customer says board is 16x10 instead of advertised 18x12. Filed 3 days ago. **Flag 2:** "Item not as described" — Customer says handles are smaller than shown in images. Filed yesterday. **Risk assessment:** Two "not as described" flags on the same ASIN within a week is a pattern. If this continues, Amazon may suppress the listing for listing accuracy issues. **Recommended actions:** 1. Verify actual product dimensions match your listing — measure a unit from current inventory 2. Check if a recent supplier batch has dimensional variance 3. Review your product images — ensure they accurately represent handle size 4. If dimensions are correct, consider adding exact measurements to Image 5 (size comparison) Want me to set up a daily monitor on this ASIN's VoC flags?

Automate Account Health →