Room operations in a house where half the room nights hang on an event.
Booking, reception, group logic and settlement in one system — built so that an event's room need is the same data model as the event itself, not a manual reconciliation between two systems.
Front office manager · Hotel director · Finance/accounting · Revenue manager
Categories and rooms with service status, reservations and events in the same grid, including both group and event allotments.
A monthly view of all allotments, with displacement analysis before you say yes to a room block.
Arrivals, departures and in-house on one screen; night audit is run from here.
Room assignment, controlled override of dirty rooms, a payment gate on group settlement and key cards at check-in.
Locked settlement (no double check-out), VAT split, invoice number, receivables and PSP settlement in the same transaction.
Separate invoicing, allotments, CSV import of attendee lists, shared or split settlement.
The system blocks overbooking in the transaction itself. No overbook switch.
Affects both the calendar and availability, not just a label.
Posts directly to a checked-in stay; items are governed by the same product catalogue as the events.
Export and deletion per guest, as a feature in the product.
An event with 400 delegates is one record, not 200 room nights you have to keep in sync by hand. The room block, the hall and the catering are connected in the data model, so a moved event moves the rooms with it.
The Property Management module. Pricing basis: per room. Housekeeping, reception, guests, channel, key cards and revenue are access areas within this module.
Norwegian and English interface; guest-facing surfaces, the employee portal and administration are fully translated. VAT handling for lodging and catering, EHF/PEPPOL invoicing and data processing in the EU. Every customer has its own database.
You don't need to take the whole platform to start.