A changed reservation should reach the whole team, rather than remain in a message on someone’s phone. ERP Core includes a calendar and reservation records for organising activities and events.
Example: a group grows from 8 to 12 guests
A customer says the group will have 12 guests instead of 8 and requests a different time. In a restaurant scenario, the responsible person checks the interval, table or zone and updates the reservation. The kitchen and service staff need the same version of the details.
Enter the group’s details
The demonstration below uses a fictional customer with six adults and two children. Select the sales channel, table or area, status and responsible staff. Kitchen notes and staff notes have separate fields. This is a form being completed, not a confirmed booking.
What do you track in a reservation?
- Time: the start and end of the booking.
- Location: the relevant zone and table.
- Guests: the total number and, where useful, adults and children.
- Notes: operational information and kitchen notes.
- Status: the reservation’s position in the configured workflow.
A straightforward workflow
- Record the request with the necessary information.
- Check availability and allocation in the context of the venue.
- Confirm the details and keep changes in the shared record.
- Before the event, review the guest count, time and notes with the team.
Notifications and calendar integrations depend on project configuration. During a demonstration, we check exactly what is sent, to whom and when.
For restaurants and event venues
The scenario could be a group table, an event requiring separate preparation or an activity involving several people. The example above is fictional; capacity and confirmation rules are defined for your operation.