A restaurant website with its own booking system.
A restaurant website with online booking lets guests reserve straight from your site, in their language, without a booking platform in between. We built one for a brasserie in France: two languages on two domains, booking requests that land in the restaurant's inbox, and a back office where the team confirms or declines each one.
Site sheet
- Built for
- A brasserie in France
- Stage
- Live
- Languages
- French and English, one domain each
- Bookings
- Requests confirmed by the team in a back office
From the guest's phone to the team's agenda
- 01
The guest books
On the site, in French or English: date, time, party size, contact.
- 02
The request is kept
It is stored, sent to the restaurant's reservations inbox and acknowledged to the guest by e-mail at once.
- 03
The team decides
In the back office, the restaurant confirms or declines each request, with an agenda view of the days ahead.
- 04
The guest hears back
Confirmed or declined, the guest receives an e-mail either way — nobody is left wondering.
A site that is yours, and that keeps working
Fast, plain pages
Menu, story, opening hours, how to come — as fast static pages that load on mobile data.
Two languages, two domains
One codebase serving each language on its own domain, so each version can be found in its own language.
Your bookings, your inbox
Requests arrive where the team already works, with the back office for the decision.
Tested before every change
Automated tests of the booking API run before anything goes live.
One-command rollback
If a change misbehaves, the previous version is back in one command.
Hosted and watched
It runs in Docker on infrastructure we operate; a change goes live in minutes.
When a website with booking is enough
A single restaurant that confirms bookings by hand — a brasserie, a bistro, a café with a terrace — usually needs a good website and a reliable request flow, not a floor-plan system. The team keeps control of every table and the guest gets an answer.
A group, or a restaurant that seats many covers a night, needs more: instant confirmation, a live floor plan, a guest CRM and WhatsApp reminders. That is TablePilot, and the booking platform we built for a restaurant group.
Small details that cost bookings
- Check the inbox accepts outside mail. A shared reservations address must accept messages from the booking system, or requests vanish silently. We test delivery before launch.
- Answer declined guests too. A guest who hears nothing books elsewhere and does not come back. A polite "no, but" keeps them.
- Holidays and closures belong in the system, not on a note by the till — otherwise guests book days you are closed.
The brasserie project
- Restaurants · FranceLive
A bilingual website and booking back office for a brasserie
A French and English website for a brasserie, with its own booking system: the guest books online, the request lands in the restaurant's reservations inbox, and the team confirms or declines it from a back office — which e-mails the guest either way.
- Two domains, one per language, from one codebase
- Booking requests stored, e-mailed to the team and acknowledged to the guest
- A back office where the restaurant confirms or declines each booking
- Automated API tests and a one-command rollback
Related
Frequently asked questions
Can a restaurant take bookings on its own website without a booking platform?
Yes. The booking form on the site stores each request, e-mails it to the restaurant and acknowledges it to the guest; the team confirms or declines it in a back office, and the guest is e-mailed the decision.
Can the website be in two languages?
Yes. We built a French and English site served on one domain per language, from one codebase.
Do we need TablePilot instead?
If you seat many covers, run several venues or want instant confirmation with a floor plan and WhatsApp reminders, yes. For a single restaurant that confirms bookings by hand, a website with a booking back office is often enough.
How do we start?
Book a discovery call with your current site or menu. We propose the pages and the booking flow, show you a working preview, and go live once you approve it.
How is it priced?
We scope it with you, including hosting and upkeep, and do not publish a price.
A new site for your restaurant?
Send us your current site or menu. We will show you the site and the booking flow we would build.