A Catalog Data Quality Score Your Whole Team Can Rally Around
You cannot fix what you refuse to measure, and most catalogs are measured by vibes.
Ask three people on a brand team how good the catalog is and you get three answers. The category manager says it is fine. The performance lead says it is the reason ads underperform. The founder has not looked in months. Everyone has an opinion and nobody has a number. That gap is where listing debt lives, quietly, for quarters at a time. The fix is not another audit deck that gets read once and forgotten. It is a single score, calculated the same way every week, that the whole team can rally around.
We are not talking about a vanity metric. We mean a catalog data quality score that is decomposable into fixable parts, owned by named people, and tracked over time like any other operating number. Once you have it, vague complaints about the catalog turn into a backlog with line items. That shift, from feeling to figure, is the entire point.
Why listing debt stays invisible
The trouble with a broken catalog is that nothing throws an error. A listing with a blank material field is live. A product with three images instead of seven still ranks, just lower. A size chart that does not match Indian fit still sells, just with more returns. None of this trips an alarm. The dashboard says complete. So the debt compounds in silence, and the only signal you get is a slow, unattributable drag on conversion and discoverability.
We have walked through this in detail before, because so much of the damage hides in fields buyers never consciously read. If you have not seen how backend attributes and image order quietly bleed performance, start with our breakdown of the catalog mistakes that kill conversion. The scoring system in this piece is the operational answer to that diagnosis. It takes the qualitative problems and makes them countable.
A catalog without a score is not a healthy catalog. It is an unmeasured one, which is a very different thing.
What a good score actually measures
A score is only useful if it maps to things a person can change this week. We avoid a single opaque number that nobody can decompose. Instead we build the score from weighted components, each one a concrete dimension of listing health. The weights shift by category, but the skeleton holds across Amazon, Flipkart, Myntra, and the quick-commerce platforms.
- Attribute completeness. What share of the category’s available structured fields are filled and valid. This is the engine of on-platform discovery, so it carries heavy weight.
- Image coverage and sequence. Whether the listing has enough images, in the right order, obeying the platform’s main-image rules. A hero shot plus six supporting frames scores higher than two stray photos.
- Content depth. Title, bullets, and description present, on-spec, and free of the obvious failures like missing keywords or banned characters.
- Variation integrity. Whether parent-child structure is correct so reviews and ranking signals pool instead of fragmenting.
- Compliance and stability. GST and GTIN configured, MRP consistent, inventory signals reliable, no suppression flags.
- Enhanced content presence. A plus content or rich media where the category and margin justify it.
Each listing gets a sub-score per component, and the components roll up into one catalog-level number. The detail is what makes it actionable. A catalog at 72 is not just a 72. It is 94 on content, 51 on attributes, and 60 on images, which tells you exactly where the week’s work goes.
Keep the rubric ruthlessly objective
The fastest way to kill a scoring system is to make it subjective. If two reviewers can look at the same listing and disagree on its score, the number is dead on arrival. So every check must be binary or counted, never judged. Attribute filled or blank. Image present or not. Seven images or four. Resist the urge to score copy quality on a feel-based scale. You can grade whether keywords from your research are present, which is checkable, but not whether the prose is elegant. Note that on-platform keyword logic is its own discipline, distinct from web search, and your scoring rules should reflect that as we argue in our piece on listing keyword research for Indian marketplaces.
From score to assignable backlog
A number on a slide changes nothing. The score earns its keep when it generates a queue of work. The mechanism is simple. Every listing below the threshold on a given component produces a task, and that task has an owner, a fix, and a point value equal to the score it will recover.
This reframes the whole conversation. Instead of a manager saying the catalog needs improvement, the standup says there are forty listings missing the occasion attribute, that is six points of catalog health, and it is assigned to the content team for Thursday. Listing debt becomes a sprint backlog. People can see what they own and what it is worth. The score moving up each week is the proof that the work mattered.
Prioritisation falls out naturally too. You do not fix the catalog alphabetically. You fix the highest-revenue listings with the lowest scores first, because that is where recovered points convert to recovered sales fastest. A cheap, low-traffic SKU at 40 can wait. A hero product at 65 cannot.
How the score connects to revenue
The objection we hear is fair. Is a catalog score just hygiene theatre, or does the number actually move money. The honest answer is that the score is a leading indicator, not a guarantee. A higher score does not promise more sales the way a discount does. What it does is remove the structural reasons a listing cannot convert, which is a precondition for everything downstream.
This is why the catalog score and your conversion work belong on the same table. Once a listing is structurally sound, the real optimisation begins, and that is a different experiment entirely. We are firm that the highest-leverage test is usually the image, not the bullet, which we make the case for in our argument on conversion rate optimisation for listings. The score gets you to the start line. CRO is the race after it.
The connection to revenue becomes legible when you put the score next to outcomes leadership already watches. Track catalog health alongside conversion rate and ad efficiency on the same view, and the correlation tells its own story over a few months. If you are building that view, the principles for a report executives will actually open carry over directly from our take on a marketplace reporting dashboard leadership will read.
Running the score as a habit, not a project
The most common failure is treating the score as a one-time cleanup. The team rallies, the number jumps from 68 to 88 over a month, everyone celebrates, and then it drifts back down. New SKUs launch with half their attributes blank. Platform schema changes add fields nobody fills. Entropy is the default state of a catalog.
So the score has to be a recurring measurement with a standing owner, not a quarterly heroics exercise. The cadence that holds in practice:
- Recalculate the catalog score on a fixed weekly schedule, automatically where the platform data allows.
- Set a non-negotiable launch threshold so no new listing goes live below a minimum score.
- Review the component breakdown in the weekly operating meeting, not a separate catalog meeting nobody attends.
- Convert every gap into an owned task with a point value and a due date.
- Track the trendline, not the snapshot, so you catch drift before it becomes debt again.
What changed recently
Two shifts in the last year make the score harder to treat as optional. The first is on Amazon itself. The platform has moved required attributes from a soft suggestion to an enforced gate, expanding the structured fields you must supply to create or edit a listing and tightening attribute usage and enumeration values across product types in its listing requirement changes. Translation for your rubric: attribute completeness is no longer just a discovery lever you choose to pull. It is increasingly a precondition for the listing existing in valid form at all, which means the weight you put on that component should go up, not down.
The second shift is where the money is moving, and it is the stronger argument for taking catalog quality seriously this year. Quick-commerce platforms have turned into serious ad networks, and a listing that is not structurally complete cannot earn the placements brands are now paying hard for. Zepto’s advertising revenue grew about 151 percent to roughly Rs 1,636 crore in FY26, per figures in its draft prospectus reported by Storyboard18, and a Datum Intelligence estimate cited by Storyboard18 projects Blinkit, Zepto, and Instamart together could pull nearly Rs 4,900 crore in advertising revenue in 2026, with FMCG and impulse brands said to be shifting between 10 and 25 percent of their digital performance budgets onto these platforms. When that much spend rides on a listing, a blank attribute or a missing image is not a hygiene problem. It is wasted media against an incomplete product page. The catalog score is what stops you from buying traffic to a listing that was never ready to convert it. If you are deciding where that spend goes first, our view on quick-commerce unit economics after platform fees is the companion read.
This is the unglamorous discipline behind Catalog & Listing Optimization, and it is deliberately mechanical. The score does not need to be clever. It needs to be consistent, objective, and visible enough that the whole team trusts it. Pair it with steady Marketplace Account Management so the launch threshold actually gets enforced, and with Marketplace SEO so the discoverability gains from a complete catalog show up where buyers search.
The teams that win at marketplace catalogs are not the ones with the most opinions about quality. They are the ones who turned quality into a number, gave the number an owner, and watched it climb. Give your catalog a score this week. The debt you have been ignoring will finally have a name.