Amazon Sales Analytics for Vendor Central: What Retail Analytics Gives You, and Where It Stops

Your buyer wants to know why a product line slipped last month, or finance wants revenue by ASIN for the quarter, so you search for Amazon sales analytics. Nearly everything that comes back is written for Seller Central: guides built around revenue by SKU, conversion rate, Buy Box percentage, and TACoS, from the point of view of a seller who sets the price and sees every checkout. A vendor's sales data comes out of different reports and follows different rules, so most of that advice doesn't carry over. This guide walks through which sales numbers Vendor Central's Retail Analytics gives you, what the console answers well on its own, and where you'll need exports or a separate tool to keep going.

Why Seller Central Sales Advice Doesn't Fit a Vendor

A seller's sales analytics starts at the storefront. The seller owns the offer, sets the retail price, and every order is the seller's own revenue, so the standard seller metrics all describe one checkout that the seller controls.

A vendor sells wholesale instead: Amazon buys through purchase orders generated by its own demand forecast, sets the retail price, and resells to the shopper as the retailer (our vendor vs seller guide covers the full trade). That's why Vendor Central reports two layers of money, and the first job in any sales analysis is knowing which one you're reading:

• Shipped Revenue is Amazon's retail revenue from the units it shipped to customers, at the prices Amazon sold them for, adjusted for returns.
• Shipped COGS is what Amazon paid you for those same units, adjusted for returns, which makes it the line closest to your own sales.
• Ordered Revenue and Ordered Units count customer orders before shipment, and they appear only in Manufacturing view.

When a report or a slide just says "revenue", find out which of these it means before anyone compares it with another number.

If you came from Seller Central

Two seller habits need translating before they work here. A seller guide treats conversion rate as a number you look up, but on the vendor side the Traffic report counts glance views and the Sales report counts shipped units. The vendor conversion rate is shipped units divided by glance views, so you build it from two reports. Buy Box percentage changes meaning too. For a product Amazon buys from you, the question is whether Amazon's own offer holds the Buy Box or a third-party seller has taken it, and that's what Buy Box share tracks.

Where Retail Analytics' Numbers Come From

Retail Analytics, under Reports in Vendor Central, groups vendor data into seven report families: Sales, Real-Time Sales, Inventory, Traffic, Forecasting, Net PPM, and Catalog. Four of them carry most sales analysis.

• Sales holds ordered and shipped revenue and units, in aggregate and per ASIN, along with Shipped COGS.
• Real-Time Sales reports by the hour at ASIN level, with a 30-day lookback. Use it to see whether a deal or a price change moved units today, then confirm the result in the Sales report once that data lands.
• Net PPM shows Amazon's product-level margin after cost of goods and services, against the prior period and year over year, for the catalog and per ASIN.
• Traffic supplies glance views, the other half of any conversion figure.

Inventory and Forecasting turn into sales questions when a dip turns out to be a stock problem, so check them whenever shipped units fall while glance views hold steady.

The Sales and Inventory reports also carry a distributor view. Sourcing View covers the ASINs Amazon bought from you under your vendor code, while Manufacturing View covers every ASIN carrying your brand, whichever vendor code Amazon bought it through, and is available to the registered brand owner. The Manufacturing vs. Sourcing View entry explains when the two disagree.

What Retail Analytics Answers Well

As long as the question fits inside one report and one date window, the console handles it with no extra tooling.

1. Period over period. Choose a granularity from daily through yearly and compare the range against the one before it, which answers "are we up or down" for the catalog or for a product line.
2. Year over year. Compare against the same range a year earlier. If your business is seasonal, this is the comparison to quote, because a soft November against a strong October tells you very little.
3. ASIN-level focus. Filter a report to a specific set of up to 100 ASINs, so the numbers describe the products under discussion instead of the whole catalog.
4. Margin next to revenue. Net PPM sits in the same Retail Analytics menu as Sales, so you can see how Amazon's margin on a product moved during the weeks its revenue moved. Expect it to read higher than your landed margin, since it leaves out chargebacks, freight, and recovery amounts.

That's enough for a weekly read on a defined set of products, and our Retail Analytics walkthrough shows where each of these controls sits.

Where It Stops

The limits show up once a question needs more than one report or more than one sitting.

Latency. Amazon's service level for weekly reporting periods is the end of the day on Monday, 48 hours after the period closes, and 72 hours after close for daily periods. A Monday morning review is looking at a week that hasn't landed yet, so the numbers on the screen are incomplete.

No join across reports. Each report downloads on its own, but most sales questions need two of them: conversion needs Sales and Traffic, explaining a dip needs Sales and Inventory, and a margin conversation needs Sales and Net PPM. Each pairing means exporting both reports for the same range, view, and ASIN set and matching the rows by ASIN in a spreadsheet.

Short history. Every report has its own lookback window, from 30 days for Real-Time Sales up to three years for annual Sales and Traffic data. Anything older is gone from the console unless you exported it while it was still there, and our report definitions guide lists the span for each report.

Nothing saved. The console keeps none of your setup between visits, so a recurring weekly read starts from a blank report every time.

What Closing the Gap Takes

There are two practical ways past those limits.

A manual export routine. Each week, pull Sales, Traffic, Inventory, and Net PPM for the same range, distributor view, and ASIN list. Name the files with those settings, archive them in one dated folder so the history survives the console's lookback, and join them by ASIN with XLOOKUP or Power Query. Our guides to exporting Vendor Central reports and combining them by ASIN cover both halves. This works for a small catalog, as long as someone owns the routine every week and never skips an export. If you have engineering time, you can automate the pulls through the Selling Partner API instead.

A layer that keeps the data for you. InsightLeap connects to Vendor Central, Amazon Advertising, and Amazon.com and pulls product-level sales, inventory, traffic, returns, and open PO units on a schedule. It keeps historic Vendor Central reports past the window Amazon's interface shows, reports Net PPM per product next to contra COGS and sales discounts, and flags ASINs that sit under 40% Net PPM for four straight weeks. When someone asks why a product slipped, the sales, traffic, and margin rows for it are already side by side.

Where to Start This Week

Whichever route you take, start with one clean baseline, because every later comparison depends on it:

1. Pick the revenue line you'll report. Use Shipped COGS when the question is what Amazon paid you, and Shipped Revenue when the question is how your products sold at retail. Label it on every sheet.
2. Wait until Tuesday to pull last week, so the weekly data has landed.
3. Pull the Sales report by week for the last 13 weeks with a year-over-year comparison, filtered to the ASINs that matter most, and note the distributor view.
4. Pull Traffic for the same weeks and ASINs, then divide shipped units by glance views for each product.
5. Pull Net PPM for the same weeks and mark any ASIN whose margin fell while its revenue held.
6. Save all three exports in one dated folder and keep it, because the console's history will expire before you need it.

You'll end up with revenue, conversion, and margin for the same products over the same weeks, and each week after that you only add one new row per ASIN.