Amazon Seller KPI Dashboard Template

An amazon seller kpi dashboard is worth building for one reason: Seller Central scatters the twelve numbers that actually predict your P&L across nine different screens, and nobody opens all nine every week. The fix isn’t software — it’s a single spreadsheet view, updated every Monday, where each metric has three things attached: where to pull it, what healthy looks like, and the specific trigger that turns a number into a task. This page is that framework in full. Build it in Google Sheets in an afternoon; graduate to Sellerboard or Scale Insights when the manual pull becomes the bottleneck, not before.

The 12 Metrics in Your Amazon Seller KPI Dashboard

1. TACoS

Pull: total ad spend (Advertising console) ÷ total revenue (Business Reports → Sales Dashboard). No native report combines them — that’s your spreadsheet’s job. Healthy: 8–15% for established brands; 20–30% acceptable during launches. Trigger: TACoS up two consecutive weeks while revenue is flat → ads are substituting for organic sales, not adding to them. Audit branded-term spend and organic rank before raising budgets again.

2. ACoS by Campaign Type

Pull: Advertising console → Campaign Manager, segmented Sponsored Products / Brands / Display. Never read blended ACoS — it hides everything. Healthy: SP exact on converting terms, 15–30%; SB, 20–40%; SD retargeting often higher and judged on incrementality. Trigger: any segment 10+ points above its 8-week average → open the search term report for that segment this week, not at month-end.

3. CVR (Unit Session Percentage)

Pull: Business Reports → Detail Page Sales and Traffic by Child Item. Healthy: category-dependent; 10–15% is solid for most physical products, 25%+ common for consumable repeat purchases. Trigger: a hero ASIN down 20%+ versus its own 8-week baseline → check price versus competitors, new negative reviews, lost A+ Content, or a competitor’s coupon before touching ads.

4. Organic vs Paid Revenue Split

Pull: ad-attributed revenue (Advertising console) subtracted from total revenue (Business Reports). Healthy: most mature accounts live near 60/40–70/30 organic-heavy. Trigger: paid share creeping up three consecutive weeks at flat total revenue → you’re renting rank. Cross-reference metric 12 to find where organic position slipped.

5. Buy Box Percentage

Pull: Business Reports → Detail Page Sales and Traffic (Featured Offer percentage column). Healthy: 95%+ on listings where you’re the brand owner; below that means suppression events or another seller on your ASINs. Trigger: any drop below 90% on an owned ASIN → same-day investigation: unauthorized seller, pricing alert, or eligibility issue.

6. IPI

Pull: Inventory → FBA Inventory → Performance tab. Healthy: 500+; Amazon’s capacity-limit threshold has hovered around 400. Trigger: trending down 3+ weeks or under 450 → attack the worst sub-score now (usually excess inventory or stranded units); capacity limits are set quarterly and grovel poorly.

7. Account Health Rating

Pull: Performance → Account Health. Healthy: green, 250+, zero unaddressed violations. Trigger: any new violation, even with a green score → respond within 48 hours. AHR degrades in steps, and the full escalation logic is covered in our account health guide.

8. Review Velocity

Pull: review count per hero ASIN, logged weekly (manually or via Helium 10 review tracking); Voice of the Customer for the leading indicators. Healthy: review count growing roughly in proportion to unit velocity; average rating stable within 0.1 stars. Trigger: two 1-star reviews on one ASIN in a week citing the same defect → pull Voice of the Customer and your latest inspection report — that’s a batch problem, not a review problem.

9. Net Margin per SKU

Pull: Payments reports + SKU Economics for the fee side, your COGS from your own books; Sellerboard automates exactly this. Healthy: 15–25% net after all Amazon fees, ads, COGS, and returns for a sustainable brand. Trigger: any hero SKU down 3+ margin points versus last quarter → run a full profitability analysis on it; fee changes, size-tier drift, and rising return rates hide here for months.

10. Refund Rate

