Why Does My Amazon Seller Central Buy Box Percentage Not Match Amazon While Other Metrics Do?
Last updated
Note: Are you comparing Amazon Seller Central data in Power My Analytics against Amazon's own dashboard and finding that most numbers match, but Featured Offer (Buy Box) Percentage is way off? This article explains why that happens and how to fix it.
The Symptom
You pull a report from your connected Amazon Seller Central account. Ordered Product Sales, Units Ordered, and Sessions all line up closely with what Amazon itself reports for the same date range. But Featured Offer (Buy Box) Percentage (or a similar rate or percentage field) is far lower than Amazon's own figure, sometimes by 50 percentage points or more.
If the gap is small and appears only on weekly, monthly, or other multi-day date ranges while single days match, see "A Smaller Gap on Weekly or Monthly Date Ranges" below.
The Most Common Cause: Your Report Isn't Scoped to One Marketplace
A connected Amazon Seller Central account covers an entire Region (North America, Europe and India, or Far East), not a single marketplace. The North America Region, for example, includes the United States, Canada, Mexico, and Brazil. If your account has activity in more than one marketplace within its Region, a report that isn't scoped to a single marketplace pulls data from all of them together.
That blending affects different kinds of metrics differently:
- Totals still add up correctly. Units Ordered, Ordered Product Sales, Sessions, and other summed metrics simply add more real activity together when more marketplaces are included. The number is still accurate, even if it isn't broken out the way you expected.
- Rates and ratios don't. Featured Offer (Buy Box) Percentage, and other metrics that are computed as a percentage or average rather than a plain sum, get skewed when the underlying marketplaces have different pricing, traffic, or Buy Box dynamics. Blending them produces a number that doesn't reflect any single marketplace's actual performance.
Metrics That Need to Be Scoped to One Marketplace
Check any of these fields for the same signature (volumes look right, this field doesn't):
- Featured Offer (Buy Box) Percentage (and its B2B variant)
- Order Item Session Percentage
- Unit Session Percentage
- Average Offer Count
- Average Selling Price
- Average Sales per Order Item
- Average Units per Order Item
- Session Percentage, Page Views Percentage, and their Browser, Mobile App, and B2B variants (Sales and Traffic by Child ASIN report)
- Refund Rate and Refund Rate B2B (Sales and Traffic by Child ASIN report)
Note: An illustrative case: In one case, an account's Ordered Product Sales, Units Ordered, and Sessions all matched Amazon's own reporting for the window in question. Featured Offer (Buy Box) Percentage, though, read about 24 to 25 percent in Power My Analytics against Amazon's own reported 97 to 99 percent. The account was authorized for more than one marketplace within its Region. That pattern (volume metrics matching while a rate metric doesn't) is consistent with an unscoped, multi-marketplace pull. Treat it as a strong signal to check your Marketplace scoping first, before assuming a data or mapping problem.
The Fix: Scope Your Report to a Single Marketplace
Add a Marketplace filter (and, where relevant, the Marketplace dimension) to your report:
- Data Studio: Add the Marketplace dimension to your table and apply a Marketplace filter, or add a drop-down filter control using the Orders Marketplace Name metric and the Sales Channel control field.
- Google Sheets and Microsoft Excel: Add Marketplace as a dimension in your query and create a Marketplace filter.
Re-run your comparison against Amazon's own report for that one marketplace only. This is the step to take before escalating a rate or percentage discrepancy as a data issue.
If Your Account Covers More Than One Marketplace
If your seller account is authorized for more than one marketplace in its Region (for example, an account covering both the United States and Canada), don't rely on a single blended report. Build one report per marketplace, or filter to one marketplace at a time, especially for any of the rate or ratio metrics listed above. This gives you a clean, marketplace-accurate figure for each market instead of one blended number that doesn't represent either.
A Smaller Gap on Weekly or Monthly Date Ranges
If single days match Amazon but a week, a month, or another multi-day range is slightly off, the difference comes from how a multi-day percentage can be calculated from the data Amazon's API provides.
For a single day, Featured Offer (Buy Box) Percentage is the value Amazon reports, so a report scoped to one marketplace matches Seller Central for that day. Amazon doesn't provide the count behind the percentage, so for a multi-day range Power My Analytics rebuilds it from the daily figures:
- Traffic Featured Offer Page Views is calculated for each day as that day's Featured Offer (Buy Box) Percentage multiplied by Page Views - Total. Because it's calculated, it can include decimals.
- For a multi-day range, Featured Offer (Buy Box) Percentage is the sum of Traffic Featured Offer Page Views divided by the sum of Page Views - Total, so busier days count for more.
Amazon calculates its own multi-day percentage from an internal view count that isn't available through its API, and Amazon has confirmed there's no way to reproduce that figure exactly from the data the API provides. The multi-day figure in Power My Analytics is a close approximation, not an error in your data.
To get the most accurate comparison:
- Compare day by day. Add the Date And Time dimension to your table (and scope it to one marketplace) to match Seller Central exactly for each day.
- Use the percentage field as-is. Scorecards and tables calculate Featured Offer (Buy Box) Percentage from the summed page views. Summing or averaging the daily percentages yourself gives a less accurate result.
- Combining days in Google Sheets or Microsoft Excel? Divide the sum of Traffic Featured Offer Page Views by the sum of Page Views - Total. For Amazon Business (B2B) traffic, use Traffic Featured Offer Page Views B2b and Page Views - Total B2B.
- Use the current field. Traffic Buy Box Page Views and Traffic Buy Box Page Views B2b are older fields that are no longer populated. Use Traffic Featured Offer Page Views instead.
Both Traffic Featured Offer Page Views fields are available in the Sales and Traffic table and the Sales and Traffic by Child ASIN table.
Other Possible Causes
Marketplace scoping is the most likely explanation when volume metrics match Amazon closely but a rate or percentage metric doesn't. If scoping to a single marketplace doesn't close the gap, or if the discrepancy also affects your totals, check the more general causes covered in Why Do the Sales Numbers Not Align with My Amazon Seller Central Reports?, including order status filters, time zone differences, and order date versus shipped date.
Still Not Matching?
If you've scoped your report to a single marketplace, compared a single day, and the discrepancy remains, submit a ticket with:
- The single marketplace you scoped to
- The metric and date range in question
- The value shown in Power My Analytics and the value shown in Amazon's own report for the same marketplace and window