How to use the Marketplace Listing Variation Checker.
Variation checks should compare the fields that define the family. A child record must not inherit a different size, color or included component by accident.
Make the workflow fit your task.
Compare each child record with the attributes that define its variation family. Preserve identifiers, flag conflicting color, size or component values and request source confirmation before changing a record.
- What you provide
- Parent product and variant records.
- What you get
- Inconsistent attributes and invalid combinations.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Fictional mug parent lists blue and green options. Variant BLUE-01 is labeled Blue but its color field says Green. Source record not supplied.
Completed example
Variant: BLUE-01 Conflict: display label Blue versus color field Green. Parent options: Blue and Green, so either value is possible in the family. Required decision: confirm BLUE-01 against the authoritative product record before changing the label or field. No automatic correction selected.
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 a child variant inherit every parent attribute?
Only where the relationship and destination rules support it. Attributes that distinguish variants must remain tied to the correct child.
Why does a blue variant show green in one field?
Trace the value to its source and inspect mapping or inherited data. Do not correct it solely from another potentially inconsistent field.
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 ↑