Discounts in the hotel restaurant: who can apply them and how they show up in the report

In a hotel restaurant the discount has more faces than anywhere else: the repeat guest, the company agreement, the kitchen error that gets compensated, the courtesy from the manager on duty and the breakfast the front desk promised without telling anyone. If all of those cases end up on the same “discount” button, the next morning’s report explains nothing. And what is not explained is not controlled.

A discount is a decision, not a button

Every time someone lowers the amount of a check, they are making a decision with money that is not theirs: it belongs to the hotel. That decision may be right, and often it is, but it has to be recorded as a decision and not as an anonymous adjustment. The difference between a well controlled hotel restaurant and one that “more or less balances” is almost never in the sales. It is in what was subtracted from the sales and whether anyone can explain it.

Think of the discount as a signature. Whoever applies it signs that the amount will not be collected, and that signature has to carry who, why, how much and under whose authorization. If any of the four is missing, the controller has a hole and the manager has a problem they will discover late.

The four pieces of data every discount must carry

It does not matter whether the system is new or old, whether the restaurant has twelve tables or eighty: a discount without these four pieces of data should not be able to close. They are the minimum that lets the controller rebuild the story without asking anyone.

• Who applied it: the user who was at the register or on the server’s handheld, with their own name, not a shared “register 1” login.
• Why: a reason chosen from a closed list, not a free text field where everyone writes whatever comes to mind.
• How much: the original check amount, the amount discounted and the percentage it represents, calculated by the system, not typed in.
• Who authorized it: if the discount exceeds the cap for the position, the name of the person who approved it, with their own credential, at that moment.

The last one is the one that gets the most resistance. In many hotel restaurants the manager “authorizes” by voice from the other end of the dining room and the cashier applies the discount under their own login. The next day the report says the cashier discounted three thousand and the manager cannot remember which ones were theirs. That is not control: it is trust without a record.

Who can apply what: the matrix by position

The simplest way to organize discounts is a matrix: for each position, which discounts they can apply on their own, up to what cap, and from what amount they need someone else to enter a credential. The matrix below is a starting example; adjust it to your hotel, but do not leave it blank.

Notice one detail: the server has no free discount. What they do have is access to the promotions that already live on the menu, because those are not their decision, they are the hotel’s. And the cashier only applies the agreement, which is not their decision either: the agreement is already signed and its percentage is already in the system, as explained on the company accounts page (Master accounts and agreements).

The reasons: a short, closed list

The list of reasons is the part of the report that adds the most value at the least cost. If it has thirty options, everyone will pick “other”. If it has six or seven well thought out ones, every discount lands in its place and the controller can total by reason without reading a single ticket.

• Management courtesy: the hotel decides to treat. Always carries the name of the manager who approved it.
• Kitchen or service error: a dish done wrong, a long delay, the wrong drink. It is compensated so the guest leaves happy.
• Company agreement: the percentage negotiated with the company that lodges its travelers with you. Applied only to the guest tied to that agreement.
• Repeat guest or loyalty program: the benefit the hotel offers for coming back.
• Active promotion: two for one at the bar, happy hour, daily set menu. It already has a date and time window defined in the system.
• Hotel employee: the staff price for team members who eat at the restaurant.
• Complaint adjustment: the guest complained and the manager resolved it with a discount. Different from kitchen error because the origin is the guest’s perception, not a verified failure.

If a reason is used less than once a month, it probably should go. If “other” is the most used reason, the list is badly built or people are hiding something in it. Both things show in the report as soon as you total by reason.

Discount, comp and agreement are not the same thing

On the floor everything is called a discount, but in the hotel report they are three different things and they are booked differently. Mixing them is the most common reason the food and beverage department revenue does not match what the controller expected.

The discount lowers the price of something that was sold

The guest consumed and paid less. The sale exists, the cost exists, and the difference is a reduction of the revenue center’s income. It goes in the report as a discount, with its reason.

The comp is consumption the hotel decided not to charge

The dish left the kitchen, the cost was incurred, and nobody paid. Under the hospitality accounting standard the comp is recorded at selling price and fully deducted, so the department’s cost of sales is not distorted. If you record it at zero, your cost percentage rises with no explanation and the chef ends up arguing about a number that is not their fault.

