How to Audit Catalog and Content Changes on Vendor Central

Someone asks whether anything changed on your listings this month, and Vendor Central has no screen that answers it. You can open a detail page and read it, and you can pull a report that shows the catalog as it stands today, but nothing in the console tells you what a field said last month. On a catalog of a few dozen ASINs you can get by opening pages. Once the catalog runs into the hundreds, a bullet overwritten three weeks ago or an item Amazon quietly stopped reordering sits there until the sales line bends far enough for someone to go looking.

The routine below closes that gap with a file you already have access to. Once a month, export the Vendor Catalog Listing report, keep the file, and compare it against last month's export, ASIN by ASIN. The comparison shows every row that moved across the whole catalog in one pass, and it tells you which ASINs deserve a closer look this month.

Why Single-ASIN Checks Don't Scale

The ASIN-level audit checklist walks one product through every field, offer condition, and vendor-side record that belongs to it. It's the right tool when you already know which ASIN is in trouble, and it's slow on purpose, because most of what it checks lives in fields nobody opens after a listing goes live.

It breaks down on volume, though. A careful pass on one ASIN multiplied across the whole catalog is more hours than any team spends on content, so in practice the checklist gets run on the top sellers and the rest of the catalog goes unread until something on it goes wrong.

A report diff works the other way around. You handle one file per month that covers every ASIN at once, and the only question you ask of it is what's different from last time. It won't replace the single-ASIN checklist, but it tells you which ASINs to run it on.

Pull the Vendor Catalog Listing Report

The Vendor Catalog Listing report lists the items in your catalog with the replenishment code Amazon holds for each one and the inventory position. It's the report behind the Out of Stock Items metric, which you read by sorting the report by inventory and filtering the replenishment code to Planned Replenishment (PR) and New Product (NP). That puts Amazon's own ordering status for every ASIN in a single file, which is why the monthly diff starts here.

Menu placement for the report can differ by account and region, so find it by its name and confirm the path on your own screen before you write it into a process. Then pull it the same way every month:

1. Open the Vendor Catalog Listing report.
2. Leave every filter off, so the file holds the full catalog and no ASIN is left out of the comparison by a setting you forgot you'd changed.
3. Export the report to a file.
4. Open the file and match its headers to what each column holds. Amazon names columns its own way and can rename them, so write a short key of the header names next to the file: the ASIN, the replenishment code, the inventory figure, and whichever content fields your export carries on your account.
5. Check the key against every new export before you compare anything, so a renamed column is caught on the day it changes.

What content fields come down in the file is worth settling on the first pull. If your export carries title and bullet text, the diff can compare them directly. If it doesn't, the replenishment code, inventory, and row-level changes still carry the routine, and the content check moves to the detail-page pass described below. The general export mechanics, including where to look when a large file doesn't drop straight into your browser, are covered in how to export Vendor Central reports.

If You Came From Seller Central

Replenishment codes have no counterpart on the seller side. On Vendor Central, Amazon buys your units on a purchase order and resells them under its own name, so the code is Amazon's record of whether it plans to keep ordering an item. A code change is Amazon changing its buying plan, and it happens on Amazon's side of the account without any action from you. If you're still mapping the rest of your old reporting across, see where your Seller Central reports went.

Set Up the Diff

The comparison runs in a spreadsheet, keyed on ASIN.

1. Name each export for the day you pulled it, for example vendor-catalog-listing_pulled-2026-09-30.csv, and never edit the original. Do the work in a copy.
2. Put last month's file and this month's file into one workbook, one sheet each.
3. On this month's sheet, pull each of last month's values onto the matching row with XLOOKUP on the ASIN. Combining Vendor Central reports by ASIN walks through the lookup if you haven't built one.
4. Add a flag column for each field you compare, set to TRUE when this month's value differs from last month's. Wrap text fields in TRIM first, so a stray space doesn't flood the list with changes nobody made.
5. Build two row-level lists as well: ASINs in this month's file that weren't in last month's, and ASINs in last month's file that have dropped out of this one. An XLOOKUP that returns nothing finds both.

Then filter on the flags and read the changes by type.

Title and Bullet Changes

Where the file carries content text, any flagged title or bullet is a change to check against your own record of what you published. Content can be overwritten without anyone telling you, so keep a master sheet of approved copy per ASIN and compare the flagged rows against it, so you can tell a change your team made from one it didn't.

