Tables - 2.60.0
Release Date: Staging 18 July 2023 | Production 1 August 2023
Status:
For detailed information on Tables 2.60.0 release please view a section below.

Tables - Ability to configure different deposit requirements per booking & cover limit - PPL-329

At the moment, an Events Admin user could only create a deposit rule that requires a deposit per person. However, this limits the flexibility Admins have when setting up their booking rules or entire Occasions. Moreover, it doesn't properly reflect the realities of larger events - those might be charged differently.
Because of that, we've decided to give Admins and Hosts more manoeuvrability when it comes to setting up booking rules and editing requirements for already existing bookings. This feature now allows Admin to add a booking rule with deposit required per booking rather than per cover. Example shown below:
This way, the Admin can simplify the deposit requirement for certain occasions or Menus in case a larger group or event is expected, where a deposit per individual would not be appropriate.
However, in order to maximise the flexibility, we've also added functionality that allows Hosts (both Events and Tables) on the ground to actively change the requirement if the conditions of the booking change. Please see the screenshots below:
Tables:
All of those changes to the deposit booking rule are also available through our External API.
Tables - Pre-Order - Pre-Order Required by Validation - PPL-1055

Currently, users can set the same arrival and pre-order dates which causes a problem as pre-order are sent in the morning on the day of the event. Since pre-orders must be prepared received and prepared in advance, we've decided to alter the pre-order logic slightly so that the pre-order date cannot be the same as Arrival Date.
Conditions for pre-order date cannot be the same as arrival date:
-
Booking rules with pre-order date set as ‘’0’’ also have the 1-day before rule applied.
-
Tables & Events applications cover this change.
For example, if the booking has:
-
Booking arrival date: 15th
-
Booking Rule: Pre-order required 1 day before
-
Pre-Order date is automatically set as: 14th.
-
User cannot set 15/07/2023 as pre-order due date either on tables or events application
If the Host user attempts to set the same date for pre-order as arrival date then they will see the following error messages:

Zonal ID | Description |
---|---|
393171 | Tables Host - Bookable areas enabled - edit bookings without creating a booking - no areas are returned |
441000 | [Tables] Tables with Events Integration - Update in Tables Host clears event tags |
442138 | Tables Host App - Validation Issue when Clicking on "Confirm & Continue" |
443485 | Tables - Cannot create booking when the booking arrival date and pre-order due date are in different months |