---
title: "Scope an Amazon data request"
url: https://www.datawebot.com/blog/amazon-seller-data-extraction-guide
description: "Identify the offer you need before requesting extraction. Public product data does not provide a seller's private orders or inventory. This source requires an availability review; keep the exact URL in the request."
updated: 2026-09-14
author: datawebot team
---

Extraction guide

# Scope an Amazon data request

Identify the offer you need before requesting extraction.

Updated September 14, 2026 · datawebot team

[← All guides](https://www.datawebot.com/blog)Field map ↓Try the workflow ↗

01 / INPUT**Exact Amazon marketplace URL**

02 / YOUR WORKFLOW**Define product, seller and market**

03 / OUTPUT**Source-specific field requirements**

## Keep the right fields.

Workflow field map

| Field / step | Input | Rule |
| --- | --- | --- |
| Product | ASIN and selected variation | A parent product and child variation differ. |
| Offer | Seller, condition and fulfillment | Keep these separate from product identity. |
| Price | Currency and observation context | Coupons and shipping need separate evidence. |

## Before you use the output

Public product data does not provide a seller's private orders or inventory. This source requires an availability review; keep the exact URL in the request.

## Check one record first.

Start with the smallest useful scope. Compare the returned record with its source, confirm variant identity and inspect missing fields before applying the mapping to a larger dataset.

Keep extraction warnings and the retrieval timestamp with downstream output. When a required field is missing, leave it unresolved or return to the source; do not fill it from an assumption.

Working references [Product and variant schema ↗](https://www.datawebot.com/docs/data) · [Supported endpoints ↗](https://www.datawebot.com/scraper) · [Incomplete or unavailable results ↗](https://www.datawebot.com/docs/troubleshooting)

[Continue this workflow](https://www.datawebot.com/scraper/amazon)