Time zone per hotel
Cancún and Mexico City don't share midnight. Seatings, attendance and reports use the hotel's time zone, not the server's.
Solutions · Chains and groups
Management compares occupancy and no-shows across properties; each hotel runs on its own time zone, its own PMS and its own rules. Roles and permissions decide who sees and who touches what.
Multi-hotel
Cancún and Mexico City don't share midnight. Seatings, attendance and reports use the hotel's time zone, not the server's.
Organization, hotel or restaurant: the most specific rule wins. A chain sets the standard; a property adjusts it.
Owner, admin, management, reservations and host, with permissions tunable per user. The host doesn't see prices; reservations doesn't touch rules.
Every action with user, IP and time. Kept for 12 months.
Emails to guests go out from each brand's own domain.
Each external channel sells at most the share of capacity you assign it, per restaurant.
Management
Reservations and covers per restaurant and seating, attendance and cancellations, hotel by hotel and as a whole. The same screen for the group's F&B director and for each property's manager, with what each is allowed to see.
Diners across the group
The guest profile belongs to the organization: if a guest dines at your Cancún hotel and then at the Mexico City one, their allergies and visits go with them. Each user sees only what belongs to the restaurants assigned to them.
Yes. Rules are defined per organization, hotel or restaurant and the most specific one wins.
Only the ones assigned to them. A host sees their restaurants; a manager, their hotel; management, the group.
Yes. The integration is configured per hotel, with its own credentials and category mapping.
Request a demo and tell us how many hotels and restaurants you run; we'll send you an annual proposal.