Ecommerce Reporting for Amazon Vendors: What to Pull, How Often, and Who Owns It

What "ecommerce reporting" means for an Amazon vendor

Someone asks for "the weekly ecommerce report." On a business that runs its own storefront, that request is simple, because everything comes out of one platform and usually one export. On a Vendor Central account it turns into a morning of downloads, because the numbers live in separate places that were never built to agree with each other.

For a vendor, ecommerce reporting draws on three sources:

• Vendor Central. Its analytics come from two separate systems. Retail Analytics covers your first-party business with Amazon: what was ordered and shipped, traffic, inventory, margin, and the demand forecast. Brand Analytics covers shopper search and purchase behavior, and it requires Brand Registry.
• Seller Central, if you run a hybrid account. The third-party half of the business keeps its own reports, with its own sales, traffic, buy box percentage, FBA inventory, fees, and net proceeds.
• Amazon Advertising. Sponsored Products, Sponsored Brands, and Sponsored Display report spend, sales, ACOS, ROAS, and search terms in a data source of their own.

None of these reconcile automatically. Even inside Vendor Central, Retail Analytics and Brand Analytics answer different questions and sit behind different access rules, so a figure from one won't line up with a figure from the other on its own. For a vendor, then, ecommerce reporting means pulling each source on a known schedule, in a known configuration, and lining the results up by ASIN so somebody can act on them.

The Vendor Central reports a routine depends on

Retail Analytics groups its reports by the question each one answers, so a reporting routine starts from the question and opens the report built for it. Our Vendor Central report definitions guide covers every report field by field. Here's what each group is for when you're pulling it on a schedule.

Sales and traffic. Sales Diagnostic reports shipped cost of goods at ASIN level on a daily basis. Traffic Diagnostic reads glance views and conversion against industry benchmarks, which is how you tell a traffic problem from a conversion problem when sales move. Real-Time Sales and Real-Time Traffic report the same territory by hour, with a 30-day lookback. Every vendor analytics report runs on Pacific time, so if you compare daily figures against a system that runs on local time, the two will be off by a few hours of orders.

Inventory and forecasting. Inventory Health tracks stock position on a weekly update cycle, covering on-hand inventory, sell-through, and lead time adherence, and its data lands 72 hours after the period closes. Forecast and Inventory Planning shows four forecast types (Mean, P70, P80, and P90), and Amazon keeps only the most recent one. Net PPM (Net Pure Product Margin) is where margin lives, with weekly figures available 48 hours after the period closes; the Net PPM glossary entry has the definition.

Operations and promotions. Operational Performance carries shipment and fulfillment quality metrics along with the chargebacks attached to them. Promotions Performance shows what deals, coupons, and Lightning Deals cost, and Sourcing Performance covers purchase order fill rates. Amazon documents no programmatic export for any of those three, so plan on reading or downloading them by hand. Geographic Sales sits alongside them and breaks sales down by state, city, and ZIP code.

Brand Analytics. Search Catalog Performance, Search Query Performance, Market Basket, Search Terms, and Repeat Purchase all sit here, behind Brand Registry. If your brand isn't enrolled, they won't show up in the account at all, so confirm access before you promise anyone a search-term analysis.

Advertising. Ad spend and ad-driven sales come from Amazon Advertising, separately from Retail Analytics. Our guide to Amazon advertising reporting covers that side.

Why generic ecommerce reporting advice falls short on Amazon

The guides that rank for this topic, Shopify's among them, organize reporting around sales and revenue, conversion and checkout, customers, marketing and acquisition, product and inventory, and returns. That list assumes you run the storefront and the checkout. On Vendor Central, Amazon holds the stock and writes the purchase orders off its own forecast, so several of those categories either look different or have no counterpart at all.

Conversion is the clearest case. Sessions don't exist in Vendor Central, so unit session percentage, the conversion rate a Seller Central or storefront report is built on, doesn't exist either. Glance views are the traffic measure, and Amazon has begun renaming them featured offer page views, so you may see either label. Traffic Diagnostic does read conversion against benchmarks, but any "conversion rate" line on a vendor report needs its definition written next to it, or someone will compare it with a sessions-based figure from another channel.

Buy Box percentage has no Vendor Central equivalent. The nearest proxy, "LBB due to price rate," only counts losses caused by price and is being phased out, and a successor, Lost Featured Offer %, has begun appearing for some accounts. The Lost Buy Box Due to Price glossary entry has the details.

