Every listing scored, with the exact fix.

Open Quality Score and your whole catalog is ranked 0 to 100, with a separate score for title, bullets, description, images, backend keywords and Sponsored Products coverage. Filter to the listings that need work or score poorly, the ones missing a description, or the ones running no ads, and each filter tells you how many before you click. Open a SKU, edit the copy, and watch the score move as you type before you push the change to Amazon.

  • Six named parameters per SKU, each with plain-English reasons like “Title is shorter than the recommended length” rather than a bare number.
  • Averages follow your filter, not the page, so the ring and the six tiles always describe the slice of the catalog you selected.
  • Edits re-score live as you type and then go to Amazon over SP-API. If Amazon rejects the change, you see its exact message and nothing is saved.

Illustration with sample data

Listing quality score

A weak listing never tells you it is weak. It just converts less.

There is no Amazon report for “this copy is costing you sales”. So Sellerbud measures the six things that are measurable — title, bullets, description, A+ content, backend keywords and Sponsored Products coverage — and turns them into one number per SKU, a reason for every point lost, and an editor that pushes the fix back to Amazon.

01 / 05The average, part by part

Listing quality128 scored SKUs
All
Title54
Bullets72
Description39
A+42
Keywords49
SP Ads48
52.3
average scoreover 128 SKUs

Illustration with sample data

  1. The average follows your filter, not your page

    Six pills sit above the table, and each one runs its own count first, so the badge tells you how big the problem is before you click it. Click one and the averages recompute over the entire slice, not the 20 rows in front of you.

    Press to tryAverage over

  2. Seven numbers per SKU, every one of them a sort

    Each row carries the total plus its six parts, colour-banded on the same two cuts everywhere. Every column sorts, so “show me the worst listings I own” is a click on Score, not an export and a spreadsheet.

  3. Named reasons, never a bare number

    A score you cannot act on is a scold. So every point lost is attributed, with a red dot where the parameter scored zero. The sentences are plain, such as “Description is missing”, and they come from stable codes the engine emits.

  4. Edit the copy and watch the score move

    Type, and 300 milliseconds later the whole draft is scored again in memory. Here is the same listing : the total moves and every section’s bar redraws. Nothing is written anywhere on that path. It is a preview.

  5. Push it to Amazon, or find out why not

    One button sends the title, bullets, description and backend keywords to Amazon as a listings patch. A rejection dressed up as a success is still treated as a failure, and Amazon’s own message is put on screen unedited.

Worked example

Fix the worst one first.

One listing, one sitting, three screens. Illustrative figures — the arithmetic is the product’s rubric, the listing is an example.

Cotton Double Bedsheet Set with 2 Pillow Covers, KingSB-HM-2210 · B09YV3T8KD53 characters of title · 3 bullet points · no description · no A+ content · 96 of 250 keyword bytes
01

Find it

The catalogue averages 52 out of 100, which says nothing about any one listing. One pill does: Poor already knows how many there are before you press it.

SKUs in the marketplace
128
Scoring Poor (under 50)
41
Catalogue average
52
Worst rated listing31.6
02

Read why

Six parameters, and three of them sit at zero because nobody checks them: there is no description at all, no A+ content names the product, and no Sponsored Products ad is running against it.

Description
0
A+
0
SP Ads
0
Keywords
38
Editable on this screen3 of 6
03

Fix and push

A description written, the bullets brought up to five in range, the keyword field filled to the budget — scored live as you type, then patched to Amazon in one action.

Description
0 → 100
Bullets
70 → 100
Keywords
38 → 100
New score58.8 (+27.2)

That is one listing, out of the 41 the Poor pill counted, in the time it takes to write a paragraph — and it is not finished. The title is still shorter than the rubric wants, no A+ content names the product and no ad is running, and the score says all three out loud instead of settling for 58.8 and calling it done.

FAQ

The questions sellers actually ask.

What exactly does the score weigh?

Six parameters, with published weights that add up to 100: title 25, bullets 20, description 15, A+ content 15, Sponsored Products ads 15 and backend keywords 10. The thresholds are just as concrete: full marks for a title between 80 and 200 characters, 5 bullet points of 80 to 250 characters each, a description of 1,500 characters or more, a live A+ document naming the product (a yes/no, so all or nothing), and a backend keyword field using most of its 250-byte budget. Images are not scored: the editor shows the gallery Amazon displays, read-only. The total is the weighted average of the six, to one decimal place; when A+ cannot apply to a product (a reseller's listing, or a store whose A+ cannot be read yet) its weight leaves the average instead of counting as zero. The rubric itself is one versioned document maintained by Sellerbud, and each stored score records the version of the rubric that produced it.

Is this an AI grader? Will it tell me my copy is bad?

No, and that is deliberate. Every one of the six scorers measures a length, a count, a byte total or a yes/no — characters in the title, bullets in range, characters of description, whether a live A+ document names the product, bytes of backend keywords, whether an enabled Sponsored Products ad exists. Nothing here judges keyword relevance, readability or whether the copy is any good, and there is no “generate” button. What it is good at is the part sellers genuinely lose track of across a few hundred SKUs: which listings are structurally incomplete, and by how much.

How often does it refresh?

Scoring is a step in each store's refresh, not a per-SKU job you have to trigger. One aggregation pass scores every SKU in the marketplace and a second rolls the results up into the per-marketplace averages and issue counts that feed your dashboard card, so stored scores update whenever the store refreshes. Two paths are immediate rather than scheduled: the live preview while you are editing, which runs on demand and stores nothing, and a save through the editor, which updates that SKU's stored score once Amazon confirms the change. Everything is idempotent — re-running recomputes from current state. When Sellerbud changes the rubric, a store's scores follow it at that store's next refresh, not before.

Do I have to leave Sellerbud to fix a listing?

Not for the copy. Title, bullet points, description and backend search keywords are edited here and pushed to Amazon over SP-API in one action, and Sellerbud updates its own record only once Amazon has accepted the submission — if Amazon objects, you get its exact message and nothing is saved. Three things are shown but not edited in the copy editor: images, which are managed on Amazon; A+ content, which has its own designer and a button to open it; and Sponsored Products, which live in the Ads console. Sellerbud reads A+ and ads at each store refresh, so a change to either shows up in the score at the next one.

How big can my catalogue be?

The filtering, sorting and averaging are done in the database rather than by walking your SKUs one at a time — an early version issued a lookup per SKU and slowed down linearly with catalogue size, which is why the current one splits the work and hydrates only the page you are looking at. Two honest details about the list itself: it pages at 20 rows, and the search box matches SKU, ASIN or title across the whole marketplace, not just the page in front of you — and it stacks with the pills.

Is there a history of my score?

No. The scores you see are current values, replaced in place on every refresh — there is no trend line, no score-over-time chart and no before/after archive, and the page does not pretend otherwise. While you are editing you do get the immediate comparison that matters: the live total against the last saved one, and the difference between them.

Which plan includes this?

Analytics. Everything on this page — the scored list and its filters, the six parameters and the reasons behind them, the live preview, and pushing a change to Amazon — is part of that product, which is paid and billed per marketplace. Scoring only runs for marketplaces that hold it, so a marketplace without Analytics is not scored at all. Scoring, previews and saves are not metered per use, and nothing here is India-only — the score is country-agnostic and works on any connected marketplace.

Know your numbers. Grow your store.

Connect your first marketplace in about two minutes, pick the plan that fits your store — and move up when the numbers earn it.

We use cookies for analytics, to improve Sellerbud, and for marketing, to measure our ads and the links we send. If you say no, we keep only what this visit needs. Privacy policy