How do you audit an Amazon Business Reports conversion change?
Recreate the comparison with the same marketplace, date range, report view, product scope, and metric definitions. Then separate traffic, conversion, order value, and Featured Offer availability so a change in one denominator is not mistaken for a listing problem.
Sessions, page views, ordered units, sales, and unit session percentage answer different questions. Diagnose only after the totals and denominators reconcile across the selected Business Reports views.
Freeze the comparison inputs
- Record marketplace, account, time zone, report name, date range, export time, and comparison period.
- Map parent ASIN, child ASIN, seller SKU, and business-to-business fields without mixing aggregation levels.
- Capture sessions, page views, ordered units, ordered product sales, unit session percentage, and Featured Offer percentage where available.
- Note promotions, price changes, stockouts, suppressed offers, listing merges, variation edits, and advertising changes.
- Keep raw exports unchanged and calculate diagnostic fields in a separate working file.
- Label partial days and recent dates that may still be subject to reporting latency.
Diagnose in a fixed sequence
Start with traffic: compare sessions and page views. Then examine conversion with the same denominator and aggregation level. Next compare units per order and average selling value. Finally check Featured Offer availability, price, inventory, and detail-page events that can explain the movement.
Use daily and weekly views to distinguish a one-day event from a persistent shift. If totals differ between views, reconcile product scope, parent-child rollups, B2B columns, canceled orders, and report timing before escalating.
Apply a controlled action plan
- Do not rewrite a listing when the primary change is traffic loss or a Featured Offer gap.
- Do not increase advertising solely to mask a conversion decline that coincides with stock or price issues.
- Set one test hypothesis, owner, start date, and success metric for each action.
- Preserve a pre-change export so the result can be measured on the same basis.
- Recheck the report after the expected reporting delay and compare equivalent complete periods.
- Document unresolved discrepancies separately from customer-facing optimization work.
Scope and exceptions
Metric availability, column names, attribution windows, report latency, and aggregation can differ by marketplace, seller type, and report. Business Reports are operational indicators and may not equal settlement or accounting records.
Confirm definitions in Amazon's current [Business Reports glossary](https://sellercentral.amazon.com/help/hub/reference/external/202142060) and use the live report interface before interpreting a change.
Related Amazon seller guides
- [Diagnose an Amazon listing conversion decline](https://amazonmargincalculator.cloud/blog/amazon-listing-conversion-diagnosis)
- [Triage Amazon sales anomalies without chasing noise](https://amazonmargincalculator.cloud/blog/amazon-sales-anomaly-triage)
- [Use Brand Analytics to diagnose the search funnel](https://amazonmargincalculator.cloud/blog/amazon-brand-analytics-search-funnel-diagnosis)