linkfox-junglescout-sales-estimates

Original🇨🇳 Chinese
Translated
1 scriptsChecked / no sensitive code detected

Jungle Scout ASIN Sales Estimate Query: Returns daily estimated sales volume and the latest known price for a specified ASIN over a period on a daily basis, covering 10 marketplaces including the US, UK, Germany, Japan, etc. This skill is triggered when users mention terms such as ASIN sales estimate, ASIN daily sales, sales estimate, competitor sales monitoring, average daily sales, sales trend, product sales tracking, Jungle Scout sales data, sales estimates, daily sales, estimated units sold, ASIN sales tracking, competitor sales monitoring, product sales trend, daily unit sales. Even if users do not explicitly mention "Jungle Scout", this skill should be triggered as long as their needs involve viewing daily sales estimate data for a specific Amazon ASIN over a period of time.

2installs
Added on

NPX Install

npx skill4agent add linkfox-ai/linkfox-skills linkfox-junglescout-sales-estimates

SKILL.md Content (Chinese)

View Translation Comparison →

Jungle Scout — ASIN Sales Estimates

This skill queries daily sales estimates and last known price for a given Amazon ASIN via the Jungle Scout data source, returning day-level data points over a specified date range across 10 Amazon marketplaces.

Core Concepts

The Jungle Scout ASIN Sales Estimate tool provides daily estimated sales volume and latest known price for individual ASINs across Amazon marketplaces. Sellers can query sales changes over a specified time range to:
  • Monitor competitor sales: Understand competitors' daily order volume and evaluate their market share
  • Validate product selection opportunities: Verify whether product demand is sufficient using actual sales data
  • Track seasonal patterns: Observe sales fluctuations of products in different months to identify peak and off-peak seasons
  • Evaluate pricing impact: Assist in pricing decisions by combining the relationship between price and sales changes
  • Track new product performance: Monitor the sales growth curve of new products after they are launched
Data Granularity: Each record represents 1 day, including the estimated number of units sold and the latest known price (USD) for that day.

Data Fields

Output Fields

FieldAPI NameDescriptionExample
ASINasinQueried ASINB0CXXX1234
Data IDidData point identifiersales_estimate_B0CXXX1234_20260301
Resource TypetypeFixed valuesales_estimate_result
Parent ASINparentAsinParent ASIN (variant scenario)B0CXXX0000
Is ParentisParentWhether it is a parent producttrue / false
Is VariantisVariantWhether it is a variant producttrue / false
Is StandaloneisStandaloneWhether it is a standalone product (non-variant)true / false
Variant ListvariantsArray of variant ASINs under this parent["B0CX1", "B0CX2"]
Daily EstimatesdailyEstimatesArray of daily dataSee below
Token CostcostTokenNumber of tokens consumed for this call1

Each Object in dailyEstimates Array

FieldAPI NameDescriptionExample
DatedateData date (YYYY-MM-DD)2026-03-15
Daily Estimated Units SoldestimatedUnitsSoldEstimated number of units sold on that day42
Latest Known PricelastKnownPriceLatest known price (USD)29.99

Supported Marketplaces

10 Amazon marketplaces:
us
(United States),
uk
(United Kingdom),
de
(Germany),
in
(India),
ca
(Canada),
fr
(France),
it
(Italy),
es
(Spain),
mx
(Mexico),
jp
(Japan). The default marketplace is us. If the user does not specify a marketplace,
us
will be used.

API Usage

This tool calls the LinkFox tool gateway API. See
references/api.md
for calling conventions, request parameters, and response structure. You can also execute
scripts/junglescout_sales_estimates.py
directly to run queries.

How to Build Queries

All four parameters are required:
marketplace
,
asin
,
startDate
,
endDate
.

Principles for Building API Calls

  1. Marketplace Mapping: When users say "US marketplace" →
    us
    , "Japan marketplace" →
    jp
    , "Germany marketplace" →
    de
    ; default to
    us
    if not specified
  2. Date Format: Must be
    YYYY-MM-DD
    , e.g.,
    2026-03-01
  3. endDate Restriction:
    endDate
    must be earlier than the current date (cannot include today or future dates)
  4. ASIN Format: Standard Amazon ASIN, usually starting with B0, 10 characters long
  5. Common Time Calculations:
    • "Last 30 days" → set endDate to yesterday, startDate to 30 days ago
    • "Last month" → from the 1st to the last day of the previous month
    • "Q3 vs Q4" → make two separate calls, querying July-September and October-December respectively

