Automaize Restaurant Reservation

Yes. Each day of the week has its own opening/closing time, and can be marked closed entirely.

Yes. Under Reservations → Settings, add a closed period with a start and end date (and an optional reason, for your own reference). Dates within that range are treated as closed regardless of the weekly opening hours.

Yes. On Reservations, pick a date next to “Print daily list for” and click Print. It opens a clean, printer-friendly page listing that day’s confirmed reservations by time, with table, party size, guest and contact details.

Availability is re-checked on the server at the moment a reservation is submitted, so only one of them will succeed; the other is asked to choose a different time.

Yes, it uses wp_mail() to send a confirmation to the guest and a notification to the restaurant’s configured email address. When you cancel a reservation from the admin screen, you can optionally send the guest a cancellation email with your own custom message.

Yes. Under Reservations → Settings → Email sender name, set the name shown to recipients instead of the WordPress default “WordPress”. It defaults to your site’s name.

Yes. Under Reservations → Settings → Email templates, edit the subject and body of both emails. Placeholders like {guest_name}, {date}, {time} and {details} are replaced with the actual reservation details when the email is sent; leave a field blank to restore its default text.

Yes. On Reservations, click “+ Add reservation”, pick date, time and the guest’s details, and check the table(s) to seat them at – check more than one to combine tables for a large party. You can choose whether to send the guest a confirmation email; availability is still checked against existing bookings for every table you check.

Yes. Under Reservations → Settings → Reservation duration, uncheck “Ask for a reservation length”. Guests then just pick a date, time and party size; the duration field disappears from the form, and each booked table is held for the rest of that day’s service (until closing time) instead of a fixed number of minutes.

Yes. Under Reservations → Settings → Large party confirmation, set a party-size threshold. Reservations above it are not confirmed automatically: the guest gets a “we’re reviewing your request” email, you get an “action required” notification, and the reservation shows up under the Pending tab on the Reservations screen with an “Approve” action. Approving opens a review screen where you check off which table(s) to seat the party at – combine several if one table isn’t enough – before confirming; the guest is then emailed that it’s now confirmed. Every table involved is held (not offered to…

Yes. Go to Reservations → Guests, search by name or email, and open a guest to see every reservation they’ve made (including any special requests they entered) plus a staff-only notes log where you can jot down things like preferences or allergies. Guests are matched by email address. You can also get there directly by clicking a guest’s name on the Reservations screen.

No. Everything runs on your own WordPress installation.

Yes, a native “Restaurant Reservation Form” widget is available in the Elementor editor (under the General category) whenever Elementor is active. It renders the exact same form as the [amzres_reservation_form] shortcode.

Yes. Use the [amzres_reservation_form] shortcode in your page builder’s Shortcode or Code/HTML element (Breakdance, Divi, Bricks, etc. all provide one). The form works the same way everywhere it’s placed.