High occupancy, small kitchen: surviving the full hotel

High season carries a cruel paradox: the days when you can sell the most are the days when the kitchen can produce the least. A full hotel does not break room service through lack of demand: it breaks it through concentrated excess. And a two-person kitchen is not saved by working faster; it is saved by shaping the demand before it reaches the pass.

The enemy is not the volume: it is the peak

A small kitchen can push out many orders in a day if they arrive spread out. What it cannot do is push out ten at once. The high-season problem is not how much gets ordered but when: every craving lands in the same two windows, and the traditional phone makes them worse because it accepts everything without warning anyone. The whole strategy fits in one sentence: flatten the peak without turning off the sale.

First tool: limit orders per time slot

Accepting every order instantly sounds like good service and is the opposite: it is promising what the pass cannot deliver. Limiting how many orders enter per time slot (what the industry calls order throttling) turns the avalanche into an orderly line. The guest who orders into a full slot is not rejected: they are offered the next available window, honestly. An order arriving fifteen minutes later than dreamed disappoints less than one arriving cold an hour late.

• Define real capacity per slot with your cook, not with your optimism: how many hot dishes come out well in twenty minutes.
• Keep whatever skips the kitchen outside the limit: drinks, cold snacks and bakery can flow without a turn.
• Review the limit by season: a Tuesday in February does not have the capacity of a holiday Saturday.

Second tool: the high-season menu is shorter

Instinct says more guests deserve more variety. Operations says the opposite: every extra dish is one more preparation, one more station and one more risk of jamming the pass. The high-season menu is designed backwards: few fast-out dishes, sharing ingredients, that two people can produce in parallel. Variety is recovered in what costs the kitchen nothing: drinks, cold desserts, boards and bakery.

In high season the winning kitchen is not the one that offers the most: it is the one that promises only what it can deliver with the hotel full.

Third tool: scheduled orders that spread the load

The scheduled order is voluntary throttling: the guest personally picks a future slot and gifts the kitchen the thing it lacks most in high season, which is visibility. The breakfast ordered the night before and the dinner reserved from the pool in mid-afternoon are production planned in calm instead of solved in panic. The more sales migrate to scheduled, the smaller the immediate peak becomes.

The panel as shock absorber: a visible queue beats a busy phone

On the phone, high season sounds like this: busy line, frustrated guest, the front desk taking orders by hand while handling a check-in. With an orders panel, the same demand comes in silently and lines itself up: every order arrives written, with room and time, and waits its turn visibly on screen. The difference is not cosmetic. The busy phone loses the sale; the visible queue keeps it and merely arranges it. That is the least celebrated function of a system like Room Order: it does not just capture orders, it absorbs the wave so a small kitchen can surf it.

The sequence to implement it without drama

1. Measure your current peak: for one week, count how many orders land in your worst hour. That number is your starting point, not your enemy.
2. Agree with the kitchen on an honest capacity per slot and set it as the limit.
3. Trim the seasonal menu: fast dishes with shared ingredients first.
4. Push what can be scheduled: breakfasts the night before, dinners from mid-afternoon.
5. Review time from order to door every week: if it grows, the slot limit was set too generously.