Recurring services

Recurring services save you from rebuilding availability every week. Create the normal pattern once, then use one-off changes for unusual dates.

Create a weekly service

1. Open Capacity.
2. Choose Add service.
3. Enter a name such as Lunch, Dinner or Sunday Lunch.
4. Select the days that share the same rules.
5. Set the service start and end times.
6. Continue through the capacity steps and save.

If Friday and Saturday need different pacing from Tuesday to Thursday, make them separate services instead of forcing one rule set across the whole week.

Table time and turn buffer

Table time is how long the booking occupies its table. Set it to the realistic dining duration for that service.

Turn buffer adds breathing room between one booking ending and the next booking using the same table. A buffer can protect reset time and reduce back-to-back pressure.

These values matter to table availability: a table that looks free at the requested arrival time may still be unavailable because an earlier booking runs into that period.

Advance booking window

Use:

• Minimum advance to stop very late online bookings when the venue needs preparation time.
• Maximum advance days to control how far into the future guests can book.

Staff can still manage bookings operationally, but the public booking path respects the configured service rules.

Edit an existing service

Choose the service for the day you want to change and edit it. Changes affect future availability for that recurring day.

For a single exceptional date—public holiday closure, private event, reduced-capacity night—use Blackouts and one-off changes instead of rewriting your normal weekly service.