Booking Engine: Closure Days

This guide explains how to apply temporary closures in booking engines (restaurants or services), allowing you to manage specific dates, date ranges, or recurring weekly closures without altering the engine’s general configuration.

1. Accessing the Closure Configuration

1. In the application, go to the Bookings section and select the Closure days option.
2. In the side menu, all active booking engines will appear. Select the engine (restaurant or service) to which you want to apply the closure.
3. Click the Add closure button.

2. Defining the Closure Type (Duration)

The system allows three modes to set the closure duration:

Single Date

Ideal for closing a specific day. Select this option and mark the desired day on the calendar.

Date Range

Useful for long periods (e.g., closure for renovations or holidays). You must select a start date and an end date. Optionally, you can add a reason (e.g., “Closed for renovations”).

Weekly

Allows closing specific days of the week during a given period (e.g., closing every Tuesday and Wednesday for the next 3 months).

• Define the start date and end date of the period.
• Check the days of the week on which the service will remain closed.

3. Advanced Configuration (Closure Scope)

Once the date is defined, you must decide what gets closed. By default, the system selects the entire restaurant or booking engine, but you can customize it:

• Closure by Category: If your engine has different categories (e.g., “Privilege”), you can close only a specific one.

  • Hide: The option disappears for the guest on that date.
  • Show as full: The option remains visible, but with a text indicating it is fully booked.

• Closure by Time Slots: Allows closing specific hours without blocking the entire day (e.g., reducing schedules in low season).

  • In the active time slot selector, check only those you want to close during the selected dates.

4. Save and Tracking

1. Click Save to apply the changes.
2. The system will generate a summary and record the action in the change history, allowing you to see which user created the closure, the date, time, and closure type.

Tip: Use this tool for changes that affect only specific dates or days. It is more efficient to manage closures this way than to modify the engine’s structural configuration for temporary changes.