The official Bukio WordPress plugin is here — add a booking form to your website in a few clicks. View it on WordPress.org

Customisable rules

The restaurant is yours. The rules should be too.

More than 50 settings decide how your booking system works: when guests can book, for how many, for how long, what can be combined, when emails go out. You define them all – enforcing them is the system's job.

Pick a rule type

Mon–Thu11:00–23:00 · kitchen 22:30
Fri–Sat11:00–01:00 · kitchen 00:00
Sunday12:00–22:00 · kitchen 21:30

Separate opening, closing and kitchen-close per day — the form always shows the day's schedule.

What can you control?

The full catalogue in six groups — every setting lives in the admin panel, no code needed:

01

Opening hours & time

  • Weekly hours per-day opening, closing, kitchen close
  • Special days holidays, closures, modified hours — one-off or weekly recurring
  • Daily breaks blocked windows within a day (e.g. 3–5 pm)
  • Advance-booking limits minimum (e.g. 2 hours) and maximum (e.g. 30 days) lead time
  • Slot length density of bookable start times (5–120 min)
Dynamic time rules
02

Tables & capacity

  • Table combining automatic merging of smaller tables for large parties
  • Oversizing ratio how large a table can go to a smaller party (0–300%)
  • Areas indoor, terrace, private room — each with own settings
  • Table definitions table counts and capacities per area
  • Party-size cap the maximum party size accepted online
Area management
03

Booking rules

  • Auto-approval instant confirmation or manual review
  • Same-day booking block same-day online bookings after opening
  • Booking until close bookable up to closing time, or only earlier starts
  • After kitchen close allow bookings after the kitchen closes (drinks)
  • Non-bookable days open, but without online booking (walk-in nights)
04

Cancellation & changes

  • Online cancellation whether guests can cancel online
  • Minimum notice how late a booking can be cancelled (e.g. 2 hours)
  • Required reason whether a cancellation reason is mandatory
  • Cancellation email automatic notification on cancellation
  • Custom policy text your own cancellation message for guests
05

Email notifications

  • Guest emails confirmation, pending, modified, rejected, cancelled
  • Reminder X hours before the booking (e.g. 24)
  • Feedback request X hours after the visit
  • Restaurant notification email to your team about every new booking
  • Individually switchable every email type can be toggled separately
AI email templates
06

Durations

  • Available lengths which durations guests can choose from
  • Party-size rules different lengths for couples and large groups
  • Day & time dependent separate order for peak times and weekends
  • Special-day durations own durations for NYE and event days
Dynamic time rules

One restaurant's complete rulebook

This is how it comes together in practice — every line set once by the owner, enforced by the system ever since:

Opening hours

  • Mon–Thu: 11–23 (kitchen 22:30)
  • Fri–Sat: 11–01 (kitchen 24:00)
  • Sun: 12–22 (kitchen 21:30)
  • Tue 14:30–16:00: break

Booking frame

  • Lead time: min. 2 h, max. 30 days
  • Approval: manual
  • Same-day after opening: blocked
  • Party cap: 20 guests

Tables

  • Combining: enabled
  • Oversizing: max. 100%
  • Indoor: 12 tables · Terrace: 8 (seasonal)

Cancellation

  • Online cancellation: allowed
  • At least 2 hours before
  • Reason: required
  • Notification email: automatic

Emails

  • Confirmation: instant
  • Reminder: −24 h
  • Feedback request: +2 h
  • Restaurant notice: every booking

NYE (special day)

  • 1–4 guests: not bookable online
  • 5–6 guests: 3–4 h
  • 7+ guests: 4–6 h

The system applies all of this to every single booking by itself — a rule-breaking booking can't even arrive.

Set it once. Every booking obeys.

Create your account, define your own rules — and your booking system will work exactly the way your restaurant does.