Install a booking widget and hand it back ready to use.
This guide is for agencies and web implementers adding Tableee bookings to a client’s site. The Business owner or an authorized dashboard admin controls which exact website origins can embed the widget. For more than five locations, contact Tableee about an Enterprise plan.
For one to five locations, Tableee Pro is £99 per location per month, plus VAT where applicable. Direct bookings have no cover fees or booking commissions.
Tableee / Your service, connected
More of your shift. One workspace.Tableee Pro
Current iframe and script embed options
Exact HTTPS website-origin setup for the Business
A desktop, mobile and handoff checklist for launch
Built around your service
Put the guide into practice
Less switching between tools. More time for your team and the guests in front of you.
By Tableee · Updated
01
Confirm the Business and its public booking page
Ask the client’s owner or authorized admin for the Business slug, booking link and an approved time to test. Use the Business website’s own booking flow and confirm what deposit, cancellation and guest-information steps should appear.
Keep the public /widget/{slug} link as a fallback booking destination.
Agree who will enter any test booking and how it will be cleared using the normal reservation workflow.
Do not run an unapproved live payment or use a real guest’s details for testing.
02
Save each exact HTTPS website origin
The Business owner or authorized dashboard admin opens Dashboard → Booking Widget → Embed and adds the site origin under Allowed origins. Enter only the origin, such as https://example.com; paths, queries, fragments and wildcard subdomains are not supported.
Add both https://example.com and https://www.example.com if the site serves both.
Include a non-default port when the published site uses one.
Check the exact scheme, hostname and port against the published page before installation.
03
Install the iframe snippet for the selected origin
In the dashboard Embed tab, select a saved origin and copy its Iframe snippet. The stable bootstrap URL checks that origin against the Business allowlist, then redirects to a short-lived signed widget URL. Copy the dashboard’s bootstrap URL; do not copy a final signed destination URL from the browser.
Preserve the /api/widget/{slug}/embed path and URL-encoded origin query.
Set a useful height and check the full flow on a smaller screen.
Do not change the slug, origin or Tableee host in the copied snippet.
Illustrative iframe markup — replace the slug and origin with values copied from the client’s dashboard
The Script copy button supplies a placeholder and loads Tableee’s widget code. It reads the embedding page’s origin automatically and creates the iframe through the same bootstrap endpoint. The data-tableee-origin attribute identifies the Tableee script host, not the client website origin to allow.
Use an HTML or embed block that permits an external script.
Keep the tableee-widget placeholder and the complete script attributes together.
The script option uses the exact origin of the page where it runs.
Illustrative script markup — copy the full client-specific snippet from the dashboard
Test the published page and resolve origin mismatches
Preview or publish on every allowed origin, then test on desktop and mobile. Confirm the correct Business and availability appear and that a test booking reaches the expected workspace. If the frame is denied, compare the live page’s scheme, hostname and port with the saved origins.
Test the production page on each apex or www address that serves it.
Verify available dates and times against the client’s booking settings.
For an approved test that creates a reservation, cancel it through the client’s normal workflow.
06
Hand off the installation and guest responsibilities
Give the client the published page location, installed method, exact saved origins and result of each agreed test. The Business remains responsible for booking rules, guest communications, privacy notices and payment terms.
Make sure the client knows who can change or remove allowed origins.
Link the Business’s privacy notice where guest information is collected.
Point the client to Tableee’s Privacy Policy and Terms for its processing terms.
Your questions, answered
Can an agency add the website origin for the client?
The Business owner or an authorized dashboard admin manages the Business’s Allowed origins list. Coordinate with them and confirm the saved entry before installing the iframe or script.
Should an agency use a signed URL from the browser?
No. Use the stable bootstrap URL copied from the dashboard. Tableee checks the supplied allowed origin and redirects to a short-lived signed widget URL.
How does pricing work for my Business?
For one to five locations, Tableee Pro is £99 per location per month, plus VAT where applicable. Direct bookings have no Tableee cover fees or booking commissions. For Stripe-powered online payments, local Stripe processing rates apply, plus the 1% Tableee commerce fee. For more than five locations, contact Tableee about an Enterprise plan using the Book a founder-led demo link on this page.