Customer reporting moves to Brand Analytics, where Market Basket and Repeat Purchase describe what shoppers buy alongside your items and whether they come back. Margin moves to Net PPM, which leaves out chargebacks, freight costs, and recovery amounts. In any period where deductions are running against you, Net PPM will look better than your landed margin, so your own deduction and freight records have to fill in the gap.

If you came from Seller Central, our map of where your reports went walks through each habit one by one: Business Reports, page views, inventory, payments, and search terms.

Building a daily, weekly, and monthly reporting cadence

Each report has its own refresh timing and its own lookback window, so the cadence has to follow the data. If you split the work into daily, weekly, and monthly passes and give each one a named owner, the pulls stay small and a missed period is easy to spot.

Daily triage, owned by whoever runs the account day to day.

1. Check Real-Time Sales for ASINs whose ordered units dropped or spiked. Negative unit values are cancellations, so an individual hour can read below zero.
2. Check Real-Time Inventory for availability. It reflects orders, cancellations, and add-to-cart activity as they land.
3. Treat yesterday's daily figures as provisional, because daily data populates on a rolling basis and the most recent days are still settling.
4. Save anything you'll want later. Hourly history older than 30 days stops being requestable, so a stockout you want to study next spring has to be captured this month.

Weekly reconciliation, owned by the analyst or operations lead.

1. Pull Sales, Inventory, and Traffic at weekly granularity, over the same weeks, in the same distributor view where the setting exists. Vendor Central weeks run Sunday through Saturday.
2. Schedule the pull for after the inventory data lands, 72 hours after the period closes.
3. Join the three files on ASIN and add the cross-report columns, such as Weeks of Coverage. The mechanics, including the distributor view and granularity mismatches that break the join, are in how to combine Vendor Central reports by ASIN.
4. Export the purchase order list from Orders, then Purchase Orders, then Manage POs, so you can read shipped units against what was on order. That data sits outside Retail Analytics.
5. Save the week's forecast file. Amazon keeps only the most recent forecast, so a week nobody saved can't be pulled again later.
6. Pull the week's Net PPM once it lands, 48 hours after the period closes.

Monthly review, owned by whoever reports to leadership.

1. Trend Net PPM by ASIN and flag the products pulling margin down. How to find and track Net PPM covers reading it one ASIN at a time.
2. Compare the saved weekly forecasts against what actually shipped.
3. Read Operational Performance for chargeback categories and Promotions Performance for what the month's deals cost.
4. Pull monthly exports once the month closes, since only complete calendar months come down.

Write down the exact settings for each recurring pull (report, distributor view, granularity, columns showing) and put them in every file name. The export itself doesn't record any of those choices, so six months from now the file name is the only way to know what you pulled. How to export Vendor Central reports lays out a naming convention built on report type, view, granularity, and date range that you can copy.

What Vendor Central will not give you

Four gaps sit underneath any vendor reporting routine, and none of them can be fixed inside the console:

• The join. Every report is its own download, on its own range, in its own view. Putting Sales, Inventory, and Traffic side by side is your work, repeated in full every period.
• History. A single export spans roughly two years, and history further back than roughly three years can't be retrieved through the interface. Hourly reports reach back 30 days, and Amazon keeps only the most recent forecast.
• Cross-channel reconciliation. Vendor Central, Seller Central, and Amazon Advertising report separately, so a hybrid vendor's total Amazon picture exists only after someone assembles it.
• The repeat. Each week the files have to be pulled again with the same settings, checked for distributor view and granularity, and rejoined.

InsightLeap does that assembly continuously. It ingests Vendor Central, Seller Central, Amazon Advertising, and Amazon.com data across your brands and products, keeps historic Vendor Central reports past what Amazon's interface will show, and generates reports automatically to share with your team. The features page lists what it tracks.

Pick the cadence before you pick a tool

Before you evaluate any reporting tool, write down the three passes above, the reports in each, the settings for each pull, and the person who owns it. That list tells you what a tool has to cover and which manual steps it would take off your team's plate. Then start saving the weekly forecast and the weekly Sales, Inventory, and Traffic exports this week. Amazon overwrites the forecast and drops hourly data after 30 days, so the sooner you start keeping your own copies, the more history you'll have when someone asks how this quarter compares with last year.