Pull: Reports → Fulfillment → Returns, or FBA Returns report; benchmark against category norms. Healthy: under 3% for most hardgoods; apparel runs structurally higher (10–20%). Trigger: a SKU 2+ points above its own baseline → read the return reason codes that week. “Not as described” is a listing fix; “defective” is a supplier conversation; both are cheaper caught early.

11. Sessions

Pull: Business Reports → Detail Page Sales and Traffic (sessions by ASIN). Healthy: stable-to-growing against the same week’s seasonality-adjusted baseline. Trigger: sessions down 25%+ on a hero ASIN with steady CVR → a visibility event: lost rank, suppressed listing, or a paused campaign. Sessions falling with stable conversion is always a traffic-side diagnosis.

12. Rank on Hero Keywords

Pull: track 5–10 money keywords per hero ASIN in Helium 10 Keyword Tracker or Data Dive; spot-check against Search Query Performance in Brand Analytics. Healthy: page one, position stable or improving on the terms that drive the bulk of revenue. Trigger: a hero term slipping more than 5 positions week-over-week → correlate with metrics 3 and 4; decide deliberately whether to defend with ads while you fix the underlying conversion or content issue.

Suggested Dashboard Layout

One row per week, columns grouped so related metrics sit together. Conditional-format each cell against its trigger threshold — the goal is a dashboard you can read in 90 seconds.

Group	Columns	Source
Money	Revenue, Net margin % (blended), Net margin per hero SKU	Payments + your COGS
Advertising	TACoS, ACoS by SP/SB/SD, Organic/paid split	Ad console + Business Reports
Conversion	Sessions, CVR, Buy Box %	Business Reports
Health	IPI, AHR status, Refund rate, Review velocity	Performance + Fulfillment reports
Visibility	Hero keyword ranks (one column per term)	Helium 10 / Brand Analytics

Below the weekly grid, keep a short “actions” log: date, metric that triggered, action taken, result. Six months of that log is the most honest performance review your account — or your agency — will ever get.

Three build details that separate dashboards people use from dashboards people abandon:

• Track hero ASINs individually, everything else blended. The top 5–10 SKUs that drive 80% of revenue each get their own CVR, sessions, Buy Box, and rank cells. The long tail gets one aggregate row. Per-SKU tracking across a 400-SKU catalog is how dashboards die.
• Baselines beat benchmarks. Every trigger above compares a metric to its own 8-week trailing average, not to an industry number. Your 9% CVR might be excellent or alarming depending on your category and price point; a 20% drop from your own baseline is unambiguous either way.
• Note causes in the cell. Prime Day week, a stockout, a price test — annotate the anomaly when it happens. Un-annotated spikes poison every baseline they touch for the next eight weeks.

What Not to Track Weekly

Discipline about exclusions keeps the dashboard readable. Leave these out of the weekly view:

• BSR. It’s a noisy derivative of sales you’re already tracking directly. Fine for competitor research; useless as a weekly KPI on your own products.
• Impressions. Ad impressions swing with bid changes and mean nothing without CTR and CVR attached — both of which are already represented downstream in your ACoS segments.
• Follower counts, storefront views, brand search volume. Real signals on a quarterly brand review; clutter on a weekly operating dashboard.
• Daily anything. Daily granularity invites reaction to noise. The exceptions are event alerts — AHR violations, Buy Box loss, listing suppression — which shouldn’t wait for Monday but also don’t belong in trend tracking.

The test for any metric that wants onto the dashboard: does it have a trigger with an action attached? If a number can move 20% and nobody would do anything differently, it’s reporting, not a KPI.

The Cadence That Makes It Work

Same operator, same morning, every week: pull the numbers (20 minutes once the template exists), scan for triggered cells, convert each trigger into a task with an owner. Skip the meeting; the dashboard is the meeting. Monthly, zoom out and ask the only strategic question the weekly view can’t answer: is net margin trending the right direction at the current TACoS, or are you buying growth you can’t keep?

If the honest answer is that nobody on the team has time to own this cadence — the pulling, the triggers, the follow-through — that’s not a spreadsheet problem. Running this exact review loop is the core of our full-service Amazon management engagement: same metrics, same triggers, with someone accountable for every red cell.