Description
Automaize Restaurant Reservation adds a simple, self-contained table booking form to your restaurant website.
For the restaurant owner:
- Define your weekly opening hours (per day of the week).
- Add closed periods for holidays or vacation, which override the weekly hours for those dates.
- Add your tables, each with its own seat count.
- Choose which reservation lengths guests can pick from (e.g. 60, 90, 120 minutes), or turn duration selection off entirely so guests just book a table with no fixed length (it’s then held until closing time).
- Set the email address that should receive new reservation notifications.
- Set the sender name shown on reservation emails, instead of “WordPress”.
- Manage and cancel reservations from a simple admin screen, optionally emailing the guest a cancellation notice with your own custom message.
- Edit any reservation straight from the admin screen – guest details, party size, date, time, duration and table(s) – with availability re-checked for the (possibly changed) slot and an optional guest notification email.
- Add reservations manually (phone bookings, walk-ins) straight from the admin screen, with the guest confirmation email optional, combining more than one table with a checkbox for larger groups.
- Customize the wording of the guest confirmation, pending-confirmation, now-confirmed, updated and cancellation emails, with placeholders for the reservation details.
- Require your own confirmation for large parties: set a party-size threshold above which reservations wait for you to approve them instead of confirming automatically, choosing which table(s) to seat them at (combining several, if needed) when you confirm.
- Look up any past guest by name or email and see their full reservation history plus special requests in one place, and keep staff-only notes about them (preferences, allergies, etc.).
- Print a clean, ready-to-hand-to-staff daily reservations list for any date.
- Optional REST API for a companion mobile app: generate an API key under Settings > Mobile app to let a dedicated app manage reservations and guests, with optional push notifications for new reservations and status changes.
For your guests, on the reservation form:
- Enter the number of guests.
- Pick a date and how long they’d like to stay.
- See, in real time, whether a table is available for that party size and time.
- Enter their name, email, optionally a phone number and any special requests, and book instantly.
- Receive an email confirmation. The restaurant owner is notified by email as well.
The plugin matches each reservation to the smallest available table that fits the party size, so a party of two won’t tie up your largest table, and automatically prevents double-booking a table for overlapping time windows.
No external services or API keys required, and no data ever leaves your site.
AI disclosure
This plugin’s code was developed with the assistance of an AI coding tool (Claude, by Anthropic). All code was reviewed and tested by Automaize before release.
Usage
Add the reservation form to any page or post in either of these ways:
- Shortcode: place
[amzres_reservation_form]in the page/post content, in a Shortcode block, or in any widget area that supports shortcodes. - Elementor: drag the “Restaurant Reservation Form” widget (listed under the General category) onto the page, if Elementor is active.
Both display the exact same form; there is nothing extra to configure per placement, since opening hours, tables and durations are all set once under Reservations.
Installation
- Upload the plugin files to the
/wp-content/plugins/automaize-restaurant-reservationdirectory, or install the plugin through the WordPress plugins screen directly. - Activate the plugin through the “Plugins” screen in WordPress.
- Go to Reservations → Tables and add your tables.
- Go to Reservations → Settings and set your opening hours, allowed reservation durations and notification email. The shortcode is also shown on this screen.
- Add the
[amzres_reservation_form]shortcode to a page, or add the “Restaurant Reservation Form” widget in Elementor.
FAQ
Can I have different opening hours per day?
Yes. Each day of the week has its own opening/closing time, and can be marked closed entirely.
Can I close the restaurant for a holiday or vacation?
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.
Can I print a list of the day’s reservations for my staff?
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.
What happens if two guests try to book the last table at the same time?
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.
Does this plugin send confirmation emails?
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.
Can I change the sender name shown on these emails?
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.
Can I customize the wording of the confirmation and cancellation emails?
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.
Can I add a reservation myself, e.g. for a phone booking or walk-in?
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.
Can I skip asking guests for a reservation length?
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.
Can I require my own confirmation for large groups?
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 anyone else) from the moment the request comes in, even while it’s still pending.
Can I see a guest’s past reservations in one place?
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.
Does this require any external services or API keys?
No. Everything runs on your own WordPress installation.
Does this work with Elementor?
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.
Does this work with Breakdance or other page builders?
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.
Where’s the public reservation page?
Since 1.20.0, the plugin publishes its own ready-made, self-contained page at /reservieren/ – no WP Page or shortcode placement needed. It’s always available at that URL and needs no admin setup. The [amzres_reservation_form] shortcode remains available if you’d rather embed the form inside other content.
Changelog
1.21.1
- New: a “Aufgaben” wp-admin Dashboard widget for the same shared to-do list the app’s “Aufgaben” tab manages – check tasks off, quick-add a new one by title, click a task to reveal its description. Gated behind
manage_options(same access level as the plugin’s other admin screens), with its own nonce-protected AJAX actions – separate from the mobile-app API key the REST routes use.
1.21.0
- New: a shared staff to-do list (title, assigned-to, description, done) for the app –
GET/POST /staff/tasks,PUT/DELETE /staff/tasks/{id}. No per-user accounts exist in the app (everyone shares the same PIN-gated access), so “assigned to” is a free-text label, not a real user reference.
1.20.3
- Tweak: the guest-facing reservation form (field labels, status/error messages, confirmation text) and the related REST/AJAX messages are now in German instead of English – the plugin’s default text, not a bundled translation (WordPress.org doesn’t allow shipping compiled translation files, but writing the plugin’s own default strings in German is unaffected by that and needs no separate .mo file).
1.20.2
- Fix: 1.20.0/1.20.1’s rewrite-rule flush for
/reservieren/ran duringplugins_loaded(before other plugins’ post types/taxonomies are registered oninit), an expensive operation that could run on every request if the version-tracking option didn’t persist as expected – risky on hosts with a tight PHP memory/time budget. Now deferred to a one-time flag consumed oninit(after post type registration), exactly once per update.
1.20.1
- Fix: the plugin header was missing
Author URI, so “Von Automaize” on the Plugins screen didn’t link anywhere.
1.20.0
- New: a dedicated, self-contained
/reservieren/page matching the website’s own design (fonts, header, footer,.btnstyling) instead of inheriting whatever WordPress theme happens to be active – same approach already used for the Event Calendar plugin’s event pages. The[amzres_reservation_form]shortcode keeps working unchanged (and is what the new page uses internally). - New:
?event=<id>(optionally&date=YYYY-MM-DDfor a recurring event’s specific occurrence) on the reservation page prefills the special-requests field (Bezug: <Veranstaltungstitel>) and defaults the date – lets an event page or a printed flyer QR code link straight into a pre-scoped reservation. - Fix: the reservation form’s date picker now correctly recognizes Sonderöffnungszeiten and the Event Calendar plugin’s per-event “Tischbuchung freischalten” override when deciding whether a date is bookable at all – previously it only knew about the regular weekly schedule and closed periods, so it could incorrectly show “wir haben geschlossen” on a date that was actually bookable.
1.19.0
- New: Sonderöffnungszeiten (special opening hours) – date ranges with their own opening hours (e.g. special hours over Christmas), managed under Settings or via the staff app’s new management screen. Unlike closed periods, these open/widen bookability – they take priority over the weekly hours and closed periods, but still yield to the Event Calendar plugin’s single-day “Tischbuchung an diesem Tag freischalten” override on any specific date. Exposed via
GET /config(special_hours) for guest display, andGET/POST /staff/special-hours+PUT/DELETE /staff/special-hours/{id}for staff management.
1.18.1
- Fix:
GET /availability/slots(what the app’s “which times are free today” check calls) could return no slots at all on a date whose bookable hours are overridden to a shorter window than the regular weekly hours (e.g. via the Event Calendar plugin’s “Tischbuchung an diesem Tag freischalten”) when duration selection is disabled site-wide. The app computes its fallback duration from the regular weekly hours (it has no way to know about a date-specific override), so it could request a too-long duration that never fit the actual, shorter window.get_bookable_slots()now recomputes the real per-slot duration itself (same as booking creation already did) instead of trusting the caller’s guess – read and write paths now agree.
1.18.0
- New:
AMZRES_Reservations::create_from_ticket_order()– creates a reservation from a paid event ticket purchase (called by the Event Calendar plugin’s new in-app ticket purchase feature once a WooCommerce order is paid). Automatically assigns a table when one is available, degrades to apendingreservation for the existing staff approve flow otherwise – never fails outright, since by the time it runs the guest has already paid. The shared insert/notify logic behind this andcreate_guest()is now a single private helper (finalize_new_reservation()), no behavior change for existing callers.
1.17.1
- The event newsletter now includes an editable intro paragraph above the event list (
GET /staff/newsletter/previewtakes an optionalintro, with a suggested default returned asintro_suggestion).
1.17.0
- Added a staff-only event newsletter:
GET /staff/newsletter/previewbuilds a subject/body draft from upcoming events,POST /staff/newsletter/sendsends it immediately via FluentCRM to contacts tagged “Website Newsletter”. Requires FluentCRM to be installed and active.
1.16.0
- Added a dedicated guest address field (
GET /staff/guests/profilenow includesaddress, newPOST /staff/guests/address), separate from the free-form notes log – overwritten in place rather than appended, for noting a delivery/catering address against a guest.
1.15.0
- Fixed: editing a reservation that has several combined tables now correctly keeps all of them pre-selected (previously only the primary table loaded, silently dropping the others if you saved). The staff REST API now returns a proper
table_idsarray on every reservation, not just a singletable_id. - Added live table occupancy to
GET /staff/tables: passdate,timeandduration(and optionallyexclude_reservation_idwhen editing) to get each table annotated withoccupied: true/false, so the app’s table picker can show what’s actually free instead of just a plain list.
1.14.0
- Added a public newsletter signup endpoint (
POST /amzres/v1/newsletter) that bridges to FluentCRM if it’s installed and active: creates/updates the contact with double opt-in (sends FluentCRM’s confirmation email) and tags it “Website Newsletter”. No API key needed since it calls FluentCRM’s PHP API directly rather than going over REST. Does nothing harmful if FluentCRM isn’t installed – the endpoint just responds with a clear “not available” error.
1.13.0
- Added a REST API for the upcoming Kerstins mobile app: public endpoints mirror the existing booking form (availability, booking, restaurant info), and a staff API (protected by a generated API key under Settings > Mobile app) covers everything the Reservations and Guests admin screens can do – list/add/edit/approve/cancel reservations, manage guest notes, and register devices for push notifications (via an optional OneSignal integration) about new reservations (staff) and status changes (guests).
- Fixed: the large-party confirmation threshold (“Require confirmation for parties larger than”) no longer lets the biggest single table’s seat count silently cap how many guests can be requested. A party above the threshold is now always routed to the host for review (and possibly seated across combined tables when confirmed), instead of being rejected outright whenever it exceeds one table’s capacity – the booking form, availability check and REST API all follow this now.
- Changed: the “Upcoming” tab on the Reservations screen now also includes pending reservations (not just confirmed ones), so everything coming up is visible in one place. The “Pending” tab remains as a focused needs-action queue.
1.12.0
- Added the ability to edit a reservation from the Reservations screen: guest name, email, phone, special requests, party size, date, time, duration and table(s) are all editable in place, with availability re-checked against the (possibly changed) slot – the reservation’s own current booking is excluded from that check, so keeping the same table is always allowed. Includes a new, editable “reservation updated” guest email, sent optionally, which only mentions the previous date/time when that actually changed.
1.11.0
- Added the ability to combine several tables on one reservation: check more than one table when adding a reservation manually, or when approving a pending large-party reservation. Table availability checks and the “Table” column/emails now account for every table on a reservation, not just one. Combined seat capacity is only a soft check – it’s flagged after saving, never blocked.
1.10.0
- Added large-party confirmation: set a party-size threshold above which reservations need your active approval before they count as confirmed, instead of confirming automatically. Includes new “pending confirmation” and “now confirmed” guest emails (both editable), a Pending tab and Approve action on the Reservations screen, and an admin notice when reservations are waiting.
1.9.0
- New:
amzres_hours_for_datefilter, so other plugins can open (or further restrict) a specific date for reservations – e.g. an events plugin making a normally closed day bookable for an event.
1.8.0
- Added a Guests screen: look up any past guest by name or email and see their full reservation history (including special requests) in one place, plus a staff-only notes log for preferences, allergies, etc. Guest names on the Reservations screen now link directly to their profile.
1.7.0
- Added a way to turn off reservation duration selection entirely: guests just pick a date, time and party size, and the table is held until closing time instead of a fixed length.
1.6.0
- Added a way to add reservations manually from the admin screen (e.g. for phone bookings or walk-ins), with the guest confirmation email optional.
- Added editable email templates: customize the subject and body of the guest confirmation and cancellation emails under Settings, with placeholders for the reservation details.
1.5.0
- Added an optional cancellation email: when cancelling a reservation from the admin screen, you can now include your own custom message, or skip the email entirely.
- Added an “Email sender name” setting so reservation emails no longer show “WordPress” as the sender.
1.4.0
- Added a printable daily reservations list: pick a date on the Reservations screen to open a clean, print-ready page for handing to staff.
1.3.0
- Renamed all internal function, class, hook and option names to use a unique
amzres_/AMZRES_prefix (previouslyarr_/ARR_, which was too short and could conflict with other plugins), per WordPress.org plugin review requirements. Existing data is migrated automatically on update; no action needed. - Removed the bundled German translation files. Translations for WordPress.org-hosted plugins are managed automatically via translate.wordpress.org.
1.2.0
- Added closed periods (holidays, vacation): date ranges under Settings that override the weekly opening hours.
1.1.0
- Added an optional “Special requests” field to the reservation form, shown to the restaurant owner in the admin reservations list and in both emails.
- Fixed the time selector only ever showing one bookable time slot in some setups.
- Fixed the anti-spam honeypot field being visible when the form was rendered outside the shortcode’s own page content (e.g. some page builder widgets).
1.0.0
- Initial release.