The agreement is a negotiated price, not a concession of the moment

The company negotiated a percentage and signed it. When its traveler consumes, the system applies that percentage to the charge, which goes to the folio or to the company’s master account as agreed. It does not pass through the cashier’s or the manager’s judgment, and that is why it is reported separately: it is the cost of having that contract, not a floor decision. If you want to know how to write the agreement so this never causes arguments, there is a full guide on the blog (How to write a hotel corporate agreement that does not end in a dispute).

How they show up in the report: an illustrative example

The numbers below are made up to show how a day of discounts in a hotel restaurant should be read. They are not data from any property or from the industry. They exist to follow the calculation and to show which questions appear on their own when the report is built properly.

Of the 6,000 discounted, 4,000 were applied by the system with no human intervention (agreement and promotion) and 2,000 were decisions by people: 1,200 by the manager and 800 by the captain. That is the first useful reading: only a third of the day’s discount depended on someone’s judgment, and that someone has a name. If tomorrow the total rises to 9,000 and the 3,000 extra are management courtesies, the conversation is with one person and about six or seven tickets, not about the whole shift.

The second reading is the percentage: 12.5 % of the day went to discounts. That number alone does not say whether it is a lot or a little; it depends on how much corporate agreement volume you have and how many promotions you decided to run. What it does say is whether it changed compared with last week, and for which reason it changed. Comparing against yourself, by reason and by revenue center, is worth more than any outside average.

The signals the controller looks for

With the report built by reason and by authorizer, reviewing discounts takes ten minutes in the morning. These are the signals an experienced hotel controller looks at first, because each one has a story behind it that is almost never good.

• Discounts applied in the last thirty minutes before the shift close, when there are no guests left in the dining room. A discount with no guest present is usually an adjustment to make something balance.
• The same authorizer every day with the same amount. The courtesy that became a habit is no longer a courtesy; it is an unapproved price.
• The “kitchen error” reason concentrated on one server. Either that server has terrible luck with the kitchen, or they are using the reason to close checks cheaper.
• Discounts on room charges after the guest signed. The guest already accepted the full amount; lowering it afterwards, without them asking, deserves an explanation.
• Agreements applied to checks not tied to a folio from that company. The agreement percentage is for the company’s traveler, not for the cashier’s friend.

The discount on a room charge

Here the hotel restaurant has a case no street restaurant has. When the guest says “To my room, please.”, the amount travels to the front desk folio and is collected at check-out. If the discount is applied before the charge is sent, the folio receives the net amount and everything is in order. If it is applied afterwards, with the charge already posted, the front desk has to reverse and post again, and that movement has to appear on both sides with the same reason and the same authorizer.

That is why verified room charge matters as much for discounts as for collection: when the restaurant system and the guest folio speak the same language, a discount on a charge is one movement with a trail, not two manual corrections someone has to reconcile by hand. How that link is built is explained on the room charge page (Room charge).

And for the controller there is an accounting consequence: under the hospitality standard, discounts and comps reduce the food and beverage department’s revenue, not the rooms department’s revenue, even though the money was collected at the front desk. If the discount on a room charge is recorded as a folio adjustment, food and beverage reports revenue it never received and rooms absorbs a reduction that does not belong to it.

What to do this week

1. Write the matrix by position on one sheet: who applies what, up to what cap, who authorizes above it. Two badly filled columns are worth more than none.
2. Cut the list of reasons to seven at most and remove “other”, or keep it only with mandatory manager authorization.
3. Remove shared register logins. Every person who can discount signs in with their own credential, even on the same computer.
4. Ask for the discount report for the last thirty days totaled by reason and by person. If the system cannot produce it, you already know the first problem.
5. Review the discounts applied in the last half hour of every shift. Ask about each one with the ticket in hand.
6. Agree with the front desk on how an already posted room charge gets corrected, and make the reason identical in both systems.

In Inn Restaurant discounts are applied by position, with a mandatory reason, a cap per role and the authorizer’s credential, and the morning report shows them by reason, by person and by revenue center, with room charges tied to the folio. If you want to see how that report reads for your hotel, the fifteen minute demo is booked from the contact page (contact).