Skip to content

PRODUCTS / DINING

KEEP DINING SERVICE IN VIEW.

You have a dining service to run and guests to look after. Keep the service and table-booking information available to your team, with relevant guest details where Lodgewave shows them.

Daylight fills a restaurant dining room
TONIGHT’S SERVICE
  • Service
  • Tables
  • Bookings
  • Guest context
  • SERVICE IN VIEW
  • TABLE BOOKINGS
  • GUEST CONTEXT
  • CLEAR RECORD CONTEXT

WHEN DETAILS LIVE APART

KNOW WHICH RECORD YOU NEED.

You may be serving overnight guests and people who are only joining you for a meal. Your team needs to check the right record without treating the two as the same thing.

Hands serving a plated dish

THE SERVICE

The dining team needs a clear view of the service itself.

THE BOOKING

A table booking has its own details. It should not be treated as an accommodation stay.

THE GUEST

Where Lodgewave shows connected guest or stay details, your team can use those details to inform the service.

THE SERVICE, STEP BY STEP

FOLLOW THE SERVICE FROM START TO FINISH.

Start with the dining information available to your team. Review bookings, look after the service and check only the guest details connected to it.

THE SERVICE NIGHT

03 · THE GUEST ARRIVES

CHECK THE GUEST DETAILS.

Where Dining shows a connected guest or stay record, check that it belongs to the dining booking you are handling before using it.

A dining room prepared for service

THE DINING WORKFLOW

THREE VIEWS OF THE SAME SERVICE.

SERVICE IN VIEW

KNOW WHAT IS BOOKED

KEEP THE RIGHT RECORD IN VIEW

GUEST CONTEXT, KEPT CLEAR

SOME DINERS ARE STAYING. SOME ARE NOT.

Your dining room can serve staying guests and restaurant-only diners in the same service. Keep each booking and its context clear.

IN-HOUSE GUEST

Where Dining shows a connected stay, use only the relevant details the product shows. That access does not let your team change the stay record or charge the guest's stay automatically.

RESTAURANT-ONLY GUEST

Your team needs the dining details for the booking in front of them. A meal-only booking does not need a room or stay record to be handled.

WHAT CHANGES FOR YOUR TEAM

THE SERVICE STAYS SIMPLE. THE CONTEXT STAYS CLEAR.

DINING TEAM

BEFORE
Service information and wider guest context can become separate lookups.
NOW
Work from the dining service and use the guest context that's already there.

FRONT DESK / GUEST SERVICES

BEFORE
A dining question may require checking whether the guest is staying, dining only, or both.
NOW
Use the relevant guest context without turning every dining booking into a room booking.

OWNER / MANAGER

BEFORE
A charge or booking can be misunderstood when its source is unclear.
NOW
Review dining activity and recorded context without presenting one transaction as another.

QUESTIONS FROM PROPERTY TEAMS

HOW DINING FITS THE WIDER STAY.

A daylight dining terrace overlooking water

NEXT STEP

SHOW US HOW DINNER RUNS AT YOUR PROPERTY.

Tell us how you take table bookings, run service and recognise guests who are staying with you. We'll show you the relevant workflow and discuss how Dining can be shaped around your property.

  1. 01Tell us about your dining operation.
  2. 02See the relevant workflow.
  3. 03Agree the next step.
Talk to us