A change you didn't make goes on this month's fix list with the old text and the new text side by side. That pair is also what you'll need if the edit has to be reversed through Amazon.

Images and A+ Content

A text export can't show you what an image looks like. If your file carries image references, a changed value tells you something moved and nothing about whether the new image is compliant. If it carries none, the diff is silent on images and on A+ Content.

Those checks stay on the detail page, and the diff decides which pages you open first: any ASIN with a flagged title or bullet, any ASIN new to the file, and your top sellers, then work the listing-side items from the ASIN-level checklist on that short list.

Broken Variations

A broken variation is a child ASIN that has come loose from its parent, either orphaned or attached to the wrong parent. If your file carries a parent ASIN column, flag every child whose parent value changed or went blank between exports. Then count children per parent in each month with COUNTIF, and any parent whose count dropped has lost a child somewhere.

If the file has no parent column, the row-level lists are your signal. A child that dropped out of the file or a new ASIN that looks like an existing product both deserve a look at the family on the detail page.

Replenishment Code Changes

Flag every ASIN whose code differs from last month, and pay the most attention to anything that moved off PR. The Out of Stock Items metric lists only out-of-stock items coded PR or NP, so an ASIN that moves to any other code drops out of that list. Your out-of-stock read gets shorter without anything coming back in stock, and the code no longer marks the item as one Amazon plans to keep replenishing.

Keep a separate note of the ASINs coded NP so next month's diff shows which ones moved to PR and which moved somewhere else. For every ASIN that left PR without a reason you know about, take the ASIN list with both codes to your Amazon contact or a support case the same week. Read the change alongside Out of Stock & Replenishable for the same ASINs, since that metric counts the glance views that arrived while a replenishable item had nothing to sell.

The Monthly Checklist

1. Export the Vendor Catalog Listing report with no filters on the same day each month.
2. Name the file with the pull date and save the untouched original.
3. Check the headers against your key and update the key if a column was renamed.
4. Load last month's and this month's files into one workbook and match rows on ASIN.
5. Flag changed values in every field you compare, with text trimmed first.
6. List the ASINs that are new to the file and the ones that dropped out.
7. Check flagged titles and bullets against your approved copy.
8. Flag children whose parent changed and parents whose child count dropped.
9. List every replenishment code change, and act on each move off PR.
10. Open the detail pages for flagged ASINs and top sellers, and run the image and A+ checks there.
11. File the results sheet next to the export, so next month starts from a clean comparison.

What the Diff Catches, and What It Misses

The diff reads the entire catalog in one pass, including the long tail nobody opens, and it catches changes nobody told you about, most importantly replenishment code moves that happen on Amazon's side of the account. It also leaves a record, so after a few months the folder of exports and results sheets shows which ASINs keep getting edited and which codes keep moving.

It has limits you should plan around. A month is a long window, and a bullet that was overwritten and restored between two pulls never shows up. Anything outside the file's columns is invisible to it, including images, A+ Content, price, and who holds the Buy Box. And when it does catch a change, you only know that it happened at some point in the last month, which makes it hard to line up against a drop in sales.

The detail-page checklist covers those gaps because it sees the rendered page and every offer condition, but only on the ASINs you open. Run the diff across the whole catalog each month and point the checklist at whatever it flags.

What Vendor Central Will Not Give You

The Vendor Catalog Listing report gets you the catalog as it stands on the day you pull it. Three things are left to you.

• A change log. Nothing in the file says what a field read last month, so the only comparison point is the export you kept.
• The comparison itself. Every lookup, flag, and parent count above is a spreadsheet you build and maintain.
• The monthly repeat, and its delay. A change that lands the day after your pull waits most of a month to be found.

InsightLeap does this step continuously. Its Notifications and Audit Alerts send daily email notifications for content changes, broken variations, and replenishment code changes as they occur, so a change reaches you in the next day's email instead of next month's diff. Navitas Organics automated its product content audits this way, and Travis May, Director of Sales - Online & Canada, described the result: "For automating our product content audits alone it has saved us more than 50% of our time a month...where our team was spending 20 hours a month we are now only spending 2 hours." Their story has the detail, and the features page covers the full set of alerts.

Where to Start This Month

Pull the Vendor Catalog Listing report today with no filters, name it with the pull date, and write the header key. You can't diff until next month, but the first file already answers one question: filter the replenishment code to anything other than PR and NP, and check that list against the items you expect Amazon to keep ordering. Then put the same pull on the calendar for the same day next month, and run the first comparison when that file comes in.