--- title: "Compare prices across retailers" url: https://www.datawebot.com/blog/track-competitor-pricing-multiple-retailers description: "Build a comparison only after confirming equivalent offers. Two stores in the sample selector demonstrate different records, not a like-for-like competitor match. Cross-source matching and exchange rates belong in your workflow." updated: 2026-09-14 author: datawebot team --- Extraction guide # Compare prices across retailers Build a comparison only after confirming equivalent offers. Updated September 14, 2026 · datawebot team [← All guides](https://www.datawebot.com/blog)Field map ↓Try the workflow ↗ 01 / INPUT**Source records from each retailer** 02 / YOUR WORKFLOW**Match variant → align basis → compare** 03 / OUTPUT**Price table with match evidence** ## Keep the right fields. Workflow field map | Field / step | Input | Rule | | --- | --- | --- | | Match | Brand, model and variant | Record ambiguous matches for review. | | Basis | Pack, condition and currency | Do not mix unit prices and bundle prices. | | Time | retrieved_at per source | Separate stale observations. | ## Before you use the output Two stores in the sample selector demonstrate different records, not a like-for-like competitor match. Cross-source matching and exchange rates belong in your workflow. ## 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/services/competitor-analysis)