datawebotExtraction guide
Enrich a catalog with source evidence
Map reported fields into a catalog review queue.
01 / INPUTExisting SKU + source product record
02 / YOUR WORKFLOWMatch → map → review
03 / OUTPUTProposed catalog field updates
Keep the right fields.
Workflow field map| Field / step | Input | Rule |
|---|---|---|
| Brand | vendor | Retain the source value before normalization. |
| Category | product_type | Treat as source taxonomy, not your final category. |
| Sale reference | compare_at_price | Keep null when the source provides none. |
02 / Inspect the example
Illustrative field mapping
titleCotton Crewneck T-Shirtbrand ← vendorExample Outfitterscategory ← product_typeTopssource_product_id ← idexample-product-001compare_at_price38.00Fictional values show field mapping only; review real source records before changing your catalog.
Before you use the output
Do not match by title alone. Use a verified source identity and inspect variants. Generated descriptions and inferred attributes need separate labels and review.
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.