How to use the SKU Generator.
SKU rules need stable attributes and a collision check. Avoid embedding changeable promotional wording or assuming codes are unique because they look different.
Make the workflow fit your task.
Choose stable attributes and a documented abbreviation scheme, then generate codes in a consistent order. Check the proposed codes against both the new batch and existing inventory, identifying collisions before use.
- What you provide
- Explicit naming rules and product variants.
- What you get
- Unique structured SKU codes with collision checks.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Rule: category-color-size. Products: mug blue small and mug blue large.
Completed example
Proposed SKUs: MUG-BLU-S and MUG-BLU-L. Check both against the existing SKU inventory.
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 SKU include a temporary promotion or current price?
Use stable identity attributes instead. Changeable commercial details can make identifiers difficult to maintain and reconcile.
Why do two different products receive the same SKU?
Add a meaningful distinguishing attribute or approved sequence rule, then rerun the collision check against the full relevant inventory.
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 ↑