In this article
Actions: Activity reservation created, modified, or deleted
Actions: Dining reservation modified or deleted
When a reservation belonging to an activity type that is integrated with table management is created, modified, or deleted in Bookings for LS Central, the solution will monitor those changes and synchronize with the table management dining reservation entry. The dining reservation will have the same Reservation no as the activity reservation.
Actions: Activity reservation created, modified, or deleted
When an activity reservation is created, the system will create a dining reservation with the same reservation no. for reference. When an activity reservation is deleted or canceled, the status on the dining reservation is set to canceled as well.
The following fields are then populated:
| Field | Description |
|---|---|
| Restaurant No. | Will be assigned the Store no. value from the activity location. |
| Reservation No. | Will be assigned the same number as the Activity Reservation No. |
| Dining Area | Will be assigned the dining area which is the default setting on the store. |
| Registered By | According to the current user. |
| Create Registered | The date and time of registration. |
| Client No. | The Activity reservation Client no. |
| Guest ID/Name | The name from the activity reservation. |
| Phone No. | The phone number from the activity reservation. |
| The email from the activity reservation. | |
| Reserved From Date Time | The time and date of the activity reservation. |
| Entry Type | Either set as Reservation or Wait list, according to status. |
| No. of Guests | The number of persons on the activity reservation. |
| Status | Set to Open or Canceled, depending on Activity Internal status. |
| Special Requests | The comments assigned on the activity reservation. |
Actions: Dining reservation modified or deleted
When the dining reservation is modified on the table management side, all the above fields are updated.
If the dining reservation is canceled or deleted, the reservation is also canceled in the Bookings module.
Note: Reservations created on the Bookings side are only kept in sync with table management entries. Reservations which are created on the table management side are not inserted into Bookings. Those would normally be “walk-ins”, and it would not be necessary to keep track of such reservations except in table management.