The hotel restaurant as its own business: when it makes sense to open it to the street
Opening the hotel restaurant to neighbors and outside bookings can be a real source of revenue, or it can quietly dilute service to the guest. The difference lies in a report almost no hotel checks: the one that separates each.
On a Saturday night, at the very same table in your hotel restaurant, there could be a couple who lives ten blocks away and has never stayed with you, next to a guest who arrived that afternoon from another city. Both pay the same check, but they represent completely different businesses, and mixing them up in the report is the easiest way to make a bad decision without knowing it.
Two businesses sharing the same space
The restaurant that serves only guests lives off demand you already paid for: the hotel's occupancy. The restaurant that also opens to the street lives off a different demand, one it has to win every night competing with any other place in the area. They are two businesses with different metrics, different clientele and different price sensitivity, even though they share the same kitchen and the same dining room.
The guest does not choose the restaurant by comparing prices with other places in the city, because they are already inside the property and the cost of going out to find another option is high. The neighbor who lives ten blocks away does compare, because they have dozens of equally close alternatives. That difference in price sensitivity means a promotion built to attract neighbors may make no sense to the guest, and a menu built only to retain the guest may not be competitive enough to attract the outsider.
Whether it makes sense to open to the street has no universal answer. It depends on how much idle capacity the restaurant has outside peak guest-demand hours, whether the hotel sits in an area with real foot traffic, and whether the team can serve two audiences without one taking quality away from the other.
When it does make sense to open to the street
There are clear signs that opening the restaurant to neighbors and outside bookings can add rather than subtract. The first is real idle capacity: if the restaurant has empty tables during hours when most guests are no longer at the hotel, that capacity costs the business nothing extra, it just needs filling.
The second sign is location: a hotel on an avenue with steady foot traffic, or near offices that generate weekday business lunches, has outside demand available that an isolated hotel in a low-traffic area simply does not, no matter how good the kitchen is.
The third sign is a kitchen and dining room team with real spare capacity, not one already working at the limit serving only guests. Opening to the street without that margin does not add a new business: it trades guest service quality for outside volume, which is exactly what you do not want.
When it does NOT make sense to open to the street
If the restaurant already runs near maximum capacity during the same hours guests eat, opening to the street in those same hours only creates internal competition: the guest who already paid to stay ends up waiting behind a neighbor who walked in without a booking. That is the worst version of opening to the street, because it hurts exactly the customer you already had secured.
It also does not make sense if the location generates no real traffic: a hotel in an area with no nearby offices or foot traffic can open its door to the street and find that almost nobody walks in, while the team spends energy on local marketing with no demand to capture.
The report that separates guest from outsider
This is the point almost no hotel gets right: if you cannot tell from your report which sale came from a guest and which came from the street, you cannot evaluate whether opening to the street is working. A restaurant's rising total revenue can hide a falling guest capture, and nobody will notice until revenue per occupied room (How food and beverage revenue per occupied room is calculated, and what a good number looks like) starts dropping for no apparent reason.
The way to separate this is not asking every table whether they are a guest, but tying every order to a folio: if the order opens from the guest's check-in record or gets charged to the room, it is a guest. If it is paid directly at the table with no lodging folio attached, it is an outsider. That distinction, made in the system and not in the server's memory, is what lets you report the two businesses separately.
This separation also protects the controller when the annual audit arrives. Food and beverage revenue that mixes guests and outsiders with no distinction makes any analysis under the hospitality industry standard harder, because revenue per occupied room stops being reliable once part of that revenue never actually came from a guest.
Outside bookings without displacing the guest
When the restaurant accepts outside bookings, it helps to place them in hours and tables that do not compete with peak guest demand. An outside booking at seven thirty, when most guests dine between eight thirty and ten, displaces nobody. The same booking at nine, during high occupancy season, does.
An illustrative example with numbers
The figures below are made up to show the calculation. They are not market data and they are not from any particular hotel.
| Item | Guests only | With street opening |
|---|---|---|
| Guest dinners | 300 | 300 |
| Outside dinners | 0 | 150 |
| Average check | 220 | 220 |
| Total monthly revenue | 300 × 220 = 66,000 | 450 × 220 = 99,000 |
| Guest dinner capture | unchanged | unchanged, stays the same |
In this example, opening to the street added 33,000 units of revenue without touching a single guest dinner, because it filled tables that would otherwise have sat empty. If instead guest dinners had dropped to 250 at the same time outside dinners rose, the story would be different: the restaurant would be replacing its own guest with an outside customer, even though total revenue would look just as good in the general report.
How to decide without guessing
- Measure table occupancy by time slot for two weeks, separating guests from outsiders if you already have some of that demand.
- Identify the time slots with real idle capacity, not the ones you assume are empty out of habit.
- Confirm with the kitchen and dining room team whether they can carry extra volume without slowing service to guests.
- Open outside bookings first only in those idle-capacity slots, not across the whole service.
- After a month, compare guest dinner capture against the prior month before expanding the outside-booking hours.
What to check every month once open to the street
- Guest dinner capture, to confirm it is not falling while outside revenue rises.
- Wait times reported by guests during hours that also carry outside bookings.
- Share of total revenue coming from outsiders, to know how dependent the restaurant is becoming on that demand.
- Restaurant reviews kept separate from lodging reviews, because a dissatisfied outside customer affects the restaurant's reputation, not the hotel's.
Opening the hotel restaurant to the street makes sense when there is real idle capacity, foot traffic and a team with margin. It does not make sense when it displaces the guest who already paid to stay. The only way to know is a report that separates every sale by folio: guest or outsider, never mixed.
What to do this week
- Check whether your system can report guest and outside revenue separately.
- Measure table occupancy by time slot over the next seven days.
- Identify a single low guest-demand time slot to test outside bookings.
- Set a limit with the team on outside tables per service that does not compromise guest attention.
- At the end of the week, compare guest dinner capture against the prior week.
Inn Restaurant automatically separates guest revenue from outside customer revenue in every report, so you know whether opening to the street is adding business or taking service away from the person who already paid to stay. If you are weighing this decision, in the fifteen-minute demo (contact) we review the report with your own history.
More articles
How to raise guest capture at the hotel restaurant without giving anything away
Guest capture is the share of people who slept at your hotel and ate there. Raising it does not depend on cutting prices or giving anything away: it depends on three touchpoints you are probably letting slide right now.
The weekday business hotel and the weekend family hotel: two restaurants in one
The same hotel restaurant serves a guest on Tuesday who wants to be done in twenty minutes and a family on Saturday who wants to stay for two hours. Here is how to adjust the menu, hours, prices and staffing without opening two kitchens.
Hostel with a bar: how to charge by bed, by guest and by consumption without killing the party
In a hostel, the guest shares the room with six strangers but shares the bar tab with none of them. Here is how to identify each person, charge for real consumption, and keep a menu in several languages without driving the bar staff crazy.
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.