Docs

SQPR reports ​

Choose which ASINs and periods sellerfox loads from Amazon's Search Query Performance Report. Use the Search Term Analyzer to analyze the loaded search-query and ASIN data.

Only Owners and Admins can configure the loading behavior or request reports manually. See Permissions for details.

Check marketplace coverage ​

Amazon does not offer SQPR data for every marketplace, so the product selector lists only the marketplaces where sellerfox supports SQPR. See Supported marketplaces for the current coverage.

A sellerfox week runs from Sunday through Saturday

sellerfox loads weekly and monthly reports for the selected ASIN-marketplace pairs. A week starts on Sunday and ends on Saturday and therefore covers different days than an ISO week.

Choose which ASINs load automatically ​

Owners and Admins set “Loading behavior” under Settings → Search Term Analyzer. “Bestsellers by revenue” is active by default. See the pricing page for the current standard allowances and the loading-behavior options for your workspace's included ASIN allowance.

OptionWhat gets loaded
“Bestsellers by revenue”First your fixed ASINs, which sellerfox always loads, then the highest-revenue ASIN-marketplace pairs, up to the number included in your subscription.
“Custom list”Exactly the ASIN-marketplace pairs you select.

If a fixed ASIN is also one of the highest-revenue ASINs, the fixed ASIN does not take a second slot. The slot goes to the next ASIN by revenue. If your fixed ASINs exceed the included number after a subscription change, sellerfox still loads all fixed ASINs and no others. Each pair above the included number then uses one credit.

The allowance counts ASIN-marketplace pairs, so the same ASIN on two marketplaces counts twice. “Bestsellers by revenue” limits the selection to the number your subscription includes. Only “Custom list” lets you select more, and each pair above the included number then uses one credit. A selection that needs more credits than the workspace has cannot be saved. See Subscription, billing & credits → Credits.

Check data coverage ​

sellerfox automatically loads SQPR reports for the ASIN selection defined by your loading behavior. Your allowance determines the scope; Amazon's request limits also limit how quickly reports arrive.

In the Search Term Analyzer, open “Data coverage” below the filters. The percentage counts the reports available for your product selection, marketplaces, period, and granularity. Each combination of ASIN, marketplace, and week or month counts separately.

Reports that are not due yet are excluded. Missing, pending, and failed reports count as not yet available. The display reaches 100% only when every due report is present. If no period is due yet, it shows “More reports to follow”.

Without a product selection, the check includes the ASINs for which an SQPR report was requested or SQPR data exists in the period. Other workspace products are not included. Search-query and KPI filters do not change report completeness. In the funnel, data coverage follows the selected marketplace and, when selected, the individual ASIN.

In the dialog, each row represents an ASIN on a marketplace and each column a week or month. Cells show the following statuses:

StatusMeaning
“Report available”The report has been loaded.
“Not loaded”No report is available for this combination.
“Loading”The request is in progress or awaiting an automatic retry.
“Failed”Loading the report failed.
“Not yet available”The period is not yet available to request.

Owners and Admins can select “Add reports” below a period. The loader preselects that period's missing and failed combinations. Check the selection and monthly allowance before choosing “Load reports”. Available or pending reports are not selected for reloading. Viewers can inspect coverage but cannot request reports.

Select “Refresh” to check again. “Check failed” means sellerfox could not check coverage; it does not mean every individual report failed.

Complete reports do not mean complete data for every search query. A loaded report may not contain a particular search term. That is not evidence of 0 impressions, clicks, or purchases.

Load a specific report ​

Open the Search Term Analyzer and choose “Load additional reports” below the filters.

Open the report selection and loaded-report history from the Search Term Analyzer.
  1. Under “ASINs”, select the products you want reports for.
  2. Under “Period (weeks)” and “Period (months)”, select at least one period. You can choose completed weeks and months from the last two years. The previous week becomes selectable on Tuesday; the previous month becomes selectable on the 3rd of the following month.
  3. Enable “Reload failed reports” if sellerfox should also request reports with the status “Failed” again.
  4. Check how many reports the request consumes. The “Reports consumed this month” bar at the top of the dialog shows how much of your monthly allowance is already used.
  5. Submit the request with “Load reports”.

Being able to select a period does not guarantee that Amazon has already made its report available. See When reports arrive and why they can be late.

sellerfox requests the exact ASINs and marketplaces you select in the dialog. Selecting a Parent ASIN does not expand into the corresponding Child variations. Select each Child variation you want individually.

