Amazon Account Health Dashboard: Proactive Monitoring Guide

How every Account Health metric feeds into the same risk engine

Amazon's Account Health Dashboard displays metrics in separate cards, which makes sellers treat them as independent scores. They are not. Amazon's internal risk engine weights these metrics together, and a decline in one amplifies the impact of another. Here is how the core four interact:

• Order Defect Rate (ODR): the percentage of orders with A-to-Z claims, chargebacks, or negative feedback. Amazon's threshold is 1%. ODR above 0.5% while Late Shipment Rate is simultaneously elevated will trigger faster review than either metric alone.
• Late Shipment Rate (LSR): orders confirmed shipped after the expected ship date. Threshold is 4%. High LSR directly feeds ODR because late shipments generate A-to-Z claims. Fix LSR first and ODR often corrects on its own.
• Valid Tracking Rate (VTR): the percentage of shipments with a valid, scannable tracking number from an integrated carrier. Threshold is 95%. VTR failures now feed the FBM offer-blocking system at the ASIN level, which means a single product line using a problematic carrier can lose its offer even if your account-level VTR looks healthy.
• FBM offer-blocking metrics: Amazon evaluates carrier-level delivery performance, on-time delivery rate, and tracking accuracy per ASIN. If a specific SKU's FBM fulfillment consistently underperforms, Amazon blocks the FBM offer for that ASIN without necessarily penalizing your entire account. This is the enforcement layer most sellers still miss.

The practical takeaway: tracking one metric in isolation gives you a false sense of safety. A VTR of 96% looks fine until you realize three ASINs in your catalog are at 88%, and those three ASINs are about to lose their FBM offer eligibility.

Pulling Account Health data via SP-API for automated monitoring

Seller Central's dashboard updates once daily. That is too slow for a brand doing 500+ orders a day on FBM. The SP-API Seller endpoint gives you programmatic access to ODR, LSR, VTR, and policy violation counts. You can poll it every six hours and pipe the data into whatever system your team already uses.

A practical SP-API monitoring stack

1. Authentication: register your app in the Amazon Developer Portal and obtain LWA (Login with Amazon) credentials. Use the getAccountHealthMetrics operation under the Sellers API section.
2. Data pipeline: schedule a Lambda function (or a cron job on your server) to call the endpoint every 6 hours. Store the response in a database. PostgreSQL or BigQuery both work. The payload includes rolling 10-day, 30-day, and 90-day windows for each metric.
3. Visualization: connect Grafana, Looker, or even a Google Sheet with Apps Script to your database. Build a single-pane dashboard showing all four core metrics with trend lines. Overlay your internal thresholds (more on those below) as horizontal reference lines.
4. Alerting: configure alerts in your monitoring tool or through PagerDuty, Slack webhooks, or email. Two tiers: Warning and Critical. Warning fires at your internal threshold. Critical fires at 75% of Amazon's published limit.

If you are running a multi-marketplace operation and already track FBA inventory metrics through automated systems, add Account Health to the same pipeline. The marginal engineering cost is low, and the downside protection is enormous.

Threshold alerts that trigger operational changes

Alerts are useless if they only produce Slack messages that people ignore. Each alert tier should map to a specific, pre-approved operational response. Define these in advance so your team acts on protocol instead of panicking.

ODR thresholds

• Warning (0.5%): review all open A-to-Z claims and negative feedback from the past 7 days. Identify the root-cause pattern (late delivery, item-not-as-described, damaged goods). Assign an owner to resolve each claim within 24 hours.
• Critical (0.75%): pause all FBM listings for affected ASINs and route orders through FBA backup inventory. Notify your account manager or agency team. Begin drafting a preemptive Plan of Action documenting corrective steps.

LSR thresholds

• Warning (2%): audit carrier pickup schedules. Confirm that handling time settings in Seller Central match actual warehouse processing time. A single holiday weekend with a 48-hour handling time set to 24 hours can spike LSR fast.
• Critical (3%): switch affected SKUs to FBA fulfillment or extend handling time. Open a carrier escalation ticket if the issue is pickup-related. Document everything.

VTR thresholds

• Warning (97%): pull a report of all shipments from the past 5 days with invalid or missing tracking. Identify whether the issue is a specific carrier, a warehouse data-entry error, or an API integration failure with your shipping software.
• Critical (95.5%): halt shipments through the offending carrier. Reroute through a carrier with confirmed Amazon tracking integration. Run a manual audit of every shipment from the past 48 hours.

For sellers navigating the new FBM prepaid returns requirements, VTR failures compound the cost: you are paying for return shipping on orders that already had tracking problems. Double the financial hit, double the urgency.

FBM offer-blocking: ASIN-level monitoring

