Amazon Review Defect Finder
Pricing
from $15.00 / 1,000 defect cluster founds
Paste an Amazon product URL and see which complaints are real patterns. It fetches the critical reviews and returns each recurring fault, how many separate reviewers named it, how many times it was mentioned, the first and last date seen, the worst star rating, and their exact words.
Paste one or more Amazon product URLs and this fetches the critical reviews itself, then builds the ledger. Only 1-3 star reviews are fetched, so you are not billed for reviews that cannot produce a finding. The fetch runs a separate review-scraper Actor on YOUR account and its publisher bills you for that run, on top of this one. Leave blank if you already have review data and are using the fields below instead. Left empty, this Actor runs on the worked example below so you can see a real ledger for free before spending anything.
Caps how many CRITICAL reviews are fetched. Five-star reviews are never requested, so this is the number the review scraper bills you for. On a free Apify plan the scraper returns at most 10 whatever you set here. Only applies when you give a product URL.
Which Store Actor fetches the reviews. The default is the most used Amazon review scraper on the Store. Change it if you prefer another; it must return objects carrying the review text, a rating, a reviewer id and a date.
Array of review objects, each with the text under text or reviewDescription, the score under rating or ratingScore, plus userId and date. Supply these OR reviewsDatasetId. Accepts output from any Amazon review scraper or a manual export. Arrives filled with a worked example, so pressing Start produces a real ledger before you change anything.
[ { "userId": "R1", "date": "2026-03-02", "ratingScore": 2, "reviewDescription": "The left earbud stopped charging after about four months. Case shows it at 100% but it is dead." }, { "userId": "R2", "date": "2026-03-19", "ratingScore": 1, "reviewDescription": "Left bud stopped charging completely around month five. Right one is fine." }, { "userId": "R3", "date": "2026-04-07", "ratingScore": 2, "reviewDescription": "Battery died on the left earbud after four months of light use. Very disappointing." }, { "userId": "R4", "date": "2026-02-11", "ratingScore": 1, "reviewDescription": "Case hinge snapped in my pocket within a few weeks. The plastic is far too thin." }, { "userId": "R5", "date": "2026-05-02", "ratingScore": 2, "reviewDescription": "The hinge on the charging case broke after about three weeks of normal use." }, { "userId": "R6", "date": "2026-05-14", "ratingScore": 1, "reviewDescription": "Hinge cracked and now the case will not stay shut at all." }, { "userId": "R7", "date": "2026-01-30", "ratingScore": 3, "reviewDescription": "Did not like the colour, it is more grey than silver in person." }]Instead of pasting reviews, give the dataset ID of a run that produced them — for example an Amazon Reviews Scraper run. Items are read from that dataset and used as the reviews. This is what makes the Actor chainable: in an Integration, set this to {{resource.defaultDatasetId}} and a scraper run will feed this one automatically. Leave blank if you are supplying reviews directly.
A defect must be named by at least this many DISTINCT reviewers to appear in the ledger
Human-readable product label for the ledger entries
Copied onto every row so you can click back to the product. Only needed when you supply reviews yourself — if you gave a product URL above, that one is used automatically. Never fetched: this Actor does not guess which Amazon marketplace your reviews came from, so a link it invented would be wrong for every .co.uk, .de and .co.jp set.