How to use the Product Taxonomy Mapper.
Use the actual destination taxonomy and its hierarchy. A plausible category label is not useful if it does not exist in the receiving catalog.
Make the workflow fit your task.
Read the destination taxonomy and map the product to the most appropriate supported path. Preserve category identifiers and explain ambiguous choices, avoiding plausible labels that do not exist in the target system.
- What you provide
- Catalog descriptions and supplied category tree.
- What you get
- Best-fit category mappings with uncertainty notes.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Target categories include Kitchen > Drinkware > Mugs. Product is a ceramic mug.
Completed example
Map to Kitchen > Drinkware > Mugs and retain the target category identifier if supplied.
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.
Should the deepest available category always be selected?
Choose the deepest category supported by the product facts and destination rules. Specificity without evidence can create a wrong classification.
Why does a sensible category name fail during import?
Check the exact destination identifier and hierarchy. A human-readable label may not match the value the receiving system expects.
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 ↑