Frequently Asked Question
[BigTracker Sales Performance Metrics Mechanics] Why is the majority of the sales metrics data on B07GXNX2GH / B07HQFFL77 ASINs are missing?
Last Updated 6 years ago
You can see in the image below a series of products that have been added to BigTracker but don’t have a whole lot of relevant data--things like Rank, Est. Sales, and Est. Revenue filed.
The explanation for the missing Data on two of the ASINs:
For the ASIN: B07HQFFL77, Amazon’s website doesn’t provide any sales rank data. The configuration of BigMovers, Est. Sales, and Est. Revenue metrics are mainly based on the sales rank data. Without the SalesRank or if the rank is too low, the system either is unable to complete the configuration or the result will be insignificant and will be displayed as “B07GXNX2GH.
Please refer to the product sales performance indicators outlined below.
All of the product sales performance indicators (including est. sales and est. revenue) are designed to forecast the potential success of a product for the next 30 days, based on historical database analysis.
The duration of the historical analysis could be chosen from 30, 60, 90, or 180 days. The system uses the historical data over that given period of time, to refine the estimated amount of sales and revenue for the customer 's future product investment decisions.
Concerning the insignificant Est. sales for the ASIN.B07GXNX2GH, the issue lies in the result of the Est. sales essentially being insignificant. I will continue to talk about the Est. Sales and Revenue mechanics.
Est. Sales and Revenue
With the SalesRank data in place, the Sales metrics fields marked in the red as seen below will populate the corresponding Est. metrics.
However, the reason behind multiple metrics being displayed as 0 is due to the Est. Sales / Est. Revenue.
If the rank of a product is relatively low, the Est. sales calculated by the system will be insignificant. If the Est. Sales are relatively low, for example: by orders of 0.1, 0.01, or 0.05. This kind of result can’t reflect the actual order amount and is also insignificant. The system will display
If the rank of the product is extremely low, the Est. sales and revenue calculated by our algorithm even with conservative approach will be really insignificant like 0.1, which doesn't have any significant value for reference. Given this, the system won't proceed to present the calculation result.
Nevertheless, if the ranking of the product is in the first couple search pages, the result of the Est. sales will be calculated higher, for example: by orders of 2000. If the actual order amount is around 2200, the margin of error is relatively small and generally seen to be acceptable. The result will be considered to have a referencing value. Once this value is considered usable, the system will proceed with the Est revenue calculation.
Below is a product with higher sales rank, when the margin of error between the estimation and actual sales data is within the accepatble range, the system will proceed with the calculation to the relative fields.
The explanation for the missing Data on two of the ASINs:
For the ASIN: B07HQFFL77, Amazon’s website doesn’t provide any sales rank data. The configuration of BigMovers, Est. Sales, and Est. Revenue metrics are mainly based on the sales rank data. Without the SalesRank or if the rank is too low, the system either is unable to complete the configuration or the result will be insignificant and will be displayed as “B07GXNX2GH.
Please refer to the product sales performance indicators outlined below.
All of the product sales performance indicators (including est. sales and est. revenue) are designed to forecast the potential success of a product for the next 30 days, based on historical database analysis.
The duration of the historical analysis could be chosen from 30, 60, 90, or 180 days. The system uses the historical data over that given period of time, to refine the estimated amount of sales and revenue for the customer 's future product investment decisions.
Concerning the insignificant Est. sales for the ASIN.B07GXNX2GH, the issue lies in the result of the Est. sales essentially being insignificant. I will continue to talk about the Est. Sales and Revenue mechanics.
Est. Sales and Revenue
With the SalesRank data in place, the Sales metrics fields marked in the red as seen below will populate the corresponding Est. metrics.
However, the reason behind multiple metrics being displayed as 0 is due to the Est. Sales / Est. Revenue.
If the rank of a product is relatively low, the Est. sales calculated by the system will be insignificant. If the Est. Sales are relatively low, for example: by orders of 0.1, 0.01, or 0.05. This kind of result can’t reflect the actual order amount and is also insignificant. The system will display
If the rank of the product is extremely low, the Est. sales and revenue calculated by our algorithm even with conservative approach will be really insignificant like 0.1, which doesn't have any significant value for reference. Given this, the system won't proceed to present the calculation result.
Nevertheless, if the ranking of the product is in the first couple search pages, the result of the Est. sales will be calculated higher, for example: by orders of 2000. If the actual order amount is around 2200, the margin of error is relatively small and generally seen to be acceptable. The result will be considered to have a referencing value. Once this value is considered usable, the system will proceed with the Est revenue calculation.
Est. Sales % and Est. Revenue %
Est. Sales % and Est. Revenue % is based on the previous est. order amount and historical information. When the ranking of the product is too low, the system will assume that the Est metrics have no referencing values. The system will proceed to not calculate the est sales and revenue, therefore, the corresponding Est. sales % and revenue won’t be populated.Below is a product with higher sales rank, when the margin of error between the estimation and actual sales data is within the accepatble range, the system will proceed with the calculation to the relative fields.