More reservations do not automatically mean growth
A restaurant might receive 800 reservations in a month. Without knowing how many actually took place, how many people were served, which bookings were cancelled and when demand peaked, that number tells only part of the story.
Rezervem Manager provides operational reporting for reservations, guest traffic, cancellations, recorded no-shows and booking sources. Interpret these figures as operational signals rather than assuming that every metric provides automatic financial attribution.
Six metrics to examine first
Reservation count: the number of bookings created or completed in a period, depending on your chosen definition.
Guests served: the total number of people who actually arrived; it is not the same as booking count.
Cancellation rate: cancelled bookings divided by a consistently defined reservation base.
No-show rate: bookings marked as no-shows divided by the relevant reservation base.
Busy days and hours: the service periods with the strongest or weakest demand.
Booking source: whether the booking is associated with the telephone, website or another supported channel.
- Keep the period and calculation method consistent.
- Do not combine cancellations with no-shows.
- Do not confuse guest headcount with reservation count.
Use consistent denominators for cancellations and no-shows
For example, if a restaurant opened 500 bookings in a month, 50 were cancelled and 20 recorded as no-shows, cancellation rate is 10% and no-show rate is 4% when both use all 500 bookings as the denominator. Those percentages change if the report instead uses only bookings expected to take place.
Decide on the calculation rules before comparing periods. The no-show explainer discusses the metric in greater detail.
How should you measure the value of a booking channel?
A channel that generates many bookings may still result in relatively few seated guests if cancellations are frequent. Compare channels using booking outcomes and party sizes, not raw volume alone. Guest Network separately supports distribution and partner tracking.
Connecting a channel to guest spend requires the relevant POS or payment integration to be active. Booking-source reports in Manager should not automatically be presented as revenue reports.
Keep prepayments, card holds and visits separate
If you use prepayments or card preauthorizations through Pay as part of a no-show policy, examine transaction amounts, statuses and rules separately. A prepaid reservation does not prove the guest attended, and an amount on hold is not revenue.
Rezervem Pay handles booking-related prepayments and card holds; Manager provides the reservation and service context.
Turn reports into operating decisions
Before trying to fill a quiet Monday service with promotions, compare capacity, cancellations and guest counts by hour. If recorded no-shows are high, consider reminders, clear cancellation options or prepayment rules for particularly exposed services.
Use the reservation-status operations guide to improve the source records, and Rezervem Manager to explore reservation operations and reporting.