Catering and Event Ordering for Restaurants: From Guest Count to Purchase Order

To order for a catering job or private party, start from the confirmed guest count and the menu, not from your order guide. For each dish, work out the usable amount you need, divide by the item's yield to get the as purchased amount, and round it into the vendor's case or pack size. Then add that event quantity to your regular order as its own line, keep it labeled and out of your par levels, and place it in time for the right truck. After the event, compare what you ordered with what you actually used, and write it down for next time.

The hard part isn't the math. It's that the event lands on top of a normal week, so the same walk in, the same trucks, and the same pars have to carry both. Regular ordering is covered in our complete guide to restaurant purchasing and inventory management. Event ordering is a one time layer on top of that loop: it adds demand for a few days, then has to get out of the way so next week's count and order come out right.

In this guide

• Why event orders go wrong
• Lock the inputs before you order anything
• From guest count to ingredient quantities
• Worked example: a 60 guest plated dinner
• Keep event product separate from your pars
• Timing the order against cutoffs, lead times, and minimums
• Special orders, deposits, and confirmations
• Receiving and storing event product
• Leftovers: what you can reuse and what you can't
• Reconcile what you ordered against what you used
• What line cooks and chefs can do
• An event ordering timeline
• FAQ

Why event orders go wrong

Most event ordering problems aren't caused by bad estimates. They come from mixing event demand into the regular system:

• Someone raises the par "for the party" and nobody lowers it again. The next two weeks come in heavy.
• Event product gets counted as regular stock. Seven packages of short rib set aside for Saturday look like seven packages you don't need to order.
• The event order misses its truck. Specialty items, whole fish, and anything you don't normally buy often have longer lead times than your usual items.
• Recipes are in cooked or trimmed amounts, and the order isn't. Ordering 19 lb of short rib because the recipe calls for 19 lb of braised short rib leaves you well short.
• The final count changes after the order is placed, and the change never makes it to whoever ordered.
• Nobody checks afterward. So the next event is estimated from memory instead of from what actually happened.

Each section below handles one of these.

Lock the inputs before you order anything

You can't order well from a vague event. Before any numbers, get these in writing from the client or whoever booked it:

Your event contract or booking form is where most of this belongs. Many restaurants set a date by which the guest count becomes guaranteed. That date is your real ordering deadline for perishables, so put it before the vendor cutoff, not after it.

From guest count to ingredient quantities

Work one menu item at a time, and keep it in this order:

1. Servings. Guest count, plus any spare plates you decide to make. The spare is your call, based on service style and how much a remake would hurt.
2. Usable amount needed. Servings × portion size, in the unit the recipe uses (cooked weight, trimmed weight, each).
3. As purchased (AP) amount. Usable amount ÷ yield. This is where most event orders come up short.
4. Purchase units. AP amount ÷ the amount in one pack or case, rounded to what the vendor will actually sell you.
5. Subtract what you can spare from stock, but only if your regular service can live without it. More on that in keeping event product separate.

The yield is the step people skip. If you haven't measured it for an item, run a quick test before the event. Our guide to restaurant yield percentage shows how, and the free yield calculator does the AP math for you. Raw to cooked loss on braised and roasted proteins can be large, so use your own test numbers, not a guess.

Rounding is the second place to slow down. Cases, packs, and catch weight items don't divide evenly into event portions, so the last step almost always leaves something over. Our guide to restaurant inventory units covers how counting units and purchasing units relate.

Plated vs buffet

For a plated dinner with preselected entrées, the counts are close to exact. For buffets, family style, and stations, people take different amounts and you don't control portions. There's no reliable universal "pounds per guest" number for that. The best source is your own records: what you sent out and what came back from the last few buffets you ran. If you have none yet, size it like a plated meal, add a cushion you're comfortable paying for, and write down what happens so the next one is based on data.

Worked example: a 60 guest plated dinner

This is an illustrative example. The restaurant, menu, yields, pack sizes, and vendor schedules are made up to show the method. They aren't typical numbers for any vendor or concept. Use your own yields and pack sizes.

The event

