SuperAPI AI Directory

linkfox-sorftime-product-search

Marketing & growth

View repository

Updated 10-16 00:00

About this skill

Sorftime Product Search

This skill guides you on how to search and filter Amazon products via Sorftime across multiple dimensions, helping Amazon sellers discover products, analyze competitors, and explore market opportunities.

Core Concepts

Sorftime Product Search supports multi-dimensional product retrieval with 16 query types, single or multi-condition AND combinations, and historical monthly snapshot lookback from January 2024. Data covers pricing, BSR rankings, monthly sales, FBA fees, and profit analysis.

Key differentiator: This tool is for searching and filtering across products. If you need detailed trend data (sales/price/BSR history) for a specific ASIN, use the Sorftime Product Detail skill instead.

Data Fields

Field API Name Description Example
ASIN asin Amazon Standard Identification Number B0CVM8TXHP
Product Title title Product listing title Anker Portable Charger...
Brand brand Brand name Anker
Current Price price Price before Coupon, local currency (e.g., USD) 29.99
Sale Price salesPrice Actual selling price after Coupon, local currency 25.99
Strikethrough Price oldPrice Original list price, local currency 39.99
Coupon coupon >0 = discount amount (500=$5); <0 = percentage (-10=10% off) -15
BSR Rank salesRank Best Seller Rank in main category 1523
Monthly Sales monthlySalesUnits 30-day sales volume (Listing level); -1 = cannot estimate 4500
Monthly Revenue monthlySalesRevenue Estimated monthly revenue, local currency; -1 = N/A 116955.00
Daily Sales listingSalesVolumeOfDaily Daily sales volume; -1 = cannot estimate 150
Daily Revenue listingSalesOfDaily Daily revenue, local currency; -1 = N/A 3898.50
Rating rating Current rating (0.0-5.0) 4.70
Rating Count ratings Number of ratings 12580
Listing Date availableDate Listing date (yyyy-MM-dd) 2022-03-15
Days Online onlineDays Days since listing 850
FBA Fees fbaFees FBA fulfillment fee, local currency 5.40
Platform Fee platformFee Platform commission, local currency 3.90
Profit profitAmount Sale price - FBA - commission, local currency 16.69
Profit Rate profitRate Profit margin, e.g., 25.83 = 25.83% 25.83
FBA Status isFBA Whether Buybox seller uses FBA true
Buybox Seller buyboxSeller Buybox winning seller name AnkerDirect
Seller Country buyboxSellerAddress Seller country code (CN, US); null if Amazon-operated CN
Seller ID buyBoxSellerId Buybox seller ID A294P4X9EWVXLJ
Category category Main category [name, NodeId] ["Cell Phones", "2811119011"]
Sub-category bsrCategory Sub-category rankings list [{nodeId, name, rank, date}]
Variations variationNum Number of variations 5
Parent ASIN parentAsin Parent ASIN if has variations, null otherwise B0088PUEPK
Weight weight Weight in grams 350
Size size Dimensions in cm [longest, 2nd, shortest] [18.5, 8.2, 3.1]
Main Image imageUrl Main product image URL https://...
Listing URL asinUrl Amazon product page URL https://www.amazon.com/dp/...

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_search.py directly to run queries.

How to Build Queries

The key parameters are marketplace (required), queryMode, queryType, and queryValue. The query system has two modes and 16 filter types that can be combined flexibly.

Principles for Building Queries

  1. Always specify the marketplace: Use lowercase site codes, e.g., us, de, jp
  2. Choose the right query mode: Use queryMode=1 for a single filter; use queryMode=2 to combine multiple filters with AND logic
  3. Match queryType with queryValue format: Each queryType expects a specific format — see the table below. Mismatched formats will cause errors
  4. Mind price units: Price filters (queryType=8) use smallest currency unit (cents for USD), so $19.99 = 1999
  5. Use open ranges when appropriate: Omit one end for open range — ,1000 means "up to 1000"; 100, means "100 or more"
  6. Use queryMonth for historical comparison: Format yyyy-MM; compare with a second call without queryMonth to see changes over time

Query Types (queryType, for queryMode=1)

queryType Name queryValue Format Example
1 ASIN Similar ASIN B0CVM8TXHP
2 Category NodeId 3743561
3 Brand Brand name Anker
4 Seller Name Store name AnkerDirect
5 Seller ID SellerId A294P4X9EWVXLJ
6 ABA Keyword Keyword Power Bank
7 Title/Attribute Match Keywords 10,000mAh 30W
8 Price Range min,max (in cents) 1,1000 (=$0.01~$10)
9 Monthly Sales Range min,max 100,1000
10 Seasonal Products Month list 1,2,3 (peak in Jan-Mar)
11 Listing Date Range start,end (yyyy-MM-dd) 2024-06-01,2024-12-01
12 Rating Range min,max 3,5
13 Review Count Range min,max 10,500
14 Rank Range bsr_min,bsr_max;sub_min,sub_max 500,5000;1,100
15 Fulfillment FBA / FBM FBA,FBM
16 Variation Count min,max 1,50

