Events Setup • Booking Rule

Created 20 November 2025 • Updated 20 November 2025

Booking Rules

Booking Rules allow you to set specific requirements and restrictions for bookings.

Navigate to Events Admin → Booking Rules

Creating a Booking Rule

Follow these steps to create a booking rule:

  1. Click Add New Booking Rule

  2. Enter the Booking Rule Name

  3. Click Add New Condition and select the required condition

  4. In the Actions section, choose the requirements you want to enforce

  5. Configure the details of the Action

  6. To add multiple Actions click +Add New Action

  7. To enable the Booking Rule click the Enabled box

  8. Click Save Changes to save the booking rule

Bookings can only link to one Booking Rule. The Booking Rules list acts as a hierarchy. If the top Booking Rule does not apply then the system will look at the next one and so on. Booking rules can be moved up and down the hierarchy list using the arrows

Disabling a Booking Rule

Follow these steps to disable a booking rule:

  1. Locate the Booking Rule

  2. Tick the rule you want to disable

  3. Click Save Changes

    As soon as you click save changes, this rule will no longer be valid for new bookings. Any existing bookings on that rule will remain on the rule unless manually removed and their requirements edited

Reordering Booking Rules

Follow these steps to reorder booking rules:

  1. Locate the arrows on the right of the page

  2. Select either the upward arrow to move the rule up, or the downward arrow to move the rule down. This will define the rule hierarchy

  3. Click Save Changes

    As soon as you click save changes, this new rule ordering will take commence. Any existing bookings on a rule will remain on the rule unless manually removed and their requirements edited

Editing a Booking Rule

Follow these steps to edit a booking rule:

  1. Locate the Booking Rule

  2. Click the edit rule symbol

  3. Make the required changes to the rule

  4. Click Save Changes

    If there are any existing bookings assigned to a rule, when making an change, it will prompt a message. You will have the option of whether you want to update the rule template and it apply to only new made bookings, OR you can accept that the system will prompt existing bookings that the rule has now been changed. This will prompt the "Requirements Updated" template to send. Click here to find out more about email templates
  5. Click "Yes, update existing bookings"

    You won't be able to make any new changes to this booking rule until the bulk update is complete. It will depend upon how many future bookings you have as to how long this could take

Copying a Booking Rule

Follow these steps to copy a booking rule:

  1. Select from the Actions column to Copy the required Booking Rule

    The copied layout will appear in an editable view. In the Internal name it will be prefixed with "Copy of...", to indicate it's a duplicate of the original
  2. Edit the fields as your require

  3. Click Save Changes

Deleting a Booking Rule

Follow these steps to delete a booking rule:

  1. Select from the Actions column to Delete the required Booking Rule

    A pop-up will display either asking "Are you sure you want to delete **name** occasion?". OR it will state "**name** cannot be deleted as it is linked to active bookings"
  2. Select yes

  3. Click Save Changes

If the Booking Rule cannot be deleted due to it having future bookings active, but you require no further bookings being assigned this requirement, we recommend you disable the Booking Rule. Disabling will prevent any future bookings being made with this requirement

Booking Rule Settings

Estate Admin level access allows the ability to enable or disable the option for the host to be able to override individual booking requirements, such as deposit, pre-order, etc, in the Host Application.

Follow these steps to enable or disable:

  1. Click the cog on the top right of the Booking Rule page

  2. Using the drop down locate either the Estate, Companies or Sites

  3. Select from the drop downs either Yes or No

  4. Click Save Changes

    Allowing the Host to override booking requirements will present a new button in the Host applications. Within Tables and Events it will be named "Edit Requirements". This can be found when editing a booking

Conditions

Name Description
Capacity → Cover Range

This will target bookings by the number of covers equal to or over the minimum value

Provisions → Occasion

This will target bookings made against any of the selected occasions

Provisions → Menu

This will target bookings that have booked with any of the selected menus

Provisions → Extra

This will target bookings that have added any of the selected extras

Actions

Name Description
Payments → Require Deposit

When requiring a deposit action, you will be required to define:

  • A description. This will be visible within the Guest Portal requirements tile

  • A monetary value defined by either an "Amount Per Booking", or an "Amount per adult/ child" split

  • A period of time the deposit is required, either "Due before arrival" or "Due after booking date"

  • As an optional setting, you can define this action to "Require deposit as part of the API and Widget booking journey"

The organiser will be required to pay a deposit within 10 minutes of the booking being created via the API or Widget, otherwise the booking will automatically be cancelled. This requires the site to have an Events integrated payment provider
Payments → Require Card Guarantee

When requiring a card guarantee action, you will be required to define:

  • A description. This will be visible within the Guest Portal requirements tile.

    It is recommended that the amount charged is entered here so it displays during the booking journey and therefore the customer is aware how much may be charged in the event of a no show
  • A monetary value defined by an "Amount per adult/ child" split

  • A period of time the deposit is required, either "Due before arrival" or "Due after booking date"

  • Enter in any terms and conditions for the credit card guarantee

  • As an optional setting, you can define this action to "Require card guarantee as part of the API and Widget booking journey"

The guest needs to guarantee the payment card within 10 minutes of the booking creation or the booking will cancel. This requires the site to have an Events integrated payment provider
Payments → Require Pre-Payment

When requiring a pre-payment action, you will be required to define:

  • A description. This will be visible within the Guest Portal requirements tile.

  • A select value - this is currently default set at 100%

  • A period of time the deposit is required "Due before arrival"

Pre-payment can only be defined in conjunction with a pre-order. Once pre-order selections are completed, the guest(s) can then pay for their selections in the guest portal
Payments → Require Extras Payment

When requiring an Extras payment action, you will be required to define:

  • A description. This will be visible within the Guest Portal requirements tile

  • As an optional setting, you can define that the extras payment be required in order to complete the booking form. You can tick: "Require payment as part of the API and Widget booking journey"

The organiser will be required to pay for any extras within 10 minutes of the booking being created via the API or Widget, otherwise the booking will automatically be cancelled. This requires the site to have an Events integrated payment provider
Pre-Orders → Require Pre-Order

When requiring a pre-order action, you will be required to define:

  • A description. This will be visible within the Guest Portal requirements tile

  • A period of time the deposit is required "Due before arrival"

In the Guest Portal guest(s) will see a countdown of time left to place their pre-orders. After this time they will no longer be able to place the pre-order themselves via the Guest Portal
Bookings → Place an Enquiry

When requiring an Enquiry action, you will be required to define:

  • A description only. This will be visible within the Guest Portal requirements tile

This action will force all attempts of bookings via an online journey into an Enquiry state

If multiple Actions are used in combination with 'Place as Enquiry' (e.g Deposit and Pre-order), these will be requested from the customer once the Enquiry as been accepted