A restaurant owner at a café table working on a tablet

TutorialsSet it up,
step by step.

Twenty-three guides written from the product itself, with every click shown: first the website, the domain and the email, then the whole operation, from bookings and live service to the kitchen, the till and the numbers.

A waiter serving a table of four in a dark wood dining room TableSpark at work.Watch the full product film · 5:57

Chapter I · Get set up

The founding afternoon.

Publish the website, put your own name on it, and answer from an address that matches. Do these three once and everything after runs on top of them.

Chapter II · Run the day

The daily machine.

The dashboard you glance at, the menu guests read, the hours and rules that guard your book, and the floor where bookings, orders and receipts actually happen.

Guide 04: Around your dashboard, with the real TableSpark screenGuide 04 · 11 steps · 10 minAround your dashboardWhat every card on the home screen means, where the alerts live, and where your account and plan are managed — the five-minute orientation that makes the rest obvious.Guide 05: How to put your menu online, with the real TableSpark screenGuide 05 · 8 steps · 10 minHow to put your menu onlinePhotograph the paper menu and let the scan draft it, then tidy sections, prices, photos and allergens in the editor — changes reach your live site the moment you make them.Guide 06: How to set your hours and booking rules, with the real TableSpark screenGuide 06 · 7 steps · 8 minHow to set your hours and booking rulesWeekly hours and bank-holiday overrides in Settings; sittings, party sizes, lead times, deposits and one-off closures on the Bookings page. Set once, enforced every night.Guide 07: How to run your bookings, with the real TableSpark screenGuide 07 · 8 steps · 10 minHow to run your bookingsEnquiries land in the Inbox, bookings live in the diary, and every party gets the right table — the picker, the waitlist and the floor-plan editor included.Guide 23: Take group pre-orders, with the real TableSpark screenGuide 23 · 9 steps · 14 minTake group pre-ordersEvery guest at a large booking gets a private link, lists their allergies and picks a dish per course; you set the cut-off and print the kitchen sheet.Guide 08: How to run service at the table, with the real TableSpark screenGuide 08 · 8 steps · 8 minHow to run service at the tableThe live floor shows every table’s state; the booking sheet is the till. Seat guests, take the order, settle one bill — without leaving the room.Guide 09: How to take orders online, with the real TableSpark screenGuide 09 · 11 steps · 12 minHow to take orders onlineYour own Order page takes dine-in, collection and delivery orders with 0% TableSpark commission — and every order lands on one screen that runs the kitchen.Guide 10: How to set up printers and receipts, with the real TableSpark screenGuide 10 · 6 steps · 6 minHow to set up printers and receiptsConnect a CloudPRNT printer, give it a role — kitchen tickets or guest receipts — shape the ticket in the editor, and print a test page before service.

Chapter III · Grow the room

The compounding part.

Know your regulars, write to them well, sell dinners before they happen, run the team without spreadsheets, and read the numbers that say it’s working.

Chapter IV · Go further

Close the circle.

The money, through your own Stripe and your own bank at 0% TableSpark commission; a walk through your restaurant exactly as a guest sees it; and the app that walk leads to.

Chapter V · Run the operation

Back of house, end of night.

Close the day with every tender and the cash drawer accounted for, run the kitchen display with courses held and fired, cost every plate from its recipe, and settle any table the way it asks.

Questions people ask before they start.

How long does the first version take?

Most of an afternoon, and the slowest part is deciding on wording rather than any technical step. The menu scan removes the part that used to take an evening. You can publish a good site the same day and keep improving it afterwards — editing is not a second project.

FILM · 1:01The whole build in sixty-one seconds: design, menu, details, edit, publish.
Do I need a developer or an agency?

No. Every step is done from the same login, including the parts that normally need a specialist — structured data, sitemaps, canonicals and search verification are configured for you rather than handed to you as a task list.

What does it cost?

Building is free; you pay when you publish. Starter is £19 a month for the website, live menu, enquiries and guest records with managed search readiness. Growth is £39 for direct reservations, availability, floor plans, deposits, reminders and a custom domain with managed SSL. Full is £69 for direct online ordering, table QR ordering and up to five sites on one bill. Prices exclude VAT, and Stripe’s standard card fees apply to online payments.

Can I use my own domain?

Yes — buy one right inside Settings from £6.33 a year and it connects itself, with HTTPS handled for you, or connect a domain you already own. Every plan starts with a free subdomain so nothing blocks you from publishing on day one.

What happens to my menu when prices change?

You change the price and republish. Search engines are pinged on publish, so the corrected page is put forward immediately rather than waiting for the next crawl. This is the whole argument for running the site yourself: a menu is only accurate if changing it takes a minute.

Do I keep my guest data?

Yes. Enquiries, bookings and newsletter sign-ups are stored under your restaurant’s own account, visible in your inbox and guest list, and exportable to CSV whenever you want them.

More on the detail behind these steps: building a restaurant website, restaurant SEO in the UK, what a restaurant website actually costs and cutting booking commission.