datawebotFill catalog workflows with source-reported fields.
Collect product identity, text, images, variants and prices while preserving provenance and missing values.
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.
| Input | Review rule |
|---|---|
| Product and variant identifiers, SKUs and option values. | Do not overwrite authoritative catalog fields without review rules. |
| Source descriptions and image links where provided. | Keep inferred or generated values labeled separately from source data. |
| Prices, currency, availability and retrieval provenance. | Validate source permissions and image usage before publication. |
Turn an incomplete record into a reviewable proposal.
Every value in this exercise is fictional. The Example Outfitters record demonstrates how a missing brand or category becomes a proposal for review; it is not a merchant catalog, customer record or automated match.
Scroll to compare →
| Keep | Record | Decision |
|---|---|---|
| Internal catalog · fictional | SKU DEMO-TEE-S-NV; brand missing; category missing | Confirm product and variant identity before proposing a mapping. |
| Proposed brand | Missing → Example Outfitters (fictional vendor) | Preserve the input value alongside any normalized brand name. |
| Proposed category | Missing → Tops (fictional product_type) | Map to your own category only after reviewing its definition. |
| Price | 32.00 USD in the fictional record | This illustrates a separate observation field; it does not instruct a selling-price change. |
| Unreported attributes | Leave null | Do not infer materials, certifications or measurements from the title. |
| Review output | Field, previous value, proposed value, evidence and decision | Require an accepted mapping before writing to the authoritative catalog. |
Make uncertain matches visible.
A confidence score is useful only when its meaning is defined. This example uses explicit identity checks instead of inventing a numeric confidence value.
Scroll to compare →
| Keep | Record | Decision |
|---|---|---|
| Confirmed identity | Verified product URL + variant ID + SKU within the same source | Ready for field-level review. |
| Candidate identity | Similar title or image without a verified identifier | Hold for a person to check; do not overwrite the catalog. |
| Conflicting authority | Internal value differs from source value | Show both values and let the field owner choose. |
| Missing evidence | Source field or variant identity is absent | Keep the field unresolved and request the missing evidence. |
Content reviewed 2026-10-07.
Your enrichment layer can match records, choose trusted sources, normalize attributes and generate content. datawebot. does not fabricate missing specifications or merge sources into a golden record.