Connect submitted reservation movements with the final guest count used in service analysis.
The reporting workflow combines initial bookings, walk-ins and drinks/shisha guests, then subtracts cancellations and no-shows. Consistent definitions matter: the same guests should not be entered as both initial bookings and walk-ins.
Lunch, dinner and Beach & Pool have individual pax sections. Review the selected meal before adding counts across the venue. A record lacking detailed pax breakdown should not be treated as if those components were verified.
The final guest count can hide movement between reservations and walk-ins. Reviewing the components helps managers understand how the service developed. Hosporiq reports submitted figures; it does not automatically replace a reservation system’s live booking ledger.
The current reporting workflow uses submitted pax data. Any direct reservation-system feed needs a separately verified integration.
Book a demo at hello@hosporiq.com. Bring your venue structure and a sample of the reporting inputs you use today so the discussion can focus on data scope, permissions and the relevant management decisions.
See how Hosporiq connects service reports, revenue analytics, purchasing, P&L visibility and executive alerts.
Request a private demo