The Listing Quality Dashboard — Amazon's own scorecard.

The Listing Quality Dashboard — Amazon's internal name has shifted between "Manage Your Experiments", "Listing Quality", and "Product Listing Quality" over the years, with "Listing Quality Dashboard" the current and most stable label — is Amazon's own scorecard for each ASIN in your catalogue. It scores attribute completeness, image count, A+ Content presence, video presence, bullet count, description length, variation-family integrity, and a number of hidden factors Amazon does not fully document. Reading the dashboard regularly is the single cheapest catalogue audit you can run, because Amazon is telling you directly which fixes are likely to move conversion before you have to measure it yourself.

Where to find it

• Seller Central: Catalog → Manage All Inventory → right-hand Listing Quality column shows the per-SKU score. The detailed view lives at Brands → Manage Your Brand → Listing Quality Dashboard (Brand Registry required for the full per-attribute breakdown).
• Vendor Central: Items → Catalog Listings → Listing Quality, with per-ASIN breakdown under the same Brand Health section.
• SP-API: the same scoring is exposed programmatically through the Listings Items API and the Brand Analytics endpoints, with one-day latency on the API surface versus near-real-time in the UI.

What the dashboard actually measures

Amazon does not publish a complete weighting table, but the contributing factors observed across thousands of audited dashboards fall into eight buckets:

• Attribute completeness. Every required and recommended category-specific attribute populated with a valid value. The largest single component of the score in most categories — typically 30–40% of the total. Missing attributes Amazon flags include material, dimensions, weight, capacity, age range, target gender, country of origin, and the per-category compliance fields.
• Title quality. Within the category byte limit, matches the Style Guide title formula (brand-first or product-type-first per category), no banned words, no double spaces, no banned symbols.
• Bullet points. All five filled, each within the per-bullet byte limit, no banned words, lead-in capitalisation correct, no duplicate content across bullets.
• Description. Present, non-trivial length (typically 1,000+ characters), no banned words, no off-Amazon URLs, no contact information.
• Images. Main image present and Style Guide-compliant (pure white, 85% fill, 1600+ px on the longest edge — Module 3 Episode 03). Secondary image count meeting the category recommendation (typically 4+, with 6+ for higher scores in most categories).
• A+ Content. A+ document assigned and live, ideally with the canonical 5–7 module structure from Module 3 Episode 08. A+ Premium status counts as additional score points where eligible.
• Video. In-gallery video present, meeting the Style Guide spec (length, format, content rules from Module 3 Episode 05).
• Variation family integrity. For parents in a variation family, all children populated with their variation-theme attribute, no orphan children, every child has its own complete content (main image, bullets, description).

The score itself

Amazon presents the score in two forms simultaneously:

• A 0–100 numeric score per ASIN, with rough quality bands at 90+ (Excellent), 75–89 (Good), 50–74 (Improvement Needed), and below 50 (Poor).
• A traffic-light status (green / yellow / red) on the inventory list view, derived from the same numeric score but easier to scan across the catalogue.

The score is recalculated on every meaningful edit to the listing — usually within minutes of the edit propagating. Score changes back-fill historical trends in the Brand Analytics-linked version of the dashboard, so you can see when a recent change moved the score and by how much.

What to do with the score — sort lowest first, fix from the bottom up

The dashboard's default sort is alphabetical or by date created; the first operational change to make is to sort by score ascending. The catalogue's lowest-scoring SKUs are where almost all the conversion lift lives. The pattern we observe across thousands of audits:

• Fixing a 30-score SKU to 70 typically lifts the SKU's conversion 10–25%.
• Fixing a 70-score SKU to 90 lifts conversion 2–5%.
• Fixing a 90-score SKU to 100 lifts conversion under 1% in most categories.

The implication: stop chasing 100% on already-good ASINs and fix the worst ones first. A catalogue with 50 SKUs averaging 60 is dramatically more profitable to fix than a catalogue with 50 SKUs averaging 88, even though both feel "incomplete" from a perfectionist standpoint. The dashboard's lowest decile is the priority queue for the next quarter's content work.

The per-attribute breakdown — where Amazon tells you the exact fix

Clicking into an individual ASIN's score opens the per-attribute breakdown, which lists every contributing factor with its current state and the change needed. Amazon's prompts are usually specific: "Add 2 more secondary images", "Enable A+ Content", "Title exceeds category byte limit by 12 characters", "Material attribute is missing". Treat the per-attribute list as the work plan; close items top-to-bottom and re-check the score after each batch of fixes.

The hidden factors Amazon doesn't fully document

• Image rendering quality. Pixelation, JPEG compression artefacts, and off-white backgrounds reduce the image-component score even when the main image is present.
• Bullet content quality. Bullets that are too short, too long, all-caps, or that repeat the title verbatim score lower even when the count is correct.
• A+ module density. A+ documents with only 2–3 modules score lower than ones with the canonical 5–7.
• Review velocity and rating. Some reports indicate the dashboard incorporates a customer-experience signal that includes review velocity and rating — meaning the score moves down when reviews stall or when rating drops below ~4.0.
• Search-and-conversion performance. The dashboard's "Compete on Discovery" sub-score (rolling out by region) factors in how the ASIN performs on relevant search queries, not just content completeness.

The Brand Analytics "Compete with X" sub-tool

For Brand-Registered accounts, the dashboard includes a "Compete with" view that benchmarks your ASIN against the top performers in the same category on the same content factors. The benchmarks surface specific gaps — "Top performers have 8 secondary images; this ASIN has 5", "Top performers have an in-gallery video; this ASIN does not". Use this view to prioritise: gaps Amazon flags as below the category median are the highest-leverage fixes.

Common traps when working from the dashboard

• Chasing 100 on the easy ASINs. Covered above. Sort ascending, work the bottom of the list.
• Treating the score as the only signal. Conversion is the real metric. A 95-score SKU with a 4.1-star rating still needs work on reviews; a 60-score SKU might already convert acceptably on a specific niche query. Combine the dashboard with Brand Analytics conversion data, not in isolation.
• Filling attributes with junk to raise the score. Padding bullets with filler content or repeating the title in the description raises the score but degrades conversion. Don't game the score; meet it with quality content.
• Ignoring the per-marketplace view. The dashboard surfaces per-marketplace scores; a high US score does not mean a high DE score on the same ASIN. Pull the dashboard per marketplace.
• Letting score drift after launch. Catalogue scores decay over time as Amazon updates the scoring rubric and as attribute requirements expand. A quarterly re-score is the operational rhythm.

Seller vs Vendor — same dashboard concept, different surface

Sellers access the dashboard through Seller Central and Brand Registry as described. Vendors access it through Vendor Central's Catalog Listings section, with additional Vendor-specific scoring components (packaging completeness, cost data accuracy, shipping-dimension accuracy) layered on top of the shared content scoring. Vendor dashboards also tie into the Customer Experience health score that Vendor Managers use during quarterly business reviews — meaning Vendor listing-quality work has a direct relationship with the commercial terms of the Vendor agreement.

What to take into the next episode

The dashboard tells you what to fix. The next episode covers the nuclear option for SKUs too broken to fix in place — when deleting and recreating an ASIN is the right move, the 60–90 day waiting rule, and exactly what you lose versus keep.