The eight places where a hotel loses food and beverage revenue

Almost no property loses revenue to one big theft. It loses it drop by drop, in scenes so ordinary that nobody treats them as a problem. A glass at the pool, a room service phone call, a comp given by word of mouth. Each one is worth little. Added up over a month of operation, they are worth what a good system costs, and often quite a bit more. These are the eight we see most often.

1. The pool bar

Nobody carries a wallet in a swimsuit. The guest orders two drinks at the lounger, the server brings them and writes the room number in a notebook or on a paper voucher. The voucher reaches the cashier sometimes, gets wet other times and disappears now and then. At check-out the front desk cannot find the charge, the guest does not mention it, and the property paid for both drinks. What stops it: posting to the room from the lounger, with the stay verified on screen, at the moment the drink is served.

2. Room service by phone

The guest calls, someone answers, jots down the order and passes it to the kitchen verbally. The kitchen prepares it, it goes up to the room, and the charge is posted the next day “with the pending items”. Or it is not posted at all. There is no ticket with a time, no charge tied to the folio, and no way to know who took the order. What stops it: the order arriving through a channel with a record, messaging or a ticket, and the charge being created at the same time as the order, not afterwards.

3. Comps by word of mouth

“Comp the dessert.” “Do not charge table 12 for the coffee.” These are legitimate manager decisions, and in a well-run operation they are recorded as a comp with a reason and an author. In most operations they are said out loud and vanish. The check closes for less, or closes with a one hundred percent discount, and at month end food cost went up and nobody knows why. What stops it: the comp being a named movement, and applying it requiring a permission that not everyone has.

4. The check closed without payment

A system that lets you close the check in one step and collect in another has two in-between states that cost money: money recorded with the check still open, which gets collected twice, and a check closed with no money, which disappears from sales. It happens in a rush, with a new server, with a screen that froze halfway. What stops it: collecting and closing being a single operation that either completes or does not run at all, and two taps in a row never charging twice.

5. The charge to the wrong room

The server types 214 instead of 241. The guest in 214 checked out yesterday, so the charge floats. Or worse: 214 is occupied by someone else, who sees a dinner they never had, complains, and the property removes it. The dinner in 241 was never collected. What stops it: the system verifying the stay before accepting the charge, showing the guest’s name and dates, and refusing to post to a room with no active guest.

6. The company with the beer included

The agreement says the company covers lodging and meals. The guest orders a beer with dinner, the server posts everything to the room, and everything lands on the company account. The company notices three months later, disputes the whole invoice and the relationship cools. Or it never notices, and the guest learned that alcohol is on the employer. What stops it: an agreement with rules by category, where alcohol falls to the guest’s personal folio without the server having to remember.

7. The shared drawer

The bar and the restaurant collect in the same drawer because they are three meters apart. The close comes up short and two cashiers look at each other. Neither knows where it came from, and neither does the manager. It happens again the following week. What stops it: one cashier shift per revenue center, even if they share the furniture, with its own float, movements and named difference.

8. The credit that never draws on the line

An agency or a company has a credit line with the property. Every stay is invoiced and sent to collections. But the restaurant consumption charged to that account never draws on the line, because the point of sale does not know the line exists. The company piles up debt beyond what was authorized, and nobody sees it until they stop paying. What stops it: credit consumption flowing into accounts receivable on its own, drawing on the client’s line and showing up in the aging report from day one.

What they have in common

None of the eight is an honesty problem. They are design problems: the system allows a path where the sale and the record come apart, and the operation, in a hurry, takes that path. When the point of sale and the hotel are the same system, most of those paths stop existing. Not because people change, but because the charge, the folio, the agreement and the drawer can no longer contradict each other.

If you want to know how much you lose, do not estimate it. Run the exercise on one real week: count the pool vouchers that never arrived, the room service orders without a ticket, the unrecorded comps, the disputed charges and the cash differences. The number that comes out, flagged as your own example and not as a market figure, is the only one that matters.

Inn Restaurant was born inside a hotel and closes these paths by design: room charge with a verified stay, agreements by category, one drawer per revenue center and credit that flows into receivables on its own. See how a pool bar runs without paper (/bar-de-alberca) and how corporate accounts are set up (/cuentas-de-empresa). And the question that opens every demo: of every hundred guests who slept with you last night, how many ate with you?