Important: queryType=1 (ASIN Similar) finds products similar to the given ASIN, not the ASIN itself. To query a single product's detail, use the Sorftime Product Detail skill.

Historical Snapshots (queryMonth)

Set queryMonth (format yyyy-MM) to query a past month's product data snapshot. This lets users compare historical prices, rankings, and sales with current data.

  • Supported range: January 2024 to present (~2 years)
  • US, GB, DE support full "unlimited" lookback mode
  • Other sites support Top 100 products only in lookback
  • AU, BR, IN do not support lookback

Query Examples for Common Scenarios

1. Find competitors of a given ASIN

queryMode: 1, queryType: 1, queryValue: B0CVM8TXHP, marketplace: us

2. Browse a category's top products

queryMode: 1, queryType: 2, queryValue: 3743561, marketplace: us

3. Analyze a brand's product portfolio

queryMode: 1, queryType: 3, queryValue: Anker, marketplace: us

4. Search by ABA keyword

queryMode: 1, queryType: 6, queryValue: Power Bank, marketplace: us

5. Discover seasonal products (Q4 peak)

queryMode: 1, queryType: 10, queryValue: 10,11,12, marketplace: us

6. Compare historical vs current data

queryMonth: 2024-11, queryMode: 1, queryType: 2, queryValue: 3743561, marketplace: us
→ Compare with current data (no queryMonth) to see price/sales changes

7. Multi-condition: new FBA products with good sales

queryMode: 2
queryValue: [{"QueryType":11,"Content":"2024-06-01,"},{"QueryType":9,"Content":"300,"},{"QueryType":15,"Content":"FBA"}]
marketplace: us

8. Find low-price high-sales products

queryMode: 2
queryValue: [{"QueryType":8,"Content":",2000"},{"QueryType":9,"Content":"500,"}]
marketplace: us

9. Check a seller's product portfolio

queryMode: 1, queryType: 4, queryValue: AnkerDirect, marketplace: us

Display Rules

  1. Present data only: Show query results in clear tables without subjective business advice
  2. Ranking clarification: When showing ranking data, remind users that lower values mean better rankings
  3. Pagination notice: Search results return max 100 products per page, up to 200 pages. If results are large, show highlights and remind users to paginate
  4. Sales estimation caveat: Values of -1 in sales/revenue fields mean "cannot estimate" — explain this to the user rather than showing -1 directly
  5. Error handling: When a query fails, explain the reason based on the msg field and suggest adjusting query criteria

Important Limitations

  • Pagination: Max 100 products per page, max 200 pages
  • Historical lookback: Only from January 2024; AU, BR, IN not supported
  • Non-structured data: Results do not support secondary analysis via _dataQuery_executeDynamicQuery
  • Sales estimation: Products in non-standard categories may return -1 for sales fields
  • ABA keyword search (queryType=6): Currently only supports ABA keywords, not arbitrary search terms

User Expression & Scenario Quick Reference

Applicable - Product search and filtering on Amazon:

User Says Scenario
"Find products that sell well in this category" Category exploration
"What are Anker's best-selling products" Brand analysis
"What are the competing products for this ASIN" Competitor discovery
"Help me find some seasonal products" Seasonal product discovery
"Which new products have monthly sales over 500" Filtered product discovery
"The price snapshot for this category during last year's Double 11" Historical snapshot comparison
"What other products does this seller sell" Seller portfolio
"Help me filter FBA products with a profit margin above 30%" Profit-focused filtering
"Products with monthly sales above 1,000 and a rating of 4 stars or higher" Multi-condition filtering
"Products whose titles contain wireless charger" Title keyword search

Not applicable - Needs beyond product search:

  • Detailed trend/history data for a specific ASIN (use Sorftime Product Detail)
  • 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 "competitor analysis" or "market research", if they need to discover and compare products across dimensions (category, brand, price range, etc.), this skill applies. If they need historical trend curves for a specific ASIN, use the Product Detail skill. If they need keyword search volume data, use ABA Data Explorer.

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.

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_search.py --out-dir <DIR> '<params>'
python scripts/response_io.py read <file> --fields "<paths>"   # or --path "<JMESPath>"

Pick --out-dir outside 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.