Amazon Business Reports: Find Your Conversion Bottleneck for Free
Seller Central’s free Business Reports already tell you which step of your funnel is broken — you just have to read three columns in order. Sessions says whether shoppers reached the page. Buy Box Percentage says whether your offer was buyable when they got there. Unit Session Percentage says whether the page persuaded them. Whichever of the three moved is the step that broke; the other two are downstream noise. This guide walks the Sales Dashboard and the Detail Page Sales and Traffic report field by field, then ends with a table of the signals that mean the free reports are enough — and the signals that mean it is time to pay.
Every metric definition quoted below is Amazon’s own wording, taken from the public Selling Partner API schema for the seller Sales and Traffic report (schemas/reports/sellerSalesAndTrafficReport.json in Amazon’s amzn/selling-partner-api-models repository), which describes the same dataset that powers Business Reports. Most are quoted from the schema’s by-ASIN object; the two rows marked † come from its by-date object, the same report aggregated by day. Definitions checked 2026-09-04.
Where the free Business Reports live
Amazon’s own instruction, from a moderator post in Seller Forums, is: “Click the menu icon (top-left of Seller Central) > Reports > Business Reports”. Amazon’s public seller site gives the same route in different words — select Reports from the Seller Central main menu, then select Business Reports.
The same post lists what is in there: the Sales Dashboard (“Quick overview of your key sales metrics”, “Compare data with previous day, week and year”), Detail Page Sales and Traffic (“Track individual product performance and variations”, “Customisable date ranges (default: 1 month)”), the Sales and Traffic Report, and the Seller Performance Report. None costs anything or needs an app authorisation.
Two of the four carry the whole diagnosis. The Sales Dashboard tells you whether something changed. Detail Page Sales and Traffic tells you where.
The Sales Dashboard: what it answers, and what it can’t
The Sales Dashboard is a comparison instrument, not an analysis instrument. It answers one question — did the account-level number move, against which baseline? Because it compares the previous day, week and year, it is the right place to separate “a real drop” from “Tuesday”.
What it cannot do is attribute. Account-level Ordered Product Sales falling 20% is equally consistent with one hero ASIN going out of stock, a seasonal dip, or a price cut that raised conversion and lowered average selling price. The dashboard cannot separate those.
So use it as a tripwire with a strict rule: the dashboard sets the date range, the Detail Page report finds the cause. Note the exact window in which the number moved and carry that window into the per-ASIN report. Diagnosing at the account level, where every product’s noise is summed together, is how sellers burn an afternoon.
Detail Page Sales and Traffic, field by field
This is the report that earns its keep. It is available by parent ASIN, child ASIN and SKU, and by date. Here is what each column means, in Amazon’s words.
| Column | Amazon’s definition | What it really tells you |
|---|---|---|
| Sessions | “Sessions are visits to your Amazon.com pages using mobile app or browser by any user. All activity within a 24-hour period is considered a session.” | Demand that reached the page. One shopper visiting five times in a day is one session. |
| Session Percentage | “The percentage of sessions that contain at least one page view for a particular SKU/ASIN relative to the total number of sessions for all products.” | Share of your own catalogue’s traffic, not market share. |
| Page Views | “Page views are the number of times any user visited your Amazon.com pages using browser or mobile app for the selected time period.” | Raw visit count. Page Views ÷ Sessions = average revisits per day. |
| Page Views Percentage | “The percentage of page views that a particular SKU/ASIN receives relative to the total number of page views for all products.” | Again your own catalogue, not the category. |
| Buy Box Percentage | “The percentage of page views where the buy box (the add to shopping cart link) appeared on the page for customers to add your product to their cart.” | Note the denominator: page views, not sessions or orders. |
| Units Ordered † | “The number of units ordered for the selected time period.” | Units, not orders. |
| Total Order Items | “The number of items that were ordered for the selected time period.” | Distinct line items, not units. |
| Unit Session Percentage | “The percentage conversion metric indicating how many units were purchased relative to the number of people who viewed the products, calculated by dividing unitsOrdered by sessions.” | Conversion rate, unit-based, so multi-unit orders push it up. |
| Ordered Product Sales | “The amount of ordered product sales, calculated by multiplying the price of products and the number of units sold for the selected time period.” | Revenue at order time, before returns. |
| Average Selling Price † | “The average price of the units sold in the selected time period, calculated by dividing the orderedProductSales by unitsOrdered for the selected time period.” | Reconciles flat units with falling revenue. |
† Quoted from the by-date object (SalesByDate). averageSellingPrice exists only there; the by-ASIN object carries unitsOrdered and orderedProductSales, whose ratio is the same number.
Three of those definitions are misread constantly, and each misreading sends people down a wrong path:
Session Percentage is internal, not competitive. Amazon’s denominator is “the total number of sessions for all products” — your products. Launch three new ASINs and every existing ASIN’s Session Percentage falls while its own Sessions stay flat. Judge an ASIN on Sessions; use Session Percentage only to see how attention is distributed inside your catalogue.
Buy Box Percentage is measured against page views. A 60% figure means the featured-offer block showed your offer on 60% of the page views the listing received — not that you won 60% of a head-to-head contest. It drops for reasons no competitor caused: an out-of-stock offer, a suppressed listing, a price Amazon will not feature. Our guide to how the Amazon Buy Box works covers the eligibility mechanics behind the number.
Unit Session Percentage counts units, not buyers. Amazon’s own illustration: “An order containing 2 copies of book A and 3 copies of book B; The number of orders is 1, the number of order items is 2 (book A and book B), and the number of units is 5 (2 + 3).” A multipack or a quantity break therefore raises Unit Session Percentage without one extra shopper converting. The buyer-side alternative is Amazon’s order-item conversion metric, “how many order items were generated relative to the number of people who viewed the products”.
The four-step funnel: locating the bottleneck
Read the columns in this order. The first abnormal one is your bottleneck; every column after it is a symptom, not a cause.
- Sessions — did people arrive?
- Buy Box Percentage — was there a buyable offer when they arrived?
- Unit Session Percentage — did the page convince them?
- Average Selling Price — did each conversion carry the revenue it used to?
The chain multiplies back to revenue: Sessions × Unit Session Percentage = Units Ordered, and Units Ordered × Average Selling Price = Ordered Product Sales. That identity is why the order matters — a traffic drop and a conversion collapse can produce identical revenue loss while needing opposite fixes.
| What the columns show | Bottleneck | Where to look next |
|---|---|---|
| Sessions down, Buy Box % and Unit Session % flat | Traffic acquisition | Ad spend and placements, keyword coverage, whether the listing is still indexed — start with a PPC audit |
| Sessions flat, Buy Box % down, Unit Session % down | Offer availability | Price, stock, a hijacked listing, a suppressed listing, or stranded inventory |
| Sessions and Buy Box % flat, Unit Session % down | Detail page persuasion | Images, title, A+ content, price against comparable offers, new negative reviews — see listing optimization |
| Sessions up, Unit Session % down, Units Ordered flat | Traffic quality | New keywords or placements pulling in shoppers with the wrong intent; check search-term reports and ACoS |
| Everything flat, Ordered Product Sales down | Price or mix | Average Selling Price, a coupon or deal that ran, or a shift toward a cheaper child ASIN |
| Session Percentage down, Sessions flat | Nothing is broken | Your catalogue grew; this ASIN’s share fell without its traffic falling |
The bottom row is worth memorising: it is the report’s most frequent false alarm, caused entirely by reading a share metric as a performance metric.
A worked read
Take an ASIN whose Ordered Product Sales fell by roughly a third month over month. The arithmetic below uses invented numbers to show the method — they are not measured data.
Month one: 4,000 sessions, 92% Buy Box Percentage, 8% Unit Session Percentage, $25 average selling price — 320 units, about $8,000.
Month two: 4,100 sessions, 61% Buy Box Percentage, 5.4% Unit Session Percentage, $25 average selling price — roughly 221 units, about $5,530.
Traffic went up. Price held. Conversion fell by a third — and Buy Box Percentage fell by almost the same proportion. When those two move together and Sessions do not, the page was not losing an argument; it was losing the add-to-cart button on a third of its page views. That investigation belongs in pricing and offer eligibility. Rewriting the copy would have cost a week and fixed nothing.
The reverse pattern — Buy Box Percentage steady in the nineties while Unit Session Percentage slides — is the one that genuinely points at the detail page.
When the free reports are enough, and when to upgrade
Business Reports answer diagnostic questions completely and profitability questions not at all: nothing in the columns above knows your cost of goods, ad spend or FBA fees. That boundary, not your revenue, should decide whether you pay for a tool.
| Signal | Verdict |
|---|---|
| You need to know which funnel step broke | Free reports are enough — that is exactly what they measure |
| You sell in one marketplace and can hold your SKU list in your head | Free reports are enough |
| Your monthly close is a spreadsheet built from Amazon’s settlement data | Free reports are enough — see FBA bookkeeping |
| You want per-ASIN traffic and conversion history | Free reports are enough; export the CSV monthly and archive it |
| You need net profit per SKU after COGS, PPC and fees | Upgrade — no native report joins those three |
| You need several marketplaces consolidated into one view | Upgrade |
| You need alerting rather than checking (Buy Box loss, conversion drop) | Upgrade |
| More than one person needs a dashboard they did not build | Upgrade |
| You are auditing FBA reimbursements at scale | Upgrade, or use a dedicated reimbursement workflow |
| Your SKU count makes manual CSV work take longer than the insight is worth | Upgrade |
If you land on the upgrade side, what those tools add is compared in our roundup of Amazon profit analytics tools. Brand-registered sellers have a second free tier worth exhausting first: Amazon Brand Analytics carries search-term and repeat-purchase data Business Reports does not.
Common mistakes
- Diagnosing at the account level. The Sales Dashboard sums every product’s noise. Set the date range there, then move to per-ASIN data.
- Comparing parent-ASIN and child-ASIN rows. A parent row aggregates its children; mixing granularities produces conversion rates that cannot be reconciled.
- Treating Session Percentage as market share. Amazon’s definition is explicit that the denominator is all of your products.
- Assuming Unit Session Percentage equals shopper conversion. It is units over sessions. Multipacks and quantity breaks inflate it.
- Chasing Buy Box Percentage without checking stock. An out-of-stock or stranded offer cannot show the buy box, and repricing will not fix it — that belongs in your inventory tracking system.
- Comparing unequal windows. 28 days against 31 days builds a 10% decline into the arithmetic before anything real is measured.
Frequently Asked Questions
What is a good Unit Session Percentage on Amazon?
There is no official Amazon benchmark; any single number quoted as one is a third party’s aggregate. The usable comparison is your own ASIN’s prior period at the same price and traffic mix, because category, price point and multipack structure all move the metric independently of listing quality.
Why is my Buy Box Percentage below 100% when I am the only seller?
Amazon’s definition ties the metric to page views where the buy box appeared, so it can fall with no competing offer at all — an out-of-stock listing, a suppressed one, or a price outside what Amazon will feature. Check offer eligibility before assuming a competitor is involved.
Do Business Reports show my profit?
No. The columns cover traffic, conversion, units and ordered product sales. Cost of goods, advertising spend and FBA fees are not in the report, so profit has to be assembled elsewhere — from settlement data by hand, or from a paid tool.
What is the difference between Sessions and Page Views?
Sessions collapse all of one user’s activity in a 24-hour period into one; Page Views count the individual visits. Page Views ÷ Sessions is therefore an average revisit rate, and a rising ratio with flat conversion usually means shoppers are comparing rather than deciding.
The bottom line
Business Reports are free, native, and sufficient for the question most sellers actually have: which step broke. Read Sessions, then Buy Box Percentage, then Unit Session Percentage, then Average Selling Price, and stop at the first abnormal column. Pay for a tool when you need what Amazon does not collect for you — cost of goods, ad spend and fees joined per SKU.