• Saturday dinner, 60 guests, plated. The guest count was guaranteed the Monday before.
• Guests chose ahead: 36 braised short rib and 24 salmon.
• Every plate gets roasted butternut squash.
• The chef wants 2 spare portions of each entrée for remakes and surprises. The squash gets 2 extra servings too.

The numbers

Here's the math behind each line:

Short rib:  38 × 0.5 lb          = 19 lb cooked
            19 ÷ 0.60             = 31.7 lb raw
            31.7 ÷ 5 lb per pack  = 6.3 packages → 7 packages

Salmon:     26 × 0.375 lb        = 9.75 lb of portions
            9.75 ÷ 0.696          = 14.0 lb of whole sides
            14.0 ÷ 3.23 lb a side = 4.3 sides → 5 sides (about 16.2 lb, roughly 30 portions)

Squash:     62 × 0.25 lb         = 15.5 lb of dice
            15.5 ÷ 0.733          = 21.1 lb whole squash
            21.1 ÷ 35 lb a case   = 0.6 case → 1 case

The salmon and squash yields are the ones from the worked examples in our yield guide. The 60% short rib yield is an assumption for this example. Measure your own, because cut, trim, and cooking method change it a lot.

Look at what happens without the yield step. Ordering 19 lb of short rib because that's what the plates need would give about 11.4 lb cooked (19 × 0.60), enough for about 22 portions. You'd be 16 plates short with 38 planned.

Folding it into the regular order

Short rib is also on the regular menu, so it goes on the same broadline order. Thursday's count shows 8 packages on hand, and the regular par for that order is 10 packages.

Regular need:   10 par − 8 on hand        = 2 packages
Event need:                                 7 packages
Combined:       2 + 7                      = 9 packages
In cases:       9 ÷ 6 = 1.5 cases          → 2 cases (12 packages)
Left over:      12 − 9                     = 3 packages into regular stock

The extra 3 packages aren't waste. Short rib is a regular item, so they go into regular stock and the next order is smaller. The squash is different. If squash isn't on your regular menu, about 13.9 lb of the case (35 − 21.1) has nowhere to go. Before you order, ask whether the vendor will break a case, or plan a use for the rest, like a soup special or staff meal. Deciding that ahead is cheaper than finding a half case in the walk in two weeks later.

Keep event product separate from your pars

Your par levels describe a normal week of usage. An event is not a normal week, so keep it out of them in three ways.

1. Add event quantities on top of the par, don't raise the par

Write the event quantity as its own number, like the 7 packages above, and add it to what the regular par says to order. Don't change the par to 17 for the week. If you do, someone will order to 17 again next week, and you'll find out from the walk in.

2. Label event product and keep it out of the regular count

When the delivery comes in, move the event portion to its own labeled spot: "EVENT SAT, SHORT RIB, 7 PKG." If anyone counts before the event, they count the event shelf separately or skip it. Otherwise the count makes regular stock look 7 packages higher than it is, and the next regular order comes in 7 packages light, which is more than a whole case.

3. Leave event weeks out when you recalculate usage

If you set pars from purchase history or from usage between counts, an event week inflates both. Note event weeks so you can leave them out, or subtract the event quantities, when you next rework pars. Holiday weeks need the same treatment, which our guide to holiday ordering and vendor schedules covers.

Timing the order against cutoffs, lead times, and minimums

Work backward from the event, not forward from today.

1. When does each item need to be in the building? That's the first prep day for it, not the event day. Braised short rib for Saturday might be cooked Friday, so it needs to arrive by Thursday. Frozen product needs its thawing time added on top.
2. Which truck gets it there? Find the last delivery that arrives before that day, then its cutoff. Your vendor ordering schedule should already list both.
3. What's the lead time for the special items? Items your vendor doesn't stock can need extra days. Ask the rep when you first book the event, not at the cutoff.
4. When is the guest count final? It has to come before the earliest cutoff for perishables. If the client can't commit that early, order for the guaranteed count and decide in advance how you'll handle increases.

Illustrative timing for the Saturday dinner

