Seasonal hotel: closing in October and reopening in March with the catalog intact
A beach or mountain hotel that closes five months a year loses more at reopening than at closing: the catalog is gone, the server who knew how to post a room charge has left and the controller starts the year with a blank sheet. Here is how to pause without erasing.
A seasonal hotel lives twice a year through the most expensive moment of any restaurant: opening. It closes in October with the menu, the prices and the team tuned by seven months of operation, and reopens in March with half the staff new, the menu in a file nobody can find and a controller asking once again how included breakfast was recorded. What is lost in those five months is not money from the drawer: it is the configuration that made the drawer reconcile.
Closing well is half of reopening well
The end of the season is usually a race: get the last guest out, empty the walk-in, settle the seasonal staff and switch everything off. In that race three things get lost that will cost weeks in March. The catalog is lost, because the system is switched off or the license is cancelled and in March the menu has to be keyed in again. The history is lost, because the season’s reports stay on a machine put away in a storeroom. And the judgment is lost, because the rules for room charges, comps and allocation value lived in the head of a manager who is no longer there.
Closing well means leaving the hotel restaurant paused, not at zero. The catalog is kept with its prices, its modifiers and its recipes. The season’s reports remain available to read in January from anywhere. And the rules stay written in the system, not in someone’s memory.
The seasonal operation page (Seasonal hotel) describes what a paused account looks like: the property does not pay to operate what it does not operate, but it does not lose what it built either.
What gets paused and what gets kept
The key distinction is between operating and existing. During the closure the restaurant does not operate: no orders, no shift closes, no room charges. But it keeps existing: the menu, the prices, the tables, the revenue centers, the users and the history are still there, ready for the first day of March.
| Element | At closing in October | At reopening in March |
|---|---|---|
| Catalog, prices and modifiers | Kept as they are | Prices are reviewed; nothing else is touched |
| Recipes and ingredient costs | Kept | Purchase costs are updated |
| Season reports | Remain available for consultation | Serve as the base for the budget |
| Seasonal staff users | Deactivated | New ones created with the same role |
| Room charge and comp rules | Kept | Applied from the first shift |
| Front desk connection for the folio | Paused | Reactivated with a test |
| Monthly fee for operating | Paused | Reactivated |
Notice that almost everything says "kept". That is what makes March a reopening and not an implementation. The only things that change from one season to the next are purchase prices, a few dishes and the people.
The intact catalog: prices, recipes and modifiers
The catalog of a seasonal hotel restaurant is not a list of dishes. It is the dishes, their prices per revenue center, their modifiers (no onion, medium rare, on the rocks), the recipes that draw down inventory and the categories the controller uses to report. Keying all of that in from scratch takes days, and keying it in a hurry introduces errors that surface in the first shift close: a dish in the wrong category, a price without tax, a modifier that charges when it should be free.
If the catalog is kept, reopening is a review and not a data entry job. The manager opens the price list, adjusts what went up, removes the three dishes that did not work and adds the two new ones. Half a morning, with the previous season’s history in view to decide what stays.
What is worth reviewing before reopening
- Selling prices against updated ingredient costs, because suppliers do not pause their increases in winter.
- Dishes with fewer than ten sales in the whole previous season: candidates to leave the menu.
- Modifiers that were used a lot and may deserve to become a dish of their own.
- Catalog categories against the accountant’s chart of accounts, so the first month-end close comes out without surprises.
- Allocation value of included breakfast, if the property changed its seasonal rate.
Seasonal staff: training fits in one morning
The seasonal hotel hires servers, cashiers and helpers every March who leave in October. With each one you start over: how to open a table, how to post a room charge, how to record a comp, how to close the shift. If that training depends on the manager having time and the system being intuitive, the first week of the season is the worst week of shift closes of the year.
What shrinks training to one morning is a system with few screens, a room charge that asks for the room and shows the guest’s name, and a comp that cannot be recorded without a reason. When the system does not let you do it wrong, training consists of showing how to do it right once. The implementation page (implementacion) describes what is taught on the first day and what is left for the second week.
The other important change is the user. Each seasonal staff member has their own access with their role, and at the end of the season that access is deactivated. That way the shift close says who closed, who voided and who gave away, and the season’s history has names instead of "the afternoon server".
An illustrative example with numbers
The figures below are invented to show the calculation. They do not describe any property or the industry. They serve to compare what it costs in hours to reopen from scratch against reopening with the catalog intact, in a 40-room hotel with a restaurant, a bar and room service.
| Reopening task | From scratch (hours) | With catalog intact (hours) |
|---|---|---|
| Key in menu, prices and modifiers | 16 | 3 |
| Load recipes and ingredient costs | 12 | 4 |
| Set up revenue centers, tables and payment methods | 6 | 0 |
| Define room charge and comp rules | 4 | 0 |
| Test the front desk connection for the folio | 3 | 1 |
| Train eight new people | 24 | 12 |
| Total | 65 | 20 |
In the example, reopening from scratch costs 65 hours and reopening with the configuration kept costs 20. That is a 45-hour difference, more than a week of one person’s work, and almost all of it falls in the week before opening, when that person also has to hire, buy and welcome the first group. At an illustrative cost of 200 per manager hour, the difference is 9,000 per season, without counting the errors in the first shift close.
The most expensive thing in the example is not in the table: it is the first week of operation with a catalog keyed in a hurry. A wrong price on the best-selling dish is discovered at month-end, and by then it was served three hundred times.
The cloud does not close in October
An on-premise server is switched off with the hotel. When it goes off, it takes the reports with it, and when it is switched on in March, sometimes it does not come on. A cloud system keeps existing even when the hotel is closed: the controller can open, in January, from home, consumption per occupied room for the whole previous season to build the budget for the next one. The article on cloud versus on-premise server (Cloud or a server at the hotel: what happens when the power goes out) goes into detail on what happens in each case.
For a seasonal hotel this has another advantage: the March budget is built with October data, not from memory. How many covers per day during Easter week, which dish sold most in July, how much the average guest posted to the room. All of that lives in last season’s reports, if the reports still exist.
The first-week-of-March list
Reopening does not end the day the first guest arrives. It ends when the first shift close reconciles, the first room charge reaches the folio and the first weekly close is compared with the same week of the previous year. That happens in the first week if the catalog was kept, and in the sixth if it was not.
- Reactivate the account and the front desk connection; post a test charge to a complimentary room and see it on the folio.
- Review prices and recipes with updated purchase costs, without touching categories or modifiers.
- Create the seasonal staff users with their role, one per person, and deactivate those left over from last season.
- Train in one morning: open a table, post a room charge, record a comp with a reason, close the shift.
- Do the first shift close with the manager alongside and compare it with the close for the same day of the previous year.
- At the end of the week, look at consumption per occupied room against the first week of the previous season.
A seasonal hotel does not close the restaurant: it pauses it. The catalog, the recipes, the rules and the reports are kept, and in March reopening is a price review and a morning of training, not an implementation from scratch.
What to do this week
- Write the list of everything that today lives in the head of the manager or the chef: comp rules, value of included breakfast, who can void. Move it into the system.
- Export or leave available the reports from the last season before switching off any equipment.
- Confirm with your vendor whether your account can be paused without losing configuration, and what the pause period costs.
- Tag in the catalog the dishes with the fewest sales of the season, so the March decision is made with data, not from memory.
- Prepare the one-morning training script and test it with the last person you hired.
Inn Restaurant lets you pause the hotel restaurant’s account during the seasonal closure and reactivate it with the catalog, the rules and the reports intact, at one price per property per month only while it operates. If you want to see what a reopening looks like in fifteen minutes, the demo is booked on the contact page (contact).
More articles
Chains and groups: comparing the restaurant of every hotel with the same rule
A group with six hotels has six restaurants reporting six different things under the same name. The corporate director asks for revenue per occupied room and receives six sheets that cannot be placed side by side. Here is how to set a single standard without taking each hotel’s menu away.
All inclusive: consumption that has value even when nobody pays for it, and the premium bar that does get charged
In an all-inclusive hotel the restaurant serves hundreds of plates a day that nobody pays for at the table. Here is how to record that consumption with an allocation value, how to post the extras to the guest folio and what the per-room report tells you.
Boutique hotel: the financial discipline of a chain without the team of a chain
Twelve rooms, one restaurant, an owner who is also the manager and a front desk clerk who also rings up the restaurant. With that team you cannot have a full-time controller, but you can have the five controls a controller would demand, and they fit in twenty minutes a day.
Your hotel’s restaurant already sells well. Now the hotel needs to know it.
Fifteen minutes, with your menu and your tables. Nothing to install.