Amazon list monitoring
Track Amazon Best Sellers lists.Spot category shifts earlier.
Capture Best Sellers and New Releases on a schedule, detect new entries, climbers, and exits, and route category changes into product research and operations.
- No credit card
- 13 Amazon marketplaces
- Two documented list parsers
2 candidates moved from New Releases to Best Sellers
Send to Lark →Trusted by 2,000+ ecommerce and development teams
Why continuous tracking
One list is a result. A sequence of snapshots reveals the opportunity window.
Lists shift with sales, seasonality, promotions, and new launches. What matters is who just appeared, who keeps climbing, and who is dropping out.
Catch an ASIN the first time it enters a list
Match the current list to the previous snapshot and review new entrants instead of rescanning everything.
Separate a one-off jump from sustained momentum
Compare multiple positions under the same list, category, and marketplace to filter short-lived noise.
Add product, review, and price evidence before deciding
Use list changes to discover candidates, then validate them with product details and review evidence.
Know the metric
List position, BSR, and keyword rank are not the same metric
This page focuses on membership and position changes in Best Sellers and New Releases. Clear boundaries prevent wrong conclusions and keep each solution page focused.
Need BSR and price tracking for individual ASINs? See ranking and price monitoring →List position
An ASIN’s position and membership status in a specific Best Sellers or New Releases list.
Answers: how is the list changing?BSR / category rank
A relative category sales rank shown on a product page; one product can have several category ranks.
Answers: how is one product performing?Keyword search position
An ASIN’s organic or sponsored position for a query; it is different from list position.
Answers: where is search visibility?Monitoring challenges
The hard part is not opening a list. It is making every run comparable.
Category, list type, marketplace, and collection time must remain explicit; entries, exits, and position deltas are calculated across snapshots.
Category depth defines the competitive set
A department and a subcategory are different markets. Keep the category name or node context with every target.
Each list type answers a different question
Best Sellers reflects current popularity; New Releases is better for watching launches and early momentum.
A new entry needs a previous snapshot
One response shows the current list. Entries, exits, and position changes require stored snapshots.
A list item is not a full product record
After discovery, enrich candidates with price, rating, reviews, brand, and product details.
Local context affects comparability
Marketplace and delivery ZIP can affect page content. Keep the same market context across runs.
List movement can create alert noise
A useful Top N, persistence rule, and review criteria matter more than alerting on every move.
From list to change feed
Store list facts first, then calculate actionable changes
Pangolinfo returns the current list as structured data. Tracker, Lark Base, or your database stores snapshots, compares deltas, and triggers rules.
CURRENT LIST
Record what is on the list and where it appears
Keep returned fields such as ASIN, title, and current position. Confirm exact fields against a live response.
- asinB0E2••••N7
- titleCompact storage rack
- position#07
- price$29.99
REQUEST CONTEXT
Keep every list snapshot in the same market context
Store list type, category, marketplace, ZIP code, and collection time with the result.
- parserNameamzBestSellers
- categoryHome & Kitchen
- site / zipcodeamz_us · 10041
- collectedAt10:32 UTC
DERIVED DELTAS
Derive entries, exits, and position deltas across snapshots
These are derived fields from consecutive snapshots, not facts returned by a single page request.
- firstSeenAt2026-09-13
- positionDelta+23
- listStatusNEW_ENTRY
- consecutiveRuns3
Configure a list monitor
Choose a list and category. Let scheduled runs find the changes.
This interactive builder illustrates a typical workflow; it does not submit or store input.
From change to decision
Every list event should answer a business question
Do not alert on every move. Define the decision first, then combine lists, product details, reviews, and persistence.
NEW ENTRY
See the new entry first, then wait for persistent evidence
Compare the current list with the previous snapshot, isolate first-time ASINs, and use repeat appearances to filter one-off noise.
- Record first-seen time
- Check whether it stays listed
- Connect New Releases with Best Sellers
Previous—
→Current#37
POSITION MOMENTUM
Sustained progress says more than a single jump
Confirm direction across several snapshots, then add price, review growth, and launch timing to explain it.
- Set a position-change threshold
- Require the rule across several runs
- Reduce promotion-driven false positives
Improved across five runs
CATEGORY LANDSCAPE
Use entries and exits to see who is reshaping the category
Aggregate brand, price band, rating, and launch timing across the list to expose competition and structural shifts.
- Measure brand and price-band distribution
- Compare new-product share and time on list
- Find less commoditized niche openings
New-product share18%
Median price$29.90
Brands31
ConcentrationMedium
PRODUCT VALIDATION
Use lists to discover and product evidence to qualify
Enrich candidate ASINs with product, review, and price data so researchers can apply their own rules.
- Collect product details and core attributes
- Add ratings, review counts, and review themes
- Configure filters in Lark Base
Two implementation paths
Choose the right Amazon list-monitoring path for your team
Business teams can start with Tracker; developers can route list data into products and pipelines through the API.
AMZ Data Tracker
With AMZ Data Tracker, choose a list, category, fields, and schedule, then send consecutive snapshots into Lark or recurring research workflows.
- Configure list tasks visually
- Store snapshots on schedule
- Customize fields and business rules
- No access or parsing code to maintain
Product research · Brand ops · Market analysis
Amazon Scraper API
With Amazon Scraper API, retrieve current lists with `amzBestSellers` or `amzNewReleases`, while your system owns scheduling, storage, delta logic, and notifications.
- Structured JSON output
- Synchronous and asynchronous modes
- 13 Amazon marketplaces
- Fits SaaS, ERP, and internal systems
Developers · Data products · Automation
Want AI to analyze candidates?After collection, use Amazon Data MCP or Amazon Scraper Skill to bring list and product evidence into agent workflows.
Workflow example
Send list opportunities into Lark Base automatically
AMZ Data Tracker collects and structures lists on schedule. Your workspace stores snapshots, calculates entries and position changes, and owns filters, permissions, automation, and AI analysis.
- Stop copying Top 100 lists every day
- Keep first-seen time for every candidate
- Route only rule-qualified opportunities
This example illustrates list data flowing into Lark; illustrative data is not presented as a customer result.
Before you start
Amazon list monitoring FAQ
Define list type, category depth, and collection frequency before deciding how to store snapshots and trigger rules.
Need technical details? Read the docs →How do Amazon list position and BSR differ?
List position is where an ASIN appears in a specific Best Sellers or New Releases list. BSR is a relative category sales rank on the product page. They are related but not identical. For individual-ASIN BSR and price, see ranking and price monitoring.
Which lists do the documented parsers support?
Pangolinfo documentation explicitly lists `amzBestSellers` and `amzNewReleases` for category-based Best Sellers and New Releases data. Test other page types with a live URL or confirm support before relying on them.
Does the API directly return “new entry”?
A single run returns the current list. New entries, exits, first-seen time, and position deltas are calculated by matching the result to earlier snapshots in Tracker, Lark, or your database.
How often should I collect a list?
Frequency depends on decision speed, category volatility, and cost. Start launch discovery daily or every 6–12 hours; use daily or weekly runs for long-term category research. Test one category before tuning thresholds.
Which Amazon marketplaces are supported?
Documentation lists 13 marketplaces: US, Germany, UK, Japan, France, Italy, Spain, Canada, Australia, Mexico, Saudi Arabia, UAE, and Brazil. Actual list and category availability depends on the target marketplace.
Can I enrich candidates with product details and reviews?
Yes. Use lists for discovery, then enrich candidates with product and review parsers for price, rating, review count, brand, and attributes.
How should I choose between Tracker and Scraper API?
Choose AMZ Data Tracker for no-code scheduled tasks and Lark workflows. Choose Amazon Scraper API for SaaS, ERP, databases, or custom alerting. Either path can be used independently.
Can I test a real category for free?
Yes. Create a list task in Tracker or register for the API, test a real list URL, marketplace, and category, then choose fields, frequency, and plan.
Start with one real category
Stop refreshing lists. Let new entrants and climbers surface themselves.
Create one list Tracker to validate the category, fields, and snapshot deltas. Move to Scraper API when the data needs to enter your product or pipeline.
