How to use the Product Attribute Normalizer.
Normalize values against a supplied vocabulary while retaining the original. A mapping decision should remain reviewable when several interpretations are possible.
Make the workflow fit your task.
Define the approved vocabulary and mapping rules, then preserve each original value beside its normalized form. Apply known mappings consistently and route ambiguous terms to review rather than choosing the nearest-looking label.
- What you provide
- Catalog fields and target vocabulary.
- What you get
- Consistent attribute values with ambiguous cases flagged.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Allowed colors: navy, black. Source values: Navy Blue; navy; midnight.
Completed example
Map Navy Blue and navy to navy; flag midnight unless an approved mapping defines its meaning.
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 unknown attribute values be forced into an allowed category?
No. Keep them unresolved until a mapping is approved. An apparently tidy catalog can conceal incorrect classifications.
Why did normalization merge two genuinely different values?
Inspect the mapping rule and source meaning. Similar spelling or marketing language does not establish equivalence.
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 ↑