Short answer: Build your event shopping list from the recipes on the event's menu, not from the last event's list.
The maths. For each ingredient: portions × raw weight per portion. Raw weight per portion is the served weight divided by the yield (what's left after trimming, peeling and cooking).
The buffer. Add a small, written buffer, about 5% on most lines, or two spare portions for dishes made to count. Then round up to the pack size your supplier sells.
The rules that stop waste. When a dish or the final guest count changes, update the dish quantities and regenerate the list. Combine events into one order per delivery day. Check the delivery against the list, line by line.
Below is one worked example, from the first count of 80 guests to the final count of 92, plus one week with three events. All quantities are example figures; your recipes and yields will differ.
Example event (made up for illustration): a Thursday company dinner, planned for 80 guests. Starter: green salad. Main: chicken breast, or a vegetarian risotto for guests who asked for it, with roast potatoes served to every guest. Dessert: panna cotta. Ten days out, the client confirms the final count: 92 guests, 6 of them vegetarian.
Why copying the last wedding's list doesn't work
Copying the list from last month's wedding and "adjusting a bit" feels faster. It goes wrong in four ways:
Different menu, different lines. A wedding with beef cheek and a company dinner with chicken share potatoes and cream, not much else.
Different portions. A three-course dinner ending at 22:00 and an all-night wedding with hot courses after midnight don't eat the same amount per guest.
Different counts. Scaling 120 guests down to 92 by eye means guessing on every line.
Old leftovers baked in. If the last list was padded "to be safe" and nobody wrote down what came back, the padding gets copied too.
The recipe is the only part that's actually the same from event to event, so build from that.
Recipe × portions × yield: the core formula
For every ingredient on the menu, you need three numbers from the recipe:
Served weight per portion: what lands on the plate (e.g. 160 g of cooked chicken).
Yield: the share of the raw weight left after trimming, peeling or cooking. Chicken breast that loses 20% in the oven has a yield of 80%.
Portions: how many guests get that dish.
Raw weight per portion = served weight ÷ yield. Line total = raw weight per portion × portions.
For the example dinner at the final count of 92 guests (86 chicken, 6 vegetarian):
Ingredient | Served per portion | Yield | Raw per portion | Portions | Net need |
|---|---|---|---|---|---|
Chicken breast | 160 g | 80% | 200 g | 86 | 17.2 kg |
Potatoes | 200 g | 80% | 250 g | 92 | 23.0 kg |
Salad leaves | 40 g | 80% | 50 g | 92 | 4.6 kg |
Arborio rice | 80 g dry | n/a (bought dry) | 80 g | 6 | 0.48 kg |
Cream 30% | 100 ml | 100% | 100 ml | 92 | 9.2 l |
Check one line: 160 g ÷ 0.80 = 200 g raw chicken per portion; 200 g × 86 = 17,200 g = 17.2 kg.
Two things make this table reliable:
Yields come from your kitchen, not the internet. Weigh a sack of potatoes before and after peeling once, write the yield on the recipe, and reuse it.
Portions come from the split, not the headcount. Chicken is cooked for 86, not 92. The 6 vegetarians are on the risotto line. Kids' plates and dietary dishes get their own lines too.
For what each portion costs, the same recipe numbers drive the plate cost: see how to cost an event menu.
Buffers: how much extra, and where
A buffer covers a dropped tray, a lower yield than usual or an extra guest. Keep it small and written down, so everyone uses the same one.
A simple house rule for the example:
About 5% on proteins, vegetables and starches cooked in bulk.
Two spare portions for dishes made to an exact count (plated desserts, the vegetarian main).
No extra buffer for rounding. If rounding up to the pack already gives you a few percent more, don't add another 5% on top.
Ingredient | Net need | With buffer | Pack size | Order |
|---|---|---|---|---|
Chicken breast | 17.2 kg | +5% = 18.06 kg | 1 kg vacuum pack | 19 packs = 19 kg |
Potatoes | 23.0 kg | +5% = 24.15 kg | 15 kg sack | 2 sacks = 30 kg |
Salad leaves | 4.6 kg | +5% = 4.83 kg | 1 kg box | 5 boxes = 5 kg |
Arborio rice | 0.48 kg | +2 portions = 0.64 kg | 1 kg bag | 1 bag |
Cream 30% | 9.2 l | +2 portions = 9.4 l | 1 l carton | 10 cartons = 10 l |
The potato line is the weak spot: 30 kg ordered for a 24.15 kg need, almost 6 kg extra, only because of the sack size. The section on combining events below fixes that.
How big the buffer should be also depends on the guest-count guarantee in your contract: if you already prepare a few percent above the guaranteed number, that margin is your buffer. Don't add a second one on top.
What changes when 80 guests become 92
The first list was built for 80 guests (75 chicken, 5 vegetarian). At the final count of 92 (86 chicken, 6 vegetarian), every line moves:
Ingredient | At 80 guests (net) | At 92 guests (net) | Difference |
|---|---|---|---|
Chicken breast | 75 × 200 g = 15.0 kg | 86 × 200 g = 17.2 kg | +2.2 kg |
Potatoes | 80 × 250 g = 20.0 kg | 92 × 250 g = 23.0 kg | +3.0 kg |
Salad leaves | 80 × 50 g = 4.0 kg | 92 × 50 g = 4.6 kg | +0.6 kg |
Arborio rice | 5 × 80 g = 0.40 kg | 6 × 80 g = 0.48 kg | +0.08 kg |
Cream 30% | 80 × 100 ml = 8.0 l | 92 × 100 ml = 9.2 l | +1.2 l |
The final count doesn't fix the order by itself. If nobody updates the dish quantities and regenerates the list, the order still goes out for the first count. Chicken for 75 portions, with the 5% buffer and rounded to whole packs, is 15.75 kg → 16 packs. That's 16 kg ÷ 200 g = 80 chicken portions for 86 chicken guests: six mains short, and the buffer has gone before service starts.
If the count drops instead, you over-order. Either way: when the final count arrives, update the dish quantities and regenerate the list before the order goes out. Put a task on the event for it, with a deadline the day before your supplier's order cut-off. The same final count belongs on the event's BEO, so the kitchen and the service team work from one number (here's a free BEO template).
How it works in Manage My Restaurants Events
In Manage My Restaurants Events, the menu sits on the event. Each dish is a line on the menu, with a quantity you type yourself. When you click Generate List, the app multiplies each recipe line by that dish's quantity and adds up the same ingredients across dishes. That gives you the event's shopping list. Each dish can also show an estimated plate cost, so costing and ordering work from the same menu. The buffer and the rounding to pack sizes described above stay kitchen rules: apply them when you place the order.
For the example dinner, the menu lines look like this:
Menu line | Quantity at 80 guests | Quantity at 92 guests |
|---|---|---|
Green salad | 80 | 92 |
Chicken breast with roast potatoes | 75 | 86 |
Vegetarian risotto with roast potatoes | 5 | 6 |
Panna cotta | 80 | 92 |
Potatoes sit in both mains, so Generate List adds 86 + 6 = 92 portions of potatoes into one line: 23.0 kg. If the chicken recipe holds 200 g of raw breast per portion, the chicken line of 86 gives 17.2 kg on the list, the same number as the table above.
Three things to know:
The guest count doesn't drive the list. Generate List reads the quantity on each dish line, never the event's guest count. Changing the guest count from 80 to 92 doesn't change the menu or the list. No quantity changes until you change it yourself: here, chicken from 75 to 86, risotto from 5 to 6, salad and panna cotta from 80 to 92.
After you change a dish, regenerate the list. On a finalized menu, saving changes to the items deletes the old list and marks the menu Revised. You then click Generate List again. Leaving the old quantities in place, or ordering from a list made before the change, is how the order ends up six chicken mains short.
It's a list of what to buy for this menu, not live stock. Manage My Restaurants Events isn't inventory or POS software: it doesn't know what's on your shelves or what the supplier delivered.
Tip: keep dishes with different counts on separate lines. A package line uses one quantity for every dish inside it. If chicken and risotto sit in one package line, you can't set 86 for one and 6 for the other. Give them their own lines.
Notes that affect buying, such as "client brings their own cake" or "one guest with a severe nut allergy", go on the event, where the chef and the manager both read them. A task like "Update dish quantities and regenerate shopping list after final count, by Mon 12:00" can be marked done on the event's task board once it's finished. More on event menus and shopping lists.
Three events in one week: one order per delivery day
Before Christmas, a venue often has three or four events in one week. Ordering for each event separately means each list gets its own buffer and its own rounding to whole packs.
Example week:
Tuesday: company lunch, 40 guests, delivered on Monday.
Thursday: our dinner, 92 guests.
Saturday: Christmas party, 60 guests, also with roast potatoes (250 g raw per portion) and panna cotta (100 ml cream).
Thursday and Saturday can share a Wednesday delivery. Each event keeps its own list, and the chef adds up the shared lines into one supplier order:
Ingredient | Thursday (with buffer) | Saturday (with buffer) | Ordered separately | Ordered together |
|---|---|---|---|---|
Potatoes | 24.15 kg | 60 × 250 g = 15 kg, +5% = 15.75 kg | 2 + 2 sacks = 60 kg | 39.9 kg → 3 sacks = 45 kg |
Cream 30% | 9.4 l | 60 × 100 ml + 2 portions = 6.2 l | 10 + 7 cartons = 17 l | 15.6 l → 16 cartons = 16 l |
Combining saves one sack of potatoes (15 kg) and one carton of cream, with no change to any recipe.
Three rules keep combining safe:
Combine by delivery day, not by week. Salad leaves for Saturday don't arrive on Monday.
Keep each event's list separate. If Saturday's count changes, you update Saturday's dish quantities and regenerate only Saturday's list, then redo the combined order.
Write on each event which delivery covers it, so nobody orders the same potatoes twice.
For the rest of the pre-Christmas rush, see corporate Christmas events in a restaurant.
Receiving the delivery against the list
The list is only half the job. When the delivery arrives, someone checks it against the list, line by line:
Weights and counts. 19 packs of chicken, not 18. Weigh a sample if the supplier charges by weight.
Substitutions. If the supplier sends 2 kg chicken packs instead of 1 kg, the total may be right but portioning changes.
Short deliveries. A missing line found on Wednesday afternoon can still be fixed. Found on Thursday at 16:00, it can't.
Quality. Leaves and fish get checked on arrival, not when the starter goes out.
Write anything that affects the event, such as a substitution or a line still missing, as a note on the event, so the chef and the manager see it in the same place. Manage My Restaurants Events doesn't record deliveries or stock, so the check itself happens on paper or in your supplier's system.
FAQ
How do you calculate food quantities for an event?
For each ingredient: portions × raw weight per portion, where raw weight per portion is the served weight divided by the yield. Add a small buffer (about 5%, or two spare portions for dishes made to count), then round up to the pack size.
How much extra food should you order for an event?
A common house rule is about 5% on proteins, vegetables and starches, and two spare portions for plated desserts and dietary mains. Don't add a second buffer on top of rounding to whole packs.
Does the shopping list update when the guest count changes?
Not in Manage My Restaurants Events. Generate List uses the quantity on each dish line, not the event's guest count. When the final count arrives, you change the dish quantities yourself (for example, chicken 75 → 86, risotto 5 → 6) and click Generate List again, before the order goes out.
Is the shopping list the same as inventory?
No. The shopping list says what to buy for one event's menu. Inventory tracks what's on the shelf. Manage My Restaurants Events does the first, not the second.
Order from the menu, not from memory
Menu, plate cost, shopping list, guest counts, notes and tasks, all on the same event. See plans: 14-day free trial, card required.
