How to use the Product Bundle Builder.
Bundles should solve a coherent use case and respect compatibility. Check included quantities and pricing instead of assuming that more items create more value.
Make the workflow fit your task.
Choose a customer use case and select products that work together to complete it. Verify compatibility, quantities and the actual bundle price, keeping unrelated additions separate from the proposed core offer.
- What you provide
- Catalog, compatibility and pricing rules.
- What you get
- Complementary bundle suggestions with reasons.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Catalog: notebook N1 costs USD 8; refill R1 explicitly fits N1 and costs USD 3; phone cable C1 costs USD 5. Create a writing bundle with no discount.
Completed example
Bundle: N1 notebook + R1 compatible refill. Quantity: one of each. Listed total: USD 8 + USD 3 = USD 11. Reason: the refill supports continued use of the notebook. Excluded: C1 phone cable, which does not contribute to the stated writing use case. Shipping and tax are not 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 a bundle include every item a customer might also buy?
Focus on a coherent use case. Extra items can complicate the offer without improving the customer's ability to complete the task.
Why does the bundle contain incompatible components?
Check product identifiers and specifications on both sides. Similar names are not enough to establish that a refill or accessory fits.
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 ↑