Buffet breakfast charged per guest: how to record it without a line at the entrance

Breakfast is the moment of the day when the most guests walk into your hotel restaurant at the same time, and also the moment when they have the least time. The line at the entrance is not caused by the kitchen or the buffet: it is caused by the question “room number?” followed by a search on a sheet printed at six in the morning that is already out of date by eight.

The line at the entrance is a symptom, not a host problem

When the breakfast entrance jams, the usual reaction is to put another person at the door. That splits the line between two people, but it does not remove it, because the time each guest takes to get through does not depend on how many people are attending but on how many questions have to be asked and how many things have to be looked up. Every arriving guest triggers the same sequence: ask the room, find it on the sheet, check whether breakfast is included, count how many they are, tick them with a pen and, if it is not included, explain the price and note the charge for someone to enter later.

That “someone enters it later” is the second problem. Breakfast charges noted on the sheet are typed in at the end of the shift, when the host has already left and the sheet has crossings out. Some of those charges reach the guest folio late, some reach it wrong and some never reach it. The front desk finds out at check-out, when the guest already has the suitcase in hand and no patience left.

And there is a third, silent problem: the kitchen does not know how many people had breakfast. It knows how many plates were washed, or how many ticks the sheet has, which is not the same thing. Without that number it cannot calculate the buffet cost per cover, and without cost per cover the breakfast included in the rate is a black box nobody can defend in front of the controller.

Three kinds of diner in the same room

In a hotel buffet breakfast, three kinds of diner sit side by side, look identical at the table and have to be handled differently by the operation. Recognizing them is the first step to stop asking all of them the same questions.

• The guest whose rate includes breakfast. They pay nothing in the restaurant, but their breakfast has a value the hotel must record to know what that rate costs. They are the most numerous and should take the least time at the entrance.
• The guest whose rate does not include breakfast and who decides to have it. They pay for the buffet, and in a well run hotel they pay it as a room charge, without reaching for a wallet, with the line everyone knows: “To my room, please.”
• The walk-in diner, or a guest’s visitor. They pay on the spot, in cash or by card, and their consumption is restaurant revenue with no folio behind it.

The printed sheet treats all three the same and that is why it is slow. A good record separates them before they arrive: it knows which rooms have breakfast included because the reservation says so, it knows which do not, and it knows that anyone not in an occupied room pays directly. The host decides nothing; the host confirms.

Checking against the guest list: what the entrance needs

The printed sheet fails because it is a snapshot from before dawn. Between six and nine in the morning there are early departures, early arrivals, room moves and guests who bought breakfast at the front desk the night before. What the entrance needs is the live guest list, with three pieces of data per room: whether it is occupied today, how many guests are registered in it and whether the rate includes breakfast, and for how many of them.

With that list on a tablet, the sequence at the door shrinks to one question and one confirmation. The guest says the room or shows the key card; the screen shows the last name and the number of included breakfasts; the host confirms how many are coming in and taps a button. If more come in than are included, the screen offers the charge for the difference to the room in that same tap. Nothing is written down for later.

1. The guest says the room number, or the host reads it from the key card.
2. The screen shows the last name on the folio, registered guests and included breakfasts.
3. The host confirms how many people are coming in. If they are the included ones, one tap records the consumption at allocation value and the guest walks in.
4. If more people come in than are included, or the rate does not include breakfast, the screen offers the charge to the folio for the difference and the host confirms it with the guest.
5. If the room is not occupied or the last name does not match, the screen says so and the diner pays directly or sorts it out at the front desk.

The room charge page (Room charge) explains why that check has to be made against the real stay and not against a typed number, and the front desk page (Front desk) describes what the agent sees when a breakfast charge enters the folio with that backing.

The guest who does not want to say their room out loud

Some guests do not like saying their room number in front of other people, and they are right. The key card, a code on their phone or simply the last name solve that without friction. What solves nothing is the printed sheet, because it forces them to say it out loud and then wait while someone looks it up.