sellerfox only requests combinations of ASIN, marketplace, and period that do not have a report yet. Every other combination is skipped, including those whose report is still queued or in processing. The one exception is reports with the status “Failed”: with “Reload failed reports” enabled, sellerfox requests those reports again.

Skipped reports do not count against the monthly allowance. Every report that is actually requested does count, even when Amazon returns no rows. The allowance is consumed when you submit the request, not when the data arrives. The allowance starts over at the beginning of each calendar month and is separate from credits.

You cannot upload an SQPR file. sellerfox retrieves every report through Amazon's official API (SP-API).

Check status and retry failures ​

“View loaded reports” shows a separate row for each combination of ASIN, marketplace, and period. You can switch between weeks and months, filter by product list and marketplace, and search by ASIN, SKU, or product title.

StatusWhat to do
“Loaded”The data is available. “View report” opens the Search Term Analyzer.
“Queued”sellerfox has scheduled the request but has not sent the request to Amazon yet. Wait.
“In processing”Amazon has accepted the request but has not finished the report. Wait.
“Attempt {x}/{y} on {date}”An automatic retry is scheduled for that date. Wait for the retry.
“Attempt {x}/{y} due”The scheduled date has been reached, but the retry has not been sent yet, so Amazon has not received the request. Wait.
“Failed”All automatic attempts are exhausted. Use “Reload report…” to submit a new request.

A failed report stays “Failed” until an Owner or Admin requests the report again with “Reload report…”. The automatic attempts before that do not count against the monthly allowance; the manual request does.

If a report never arrives, first check the marketplace, ASIN, period, and displayed status. If the issue persists, contact support.

When reports arrive and why they can be late ​

An SQPR report is not available the moment the attribution period closes. Amazon provides the report no earlier than four days after the week or month ends. The sellerfox schedule follows that: sellerfox requests the previous week's report every Wednesday and the previous month's report on the fourth day of the following month. Manual requests, by contrast, go to Amazon immediately. See Data refresh schedule for the full timing.

How a report is loaded ​

  1. The attribution period closes. No row appears yet, because sellerfox has not requested the report.
  2. sellerfox requests the report; the row shows “Queued”.
  3. Amazon accepts the request; the row shows “In processing”.
  4. The report is complete; the row shows “Loaded” and the data appears in the Search Term Analyzer.

A first failed attempt is normal ​

The report is not always ready for the first scheduled request, so all reports for the previous week or month may initially fail. This is not a problem with your workspace and needs no action.

sellerfox then requests the report again automatically. The row shows “Attempt {x}/{y} on {date}”: {x} is the next attempt, {y} the total number of planned attempts, and {date} the scheduled date. A retry does not happen immediately but several hours later. Only when every planned attempt has failed does the row change to “Failed”, and a manual request becomes worthwhile.

Why loading can be delayed further ​

Amazon limits how quickly reports can be retrieved, and all tools connected to the same Seller Central account share that limit. A report then stays in processing longer than usual. sellerfox keeps loading reports automatically, so you do not need to trigger anything again.

What SQPR counts ​

sellerfox loads and analyzes the reports per ASIN. In “KPI Overview”, each row is one search query on one marketplace and expands to the corresponding ASINs. The detail view and exports grouped by ASIN label the ASIN column Child ASIN.

Report valueWhat it shows
Search volumeHow often customers searched for the query during the report period
Market KPIsImpressions, clicks, add-to-cart actions, and purchases across all ASINs from all sellers in the search results for the query
ASIN KPIsThe same values, but for your own ASIN only, plus your ASIN's share of each Market KPI

Market KPIs describe the whole search query, not an individual ASIN. Two ASINs show the same Market KPIs when they cover the same periods for the same query and marketplace. Differences can arise when reports are missing or loaded reports do not contain the search term. sellerfox sums only periods with data for that query. Check the affected ASINs under “Data coverage” and load missing reports.

From those values, sellerfox additionally calculates CTR Market (SQPR), CTR ASIN (SQPR), CTR Diff. ASIN (SQPR), ATCR Market (SQPR), ATCR ASIN (SQPR), ATCR Diff. ASIN (SQPR), CVR Market (SQPR), CVR ASIN (SQPR), CVR Diff. ASIN (SQPR), and Sales Volume (SQPR). The KPI Explorer shows the formula for each one.

SQPR purchases are not your order total

SQPR purchases are purchase actions that originate from the search results for a query. The order counts in Seller Central and in sellerfox, by contrast, include every order, including purchases that did not come from the search results for that query. The two figures are therefore not interchangeable. For why the values diverge and how to reconcile the two sources, see Troubleshooting → SQPR orders do not match my orders in Seller Central.