Operations

Catalog Audit: Your Listings Are Leaking Money

Catalogs do not break loudly. They decay one suppressed SKU, one dead variation, one stale image at a time, and the revenue leak never shows up as an alert.

Key takeaways
  • Catalogs decay silently through attribute drift, image policy changes, dead variations, and keyword rot; none of it triggers an alert, all of it costs revenue.
  • Run the audit from an export of every SKU across every marketplace, not from memory: suppressed listings, blank attributes, and MRP mismatches hide in the long tail.
  • Assign one owner, run it quarterly on a calendar, and expect two to four working days for a few hundred SKUs across three or four platforms.

Nobody notices catalog decay because nothing announces it. A marketplace tightens an image policy and quietly demotes your listings. An attribute schema changes and your bestseller drops out of a filter it lived in for a year. A variation goes dead after a parent-child restructure and nobody notices until a customer asks why the large size vanished. Each event costs a little. Across three hundred SKUs and four platforms, the leaks compound into a real number that never appears on any dashboard, because dashboards report what sells, not what silently stopped being findable. The fix is not heroics. It is a quarterly audit run like a checklist, the same way every time.

Why catalogs decay

Four forces do most of the damage.

  • Attribute drift. Amazon, Flipkart, Myntra, and Blinkit all revise attribute schemas continuously. Fields get added, renamed, or made mandatory. Listings created under the old schema carry blanks in fields that now power filters and search, and no one tells you.
  • Image policy changes. Background rules, minimum resolutions, model requirements, and pack-shot norms shift. Images that passed at upload can fall out of compliance and trigger suppression or quiet demotion months later.
  • Dead variations. Parent-child restructures, out-of-stock children, and merges leave orphaned or unbuyable variations that split reviews and strand traffic.
  • Keyword rot. Search language moves. Titles and backend keywords tuned eighteen months ago no longer match how buyers phrase queries today, so organic rank erodes without any policy violation at all.

The quarterly audit flow

Run the steps in order. Each produces a defect list; fixes get filed and tracked, not done ad hoc mid-audit.

1. Pull the full picture

Export every SKU from every marketplace: listing reports, inventory reports, and catalog downloads. Then crawl your own listings the way a buyer would, searching your brand and browsing your storefront on each platform. The gap between what your export says exists and what a buyer can actually find is your first defect list.

2. Suppressed and inactive SKUs

Check suppressed, blocked, and inactive listings on each platform. Classify each: policy suppression, missing mandatory field, image violation, pricing error, or stock-driven. Suppressed hero SKUs are the single fastest revenue recovery in the whole audit, so fix these first, before the audit even finishes.

3. Attribute completeness

For each category you sell in, pull the current attribute template and diff it against your live listings. Score every SKU on mandatory and recommended field completeness. Prioritise the attributes that drive filters: size, material, colour, pack size, and category-specific fields. A listing missing a filter attribute is invisible to every buyer who uses that filter.

4. Image compliance

Re-read each platform’s current image policy, then sample-check hero SKUs against it: main image background, resolution, image count, and any category-specific requirements. Flag listings still running launch-era photography. If a batch fails, a single consolidated reshoot brief is cheaper than piecemeal fixes.

5. Price and MRP integrity

Reconcile listing MRP against pack MRP and your master price file for every SKU. Mismatches cause suppression on some platforms and compliance exposure everywhere. While in the price file, flag SKUs whose selling price has drifted below floor through stacked promotions no one remembers enabling.

6. Duplicates and dead variations

Search each platform for duplicate listings of your own products, created by old vendors, resellers, or historical uploads. Duplicates split reviews, confuse rank, and occasionally undercut your price. Then walk every parent-child family and kill or repair orphaned and unbuyable variations.

7. Review-to-rating drift

For each hero SKU, read the last ninety days of reviews, not the star average. The average lags: a product can hold four stars while recent reviews turn sharply negative, and the rating catches up a quarter later, after the damage. Recurring complaints are either a product defect or a listing that sets wrong expectations. Both are fixable this quarter if caught now; this is also where a structured Reviews & Ratings process earns its keep between audits.

8. Search rank spot checks

Pick your ten most important search terms per platform. Record where you rank organically, this quarter versus last. You are not chasing daily movements, you are catching structural slides: a hero SKU that fell from page one to page three signals keyword rot, a suppression event, or a competitor shift worth investigating.

Who owns it and how long it takes

One named owner, usually a catalog or marketplace executive. Committees do not run audits; they schedule meetings about them. For a few hundred SKUs across three or four platforms, budget two to four working days: one to pull and reconcile exports, one to two for the checks, one to file defects with owners and deadlines. Put the audit on the calendar for the first week of each quarter and treat the defect list like a sprint backlog: every item gets an owner, a deadline, and a verification step, because an unverified fix on a marketplace has a habit of not being a fix at all. Agencies running Amazon India Account Management do a version of this monthly for exactly this reason: the work is boring, and it pays better than most advertising.

The leak you fix is the growth you did not have to buy

Every suppressed SKU restored, every attribute filled, every duplicate killed recovers revenue at zero ad spend. That is the quiet argument for the quarterly audit: it is the cheapest growth lever in the operation, and it only works if it runs on a calendar instead of a memory. Book the first week of next quarter now, and run the checklist exactly as written.

FAQ

Quick answers.

Quarterly for the full audit, with a lighter monthly pass on suppressed listings and buyability. Marketplaces change image policies and attribute schemas often enough that an annual audit leaves two or three quarters of silent leakage.
Marketplaces regularly add, rename, or make mandatory new attribute fields. Listings created under the old schema sit with blanks in fields that now drive filters and search, so they quietly disappear from filtered results without ever being flagged to the seller.
For a catalog of a few hundred SKUs across three or four marketplaces, plan two to four working days for one person with clean exports: roughly one day to pull and reconcile data, one to two days for checks, and a day to file and prioritise fixes.
One named person, usually a catalog or marketplace executive. Ownership by committee is how audits get skipped. The owner runs the checklist, files the defects, and tracks fixes to closure; category managers help prioritise.
When a product's recent reviews turn negative faster than its headline star rating falls. The average lags because it carries old positive reviews. Reading the last ninety days of reviews per hero SKU catches product or listing problems a quarter before the rating shows them.

Related insights

From the wire

India's Commerce Engine

Put it
to work.

hello@zane.marketing

Book a meeting