An ASIN is useful identity evidence, but it does not by itself identify a marketplace offer. A product batch can contain the same ASIN from different national sites, ambiguous currency symbols and conflicting duplicate observations. Importing those rows under one bare key can overwrite valid differences or hide a source problem.
Amazon Catalog Variation Quality Auditor reads an existing product export and creates an assessment for each ASIN and observed marketplace scope. It preserves missing-value states, checks duplicate consistency and inspects supported variation references before a catalog import accepts the data.
Start with an observed marketplace URL
The example retains a shortened projection of the installed public historical snapshot. Price, stock and review values belong to that saved observation. The attributes list is deliberately shortened for illustration, so this example should not be presented as an exhaustive product specification.
{
"items": [
{
"asin": "B0FC5SJNQX",
"url": "https://www.amazon.com/dp/B0FC5SJNQX",
"title": "Logitech MX Master 4 Ergonomic Wireless Mouse with Haptics - Graphite",
"price": {
"value": 119.99,
"currency": "$"
},
"inStock": true,
"brand": "Logitech",
"attributes": [
{
"key": "Connectivity Technology",
"value": "Bluetooth, Radio Frequency, USB"
}
],
"stars": 4.3,
"reviewsCount": 2019,
"breadCrumbs": "Electronics > Computers & Accessories > Computer Accessories & Peripherals > Keyboards, Mice & Accessories > Mice"
}
],
"maxInputRows": 100,
"maxResults": 10
}
A verified product URL must reference the same ASIN on a supported marketplace host. The generated convenience URL used when evidence is missing does not establish where the source observed the offer. Keep canonicalUrlSource and marketScope beside the exported link.
Preserve price states
The assessment distinguishes a missing price field, an observed absent value, a literal zero, a usable price and an unparseable value. Those states support different import decisions. Replacing all of them with zero would manufacture a free offer from an export error.
Currency also needs evidence. A bare dollar symbol can be ambiguous. The output preserves the symbol while resolving an ISO currency only when the supported source evidence allows it. Keep the raw source projection and the assessment together rather than assuming that every symbol has the same monetary meaning.
Review duplicate conflicts before choosing a winner
Two rows sharing an ASIN and marketplace can disagree about price, stock or other catalog fields. A deterministic import should expose that conflict and send it to a review rule. Choosing whichever row happened to arrive last hides the reason a downstream price changed.
Preserve duplicateSourceRowCount and evidence indices. If the export contains different observation times, the receiving system can apply a separately documented freshness policy. The audit itself should not be described as a new source check merely because it processes a recent upload of old rows.
Treat variation coverage as its own claim
An absent variants field does not prove the product has no variations. The contract can qualify an otherwise complete assessment when variation scope was never captured. Parent references, malformed variation identities and duplicate entries also need their own inspection.
The currently selected ASIN appearing in its own variation list can be normal scraper output. A useful gate distinguishes that informational case from an actual hierarchy problem instead of rejecting every self-reference indiscriminately.
Stage assessments before replacing an accepted catalog. Require the states your application needs for monetary display, stock handling and variation navigation. Keep diagnostics for invalid rows and source coverage limits. The resulting import is easier to explain because its acceptance decision depends on explicit field and scope evidence, with a clear route for records that need another authorized collection or a human review.
Price and verification scope
Listing pricing read on 23 October 2026 is $0.015 per result-found event on the FREE tier. The documented unit is: One useful catalog assessment delivered with source evidence and a recommended next step. Source errors, invalid rows and budget diagnostics request no result event. Other platform tiers have their own rates. This pricing record has no separate start event. A usable result from an illustrative input can still be billable; inspect the applicable listing and run spending limit before executing it. maxResults is an output cap, separate from the platform's Max total charge option.
This article uses the installed source contract from build 0.1.2 (t1y4GVwth4cSw2MAZ). The example is a shortened historical source projection, with local pure-transform validation only. No new Apify cloud build or run was started for this article. Local output does not establish cloud delivery, customer acceptance or commercial results.
Inspect the Actor's current input and pricing.
AI-assisted draft; independent technical and cover review is required before publication.
Top comments (0)