Amazon new product monitoring
Detect new Amazon products. Validate them before the market catches up.
Scan New Releases, target categories, or competitor storefronts on a schedule, identify first-seen ASINs, and enrich them with product, price, and review evidence.
- No credit card
- 13 Amazon marketplaces
- New Releases, category, and seller sources
2 first-seen products persist with low review counts
Send to Lark →Trusted by 2,000+ ecommerce and development teams
Why continuous tracking
Finding a new product is the start. Validation is what reduces false positives.
“First seen” does not mean “worth launching.” A useful workflow explains where a product appeared, what demand evidence exists, and how it performs next.
Catch an ASIN the first time it appears in a target source
Compare New Releases, category, or seller lists with the previous snapshot and mark first-seen ASINs automatically.
Use consecutive snapshots to see whether a new product keeps growing
Track price, reviews, rating, and BSR over time to separate short exposure from sustained progress.
Turn a new-product signal into a comparable candidate record
Add first-seen time, product details, reviews, and price before routing a candidate to researchers.
Know the metric
“New product” has at least three meanings—define yours first
A product may be new to New Releases, newly present in a category or seller list, or simply new to your tracker. Those are different facts.
Need to monitor BSR and price after discovery? See ranking and price monitoring →First seen in category
Compare category product lists over time to identify ASINs absent from the prior snapshot.
Answers: what just appeared in the category?Seller / storefront launches
Compare a target seller’s public product list to see newly added products and expansion direction.
Answers: what is a competitor launching?First tracked time
The time your workflow first sees an ASIN is not necessarily its official Amazon creation date.
Answers: when did we start observing it?Monitoring challenges
The hard part is not finding a few new products. It is proving when they appeared and whether they matter.
Discovery source, target category or seller, marketplace, and collection time must stay explicit. “New” is calculated across snapshots, not guessed from one page.
The source defines what “new” means
New Releases, category pages, and seller lists have different coverage. Configure and label each source separately.
First seen is not the same as launch date
Amazon pages may not expose an exact creation date. Record firstSeenAt honestly instead of inferring an official launch date.
New-ASIN detection needs a baseline
The first run creates a baseline. Relative additions become reliable from the next snapshot onward.
A new listing is not a product decision
Enrich price, rating, reviews, brand, variants, and BSR before judging competition or quality.
Parent-child ASINs and variants create duplicates
One product may surface through several child ASINs. Deduplication should match your research model.
Large scans create noisy candidate queues
Brand, price band, rating thresholds, and repeat appearances should filter candidates before alerts fire.
From discovery record to product evidence
Store where a product was found, then decide whether it deserves follow-up
Pangolinfo returns current New Releases, category, or seller lists. Tracker, Lark Base, or your database stores snapshots, detects additions, and enriches candidates.
DISCOVERY RECORD
Record where a new product was first discovered
Keep ASIN, title, source, and page position. Confirm exact fields against a live response.
- asinB0E2••••N7
- titleCompact storage rack
- sourceNew Releases
- price$29.99
REQUEST CONTEXT
Keep the source and market context consistent
Store parser, category or seller target, marketplace, ZIP, and collection time with every result.
- parserNameamzNewReleases
- targetHome & Kitchen
- site / zipcodeamz_us · 10041
- collectedAt10:32 UTC
DERIVED DELTAS
Put relative additions and early performance in one record
firstSeenAt, isNew, and repeat count are derived across snapshots; reviews and BSR come from detail enrichment.
- firstSeenAt2026-09-13
- firstSourceNew Releases
- isNewtrue
- consecutiveRuns3
Configure a new-product monitor
Choose a discovery source. Let scheduled runs find first-seen ASINs.
Start with New Releases, a category, or a seller list. This demo does not submit or store input.
From change to decision
Every new-product signal should pass a validation rule
Do not send every first-seen item to the team. Use source, persistence, and product evidence to decide the next step.
NEW ENTRY
Watch a target seller for new products and expansion direction
Compare a seller’s public product list over time, record first-seen ASINs, and enrich brand, category, and price.
- Detect additions to the seller list
- Group launches by brand and category
- Assign qualified items to competitor research
PreviousNot seen
→CurrentB0E2••N7
CATEGORY INFLUX
Measure new-product volume against the size of the category
Track additions, brands, and price bands within a fixed category to separate one launch wave from a structural change.
- Count new ASINs by period
- Compare brands and price bands
- Find where commoditization is rising
New-product volume rose this week
NEW RELEASES
Use New Releases to discover, then product data to qualify
New Releases provides a discovery source; reviews, price, attributes, and later BSR show whether a candidate matters.
- Record time of New Releases appearance
- Enrich details and review fields
- Watch for stronger demand signals
Reviews18
Current price$29.90
Rating4.6
BSR#18,420
PRODUCT VALIDATION
After first discovery, monitor early product performance
Track price, rating, review count, and BSR over time to separate short exposure from genuine growth.
- Record first seen and days observed
- Track review growth and rating stability
- Route unusual growth to researchers
Two implementation paths
Choose the right Amazon new-product monitoring path for your team
Business teams can configure discovery and validation in Tracker; developers can build new-product databases and alerts with the API.
AMZ Data Tracker
With AMZ Data Tracker, choose New Releases, category, or seller sources, then send new ASINs and detail fields into Lark or recurring research workflows.
- Configure discovery sources visually
- Detect relative additions automatically
- Enrich product and review fields
- No access or parsing code to maintain
Product research · Brand ops · Market analysis
Amazon Scraper API
With Amazon Scraper API, use amzNewReleases, amzProductOfCategory, or amzProductOfSeller to retrieve current lists while your system owns snapshots, delta logic, enrichment, 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 screen new-product candidates?Once discovery and validation fields are ready, use Amazon Data MCP or Amazon Scraper Skill to bring new-product records and evidence into agent workflows.
Workflow example
Send new-product signals into Lark Base automatically
AMZ Data Tracker collects source lists and enriches product fields. Your workspace stores first-seen time, filters candidates, assigns owners, and runs AI analysis.
- Stop checking categories and storefronts manually
- Keep source and first-seen time for every candidate
- Filter and assign candidates with your own rules
This example illustrates new-product data flowing into Lark; illustrative data is not presented as a customer result.
Before you start
Amazon new product monitoring FAQ
Define the discovery source, target scope, and qualification criteria before choosing frequency, enrichment fields, and alerts.
Need technical details? Read the docs →What does “new product” mean on Amazon?
A product may be new to New Releases or newly present in a category or seller list relative to the previous snapshot. The page’s firstSeenAt value records when your workflow discovered it—not necessarily Amazon’s official creation date. For later BSR and price, see ranking and price monitoring.
Which sources can be used to discover new products?
Documentation lists amzNewReleases, amzProductOfCategory, and amzProductOfSeller for current New Releases, category, and seller product data. Scheduled comparisons identify relative additions.
Does the API directly return a “new product” flag?
A single run returns current page or list facts. Relative additions, first-seen time, and repeat count are calculated across snapshots in Tracker, Lark, or your database.
How often should new-product monitoring run?
Frequency depends on how quickly the source changes and how fast the team acts. Start priority sellers or categories daily or every 6–12 hours; use weekly runs for slower categories.
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 category, seller-page, and New Releases availability depends on the target marketplace.
What can be added after a new product is found?
Enrich title, images, price, brand, attributes, rating, review count, BSR, and review data through product-detail and review collection. Confirm exact fields and cost with a live response.
How should I choose between Tracker and Scraper API?
Choose AMZ Data Tracker for no-code scheduled discovery and Lark workflows. Choose Amazon Scraper API to build a new-product database, SaaS, ERP integration, or custom alerting.
Can I test a real discovery source for free?
Yes. Choose a real New Releases page, category, or seller target in Tracker, validate the first snapshot and detail fields, then choose frequency, rules, and plan.
Start with one real discovery source
Stop checking categories and storefronts. Let new-product signals enter your candidate queue.
Create one new-product Tracker to validate the source, fields, and first-seen logic. Move to Scraper API when you need your own database or product integration.
