How to price a dish in a hotel: cost, margin, room rate and guest

The chef proposes a new dish, the manager asks how much it will cost and someone answers with the price at the restaurant across the street. That is how many hotels set prices, and that is how a dish ends up leaving less than it costs to serve. A hotel restaurant has an advantage the street restaurant does not: it knows how much its guest pays to sleep, and that number also helps price dinner.

Why in a hotel the kitchen does not set the price alone

In a street restaurant, the price is a negotiation between cost and the competition on the block. In a hotel restaurant there are two more people at the table. There is the controller, who looks at food cost as a percentage of sales under the hospitality accounting standard and compares it month to month. And there is the guest, who did not pick your restaurant out of twenty options: they picked it because they sleep upstairs, and their willingness to pay is anchored to what they paid for the room.

That changes two things. First, the price has to close on a target cost the controller can defend in the meeting, not only on intuition. Second, the same dish can carry several legitimate prices depending on who orders it and where: the corporate guest under an agreement, the weekend family at the pool and the guest ordering to the room at ten at night are not buying the same thing.

Step 1: the complete recipe cost

Everything starts with what it costs to put the plate on the table. Not the cost of the main ingredient, but the whole recipe, weighed and with waste. The recipe that lives in the chef’s head always comes out cheaper than it really costs.

What a serious recipe cost includes

• Every ingredient in the real portion quantity, including the oil, the salt and the side that “costs nothing”.
• Waste: the fish is bought whole and served as fillet; the cost per portion is the whole fish divided by usable portions.
• What comes along without being ordered: the table bread, the salsa, the butter. If it goes out with every main, it is spread across the mains.
• Packaging, if the dish is also sold to the room or to go.

That cost should live in the system, tied to the dish, and be updated when the purchase price changes. A recipe cost from eight months ago no longer describes the dish you serve today.

Step 2: the target cost and the base price

The target cost is the share of sales the hotel accepts spending on ingredients. The controller sets it with the food and beverage director, and it is usually different per category: one for food, a lower one for beverages, perhaps one of its own for the breakfast buffet. There is no universally correct number; there is the number that closes your hotel’s income statement.

With the recipe cost and the target cost, the base price comes from a division: recipe cost divided by target cost. If the dish costs 84 and the target is 35 %, the base price before tax is 84 divided by 0.35, that is 240. That is the price which, sold at that cost, leaves exactly the margin the hotel set out to earn.

Tax and rounding on the menu

The base price is before tax because the tax is not yours. If the menu shows tax-inclusive prices, as is common in hotels, it is added at the end. With a 16 % tax, 240 becomes 278, which on the menu rounds to 280 so it reads cleanly. What matters is that rounding happens after the calculation, and always toward a figure the guest reads without effort.

Step 3: the room rate as a reference

Here is the piece only a hotel restaurant has. The guest has just paid a rate for the night, and without noticing compares the price of dinner with that number. A main course that costs a small fraction of the rate feels reasonable; one that approaches half the rate feels expensive even if the restaurant across the street charges the same.

That is why every main dish is worth checking against the hotel’s average rate. There is no correct ratio, but there is a simple test: ask whether the guest who paid your average rate would see that price as a natural part of the stay. If your rate changes by season, the answer changes too, and that is where date-based price rules come in instead of a new menu every season, as described on the seasonal operation page (Seasonal hotel).

Step 4: adjustments by guest segment

The base price is the restaurant price for the guest who pays at the table. From there, each segment and each revenue center applies an adjustment, and that adjustment should be a rule in the system, not a discount the server remembers.

The corporate agreement deserves a note. The discount must be written with its cap and with the list of what it covers, because an ambiguous agreement produces disputed charges at the guest’s check-out. The article on how to write a corporate agreement (How to write a hotel corporate agreement that does not end in a dispute) has the detail, and the company accounts page (Master accounts and agreements) shows how the system applies the discount only to the guest who is under that agreement.

A complete illustrative example

The figures below are invented to show the calculation. They are not prices from any property. Imagine a Veracruz-style fish in the restaurant of a hotel with an average rate of 1,800 per night.

1. Recipe cost with waste, side and table bread: 84.
2. Food target cost set by the controller: 35 %. Base price before tax: 84 divided by 0.35 = 240.
3. Tax at 16 %: 240 times 1.16 = 278. On the menu: 280.
4. Test against the rate: 280 is around 16 % of 1,800. A guest who paid that rate sees it as a natural part of the stay.
5. Guest under a corporate agreement at a 10 % discount: pays 216 before tax. The cost is still 84, so the real food cost rises to 39 %, but the dish leaves 132 per unit and the agreement brings volume.
6. Room service with a 15 % surcharge: 240 times 1.15 = 276 before tax, 320 with tax on the in-room menu. The 36 surcharge covers the trip and the tray.

Notice that the same dish has three legitimate net prices: 216, 240 and 276. All three come from a single recipe cost and explicit rules. None depends on the server remembering, and all three are reported by segment so the controller sees the real food cost of each.

Common pricing mistakes in a hotel

• Copying the price of the restaurant across the street without knowing its cost or its guest.
• Calculating with the tax-inclusive price and believing the margin is higher than it is.
• Setting a single price for every revenue center and losing the room service surcharge or giving away the pool portion.
• Leaving the agreement discount in the server’s memory instead of in a rule tied to the folio.
• Recording the package dinner at zero and making the restaurant look worse than it is in the report.
• Not updating the recipe cost when the supplier raises prices; the price stays and the margin leaves.

What to do this week

1. Ask the chef for the recipe cost of the ten best-selling mains, with waste and sides.
2. Ask the controller for the food and beverage target costs used in the income statement.
3. Recalculate the base price of those ten dishes and compare with the current menu price; note the ones that fall short.
4. Check every price against the hotel’s average rate and flag the ones that feel outside the stay.
5. Write the segment adjustments as rules: agreement with a cap, room service surcharge, package allocation value.
6. Configure those rules in the system and delete the discounts that live in the team’s memory today.

Inn Restaurant keeps the recipe cost tied to the dish and applies prices per revenue center and per agreement as rules, with the corporate guest’s discount tied to their folio. If you want to see your hotel restaurant’s menu with those rules in place, book a 15-minute demo (contact).