Units sold, last 30 days
listing.units_sold_30d≈ EstimatedUnifiedSoonOnly the marketplace knows the true number, and AIsa does not pretend to. One request returns each estimator's figure, how it was counted and how far apart they are.
Side by side
Up to three estimates in one call
One estimator answers by default. Ask for more and they're queried at once. You always get every raw figure and its method; the median, range and agreement are there if you ask. When the spread is too wide, the summary is a range, never a single number.
- one estimator, per query
- [$X]
- side by side, per query
- [$Y]
- estimators on amazon:US
- 6
How many units has B0DEMO1234 sold on Amazon US in the last 30 days? Ask three estimators and show me where they disagree.
One listing, three estimates
Example · amazon:US:B0DEMO1234 · 3-in-1 travel charger
- median
- 1,460
- range
- 1,180–1,920
- agreement
- medium
- inside Amazon's own band
- 3 of 3
| Source | Figure | Value type | Counted as | Read at | Bias here | |
|---|---|---|---|---|---|---|
| Jungle Scoutestimator | ≈ 1,180 | Estimated | units.ordered.rolling_30d | 06:10 UTC | [±N%] | |
| SellerSpriteestimator | ≈ 1,460 | Estimated | units.ordered.rolling_30d | 05:52 UTC | [±N%] | |
| Sorftimeestimator | ≈ 1,920 | Estimated | units.ordered.rolling_30d | 04:30 UTC | [±N%] | |
| Amazon badgereference · via Keepa monthlySold | 1K+ | Observed | amazon.bought_past_month | 06:02 UTC | reference |
Bias fills in from the first calibration report. The Amazon badge is only a reference: it is read off the listing, in coarse steps.
How AIsa counts it
metric units.ordered.rolling_30d · v1- Window
- Rolling 30 days, ending when read
- Time zone
- The marketplace's own; Pacific for amazon:US
- Currency
- None, these are units
- Counted at
- Units ordered, before returns and cancellations
- Channel
- All sales on the listing, not split by channel
- Counted for
- This variant (child ASIN), not the parent
- Method
- A third-party model's estimate
- Refresh
- Daily; lag published with the first calibration report
An estimator that counts another way, say after returns or for the whole parent listing, is filed as its own metric and shown beside this one. It is never folded in.
How far each estimator runs
Sales have no public answer key, so AIsa measures estimators against what the marketplaces publish themselves, and reports the gap by marketplace, category and price band.
- Amazon's “bought in past month” badgeObservedCoarse steps such as 100+ and 1K+, without returns or cancellations.
- TikTok Shop sold countObservedA running total. Two reads a week apart bound the week's sales.
- Sellers' own numbersReportedFrom sellers who connect their store. Used to check their own listings only, unless they agree to more.
| Estimator | Home & Kitchen | Electronics | Beauty |
|---|---|---|---|
| Jungle Scout | [±N%] | [±N%] | [±N%] |
| SellerSprite | [±N%] | [±N%] | [±N%] |
| Sorftime | [±N%] | [±N%] | [±N%] |
What it costs
- One estimator
- [$X] per query
- Two or three, side by side
- [$Y] per query
- Several marketplaces in one call
- Adds up per marketplace
You pay for the query and the comparison. No estimator is promised to be right.