01 / Direct answer
The short answer.
To validate ecommerce product demand, combine market demand, seller concentration, product economics, review barriers, historical pricing, and search-interest direction. Do not treat one sales estimate or trend chart as proof; define entry thresholds before ordering inventory.
- Screen the market before comparing individual listings.
- Require multiple independent demand and competition signals.
- Turn the shortlist into a small, measurable validation test.
02 / The problem
Why this decision is difficult.
A high sales estimate can reflect a mature, expensive market rather than an opportunity a new seller can enter.
Demand, seller density, price, margin, review depth, and search momentum often live in different tools and cannot be compared consistently.
Teams commit to samples, inventory, and ads before defining the evidence that would make a product worth testing.
02 / Market lens
18 demand regions, with coverage shown by signal
Google Trends provides the shared 18-region demand layer. Amazon coverage is narrower and is labeled separately for discovery, catalog, sales, and price-history research.
United StatesNew York
Discovery, catalog & TrendsCanadaToronto
Catalog, sales & TrendsMexicoMexico City
Catalog, sales & TrendsBrazilSão Paulo
Price history & TrendsUnited KingdomLondon
Catalog, sales & TrendsFranceParis
Catalog, sales & TrendsSpainMadrid
Catalog, sales & TrendsNetherlandsAmsterdam
Search-demand signalGermanyBerlin
Discovery, catalog & TrendsItalyMilan
Catalog, sales & TrendsPolandWarsaw
Search-demand signalSwedenStockholm
Search-demand signalTurkeyIstanbul
Search-demand signalUnited Arab EmiratesDubai
Search-demand signalIndiaMumbai
Catalog, sales & TrendsSingaporeSingapore
Search-demand signalJapanTokyo
Discovery, catalog & TrendsAustraliaSydney
Search-demand signalCoverage varies by API. The map labels the strongest verified signal available for each region; it does not imply every Amazon endpoint is available in all 18 regions.
04 / What data can answer
Use evidence that matches the question.
Start at market level. Compare category revenue, seller and brand concentration, new-product share, average price, ratings, BSR, and estimated margin before looking at individual listings.
Then move to product candidates. Filter by sales, revenue, review count, rating, price, listing quality, seller type, click growth, and conversion indicators. Use search-interest history as supporting evidence—not as proof of marketplace sales.
For shortlisted ASINs, compare historical price, promotions, Buy Box, BSR, seller count, rating, reviews, and daily sales estimates. A one-day snapshot cannot show whether a product is durable or temporarily boosted.
A strong candidate is not simply popular. It has enough demand, a realistic price and margin window, evidence of recent entry, and a weakness you can address in the product or offer.
05 / Practical workflow
Move from uncertainty to a bounded test.
- 01
Write an entry thesis: target market, price band, minimum margin, maximum review barrier, and the customer problem you intend to solve.
- 02
Screen category markets first, then shortlist products that fit the thesis instead of searching for a single “winning product.”
- 03
Compare marketplace demand with search-interest direction, then inspect price, BSR, seller-count, and sales history for shortlisted ASINs. Remove candidates supported by only one metric.
- 04
Save the evidence and define a small validation test before ordering inventory or increasing ad spend.
06 / Nexscope APIs
The live capabilities behind this workflow.
Amazon Market Research API
Screen Amazon category markets by size, concentration, seller structure, new-product share, price, rating, BSR, and margin ranges.
Market sizeSeller densityNew-product shareAmazon Product Discovery API
Find keyword-based product candidates using click growth, conversion, pricing, review, and profitability indicators.
Click growthConversion signalsProduct economicsAmazon Product Database API
Filter products across supported Amazon marketplaces by price, sales, revenue, reviews, rating, BSR, listing quality, and seller type.
Sales and revenueReviews and ratingListing qualityGoogle Trends Keyword API
Compare how search interest changes over time and across regions as a supporting demand signal.
Interest over timeRegional demandKeyword comparisonAmazon Product Price Series API
Validate shortlisted ASINs with historical price, promotion, Buy Box, BSR, seller-count, rating, review-count, and monthly-sold observations.
Price and promotion historyBSR historySeller changesAmazon Sales Estimates API
Compare day-level sales estimates and the last known price across supported Amazon marketplaces.
Daily sales estimatesLast known priceDate-range comparison07 / Common questions
Frequently asked questions.
- What data should I check before selling a product?
- Check market size, seller and brand concentration, price range, margin potential, sales history, review depth, listing quality, search-interest direction, and evidence that newer products can enter the market. Define acceptable thresholds before choosing a candidate.
- Is Google Trends enough to validate product demand?
- No. Google Trends shows relative search-interest direction, not marketplace sales or profit. Use it alongside product sales estimates, price history, seller density, reviews, conversion signals, and your own unit economics.
- How do I separate high demand from high competition?
- Compare demand with concentration and entry barriers. A market is more testable when demand is meaningful, revenue is not locked by a few brands, review counts are reachable, and recent products show traction at a viable price.
- When is a product ready for a small test?
- A product is ready when it meets your written thresholds for demand, margin, review barrier, price, and differentiation, and no single metric carries the thesis. Start with the smallest test that can validate customer response and unit economics.
“Compare product opportunities for my target keyword. Rank the markets by demand, competition, new-product share, price, reviews, growth, and margin signals, then explain which assumptions still need testing.”Open API documentation