Amazon does not give ASIN-level Account Health data through the SP-API in the same structured format as account-level metrics. You need to supplement API data with manual checks. Every week, pull your FBM performance notifications from Seller Central and cross-reference against your top-revenue FBM ASINs. If an ASIN receives an offer-blocking warning, treat it as a Critical alert and activate FBA backup immediately. Losing the Buy Box on a top SKU for even three days can cost thousands in revenue.

Documenting metric recovery for appeals

If your account does get flagged, Amazon's Account Health team will ask for a Plan of Action. The sellers who recover fastest are the ones who started documenting before the flag. Here is what your documentation package should include:

1. Root-cause analysis: a specific, factual statement of what caused the metric breach. "Our carrier experienced a regional service disruption" is better than "shipping delays occurred." Include carrier incident reports if available.
2. Timeline of corrective actions: log every step your team took, with dates and timestamps. Screenshots from Seller Central showing metric movement. Emails to your carrier. Internal process change memos. Amazon wants evidence, not promises.
3. Preventive measures: describe what you changed permanently. Switched carriers for specific regions. Added a second carrier as backup. Adjusted handling time. Implemented automated threshold alerts. Be specific about tools and workflows.
4. Supporting data: include before-and-after metric snapshots showing improvement. If you built an automated dashboard, export the charts. Visual evidence of recovery is persuasive.

Keep a running "Account Health Log" in a shared document or project management tool. Every time an alert fires, log the date, the metric, the value, the action taken, and the outcome. This log becomes your appeal evidence if you ever need it. Our account suspension and reinstatement guide covers the full appeal framework in detail.

Weekly Account Health review: a meeting template

A 20-minute weekly review prevents 90% of Account Health crises. Here is the agenda format we use with managed accounts:

1. Metric snapshot (3 min): review ODR, LSR, VTR, and policy violation count. Compare to prior week. Flag any metric that moved more than 0.1 percentage points in the wrong direction.
2. Open violations and cases (5 min): review any active policy violations, intellectual property complaints, or product authenticity flags. Assign owners and deadlines for resolution.
3. FBM ASIN-level flags (3 min): check for any new offer-blocking warnings or suppressed offers. Confirm FBA backup status for flagged ASINs.
4. Carrier performance (3 min): review carrier-level on-time delivery and tracking accuracy. Identify any carrier trending below 95% on-time.
5. Action items from prior week (3 min): confirm completion of last week's corrective actions. Close resolved items. Escalate anything still open.
6. Log update (3 min): update the Account Health Log with this week's data points and decisions. This becomes your institutional memory.

Attendees: marketplace manager, operations/fulfillment lead, and (if applicable) your agency account manager. Keep the meeting tight. If a topic needs deeper investigation, assign it as a follow-up with a 48-hour deadline.

Escalation protocol: who does what, and when

Define three escalation tiers in writing. Post them where your team can find them under pressure.

• Tier 1 (Warning threshold breached): marketplace manager investigates root cause within 4 hours. Notifies ops lead. Documents findings in Account Health Log.
• Tier 2 (Critical threshold breached): marketplace manager activates pre-approved operational change (FBA switch, listing pause, carrier reroute) within 2 hours. Ops lead confirms execution. Agency team notified for review. Begin drafting preemptive Plan of Action.
• Tier 3 (Amazon warning or enforcement received): full team response. Submit Plan of Action within 24 hours per Amazon's seller performance guidelines. Agency team leads the appeal. Marketplace manager provides documentation package from the Account Health Log.

Print this protocol. Laminate it if you have to. When an account is at risk, people forget processes. Written escalation paths prevent paralysis. If you are expanding into EU marketplaces, replicate these protocols per region, because Account Health thresholds and enforcement timelines differ between Amazon Europe marketplaces and the US.

The metric Amazon watches that most sellers ignore

Buyer messaging response time. It does not appear as a standalone Account Health metric, but slow responses to buyer messages correlate strongly with A-to-Z claim escalation. Amazon's own Seller Central documentation states that responding to buyer messages within 24 hours reduces A-to-Z claim rates. Track your average response time weekly. If it drifts above 12 hours, add staffing or automate initial responses through Amazon's buyer-seller messaging templates.

One more often-overlooked signal: the Voice of the Customer dashboard. It aggregates return reasons and customer complaints at the ASIN level. A spike in "item not as described" returns for a specific SKU is a leading indicator of ODR increase. Catch it in the VOC dashboard before it hits your defect rate.

Account Health is an operational discipline, not a monthly check-in. Build the alerts, run the meetings, document everything. The brands that treat this as infrastructure never have to write a Plan of Action under pressure.

Your Account Health metrics are either a system you control or a surprise that controls you. Hyperzon's operations team builds the monitoring, alerts, and escalation protocols that keep accounts in good standing while you focus on growth. Get a free Amazon audit.

Article was originally published on 20 October, 2026