datawebotIndependent source guide
Amazon product data extraction: ASINs, offers and prices
Plan Amazon product data extraction around ASINs, variations, seller offers and price observations. Check comparison fields and when authorized SP-API applies.
Model Amazon product, seller offer and price observation separately
Amazon defines an ASIN as the identifier for an item in its catalog. A selling-partner listing has its own seller-provided SKU and listing data. For price research, connect the catalog item to each seller offer, then record what was visible in a particular marketplace and at a particular time.
Scroll to compare →
| Record layer | Amazon fields to keep together | Do not infer |
|---|---|---|
| Marketplace view | Storefront domain, locale, currency and source URL as observed; keep marketplace ID only when an authorized data source supplies it. | A result on one country storefront is not the same offer or currency on another. |
| Catalog item | ASIN, title, brand, category and the parent/child relationship when Amazon exposes it. | A parent variation group is not a purchasable child offer. |
| Seller listing and offer | Seller display name, condition, fulfillment wording and seller SKU only in a seller-authorized record. | An ASIN does not identify one seller, condition or fulfillment promise. |
| Price observation | Displayed amount and currency, visible shipping or promotion, selected option, destination context and capture time. | One observation is not a historical transaction, guaranteed checkout total or current network-wide inventory. |
Fields to capture from an Amazon product page
Use this field map for a defined research request. Keep the source label and missing-value state with every field, and distinguish Amazon's catalog and seller APIs from a buyer-facing product page.
Scroll to compare →
| Field group | Useful fields | Interpretation rule |
|---|---|---|
| Catalog identity | ASIN, title, brand, category, main image URL and source URL. | Use ASIN for the catalog item; preserve title and brand as source text rather than a permanent identifier. |
| Variation | Child ASIN, selected color/size/model/pack option, and parent relationship when shown. | Compare the same child configuration. A variation family can group distinct purchasable items. |
| Seller offer | Seller name, item condition, fulfillment label and the displayed offer state. | Keep each seller's offer separate even when the ASIN is shared. Do not turn an availability phrase into a stock count. |
| Price and delivery | Displayed item amount, currency, visible shipping amount or wording, coupon/promotion label and delivery context. | Preserve conditional savings separately from the base amount; do not calculate a delivered total unless all components are visible. |
| Observation | Capture time, marketplace, selected option and exact product-page URL. | Use null or an explicit missing_fields entry when the page does not show a requested signal. |
Illustrative Amazon offer records: two sellers, one ASIN
Illustrative schema only. The identifiers, seller names, amounts and timestamps below are invented; no Amazon extraction was performed. The array shows why each seller offer needs its own record even when the catalog ASIN matches.
Example
[
{
"marketplace": "example-marketplace",
"asin": "B0EXAMPLE1",
"parent_asin": "B0EXAMPLE0",
"variation": { "color": "Example blue", "size": "Example size" },
"seller": "Example seller A",
"condition": "New",
"fulfillment": null,
"price": { "amount": "29.00", "currency": "USD" },
"shipping": null,
"observed_at": "2026-09-28T10:00:00Z",
"source_url": "https://www.amazon.example/dp/B0EXAMPLE1",
"missing_fields": ["fulfillment", "shipping"]
},
{
"marketplace": "example-marketplace",
"asin": "B0EXAMPLE1",
"seller": "Example seller B",
"condition": "New",
"fulfillment": "Seller fulfilled",
"price": { "amount": "27.50", "currency": "USD" },
"shipping": { "amount": "4.00", "currency": "USD" },
"observed_at": "2026-09-28T10:00:00Z",
"source_url": "https://www.amazon.example/dp/B0EXAMPLE1"
}
]Run four checks before comparing Amazon offers
A low price is useful only when the item and offer are comparable. Use these checks before calculating a price gap or adding an observation to a history.
Scroll to compare →
| Check | Pass when | Hold the comparison when |
|---|---|---|
| Marketplace and currency | Both records refer to the intended Amazon storefront and use the same currency basis. | The domain, locale or currency differs, or the amount's currency is unstated. |
| Catalog item and option | The ASIN and selected child configuration match, including model, size, color or pack quantity where relevant. | Only a similar title or parent group matches; a distinguishing option is missing. |
| Seller, condition and fulfillment | Seller, new/used condition and shipping basis are visible and either match or are deliberately analyzed as separate offer types. | One row is used, refurbished or seller-fulfilled while the other is a different offer type. |
| Price context and time | Base amount, visible promotion, shipping context and observation time are captured separately. | A conditional coupon, membership deal or unknown delivery charge is folded into the base price. |
Choose a public product page or an authorized Amazon API by the data owner
A shopper-facing page and the Selling Partner API answer different questions. Amazon's documentation separates catalog items from seller listings and requires the relevant role and authorization for seller-scoped operations. Check the exact operation and account scope before planning an integration.
Scroll to compare →
| Route | Good fit | Scope boundary |
|---|---|---|
| Public product page | The item, selected offer and delivery/price wording visible to a shopper on a specified storefront. | It does not expose a seller's private inventory, orders or reporting just because an item page is public. |
| Catalog Items API | Catalog attributes, identifiers, browse context and item relationships for supported Amazon marketplaces. | Keep this Amazon API’s catalog fields and required developer role or operation scope distinct from shopper-facing page observations. |
| Listings Items API | A selling partner or authorized application managing or reading that seller's own SKU listings. | A seller SKU is account-scoped listing identity, not a universal product identifier. |
| Product Pricing API | Seller-side pricing use cases documented for eligible, authorized applications. | Do not assume this API grants unrestricted access to every seller's data or public price history. |
What a public Amazon product page cannot establish
A product page is one view of a catalog item and offer at a particular time. Keep its limits visible when an analysis moves from storefront evidence to business conclusions.
Scroll to compare →
| Visible page signal | What it can support | What it cannot prove |
|---|---|---|
| Availability wording | The status shown for the selected view and time. | Exact seller stock, warehouse inventory, future availability or a completed sale. |
| Displayed price or featured offer | The offer and amount shown in that view, with its visible conditions. | All competing offers, an offer's full price history, or the buyer's final order total. |
| Product title and attributes | A source-attributed description of the catalog item or selected variation. | A perfect cross-retailer match when model, size, pack quantity or region differs. |
| Seller and fulfillment label | The seller and fulfillment information visible in that page view. | Private seller reports or exact order-level delivery costs for an unknown destination. |
Amazon product data questions analysts ask
These distinctions prevent the most common Amazon catalog and offer matching errors.
Scroll to compare →
| Question | Answer | Source basis |
|---|---|---|
| Is an ASIN the same as a seller SKU? | No. Amazon defines an ASIN for the catalog item; a selling partner SKU identifies a listing in that seller catalog. | Amazon SP-API terminology |
| Does one ASIN always mean one offer? | No. Multiple sellers or offer conditions can refer to one catalog item. Keep seller and offer context in separate records. | Amazon catalog and listing model |
| Can a public product page provide exact seller inventory? | A page may show availability wording, but that does not establish a numeric private stock count. | Public page observation limits |
| When should I consider SP-API? | When the task concerns a seller or vendor account, its listings or an authorized workflow; check Amazon role and operation requirements. | Amazon onboarding and operation docs |
Use the Amazon field map in a broader product-data workflow
Start with the source question, define the exact storefront and item, and keep each offer observation auditable. See datawebot's documentation for general request inputs and result fields.
Scroll to compare →
| Next step | Use it for | Relevant page |
|---|---|---|
| Amazon seller-data request checklist | Clarify the source URL, ASIN/variation, seller context and analysis question before requesting work. | /learn/amazon-seller-data-extraction-guide |
| Request input rules | Check which source URLs and limits a request can use. | /docs/inputs |
| Result fields and missing values | Read how data fields and unknown values should be interpreted. | /docs/data |
| Product price-history guide | Plan comparable, time-stamped observations rather than treating one page view as a trend. | /learn/build-product-price-history-database |
| Dynamic-pricing strategy | Use source evidence as an input to a repricing decision, separate from the seller’s authorized price controls. | /solutions/dynamic-pricing-optimization |
| Walmart item and seller offers | Compare another marketplace’s item/offer model when the research spans retailers. | /scraper/walmart |
Content reviewed 2026-10-07.