Resort with five revenue centers: one close, one standard, five different businesses

A resort with five revenue centers has five businesses that barely resemble each other: the restaurant sells covers, the pool bar sells drinks to people without a wallet, room service sells convenience, the coffee shop sells speed and the lobby bar sells the last drink of the night. But the guest is the same, the folio is the same and the hotel controller is the same. The challenge is not running five revenue centers: it is closing them as one and reading them as five.

Five different businesses with the same guest

The first thing to accept is that the five revenue centers do not behave the same and should not. The restaurant has a high ticket and few transactions; the coffee shop has a low ticket and many. The pool bar sells almost everything as a room charge because nobody carries cash in a swimsuit; the lobby bar takes cards from outside customers who came in for a wedding. Room service has the highest delivery cost and the margin most sensitive to cancellations.

If you try to give all five the same menu, the same hours and the same server, you will kill what each one does well. If you let each one close however it wants, you will have five shift closes that do not add up. The solution is in the middle: five different operations on one recording standard.

That standard is what lets the controller consolidate in minutes and lets the food and beverage director compare like with like. The resort page (Resort) shows how a property like this is set up, with each revenue center separate in operation and joined at the close.

The single standard: catalog, payment methods and shift close

The standard has three pieces and all three live in the system, not in a manual nobody reads. The first is the catalog: products can differ by revenue center, but the categories are the same (food, domestic drinks, premium drinks, comps, extras) and the price of a given product is the same everywhere unless an explicit rule says otherwise.

The second is payment methods. All five revenue centers accept the same ones: cash, card, room charge with verified folio, charge to a company account and comp with a reason. Nobody invents a new payment method at the pool bar because "that is how it has always been done". The third is the shift close: same format, same fields, same logical closing time, even if the lobby bar closes at two in the morning and the coffee shop at six in the evening.

The table is not a recipe: it is an example of what a resort looks like where each revenue center has its own logic but all deliver the same close. The property’s logical closing time (for example, four in the morning) is what defines which day each sale belongs to, and that time is set by the controller, not by each revenue center.

The consolidated close: one close, not five added by hand

In many resorts the consolidated figure is a spreadsheet someone fills in at seven in the morning with five printed shift closes. Each close has its own format, one comes without the comps, another mixed room charges with card, and the pool bar’s arrived on a napkin. The controller spends two hours reconciling and the result comes out with a margin of error nobody wants to admit.

A real consolidated close is not assembled: it is read. If the five revenue centers record in the same system with the same standard, the property’s daily close is the automatic sum of the five shift closes, with the detail available by revenue center, by payment method and by category. The controller does not reconcile: the controller reviews. And what gets reviewed are the exceptions, not the totals.

What the consolidated close has to show on a single screen

• Total net food and beverage sales for the property and net sales per revenue center.
• Breakdown by payment method, with room charges separated from cash and card.
• Comps and voids for the day, by revenue center and with a reason.
• Cash differences by revenue center, even when they are zero.
• Consumption per occupied room for the day, with occupancy taken from the front desk.
• Room charges not yet reflected on the folio, which should be zero.

Comparables by revenue center: the same metric, a different context

A single standard does not mean a single target. The metric compared across revenue centers is the same (net sales, average ticket, ingredient cost, comps as a share of sales), but each revenue center is compared against itself and its own history, not against its neighbor. The pool bar on a Tuesday in July does not look like the pool bar on a Saturday in December, let alone the restaurant.

What does get compared across revenue centers is discipline: how many voids after sending to the kitchen, how many comps without a reason, how many cash differences, how many room charges rejected by the front desk. Those indicators do not depend on the type of business and they do say who is operating well. The article on the eight places where consumption leaks in a hotel (The eight places where a hotel loses food and beverage revenue) describes most of them.

An illustrative example with numbers

The figures below are invented to show the calculation. They do not describe any resort or the industry. They serve to see how a one-day consolidated close with five revenue centers is read, with 180 occupied rooms.

With 180 occupied rooms, food and beverage consumption per occupied room for the day is 252,000 ÷ 180 = 1,400. But the number that matters is in the last column. Restaurant comps are 3,600 on 126,000, that is 2.9 % of sales. Room service comps are 2,700 on 27,000: 10 %. A revenue center that gives away one in every ten units of sales has a problem, and without the per-center column that problem hides inside the 3.5 % total.

Now look at the pool bar’s average ticket: 150 with 300 transactions. If last week it was 180 with the same transactions, someone is selling domestic drinks where they used to sell premium, or recording premium as domestic. Neither shows up in the property total; both show up in the revenue center’s row.

Who reviews what

A consolidated close reviewed by one person is a consolidated close nobody reviews when that person goes on vacation. In a resort with five revenue centers, the review is split by level, and each level looks at a different thing on the same screen.

• The supervisor of each revenue center: their shift close, their cash differences and their voids, before going home.
• The food and beverage manager: average ticket and comps by revenue center, every morning, against the previous week.
• The controller: the consolidated close, room charges against folios and the exceptions, every morning before eight. The page for the controller (/para/contralor) details this view.
• The hotel general manager: consumption per occupied room and departmental margin, every Monday.
• The front desk: pending room charges and guest disputes at check-out, in real time.

The rule that keeps the review from turning into bureaucracy is simple: nobody reviews totals, everybody reviews exceptions. If the pool bar close reconciles, the controller does not open it. If it has a 400 difference, the controller does.

The traps of the consolidated close

• Adding revenue centers with different logical closing times. A one-in-the-morning sale at the lobby bar belongs to the previous day or the next depending on what the controller decides, and that decision applies to everyone.
• Consolidating with tax in some revenue centers and without tax in others. All net or all gross; the standard says net.
• Letting one revenue center record room charges as "other" because its terminal does not have the option. Five revenue centers, one list of payment methods.
• Counting the included consumption of the all-inclusive plan in one revenue center and not in the others. Either it is valued everywhere with the same allocation value, or nowhere.
• Reporting tips inside sales at the pool bar because they are collected in the same movement. Tips belong to the team, not to the property.

What to do this week

1. Set the property’s logical closing time with the controller and apply it in all five revenue centers starting tomorrow.
2. Unify the list of payment methods across the five revenue centers and remove any "other" option someone invented somewhere.
3. Check that catalog categories are the same in all five revenue centers, even if the products change.
4. Pull comps as a share of sales by revenue center for the last seven days and look for the one that breaks the pattern.
5. Assign in writing what each level reviews every morning, and test the exceptions-only rule for one week.
6. Cross-check the week’s room charges with the front desk folios and count how many never arrived.

Inn Restaurant runs each revenue center with its own menu and its own shift close, and consolidates the property’s close on a single screen with room charges tied to the folio. If you want to see how a five-center day is read in fifteen minutes, the demo is booked on the contact page (contact).