Two cutoffs on Wednesday morning and afternoon, both after the Monday guarantee. That's the shape you want.

Minimums

An event often changes your minimums picture. A big event can push an order well over a minimum you normally struggle to hit. A one off order from a specialty vendor for a few items can fall short of theirs. Our guide to vendor order minimums and delivery fees walks through whether to pay the fee, add items, or move the order.

Special orders, deposits, and confirmations

Events are where restaurants buy things they don't normally buy: a whole beef tenderloin, a specific cheese, a flower for the cake, a case of a wine the client asked for. Those need more care than a regular order line.

• Confirm the order back. Ask the vendor to confirm the item, pack size, quantity, and delivery date in writing. A text or email reply is enough. Special items are the ones most likely to be misread.
• Ask whether it can be returned. Special order and cut to order items are often final sale. Know before you order, so a dropped guest count doesn't leave you owning product you can't use.
• Ask about prepayment. Some vendors want payment or a deposit for special orders, especially from accounts that don't normally buy the item. Find out when you place it.
• Get a price before the invoice. Write the quoted price on the purchase order so you can check it when the invoice comes in.
• Line up a substitute. Decide ahead what you'd use if the item is shorted, and tell the client if a substitution would change the menu. Our guide to shorted deliveries and substitutions covers what to do at the door.
• Match your client deposit to your exposure. If you're buying nonreturnable product for an event, your own deposit and cancellation terms with the client should cover it. That's a business decision for you, not a rule, but make it on purpose.

If the event needs a specialty vendor you don't use, it's worth thinking about whether that's a one time order or a sign you need a regular specialty source. Our comparison of broadline and specialty distributors can help with that call.

Receiving and storing event product

• Check the event lines first. When the truck arrives, check event items against the purchase order before anything else. A short on a regular item can wait for the next truck. A short on event salmon the day before can't.
• Weigh catch weight items. Proteins and whole fish are often sold by actual weight. If the salmon sides come in lighter than planned, you'll get fewer portions, and the day before is the time to know.
• Label and separate. Event name, date, and item, on its own shelf or in its own bins.
• Check walk in space before the truck comes. An event on a busy weekend can mean more product than your walk in normally holds. Plan where it goes, and rotate regular stock so the oldest still gets used first.
• Keep cold food cold. The FDA Food Code calls for time/temperature control for safety food to be held at 41°F (5°C) or below, or at 135°F (57°C) or above when held hot (section 3-501.16). Your state or local code may differ, so check what your inspector expects.

Leftovers: what you can reuse and what you can't

Leftovers fall into three groups, and only one of them really comes back into inventory.

Two Food Code details matter most for events:

• Cooling cooked food. Cooked time/temperature control for safety food has to be cooled from 135°F to 70°F within 2 hours, and to 41°F or below within 6 hours total (section 3-501.14). A full hotel pan of braised short rib won't do that sitting on a rack, so cool it in shallow pans or an ice bath.
• Food held without temperature control. If a buffet or drop off uses time instead of temperature as the control, under the 4 hour option the food has to be marked and then cooked and served, served, or discarded within 4 hours of leaving temperature control (section 3-501.19). That option also requires written procedures. Food held this way doesn't go back in the walk in.

Local health codes adopt the Food Code with their own changes, so treat these as the federal model, not your local rule.

For ordering, the takeaway is simple: the leftovers you can reuse are mostly the ones you never prepped. That's an argument for prepping close to the count and keeping spares as raw product where you can, rather than cooking extra and hoping.

Reconcile what you ordered against what you used

This is the step that makes the next event easier. Within a day or two, while people still remember, fill in a short table for the main items.

Illustrative reconciliation for the Saturday dinner

Made up numbers, continuing the example above.

What it tells you

Short rib actual yield:  41 portions × 0.5 lb ÷ 33.1 lb = about 61.9%
                         Planned 60%. Close enough; keep using 60%.

Salmon expected:         16.4 lb × 0.696 ÷ 0.375 = about 30.4 portions
                         Actually cut 29. Slightly low; check the trim next time.

