datawebotExtraction guide
From a storefront to price records
Inspect the relationship between products, variants and prices.
01 / INPUTPublic product or collection URL
02 / YOUR WORKFLOWVisit → parse → preserve relationships
03 / OUTPUTProduct records and nested variants
Keep the right fields.
Workflow field map| Field / step | Input | Rule |
|---|---|---|
| Product | Source ID + title | Keep the source namespace. |
| Variant | SKU + named options | A product can contain multiple prices. |
| Price | Decimal amount + currency | Retain nulls and source context. |
02 / Inspect the example
| Variant | SKU | Example price | Example availability |
|---|---|---|---|
| Small / Navy | DEMO-TEE-S-NV | USD 32.00 | Example: available |
| Medium / Navy | DEMO-TEE-M-NV | USD 32.00 | Example: available |
| Medium / Sand | DEMO-TEE-M-SD | USD 34.00 | Example: unavailable |
| Large / Navy | DEMO-TEE-L-NV | USD 32.00 | Example: unknown |
All names, identifiers, prices and availability values are fictional. They do not describe a merchant’s catalog or inventory.
Before you use the output
The saved result includes two visited pages: currency verification and the product response. Four variants do not mean four page credits.
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.