How to use the Ecommerce Return Policy Draft Generator.
A return policy draft should reflect actual business terms and applicable requirements supplied by the owner. Mark unresolved conditions before publication.
Make the workflow fit your task.
Turn the owner's approved return conditions into plain language, separating eligibility, process and unresolved costs. Keep the stated window and item condition intact and flag terms that need a business or legal decision.
- What you provide
- Actual return terms and supplied legal requirements.
- What you get
- Customer-readable draft with missing conditions highlighted.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Store terms supplied by the owner: unused items may be requested for return within 30 days of receipt. Return requests go to returns@example.com. Return-shipping responsibility and refund timing are undecided.
Completed example
Draft: You may request a return for an unused item within 30 days of receipt. Contact returns@example.com with your order reference to begin the request. Resolve before publication: who pays return shipping, how approved returns are sent back, refund timing and any applicable requirements or exceptions. This example does not fill those missing terms.
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.
Can the draft decide who pays return shipping when the owner has not specified it?
No. Mark that responsibility unresolved. The copy should not establish a commercial term by assumption.
Why does the return policy contradict a product-specific exception?
Compare the general wording with the approved exception and explain its scope explicitly before publication.
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 ↑