• Short rib: the catch weight came in under the nominal 35 lb, and the yield ran a bit better than planned, so it more or less evened out. Two spares were right, and one got used.
• Salmon: 5 spare raw portions went back on the regular menu, which only works because salmon is a regular item. For an item you don't normally carry, you'd want a smaller cushion.
• Squash: the leftover was predictable from the case size, and the soup special handled it. Next time, ask about a broken case first.

Keep the reconciliation with the event's purchase orders. Our guide to tracking restaurant purchase orders covers how to set up an order history you can actually find things in. The next time someone books a 60 guest dinner, you start from this table instead of from scratch.

What line cooks and chefs can do

• Don't pull from the event shelf for regular service. If you need it, ask first. That's how event dinners end up four portions short.
• Weigh trim and cooked yield on event items if the chef asks. It's the data that makes the next order right.
• Tell the chef early if product looks off. Thin salmon sides or short rib with heavy fat cap change the portion count. Thursday is better than Saturday.
• Follow the event prep list, not the regular one. Our restaurant prep list guide covers how to set one up by station. The free daily prep list template works for event prep too.
• Label everything you make for the event, including leftovers, so it's clear what was prepped, when, and whether it went out to guests.

An event ordering timeline

FAQ

How much food should a restaurant order per guest for a catering event?

There's no single number that works across menus. For plated events, multiply servings by portion size and divide by the item's yield. For buffets and stations, use your own records from past events, since consumption varies a lot. If you don't have records yet, start from plated portions, add a cushion, and write down what you actually used.

Should a catering order go on a separate purchase order?

If the event uses items or vendors you don't normally buy from, yes. If the event items come on your regular truck, they can share the regular purchase order, but mark the event lines with a note so you can find and reconcile them later.

Should I raise my par levels for a big event?

No. Add the event quantity on top of what your regular par says to order, and leave the par alone. A par raised for one event tends to stay raised, and the following weeks come in heavy.

What can I do with leftover food after a catering event?

Unopened product can go back into regular stock. Food you prepped or cooked but never sent out can often be cooled, labeled, and used soon, if it was held at safe temperatures. Food that was served to guests generally can't be served again under the FDA Food Code, so discard it. Check your local health code, since it may differ.

How far ahead should I order for a large event?

Work backward from the first prep day for each item to the last truck that arrives before it, then that truck's cutoff. Special order items may need extra lead time, so ask your rep when the event is booked. Make sure the guest count is final before the earliest perishable cutoff.

Event ordering in Proteus Kitchen

Everything in this guide works on paper or in a spreadsheet: a quantity sheet, a note on the purchase order, a label on the shelf, and a reconciliation table. Proteus Kitchen doesn't have a separate catering or events module. What it does is keep the purchasing side in one place. When you build a purchase order, Proteus shows each item's current amount, its target, and a suggested quantity, and you can change the quantity or add products before you save it. Each order has a delivery date and a notes field, so the event name and date can go right on the order.

Proteus stores each vendor's delivery days and order deadlines, so you can see which cutoffs the event order has to make. Order history can be filtered by vendor, status, and date range, and you can duplicate a past order as the starting point for the next similar event. Proteus doesn't place orders with vendors for you and doesn't need a POS integration. You still send each order through the vendor's portal, a text, or an email, and mark it submitted.

To get the yield math right before your next event, start with the free yield calculator. If your order guide or inventory is already in a spreadsheet, Free Restaurant Setup covers bringing it in, and there's a 30 day free trial below.

Sources

• U.S. Food and Drug Administration, Food Code 2022: section 3-306.14 (returned food), section 3-501.14 (cooling), section 3-501.16 (hot and cold holding), section 3-501.19 (time as a public health control)

Next step: build the quantity sheet for your next event

1. Write down the menu, every component, and the servings for each.
2. Add portion sizes and your yields. Test any yield you've been guessing.
3. Convert to AP amounts and round into pack sizes, noting what will be left over.
4. Find the truck and cutoff for each item, working back from its prep day.
5. Put the event lines on the purchase order with a note, and book 15 minutes after the event to reconcile.