Orders and table bookings on the restaurant’s own website.

Order a dish, then confirm it as staff

The demo runs the production build for a fictional restaurant, Demo Bistro: an invented menu, public-domain photos and test guests. New orders and bookings arrive every hour and move through the kitchen on their own, so the admin panel always has today’s work. Emails and online payment are switched off. The demo account is a manager: orders, bookings, the menu and opening hours; settings and staff accounts stay with the owner. Nothing is reset, so what you change stays for the next visitor.

Delivery apps own the guest. Phone bookings live in a notebook.

• An order placed through a delivery app belongs to the app: the guest’s contact, the order history and a fee on every order.
• Bookings taken by phone end up on paper, and nobody sees how full the evening already is.
• A new dish, a sold-out item or holiday hours have to be changed in several places by hand.

Restaurant Platform puts ordering and booking on the restaurant’s own website and gives staff one admin panel for orders, bookings, the menu and opening hours. Delivery partners stay linked for the areas the restaurant does not deliver to itself.

What guests and staff get

A menu guests can order from

• Categories and dishes with photos, descriptions and prices including VAT, with separate rates for food and drinks.
• Options with surcharges — sides, sauces, extras — including choices the guest must make.
• Allergens, sold-out and hidden dishes, and a special price for a set period.
• Alcohol is marked on the dish and sold to adults only.

Pickup and delivery

• The guest chooses pickup or delivery; delivery zones are set by postal code, each with its minimum order, fee and hours.
• Time slots with a capacity per slot, or as soon as possible when the kitchen allows it.
• Payment in cash or by card on handover, or online through the Comgate payment gateway.
• The server prices every order again and refuses one whose total has changed since the guest saw it.

Table booking

• The guest picks the party size and the date and sees only the times that are still free.
• A suitable table is assigned automatically; larger groups are asked to call.
• The confirmation contains a link for cancelling until the deadline the restaurant sets.
• Staff enter bookings taken by phone in the admin panel, against the same tables.

An admin panel for the day

• The dashboard shows new orders, orders in progress, orders due today and bookings waiting for an answer.
• A new order or booking sends an e-mail and sounds an alert in the open admin panel.
• Orders move through confirmed, preparing, ready, out for delivery and completed; a cancellation needs a reason, which the guest receives.
• Each order can be printed for the kitchen, and its history shows who changed what and when.

Menu, hours and content without a developer

• Dishes, categories, options and allergens, with a CSV import and export of the whole menu.
• Timetables for opening hours, pickup, delivery and bookings, plus holidays and other exceptions.
• Banners, the gallery, text pages and the website’s own texts, with a report of missing translations.
• A save shows on the website within seconds, without a deploy.

Three languages, built for search

• The website in Czech, English and Ukrainian, each page with its own address and language alternates.
• A sitemap and structured data for the restaurant and its menu, generated from the content.
• The admin panel in Czech, English, Russian and Ukrainian, switched in its settings menu.

From the cart to the counter

1. The guest orders

   Dishes and options, pickup or delivery, a time slot, and payment on handover or online. The guest gets an e-mail with a link to follow the order.

2. Staff are alerted

   The kitchen receives an e-mail, and the open admin panel shows a banner and plays a sound.

3. The kitchen moves it on

   Confirmed, preparing, ready, out for delivery, completed. The guest is e-mailed when the order is confirmed, and with the reason if it is cancelled.

Guest data handled with care

The platform keeps only what an order, a booking or a message needs, and removes personal data once it is no longer needed.

• Names, phone numbers and e-mails are anonymised automatically after a retention period the owner sets, 24 months by default.
• A guest who asks to be forgotten is anonymised in orders, bookings and messages with one command.
• Four roles — owner, administrator, manager and content editor; every admin action is checked on the server and written to an audit log, with secrets redacted.
• Online payments are made on the payment gateway’s page; card details never reach the restaurant’s server.
• Google Analytics runs only when it is configured and the visitor agrees; without it there is no cookie banner at all.

Frequently asked questions

Type

Client project, shown with invented data

Demo

Live, new orders and bookings every hour

Website

Czech, English, Ukrainian

Admin panel

Czech, English, Russian, Ukrainian

Stack

PHP, Symfony, Doctrine, EasyAdmin, PostgreSQL, Next.js, React, TypeScript, Tailwind CSS, Docker, Caddy

• Live demo website
• Demo admin panel