How to use the Purchase Order Generator.
A purchase order should specify what the supplier is authorized to deliver. Include units, delivery location and acceptance criteria so a quantity cannot be mistaken for a pack size.
Make the workflow fit your task.
Describe items with units, pack sizes, quantities and agreed prices, then add delivery and acceptance requirements. Separate the order subtotal from unresolved freight or tax. Confirm supplier details and approval status before using the draft as an authorization.
- What you provide
- Approved purchasing details and supplier information.
- What you get
- Structured PO draft with clear quantities and terms.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Order 12 boxes of labels, 100 labels per box, at USD 5 per box; delivery to the supplied warehouse address.
Completed example
Quantity: 12 boxes / 1,200 labels. Goods subtotal: USD 60. Confirm freight, tax, delivery date and approval before sending the order.
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.
How should an order distinguish twelve boxes from twelve individual items?
State both the ordering unit and units per pack, so the intended total quantity can be checked.
Why does the supplier's confirmation show a different total quantity?
The supplier may use a different unit or pack size. Reconcile item codes and unit definitions before approving fulfillment.
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 ↑