Per-Head vs Flat Catering Pricing for Event Venues

Per-head catering pricing charges by final guest count and follows demand, while flat catering pricing locks a set amount regardless of headcount. Per-head protects your margin on big events; flat makes the final invoice predictable and easy to collect. Most event venues use a blend.

How you price catering is not just a menu decision. Per-head vs flat catering pricing at a venue quietly decides how much guest-count risk you carry, how predictable your final payment is, and how often you end up renegotiating the week of the event. Get the model right and the final invoice writes itself. Get it wrong and you are chasing a moving number ten days before the wedding. This guide compares the two head to head and shows when each wins.

How per-head pricing works

You set a price per guest, say $95, and the catering bill is that price times the final guaranteed count. At 120 guests, catering is $11,400. At 150, it is $14,250. The couple pays for exactly what they consume, which feels fair to them and scales your revenue with the size of the event.

The tradeoff is uncertainty. Until the guest count is locked, usually 10 to 14 days out, your final invoice is a moving target. If the count drops, your revenue drops with it, which is exactly why per-head models pair with a food and beverage minimum to set a floor.

How flat pricing works

You quote one number for the catering package regardless of headcount within a stated band, say $12,000 for up to 130 guests. The couple knows the figure the day they sign, and so do you. The final invoice is settled early, which makes collecting the balance clean and predictable.

The tradeoff is margin risk in the other direction. If the couple packs in 130 guests, your food cost eats into a fixed price. Flat pricing works best when you cap the guest band tightly and price the cap to protect your food cost percentage at the top of the range.

Margin and risk, side by side

• Guest-count risk. Per-head shifts it to the couple; they pay for what they bring. Flat keeps it with you; a full house costs you more to feed at a fixed price.
• Revenue predictability. Flat wins. You know the catering total at signing. Per-head stays fluid until the count locks.
• Perceived fairness. Per-head feels fair to couples with smaller lists. Flat feels simple and safe to couples who dislike surprises.
• Upside on big events. Per-head captures it automatically. Flat leaves it on the table once you pass the band's midpoint.

Why the blend usually wins

Most event venues land on a hybrid: per-head catering with a food and beverage minimum underneath it. The couple pays per guest, so big events pay you more, but the minimum guarantees the date clears its costs even if the list shrinks. That gives you per-head's upside and flat's floor at the same time. For sizing that floor, see how to set a venue pricing model that pairs per-head rates with a minimum.

How pricing model affects your final payment

The catering model decides when your final invoice can be settled. With flat pricing, the balance is known at signing and can be scheduled early with confidence. With per-head, the final payment has to come after the guaranteed count is set, which is why per-head venues collect a final balance 10 to 14 days out, right after headcount locks.

This is where billing built for the event date matters. With software made for event venues, you enter the final guaranteed count and the per-head total recalculates, the balance updates, and the couple sees the exact figure in their portal before it is due. No manual math, no ambiguity about what the last payment is. For structuring those milestones backward from the event date, read how to set a wedding venue payment schedule.

Keep the final invoice honest

Whichever model you use, the couple should always be able to see how the catering total was reached. Per-head charges should show the rate and the count. Flat charges should show the band. When the invoice is itemized and lands in the couple's portal, disputes over the final catering figure nearly disappear, because the couple watched the number take shape. VenueBill keeps that itemized line visible from signing to final payment so the last invoice is never a shock.

A quick per-head vs flat checklist

• Use per-head to scale revenue with event size and shift count risk to the couple.
• Use flat to lock the catering total early and collect a predictable balance.
• Blend the two: per-head rates with an F&B minimum floor.
• Time the final payment to when the guaranteed count locks under per-head.
• Keep the catering charge itemized so the final invoice reconciles cleanly.

The right catering model is the one that matches how much guest-count risk you want to carry and how early you want your final invoice settled. To see per-head totals recalculate and flow into a payment schedule automatically, start a free 14-day trial of VenueBill with no card required. Compare plans on our pricing page.