Included versus paid breakfast: how each one is recorded

This is the part that confuses the operation most and matters most to the controller. An included breakfast is not free: the hotel sold it inside the room rate. If the restaurant records it at zero, its food revenue looks lower than it is and the room looks more profitable than it is. If it records it at menu price, the opposite happens. The correct practice is to define an allocation value per included breakfast, agreed between food and beverage and the controller, and to record every included breakfast at that value as internal restaurant revenue.

Paid breakfast is simpler: it is recorded at menu price, with tax, and charged to the guest folio or collected directly from the walk-in diner. What cannot happen is paid breakfast mixing with included breakfast in the same count, because then nobody knows how much real revenue the buffet produced or what it cost to serve the rate with breakfast.

This treatment has a name in the hospitality accounting standard, which separates rooms revenue from food and beverage revenue and requires packages to be allocated between the two. The article on food and beverage revenue per occupied room (How food and beverage revenue per occupied room is calculated, and what a good number looks like) explains how that allocation value feeds the metric that is later discussed in the meeting.

The real count: why the kitchen needs the number of covers

The buffet is produced before anyone arrives, and the kitchen decides how much to prepare with a number that is usually yesterday’s estimate. If the entrance record counts every person who walks in, in real time, the kitchen can see at eight thirty how many covers are in so far and how many rooms with included breakfast have not come down yet. With that it adjusts buffet replenishment instead of preparing “just in case”.

The real count also feeds cost per cover, which is the figure that gives the allocation value its meaning. Total cost of what the buffet consumed divided by the day’s real covers: if cost per cover rises and the allocation value does not, the rate with breakfast is subsidizing the restaurant without anyone having decided it.

An illustrative example: one morning with numbers

The figures below are made up to show the calculation; they are not market data and not from any property. Imagine a 50-room hotel with 35 rooms occupied this morning and 60 guests registered in them. The buffet price is 220 including tax and the agreed allocation value for included breakfast is 120.

With the printed sheet, this hotel would have reported “about 50 people” and revenue of 3,080, and the kitchen would have prepared for 70. With the per-guest record it reports exactly 46 covers, 6,920 in revenue counting the allocation, and it knows that 8 guests with breakfast paid in the rate did not come down. That last piece of data is what allows tomorrow’s buffet production to be adjusted, and what explains why cost per cover never matched the plate count.

Frequent mistakes in breakfast recording

• Recording included breakfast at zero. Restaurant revenue looks low, cost per cover looks impossible and the controller cannot allocate the package.
• Collecting cash at the entrance from the guest without included breakfast instead of charging the folio. The verified charge is lost, a register opens at the door and the line gets longer.
• Counting covers by washed plates or by ticks on the sheet. Neither gives the real number, and the kitchen produces on false data.
• Letting the unregistered companion in on the account holder’s included breakfast. It is a comp nobody authorized, repeated every morning of the stay.
• Typing the charges from the sheet into the system at the end of the shift. Every transcription reaches the folio late and some never do.

What to do this week

1. Tomorrow, time the average per guest at the breakfast entrance and count how many questions the host asks each one; that is your starting point.
2. Ask the front desk for the live guest list with room, last name, registered guests and included breakfasts, and put it on a tablet at the entrance.
3. Agree the allocation value for included breakfast with the controller and start recording it that way from day one.
4. Establish that every breakfast paid by a guest is charged to the folio at the entrance, with one tap, and that only walk-in diners pay directly.
5. Hand the kitchen the real count for the next day at nine in the morning and compare it with what was produced; adjust the following day’s production by that difference.

Inn Restaurant checks the breakfast entrance against the hotel’s active stays, records included breakfast at allocation value and charges paid breakfast to the folio with one tap, with no sheet and no transcription, and the real count visible to the kitchen. You can see it with a test guest list in a 15-minute demo (contact).