Amazon Product Data: What It Includes and How to Use It

What Amazon Product Data Actually Contains

Amazon product data is the machine-readable record of a listing as the marketplace presents it. It has two layers: a catalog layer describing the item itself, and an offer layer describing the commercial terms attached to it at a given moment. Keeping them separate enables historical comparison.

The catalog layer holds identity, brand, title, images, dimensions, category placement and variation structure. The offer layer holds price, list price, buy box owner, stock state, coupon and deal badges. Price and availability move faster than titles or categories, so every record should carry a collection timestamp.

Which ASIN Detail Fields You Can Collect

A full ASIN payload from addAsinTask goes well beyond a price and a rank. It returns identity, customer signals, commercial terms, ranking positions, content blocks such as fivePoint, description and aplus, physical attributes including dimensions and productInformation, and relationship data through variantAsin and relateMap.

Four fields are easy to overlook and hard to reconstruct later. bought estimates monthly sales volume, newOnAmz flags items listed within the last month, stockState reports availability, and bs and newReleases show list membership. Definitions for every attribute appear in the ASIN field reference.

How to Get Amazon Product Data

Manual collection stops scaling after a few hundred items. Building your own collector means running proxies, parsers and layout detection across 23 marketplaces, where every front-end change becomes your incident. Buying raw files from a delivery service moves that burden to the provider while analysis, storage and modelling stay with you.

The API model is plain by design. You submit tasks to https://ksicdata.com/api with your ks-token header, and results arrive as raw JSON files over FTP, SFTP or cloud storage. Each request carries up to 2,000 items, and the pipeline refreshes tens of millions of records daily. See the API documentation.

• addAsinTask: detail data for a list of ASINs
• addKeywordTask: keyword search result pages, first three pages
• addBsr100Task: top 100 of a Best Sellers or New Releases list
• addCategory400Task: category listings up to 400 pages, extracting ASINs
• addSellerTask: seller store information such as rating and address
• addSellerAsinTask: the ASIN list of a seller store

Using Product Data for Sourcing and Pricing

Sourcing works best as a ranking problem. Ratings count, review volume, mainRank, estimated monthly sales and the number of competing offers let a team score hundreds of candidates by momentum instead of intuition. Adding newOnAmz and newReleases to the same model highlights categories where recent listings are still gaining traction.

Pricing is more operational. A daily snapshot of price, listPrice, buybox, coupon and deal shows who holds the buy box, how deep promotions run and how quickly competitors react. Because raw JSON keeps seller and offer context, repricing logic can be tested against real history. See product data solutions.

Competitor and New-Listing Monitoring

At catalog scale, competitor analysis becomes a diffing problem. Collect a fixed ASIN set on a schedule, store every snapshot and compare consecutive versions. New variants, changed dimensions, added A+ content, a fresh coupon or a move between category nodes all appear as field-level differences that are simple to alert on.

Seller-level data completes the picture. Store ratings and addresses from addSellerTask, combined with the ASIN list returned by addSellerAsinTask, show when a competitor's assortment expands or contracts. That pairing also powers new-listing monitoring: when a tracked store publishes an ASIN, it appears on the next collection cycle. More: competitor analysis solutions.

Marketplace Coverage and Practical Limits

Coverage spans all 23 Amazon marketplaces, from US, DE, UK and JP to smaller regions such as SG, TR and ZA. Accuracy is maintained at 99.9 percent and the pipeline runs continuously rather than in one-off exports. Free data samples let you inspect real payloads before committing to a schema.

Two limits deserve planning. Some attributes do not exist in every marketplace, so downstream code must treat optional fields as optional; presence also varies by category and listing type. A short pilot against your own ASIN list, using the ASIN listing data service, confirms exactly what you will receive.

FAQ