A website as goodas your dining room.
We build your restaurant's website and booking system as one. Guests see your actual room, choose their table and pay a deposit if you ask for one. No per-cover fees, and we look after it every month.
Most restaurants buy a website from one supplier and bookings from another. We build one place, and run it for you every month.
Four questions, then a table
The real flow at FLO, in the order a guest meets it. Party, evening, time, and then the seat itself.
One question at a time
The form asks for a party size and nothing else. Every answer folds into a single line and opens the next question, so the guest is never looking at a wall of empty fields.
Only the nights you trade
Mondays are missing because FLO is shut on Mondays. The dates come from the restaurant's own trading hours, so a guest is never offered an evening that cannot happen.
The real slots, not a wish
Every time here is one the engine can actually seat, checked against the floor as it stands that second. Last seating follows the weekday, because Friday runs later than Tuesday.
Then they pick their seat
The room itself, by the window or by the fire. Green rings are free, crossed tables are taken, and the one they choose is held for five minutes while they finish.
Guests pick their own table.
Guests book the window, the booth or the corner they wanted. Your team sees the same floor in the host panel, so nobody promises a table that's already gone.
Live component, sample occupancy. Change the party size and watch the small tables drop out.
Or choose a table from the list
Nothing chosen yet. Pick a table above.
The Red Room, modelled
FLO's real dining room, rendered from its 3D model and running on this page. It opens as a lit plan; press 3D to walk around the model itself. Tap a table to choose it. Free tables carry a green ring, taken ones a cross, and anything too small for the party dims out.
- Free
- Yours
- Taken
- Too small for your party
One booking, two views.
The guest gets your room, your menu and a confirmation in your colours. Your team gets the night: covers by the hour, who has arrived, who paid a deposit, and every guest's notes and allergies.
Demo data only. Reset demo data puts the week back.
Open it full screenSeat a table, mark a no-show, move a booking, close a day. This is the panel FLO's hosts sign into, in Latvian as they use it, on made-up guests that never leave this site. UK restaurants get it in English.
Your site,built around the booking.
Menu, private dining, events and gift pages, written and built for you, and edited by you when the menu changes. When you leave, the site leaves with you.
Your room, not a template
We design the site from the restaurant itself: its colours, its light, its photographs. FLO's is near-black and garnet because the room is.
One system underneath
The menu, the photos and the page text are edited in the same panel as the book. Change a dish at four and it is on the site at five.
Booking on your own domain
The table picker lives on your own site, in your style, not on a portal page with someone else's name at the top.
One supplier, one bill
The site and the booking are one build with one login, so there is no plugin and no widget to come apart on a Friday.
Coming from ResDiary, OpenTable, Collinsor a phone and a diary?
We move your future bookings and your guest list, run both systems side by side for a week, and switch on a quiet night. Live within 30 days of your floor plan, photos and menu, or no monthly fee until you are.
Moving your bookings and guest list is part of Signature and Group.
Send us the end date
Tell us when your current contract ends and we plan the switch for the week after it.
We move your book
Future bookings and your guest list come across from your old tool's export.
A week side by side
Both systems run together for a week, so nothing booked in the old one is lost.
Switch on a quiet night
We pick the night with you, and a named person is on the phone or WhatsApp through that service.
FLO takes its bookings by the table, on its own site.
The Red Room, the bar and the terrace are one modelled room on floresto.lv. A guest picks the window table or the seat by the fire, and the host stand sees the same floor.
A booking system is judged on the night it is busy
Anyone can take a booking on a quiet Tuesday. What follows is how the engine behaves when two guests reach for the last table at the same second, and it is all checkable in the code.
One table cannot be sold twice
A Postgres exclusion constraint over the restaurant, the table and the time range. An overlapping sale is refused by the database itself, so the guarantee survives any number of servers and holds even if the check above it is wrong.
reservations_no_double_bookingThe check and the booking are one act
Availability is read and the reservation written inside the same lock. Nothing can slip between them. Two servers racing for six tables produced exactly one winner, eighteen times out of eighteen.
read + write, one lockA table being chosen is held
Pick a table and it is yours for five minutes while you type. A second guest sees it as taken rather than filling in the whole form and losing it. The hold blocks its own sitting, not the whole evening.
holds_no_double_holdDeposits, when you want them
Stripe hosted checkout, so no card detail ever touches the site. The paid callback is signature-checked, refunds are a decision a person makes, and with no key set the deposit step simply is not there.
Stripe CheckoutThe guest is texted, in their language
A confirmation with a link to manage or cancel, sent after the booking is committed so another company's latency never sits between the guest and their table. Every message is logged, with its delivery status and its cost.
Sinch, EU regionEach guest language has its own pages
Every language a restaurant serves gets its own URLs and reciprocal hreflang. FLO runs in Latvian, Russian and English, and two separate checks fail the build if an untranslated string reaches either the site or the panel.
per-language URLsEvery person has their own sign-in
Staff accounts with hashed passwords, permissions from a single registry, and an activity log naming who did what. Add a capability and the compiler refuses to build until every action declares which permission it needs.
per-person accountsThe engine is tested, not asserted
Eighty-seven tests drive the real booking engine over HTTP: double-booking races, hold expiry, trading hours per weekday, the SMS pipe, refusal messages. Run on 23 August 2026: 87 of 87.
87/87 passingA setup fee, then one monthly.No cut of your covers.
The setup pays for the build. The monthly pays for hosting, updates and changes within two working days. There is no commission and no charge per booking, so a full Friday costs the same as a quiet Tuesday. All prices exclude VAT.
The first ten UK restaurants get Signature for the Essentials setup.
- Build weeks from January, booked in order of payment
- Live within 30 days of your floor plan, photos and menu, or no monthly fee until you are
- In return, we film your room for our site, you give us a quote after 60 days and take one reference call a month
Usually £3,900
£2,450
setup, paid on signing
£249 a month, locked for as long as you stay
Year one: £5,438
Essentials
Your new website with booking, and your room as a rendered image.
£2,450setup
£165a month
- New website, up to six pages
- Table choice on a rendered image of your room
- Deposits through your own Stripe account, 0% to us
- Email and SMS reminders
- Host panel: service, floor, guests, events, reports, rota
- Menu and site copy you edit yourself
- Hosting, updates, changes within two working days
Year one £4,430
Signature
RecommendedEverything in Essentials, with your room as a full 3D model and the switch done for you.
£3,900setup
£249a month
- Everything in Essentials
- Table choice on a full 3D model of your room
- Your bookings and guest list moved from your current tool
- Copy written for you, a photo brief and your Google Business Profile tidied
Year one £6,888
Group
Two or more venues under one brand, each with its own site.
£4,950setup for two sites
£365a month
- One site per venue, one shared brand
- Table choice at every venue
- Bookings moved, copy written and Google profile tidied for each venue
- Each extra site £1,450 setup and £145 a month
Year one £9,330
The terms, plainly
- First term 12 months, then monthly with 30 days' notice
- No billing after your notice ends, ever
- If you leave, you leave with your website: your domain, copy, photos, a static copy of the site and your guest list as a file
- Founding prices never go up. List prices rise at most 5% a year
Year one, side by side
A 60-cover dinner restaurant, our estimates.
UK agency sites run £2,500 to £10,000; we used £3,500, plus a booking tool at £99 setup and about £180 a month. The network row uses a reported UK rate of £179 a month plus £2 per network cover, at 250 network covers a month. Something out of date? Tell us and we will correct it.
What no-shows cost you, every month.
About 11 times the Signature monthly of £249.
Deposits and reminders bring that down. Resos measured 0.80% no-shows on bookings with payment protection, against 2.47% without. That is an association, not proof of cause.
Book a 30-minute walkthroughSources: Resos No-Show Index, 3.77 million reservations at 2,417 restaurants, 54% of them in the UK, August 2025 to July 2026 (2.33% on average). OpenTable, October 2026: a no-show table of two costs £55.70 on average.
What owners ask us first.
Will guests still find us without OpenTable?
Keep any listing you want. Couvert runs the bookings on your own website, which is where guests land when they search for you on Google or tap the link on your Instagram.
Do deposits put guests off?
You decide per night and per table size. You can ask only on Fridays, Saturdays and for large tables, and keep the amount small and explained at booking.
What happens to our current contract?
Send us the end date and we plan the switch for the week after it. Until then you stay on your current tool.
Who do we call when something breaks during service?
A named person, by phone or WhatsApp, during service hours.
Can we leave?
After the first 12 months, any month, with 30 days' notice. You keep the site, the domain and the guest list, and billing stops when your notice ends.
Where is our data kept, and who owns it?
You own it. It is stored in the EU, under a data processing agreement we sign with you.
Who are you?
A small team in Riga, Latvia, two hours ahead of London. FLO was our first restaurant.
How long does it take?
About 30 days from your floor plan, photos and menu to live. If it takes longer, there is no monthly fee until you are.
We build Couvert because a restaurant's website and its booking should feel like the same place, and to a guest they are. It started at FLO in Riga, and we now build it for independent restaurants in the UK.
Notes from the floor
See what your guests would see
Walk through the demo room, or book thirty minutes with us. Send a photo of your dining room first and we bring your own tables to the call.