A hotel may host a banquet in its hall and a dinner in its restaurant on the same evening. Sales works with both events, but each has its own layout, capacity and reservations. A shared date is not a reason to combine their records.
100LICA supports multiple events and seasonal overviews. Operations keeps the context of each event, while the responsible team can see the wider picture.
Every event has its own setup
A restaurant dinner and a large banquet may have different tables, prices and sales rules. A reservation needs to remain linked to the event it was created for. This is especially important when a guest says only that they are coming “for New Year”.
The first sales question is then which programme the guest wants. Seat selection and the rest of the reservation process follow from that. Clear event names help guests and staff alike.
What a combined overview should show
Managers benefit from an overview of reservations and payments across events. But a total is meaningful only when it is clear what it includes. Reserved seats, recorded payments and arrivals describe different things.
Currencies also need to be kept separate. Amounts in different currencies do not form a comparable revenue total without conversion rules. 100LICA overviews separate amounts by currency instead of presenting them as one sum.
Permissions follow responsibility
Every employee does not need the same access. Staff checking arrivals and staff recording payments perform different jobs. Organisation boundaries and user roles help align access with the task.
Before the season, list events, responsible people and required permissions. Then check one everyday task for each role: finding a reservation, recording a payment or checking an arrival.
A shared overview supports decisions when the individual records are in good order. To discuss working with multiple rooms and events, email sales@100lica.rs.
