How to use the Supplier Catalog Comparison Tool.
Catalog comparison needs an explicit matching key and change policy. Keep ambiguous matches separate from confirmed additions or removals.
Make the workflow fit your task.
Choose a stable matching key and align field meanings before comparing catalogs. Separate confirmed changes, additions, removals and ambiguous matches, retaining both old and new values for review.
- What you provide
- Two supplied catalogs and matching identifiers.
- What you get
- Added, removed and changed products with uncertain matches.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Current SKU A costs 10; supplier update lists A at 12 and new SKU B at 8.
Completed example
A: price changed from 10 to 12. B: new record. Confirm currency and effective date before updating.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Does an absent SKU always mean the supplier discontinued it?
No. The supplied update may be partial or filtered. Confirm coverage and the change policy before treating absence as removal.
Why are many records falsely appearing as new products?
Check key formatting, leading zeros and duplicate identifiers. Matching problems can look like widespread catalog changes.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