---
title: "Enrich a catalog with source evidence"
url: https://www.datawebot.com/blog/product-data-enrichment-incomplete-catalogs
description: "Map reported fields into a catalog review queue. Do not match by title alone. Use a verified source identity and inspect variants. Generated descriptions and inferred attributes need separate labels and review."
updated: 2026-09-14
author: datawebot team
---

Extraction guide

# Enrich a catalog with source evidence

Map reported fields into a catalog review queue.

Updated September 14, 2026 · datawebot team

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

01 / INPUT**Existing SKU + source product record**

02 / YOUR WORKFLOW**Match → map → review**

03 / OUTPUT**Proposed 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. |

Synthetic catalog data · not a retrieval result

01 / Example record Fictional product

### Cotton Crewneck T-Shirt

`No source URL`

Products

1

Variants

4

Record origin

Synthetic

Page visits

Not applicable

[Field definitions](https://www.datawebot.com/docs/data)

02 / Inspect the example

Illustrative field mapping

`title`Cotton Crewneck T-Shirt

`brand ← vendor`Example Outfitters

`category ← product_type`Tops

`source_product_id ← id`example-product-001

`compare_at_price`38.00

Fictional values show field mapping only; review real source records before changing your catalog.

Illustrative schema · synthetic records

[Example CSV](https://www.datawebot.com/samples/catalogue-example.csv) · [Example JSON](https://www.datawebot.com/samples/catalogue-example.json) · [Use with an agent](https://www.datawebot.com/docs/agents)

## 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.

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/solutions/product-catalog-enrichment)