How to use the Grocery List Generator.
A grocery list should consolidate matching ingredients without mixing incompatible units or forms. Subtract pantry stock only when the user confirms it is usable and intended for the plan.
Make the workflow fit your task.
Combine recipe quantities only when ingredient form and units are compatible. Subtract confirmed usable pantry amounts and keep optional items separate. Show unresolved conversions or package-size choices before producing the final shopping list.
- What you provide
- Selected recipes and existing pantry inventory.
- What you get
- Consolidated ingredient shopping list.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Two recipes need 2 onions and 3 onions; pantry has 1 usable onion. One recipe also needs 500 g potatoes.
Completed example
Buy 4 onions and 500 g potatoes. Calculation: 2 + 3 − 1 = 4 onions. Keep variety or preparation requirements separate when the recipes specify them.
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 dried and cooked beans be combined into one quantity directly?
They are different forms with different yields. Keep them separate unless a suitable conversion and recipe requirement are supplied.
Why does the list underbuy ingredients after subtracting pantry stock?
The pantry amount may be outdated, unusable or reserved for another meal. Confirm what is available for this plan.
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 ↑