Wedding Catering Inventory: Per-Plate Planning & Returns

The headcount is a guess

The family gives you a headcount on the phone. They change it twice before the mehendi. On the night, the pandal holds whoever actually turned up, plus the driver's cousins and a band that nobody counted.

You buy for the number you were given, cook on site, and load whatever's left back into the tempo at midnight. Then the next booking is three days away, and that's where the money goes. The leftover paneer, the cream tins and the half sack of basmati come back to the godown with no record of what they are or when they arrived.

This post walks through a method that works on paper or in software. You build a per-plate material list from the menu, write the buffer down, keep an issue sheet for every event, and count and rotate whatever comes back before you buy again.

Why caterer stock leaks between godown and venue

The leak isn't one big mistake. It's a handful of small habits that pile up across a season.

• Buying per dish, not per plate. The head cook says "paneer for the sabzi, maybe a bit extra" and the purchase gets made by feel.
• The buffer lives in someone's head. Everyone pads the order a little. The cook pads it, the owner pads it, and the supplier rounds it up. Nobody can say afterwards how much padding there was.
• Stock leaves in trips. The first van goes in the afternoon. A boy goes back for more oil at nine. Nobody writes down the second trip.
• Returns get dumped. Unopened curd, sealed cream and spare vegetables go back on the godown shelf behind the fresh purchase for the next event. A week later they're thrown out.

Each habit makes sense at midnight after a wedding. Put together, they mean you can't say what one plate actually cost you. We covered the wider planning side in perishable inventory planning for catering businesses. This post sticks to the wedding cycle of buying, issuing and handling returns.

Build the material list per plate

Start from the menu, not the shopping list. For every dish, write down the raw materials one plate uses, in grams or millilitres. That's your recipe card. You only build it once per dish and then fix it as you learn.

Then split the list into two groups:

• Perishables: paneer, curd, cream, milk, khoya, fresh vegetables, herbs, meat, fish.
• Carry-over stock: rice, dal, atta, oil, ghee, sugar, whole and ground masala, dry fruit.

The split matters because the two groups behave differently. Carry-over stock comes back and gets used at the next event. Perishables either get eaten tonight or turn into a loss. Your buying discipline should be tight on the first group and can be looser on the second.

Multiply each per-plate figure by the confirmed headcount, and you have the base order before any padding.

Write the buffer down

Every caterer keeps a buffer, and you should too. Running out of dal at a wedding costs you more than any waste ever will. The fix isn't removing the buffer. It's writing it down on its own line.

Set the buffer per group, not per event mood. Keep a thinner buffer on perishables and a wider one on carry-over stock, because the extra rice comes back but the extra paneer usually doesn't. Write it next to the base quantity so the sheet shows both: base, buffer, total ordered.

After the event, you compare what was used against the base. Over a few weddings you'll see whether your buffer on paneer is too fat or your rice figure per plate is too thin. That's learning you can't get from a buffer nobody wrote down. The same logic applies to banquet kitchens, as we covered in headcount buffers for hotel banquets.

A worked example: one sangeet dinner

Worked example, with illustrative quantities rather than a recommendation. Say you have a sangeet dinner with 400 confirmed plates and a menu of paneer butter masala, dal makhani, jeera rice and boondi raita. For example, the per-plate cards might read:

• Paneer: 80 g per plate, so 32 kg base
• Whole urad and rajma for dal: 40 g per plate, so 16 kg base
• Basmati (raw): 90 g per plate, so 36 kg base
• Curd for raita: 60 g per plate, so 24 kg base
• Fresh cream: 15 ml per plate, so 6 litres base

Suppose you set a written buffer of 5% on perishables and 15% on carry-over stock. That makes paneer 33.6 kg, curd 25.2 kg and cream 6.3 litres. On the dry side, dal comes to 18.4 kg and basmati to 41.4 kg. Each line shows base, buffer and total, so nobody has to guess later where the extra came from.

Say the night ends with 2 kg of paneer used from the buffer, three sealed curd tubs unopened and about 4 kg of raw basmati left over. Now you know the paneer buffer was close to right, the curd buffer wasn't needed, and the rice comes back as carry-over stock.

The issue sheet that travels with the event

The issue sheet is one page per event, and it goes in the van. It needs these columns:

• Item and unit
• Planned (from the per-plate list, buffer included)
• Issued at loading
• Extra issued, with time and who took it, for the second trip
• Returned unopened
• Returned opened
• Consumed, which is issued plus extra minus everything returned

Two people sign at loading: whoever runs the godown and the head cook. That's not about distrust. It just makes "I thought you packed the cream" impossible.

The extra-issued column is the one people skip, and it's the most useful. If the second trip happens at every wedding, either the per-plate figure is wrong or something is going missing between the godown and the venue.

Counting what comes back

Count the returns the same night or first thing next morning, before anyone loads for the next booking. Once returned stock mixes with fresh purchases, the issue sheet stops balancing.

Sort the returns into three piles:

• Unopened and sound. Sealed packs within date that were kept cold. Note that a sealed curd tub that sat in a hot van for hours isn't really "unopened and fine". Check how it was held, not just whether the seal is intact.
• Opened but usable. Things like dry masala and part bags of rice. Re-bag them, label them and use them first.
• Discard. Opened dairy, cut vegetables, anything cooked. Write it on the sheet as waste so it shows up in the plate cost instead of disappearing.

The discard line hurts to fill in, and that's why it's worth keeping. Over a season it tells you which dishes overproduce. For the margin side of that conversation, see restaurant food cost control and waste margins. The plate maths works the same way for caterers.

Unopened returns go to the front

This is the step that actually saves stock. Returned packs get a label with the event name and the return date, and they go to the front of the shelf or the top of the chiller. The next event's issue sheet takes from returns first, and only then from fresh stock.

That's first-expiry-first-out applied to a catering godown. Before you place the next order, check the returns pile and take it off the purchase list. If you have three tubs of curd sitting there, the next wedding orders three fewer. For the rotation routine itself, the FEFO workflow for commercial kitchens covers it, and the 2-page FEFO cheatsheet is handy to pin up in the godown.

Where paper holds up and where it strains

A clipboard and printed sheets will carry you a long way. With one event a day and one godown, a paper issue sheet and a recipe-card file are enough. For a tidier version, the expiry-tracking spreadsheet template gives you a place to log return dates.

Paper starts to strain in peak season. Picture two weddings and a reception on the same weekend from one godown. Returns from the Friday event need to land on the Saturday issue sheet before loading, and the per-plate history you want is spread across dozens of loose pages. That's the point where people stop counting returns because there's no time. It's also where the losses come back.

Trying it on your next booking

Try the method on one wedding before you change anything else. Build the per-plate cards, write the buffer on its own line, sign the issue sheet and count the returns the next morning. The numbers from that one event will tell you more than a season of guessing.

If you'd rather track returns and expiry in one place than in a stack of sheets, ShelfLifePro serves catering operations. You can see how it fits at our catering page, and every plan comes with a 14-day free trial, no credit card required.