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
| Field | API Name | Description | Example |
|---|---|---|---|
| Product Title | title | Product listing title | Anker Portable Charger... |
| Brand | brand | Brand name | Anker |
| ASIN | asin | Amazon Standard Identification Number | B0088PUEPK |
| Parent ASIN | parentAsin | Parent ASIN if has variations, null otherwise | B0088PUEPK |
| Category | category | Main category [name, NodeId] | ["Cell Phones", "2811119011"] |
| Sub-category Rankings | bsrCategory | Sub-category rank list with nodeId, name, rank, date | [{nodeId, name, rank, date}] |
| Listing Date | availableDate | Listing date (yyyy-MM-dd) | 2022-03-15 |
| Days Online | onlineDays | Days since listing | 850 |
| Sale Price | price | Sale price after Coupon, local currency (e.g., USD) | 25.99 |
| Coupon | coupon | >0 = discount amount (500=$5); <0 = percentage (-10=10% off) | -15 |
| Platform Fee | platformFee | Platform commission, local currency | 3.90 |
| FBA Fees | fbaFees | FBA fulfillment fee, local currency | 5.40 |
| FBA Detail | fbaDetail | FBA breakdown: [delivery fee, month:storage fee, ...] | [475, "1-9:5", "10-12:15"] |
| Profit | profitAmount | Sale price - FBA - commission, local currency | 16.69 |
| Profit Rate | profitRate | Profit margin, e.g., 25.83 = 25.83% | 25.83 |
| BSR Rank | salesRank | Best Seller Rank in main category | 1523 |
| BSR Trend | rankTrend | Main category rank history, interleaved [date, rank, ...] | [20250101, 1523, ...] |
| Sub-BSR Trend | bsrRankTrend | Sub-category rank history per node | [{NodeId, Rank: [...]}] |
| Rating | rating | Current rating (0.0-5.0) | 4.70 |
| Rating Count | ratings | Number of ratings | 12580 |
| Star Distribution | fiveStarRatings / fourStar... / oneStar... | Star percentage, e.g., 57.7 = 57.7% | 57.7 |
| Daily Sales Trend | listingSalesVolumeOfDailyTrend | Interleaved [date, volume, ...]; -1 = cannot estimate | [20250101, 150, ...] |
| Monthly Sales Trend | listingSalesVolumeOfMonthTrend | Interleaved [date, volume, ...]; -1 = cannot estimate | [20250101, 4500, ...] |
| Daily Revenue Trend | listingSalesOfDailyTrend | Interleaved [date, revenue, ...]; unit = cents; -1 = N/A | [20250101, 38985, ...] |
| Monthly Revenue Trend | listingSalesOfMonthTrend | Interleaved [date, revenue, ...]; unit = cents; -1 = N/A | [20250101, 1169550, ...] |
| Price Trend | priceTrend | Sale price history; unit = cents; -1 = no price that day | [20250101, 2599, ...] |
| List Price Trend | listPriceTrend | Strikethrough price history; unit = cents; -1 = N/A | [20250101, 3999, ...] |
| Buybox Seller | buyboxSeller | Buybox winning seller name | AnkerDirect |
| Seller Country | buyboxSellerAddress | Seller country code (CN, US, etc.); null if Amazon-operated | CN |
| FBA Status | isFBA | Whether Buybox seller uses FBA | true |
| Seller Count | sellerNum | Number of sellers on this listing | 3 |
| A+ Content | aPlus | Has A+ content | true |
| Video | hasVideo | Has video on listing | true |
| Brand Store | hasBrandStore | Has brand storefront | true |
| Weight | weight | Weight in grams | 350 |
| Size | size | Dimensions in cm [longest, 2nd, shortest] | [18.5, 8.2, 3.1] |
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).
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/sorftime_product_detail.py directly to run queries.
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
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
- 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 |
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.
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.
Handling Large Responses
To avoid overflowing the agent context, persist the response to disk and extract only the fields you need:
python scripts/response_io.py run --script scripts/sorftime_product_detail.py --out-dir <DIR> '<params>'
python scripts/response_io.py read <file> --fields "<paths>" # or --path "<JMESPath>"
Pick
--out-diroutside any git working tree (e.g./tmp/...on Unix,%TEMP%/...on Windows). Persisted responses may contain PII, pricing, or auth-sensitive data — do not commit them. Files are not auto-deleted; clean up when the task is done.
run writes the full response to a file and emits only a schema preview + file path. read projects specific fields, with --limit/--offset for slicing and --format json|jsonl|csv|table for output.
When to prefer this pattern — apply your judgment based on the response characteristics, e.g.:
- High field count per record, or fields you don't need
- Batch/paginated results (multiple items per call)
- Long-text fields (descriptions, reviews, HTML, time series)
- Output reused across later steps rather than consumed immediately
For small, single-use responses, calling the main script directly is fine.
⚠️ The preview is a truncated schema + sample, not the full data. Any field-level decision must read from the persisted file via read.
For more high-quality, professional cross-border e-commerce skills, visit LinkFox Skills.