Flexatech Table Reservations

Flexatech Table Reservations takes table bookings on your own site. Guests pick a party size, a day and a free time, then leave their name and a way to reach them. The plugin finds a table that fits, and you see every booking in the admin, day by day.

• A reservation form, as a block or the [fxtr_reservation_form] shortcode.
• A page where guests change or cancel their booking from the link in their email, as a block or the [fxtr_manage_reservation] shortcode. No account needed.
• Tables, areas, shifts and closed dates, so only real free times are offered.
• The table is held for a few minutes while the guest fills in the form.
• Confirm every booking yourself, or let small parties through on their own.
• HTML emails for the guest and for you, with an editor in the admin, and a reminder before the booking.
• Optional: Google Calendar sync, Sign in with Google on the form, Cloudflare Turnstile against spam, a map of your address, and a webhook.

External services

The plugin works without any of the services below. The deactivation survey is the only one on by default, and it runs only in the admin. Every other service is off until you turn it on or fill in its keys.

Deactivation feedback (Flexa Product Intelligence)

When you go to deactivate Flexatech Table Reservations on the Plugins screen, a short optional survey asks why. It is served by Flexa’s product intelligence service at https://product-intelligence.flexacommerce.com. It runs only on wp-admin/plugins.php, never on the front end, and never blocks deactivation.

What is sent, and when:

• On opening the Plugins screen: a request to /api/v1/config (product slug and tier) to load the survey configuration. The answer is cached for 6 hours.
• When you deactivate or use the survey: the reason you pick and any message you choose to type, sent to /api/v1/deactivations, /api/v1/events, /api/v1/feedback, /api/v1/feature-requests and /api/v1/recovery-events.

Every request includes an anonymous per-site identifier (a random UUID), the plugin version and tier. By default the survey also sends your WordPress version, PHP version and locale. No email, site domain, user identity, IP address or reservation data is collected. To stop sending the environment details, use add_filter( 'fxtr_deactivation_survey_config', fn( $c ) => [ 'collect_environment' => false ] + $c );. To turn the survey off completely, use add_filter( 'fxtr_deactivation_survey_enabled', '__return_false' );.

Flexa Terms of Service: https://flexacommerce.com/pages/terms
Flexa Privacy Policy: https://flexacommerce.com/pages/privacy

Google Calendar API

Copies bookings to a Google calendar you choose, and can read a second calendar whose events block online booking at those times. It runs only after you connect a Google account in the Google Calendar tab, with an OAuth client you create in Google Cloud.

• When you connect or disconnect: your site talks to accounts.google.com and oauth2.googleapis.com to sign in, refresh and revoke the access token.
• When a booking is made, moved or cancelled: your site sends the event to www.googleapis.com. The event holds the guest’s name, party size, date and time, table names, phone, email, notes and a link to the booking in your admin.
• When the form shows free times: your site asks www.googleapis.com for the events on the blocking calendar for that day.

Google Terms of Service: https://policies.google.com/terms
Google Privacy Policy: https://policies.google.com/privacy
Google APIs Terms of Service: https://developers.google.com/terms

Sign in with Google (Google Identity Services)

When you tick “Sign in with Google on the booking form”, the guest’s browser loads https://accounts.google.com/gsi/client on the booking page. A guest who uses the button shares their name and email address from their Google account, which fill in the form. Nothing is sent to Google from your server.

Google Terms of Service: https://policies.google.com/terms
Google Privacy Policy: https://policies.google.com/privacy

Cloudflare Turnstile

When you fill in a Turnstile site key and secret key, the guest’s browser loads https://challenges.cloudflare.com/turnstile/v0/api.js on the booking page to check that the guest is a person. When the form is sent, your site sends the Turnstile answer, your secret key and the guest’s IP address to https://challenges.cloudflare.com/turnstile/v0/siteverify.

Cloudflare Website Terms of Use: https://www.cloudflare.com/website-terms/
Cloudflare Privacy Policy: https://www.cloudflare.com/privacypolicy/

Google Maps

When you tick “Show a map”, the booking page shows a Google Maps embed (https://maps.google.com/maps) of the restaurant address you entered. The guest’s browser loads it from Google. The directions link next to the address also opens Google Maps. Only the restaurant’s address is sent, never guest data.

Google Maps Terms of Service: https://maps.google.com/help/terms_maps/
Google Privacy Policy: https://policies.google.com/privacy

Webhook

When you fill in a webhook URL, your site sends a JSON POST to that URL when a booking is made, changes status or moves. The body holds the booking, including the guest’s name, phone, email, party size, date, time and notes. The URL is one you choose and control, so its terms and privacy policy are those of whoever runs it.

Source code

The admin screen is a React app compiled into assets/dist. Its source ships with the plugin in apps/admin/src, together with the build files: package.json, pnpm-lock.yaml, apps/admin/vite.config.ts and apps/admin/tsconfig.json.

To build it:

1. Install Node.js 20 or later and pnpm 9 or later (npm install -g pnpm).
2. Run pnpm install in the plugin folder.
3. Run pnpm build. The files are written to assets/dist.

The JavaScript and CSS in assets/js and assets/css are not compiled and can be read as they are.