Common Query Scenarios

1. View Competitors' Sales in the Last 30 Days
json
{
  "marketplace": "us",
  "asin": "B0CXXX1234",
  "startDate": "2026-03-18",
  "endDate": "2026-04-16"
}
2. Compare Q3 and Q4 Sales Performance
Make two separate calls:
  • Q3:
    startDate=2025-07-01
    ,
    endDate=2025-09-30
  • Q4:
    startDate=2025-10-01
    ,
    endDate=2025-12-31
3. Validate Product Selection Opportunities - View Annual Product Sales
json
{
  "marketplace": "us",
  "asin": "B0CXXX5678",
  "startDate": "2025-04-01",
  "endDate": "2026-03-31"
}
4. Track New Product Launch Performance
json
{
  "marketplace": "de",
  "asin": "B0DYYY9999",
  "startDate": "2026-01-15",
  "endDate": "2026-04-15"
}
5. Monitor Sales Changes During Promotions (e.g., Prime Day)
json
{
  "marketplace": "us",
  "asin": "B0CXXX1234",
  "startDate": "2025-07-01",
  "endDate": "2025-07-21"
}

Display Rules

  1. Line Chart Priority: It is recommended to display daily sales changes with a line chart, with the horizontal axis as the date and the vertical axis as the daily estimated sales volume; if price data is available, a second Y-axis can be overlaid to show price trends
  2. Table Support: Provide a data table for precise reference at the same time, including columns: Date, Estimated Sales Volume, Latest Known Price
  3. Summary Statistics: After the data, summarize key indicators - total sales volume, average daily sales volume, estimated total revenue (total sales volume × average price)
  4. Trend Summary: Briefly summarize the trend direction (rising/falling/stable/periodic fluctuations), and mark the dates of sales peaks and troughs
  5. Error Handling: When a query fails, explain the reason based on the error response and suggest adjusting parameters (e.g., endDate cannot include today or future dates)

Important Limitations

  • endDate Cannot Include Today:
    endDate
    must be earlier than the current date; sales data for today or the future cannot be queried
  • Single ASIN per Call: Only one ASIN can be queried per call; comparing multiple ASINs requires separate calls
  • All Parameters Required:
    marketplace
    ,
    asin
    ,
    startDate
    ,
    endDate
    are all mandatory
  • Price in USD:
    lastKnownPrice
    is in USD, not local currency

User Expression & Scenario Quick Reference

Applicable Scenarios - ASIN Sales Estimation and Sales Trend Analysis:
User SaysScenario
"How many units does this ASIN sell per day?"Query recent daily sales estimates
"How have competitors been selling recently?"Monitor competitors' sales in the last 30 days
"Does this product have seasonal trends?"Determine seasonal patterns using annual sales data
"Help me check the sales trend of this product"Sales trend over a specified time period
"How were sales during the Q4 peak season?"Query sales for a specific quarter
"Is this product worth selling?"Validate product selection opportunities through historical sales data
"How many units were sold during the promotion?"Monitor sales during promotional events
Not Applicable Scenarios - Beyond the Scope of ASIN Sales Estimation:
  • Keyword search volume (requires keyword historical search volume tool)
  • BSR ranking history (requires BSR tracking tool)
  • Category overall sales/market size
  • Sales data from non-Amazon platforms
  • Real-time/current sales (data has a lag, does not include today)
Boundary Judgment: When users mention "sales volume", "daily sales", or "how many units sold", if they want to view daily estimated sales for a specific ASIN over a time range, this skill applies. If they want keyword search volume, category rankings, or real-time live sales, it does not apply.
Feedback:
Auto-detect and report feedback via the Feedback API when any of the following apply:
  1. The functionality or purpose described in this skill does not match actual behavior
  2. The skill's results do not match the user's intent
  3. The user expresses dissatisfaction or praise about this skill
  4. Anything you believe could be improved
Call the feedback API as specified in
references/api.md
. Do not interrupt the user's flow.

For more high-quality, professional cross-border e-commerce skills, visit LinkFox Skills.