An illustrative 100LICA scenario. This describes how a New Year’s Eve dinner could be organised using available product features. It is not a report on a completed event, a confirmed restaurant endorsement or achieved business results.
An evening where every table has a plan
For a New Year’s Eve dinner at La Pista, imagine selling assigned seats in advance. Some guests come as couples, others book for a group. As sales draw to a close, the organiser needs to connect three kinds of information: where guests will sit, what has been paid and what needs to be prepared for their arrival.
The challenge is more than collecting reservations. Sales, the person checking payments and entrance staff need information that refers to the same reservation.
In this scenario, 100LICA connects those steps within one event. Specific prices, capacity, deadlines and cancellation rules remain subject to agreement with the organiser.
1. Preparing the room before sales open
The team prepares the tables and seats for the evening. They check numbering, capacity and which seats will be offered to guests. The system’s floor plan should reflect the actual restaurant layout, including constraints the organiser assesses on site.
When a guest requests a table for a group, sales discusses specific seats. The reservation is linked to the chosen seats, so the same layout remains the reference during event preparation.
2. Seat selection and reservation status
A guest chooses available seats. A temporary hold gives them a limited time to continue, while availability checks handle competing selections of the same seats.
The organiser defines in advance what is required to confirm a reservation and what happens when a deadline expires. Staff distinguish a temporary selection, a created reservation and its financial position. Guests receive explanations that match their actual situation.
3. Payments the team can verify
An authorised employee records a verified payment against the reservation. If the guest pays in instalments, the team tracks the recorded amounts and remaining balance. A PDF pro forma invoice can support payment communication.
This scenario relies on manual records. It does not assume active card payments or automatic bank reconciliation. A pro forma invoice does not replace a fiscal receipt or other documents the organiser is required to issue.
4. Names and menu choices before the event
The person who reserved a table updates the details for already reserved seats through secure access. Names and available menu choices remain connected to the reservation.
For a special dietary request, staff confirm what is possible with the kitchen. Entering a note does not guarantee that a request can be fulfilled. The organiser sets an update deadline and a process for changes afterwards.
5. Arriving in separate groups
Some members arrive earlier. Staff check the reservation by QR code or manually and record the number of guests who have arrived. When the others follow, staff can see how many arrivals remain under that reservation.
Before the dinner, the team rehearses with the actual devices and internet connection at the entrance. A responsible person is assigned to resolve disputed situations, so those decisions do not fall solely on the employee greeting guests.
What a real case study would measure
After implementation, we would compare time spent finding a reservation, updates staff copy manually and discrepancies during arrival checks. Each measure needs a baseline, an observation period and a consistent method.
We do not currently state improvement percentages, revenue achieved or employee quotations. A completed case study would add the confirmed event date, approved layout, features actually used and results the restaurant authorises for publication.
Applying the scenario to your event
This scenario is for restaurants selling assigned seats in advance and looking to connect reservations, payment records and arrivals. To discuss your layout and evening’s rules, email sales@100lica.rs.
