This skill guides you on how to query Amazon product detail and historical trend data by ASIN via Sorftime, helping Amazon sellers analyze product performance, pricing strategy, and competitive positioning.
Core Concepts
Sorftime Product Detail provides comprehensive product-level data by ASIN, with historical trend data going back to 2021. It covers sales volume & revenue trends, price & promotion tracking, multi-level BSR ranking history, and real-time profit analysis with FBA fee breakdown.
Key differentiator: This tool returns trend/time-series data for individual products. If you need to search/filter products across a category, brand, or seller, use the Sorftime Product Search skill instead.
Data Fields
Response data covers the following categories (see references/api.md for complete field reference):
- Basic info: title, brand, ASIN, listing URL, images (main + A+), store name, bullet points, product badges, off-sale status, last update date, weight, size
- Variations: parent ASIN, variation count, child ASINs, variation attributes
- Pricing & profit: sale price, coupon, platform fee, FBA fees (with detail breakdown), FBM shipping cost, profit amount & rate
- Sales: official monthly sales (Amazon-published)
- Rankings: BSR rank, category tree, sub-category rankings, listing date, days online
- Ratings: rating score, rating count, star distribution (1-5 star percentages)
- Seller: Buybox seller name/ID/country, FBA status, seller count
- Listing features: A+ content, video, brand store, feature ratings, product info, properties
- Promotions: brand promotion, deal type, extra savings
- Trends (time-series): BSR rank, sub-BSR rank, daily/monthly sales volume, daily/monthly revenue, price, list price, deal status
Supported Marketplaces
US (United States), GB (United Kingdom), DE (Germany), FR (France), IN (India), CA (Canada), JP (Japan), ES (Spain), IT (Italy), MX (Mexico), AE (United Arab Emirates), AU (Australia), BR (Brazil), SA (Saudi Arabia)
Default marketplace is US. Use us when the user doesn't specify a marketplace.
Note: Sorftime uses lowercase codes (e.g., us, gb, de), and UK is coded as gb (not uk).
How to Call
- API Endpoint：
POST /sorftime/amazon/productDetail(For complete parameters/responses/error codes, seereferences/api.md） - Python Script：
python scripts/sorftime_product_detail.py '<JSON 参数>' [--inline] - Cost Constraints: This tool consumes compute; by default, the same parameter combination in the same session is called only once, and the script has a 24h local cache. On failure/empty results, do not automatically switch keywords, paginate, or change zip codes to probe continuously; if further retrieval is needed, first explain to the user that additional consumption will be incurred.
Output Strategy (Script Default Behavior)：
- Alwayswrite the complete response to
<cwd>/linkfox/<YYYY-MM-DD>/<session>/data/linkfox-sorftime-amazon-product-detail-<timestamp>.json（<cwd>is the working directory when the script is executed, which in Claude Code is the current project directory;<session>is taken from the environment variableSESSION_ID, automatically aggregated according to the user's task;writing to /tmp is prohibited, if the current directory is not writable, report an error) - Response body ≤ 8 KB: after saving to disk, print the complete JSON to stdout
- Response body > 8 KB: after saving to disk, stdout outputs only a summary (top-level fields, common counts such as
total/costToken, length of the largest list field + first 3 samples) - Add
--inlineto force full printing to stdout (also saved to disk)
Data Reading Suggestions: First look at the summary to determine whether it is sufficient; when specific fields are needed, prefer to use jqorConvertFrom-Json to extract on demand from the saved json file, avoiding bringing the entire JSON into context.
Resolve Authentication and Compute Issues
When the following abnormal situations occur, use references/onboarding.md to guide resolution:
Abnormal Situations
- API Key not configured: The environment variable is not configured with
LINKFOX_AGENT_API_KEY, andLINKFOXAGENT_API_KEY。 - Response 401 or 402 status code
- Response indicates insufficient compute or balance: The message contains "insufficient compute balance/insufficient billing/insufficient balance/quota exceeded/insufficient balance/package expired/recharge required/please recharge", or content with similar meaning.
How to Build Queries
The key parameters are asin and marketplace (both required), plus optional trend date range controls.
Principles for Building Queries
- Always specify the marketplace: Use lowercase site codes, e.g.,
us,de,jp - Choose trend inclusion carefully: Default includes trends (last 15 days). Set
includeTrend: 2if only basic product info is needed - this saves cost and speeds up response - Specify date range for historical analysis: Use
queryTrendStartDateandqueryTrendEndDate(yyyy-MM-dd) when users need trends beyond the default 15 days. Be aware this costs double - Batch ASINs when comparing: Up to 10 ASINs can be queried at once, comma-separated - use this for competitive comparison rather than calling one at a time
Query Examples for Common Scenarios
1. Quick product check (default 15-day trend)
asin: B00FLYWNYQ, marketplace: us
2. Long-range trend analysis (specify dates)
asin: B00FLYWNYQ, marketplace: us
queryTrendStartDate: 2025-01-01, queryTrendEndDate: 2025-03-31
3. Batch ASIN comparison
asin: B0088PUEPK,B00U26V4VQ,B0CVM8TXHP, marketplace: us
4. Product info only, no trends
asin: B0088PUEPK, marketplace: us, includeTrend: 2
5. BSR ranking history (German market)
asin: B00FLYWNYQ, marketplace: de
queryTrendStartDate: 2024-06-01, queryTrendEndDate: 2025-01-01
Trend Data Interpretation
Trend arrays use an interleaved format: even indices are dates, odd indices are values.
[20250101, 150, 20250102, 180, 20250103, 165, ...]
^date ^val ^date ^val ^date ^val
- Sales volume/revenue trends: value of
-1means "cannot estimate" (e.g., category changed to Amazon Renewed) - Price trends: units are in local currency smallest unit (cents for USD);
-1means no available price that day - BSR rank trends: for
bsrRankTrend, format is[{NodeId: xxx, Rank: [date, rank, ...]}]per sub-category - Deal trend: value
1= has active Deal that day,0= no Deal
Display Rules
- Present data only: Show query results in clear tables without subjective business advice
- Ranking clarification: When showing ranking data, remind users that lower values mean better rankings
- Price unit awareness: Trend data uses smallest currency unit (cents for USD). Convert to standard currency when displaying to users
- Sales estimation caveat: Values of
-1in sales/revenue fields mean "cannot estimate" - explain this to the user rather than showing -1 directly - Trend visualization: When showing trend data, present key data points in a readable table rather than dumping raw arrays
- Off-sale handling: When
offSaleis true, clearly inform the user the product is currently unavailable/off-sale - Error handling: When a query fails, explain the reason based on the
msgfield and suggest adjusting query criteria
Important Limitations
- Max 10 ASINs per query
- Trend cost: Default returns last 15 days; querying > 15 days costs double
- Non-structured data: Results do not support secondary analysis via
_dataQuery_executeDynamicQuery - Sales estimation: Products in non-standard categories (e.g., Amazon Renewed) may return -1 for sales fields
User Expression & Scenario Quick Reference
Applicable - Product detail and trend queries by ASIN:
| User Says | Scenario |
|---|---|
| "Check the sales trend of this ASIN" | Sales trend |
| "How has the price of this product changed recently" | Price history |
| "Help me look at the profit margin of this product" | Profit analysis |
| "The BSR ranking trend of this ASIN" | Ranking history |
| "Compare the data of these ASINs" | Multi-ASIN comparison |
| "What is the FBA fee for this product" | FBA fee breakdown |
| "How long has the product been listed, and how are the ratings" | Basic product info |
| "Is this product still on sale" | Off-sale status check |
| "Does this product have any Deal promotion records" | Deal history |
| "Look at the variation information of this product" | Variation details |
Not applicable - Needs beyond single-product detail:
- Searching/filtering products across a category or brand (use Sorftime Product Search)
- ABA search term ranking data (use ABA Data Explorer)
- Advertising / PPC strategy
- Product reviews content analysis
- Patent or trademark checks
Boundary judgment: When users say "product analysis" or "competitor comparison", if it boils down to checking specific ASINs' detail data and trend curves, then this skill applies. If they're asking to discover or filter products across a market, it does not apply.
Compute Consumption Rules
Billing follows dynamic rules: compute consumed = number of Sorftime internal queries × 6. Number of Sorftime internal queries: the number of queries required for different query conditions may differ, and this number is determined by Sorftime.
Important: The service of this skill is calculated dynamically by a multiplier and may consume a large amount of compute at once. The user must be reminded, and the user decides whether to continue.
Feedback:
Auto-detect and report feedback via the Feedback API when any of the following apply:
- The functionality or purpose described in this skill does not match actual behavior
- The skill's results do not match the user's intent
- The user expresses dissatisfaction or praise about this skill
- 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.