How to use the Shipping Policy Draft Generator.
Shipping copy should distinguish dispatch time from delivery estimates. Keep regions, exclusions and actual fees explicit.
Make the workflow fit your task.
Separate order processing from carrier transit and identify the regions, fees and exceptions actually covered. Use the supplied estimates without turning them into guaranteed arrival dates, and explain how customers can obtain updates.
- What you provide
- Shipping regions, costs and actual delivery policies.
- What you get
- Clear policy draft with explicit exceptions.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Approved terms: orders dispatch within two working days; carrier delivery estimate is three to five working days after dispatch. Regions and fees are not supplied.
Completed example
We dispatch orders within two working days. After dispatch, the carrier's estimated delivery time is three to five working days. Processing and transit are separate stages, and the carrier estimate is not a guaranteed arrival date. Before publication, add the verified delivery regions, fees and any exclusions.
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 dispatch time be presented as the complete delivery time?
No. Dispatch and transit are different stages. Preserve both so customers understand what the stated estimate covers.
Why does the shipping draft promise delivery sooner than operations can support?
Check whether processing days, carrier transit and excluded days were combined incorrectly. Keep the assumptions visible.
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 ↑