Case study · FLŌ restorāns, Rīga

FLO, booked by the table.

A modern European dining room on the Daugava embankment, with a red room, a bar and a terrace. FLO wanted guests to reserve the seat they would actually sit in. We built the site, the booking, a 3D model of the room and the panel the staff run the night from, all on Couvert.

Where
11. novembra krastmala 13
Open
Tue to Sun, from noon
Built
Site, booking, 3D, panel
FLO's Red Room at lunch: grey chairs, white cloths and the garnet wall
18Tables

Every one bookable by name, from Krasts at the window to the terrace.

68Seats

Two-tops to a five-seat round, each offered only to a party it fits.

3Rooms

The Red Room, the bar and the terrace, one model.

3Languages

Latvian, English and Russian, from the first page to the confirmation.

Anna, FLO's founder, holding the menu at the door
Anna, founder
The brief

A time slot tells a guest nothing.The window table on a Friday tells them everything.

FLO’s tables are not interchangeable. In the Red Room two sit in the arched windows, three in the hall and three by the fireplace; four more are at the bar and six out on the terrace. Guests ask for a table by where it is, so the booking had to start there too.

It also had to belong to FLO. The same dark room on the site, the same garnet, in Latvian, English and Russian, with no marketplace between the restaurant and the people who eat there.

Try it

Book a table at FLO, right here.

This is FLO’s own booking, the same engine and floor plan as floresto.lv, running against a demo book on this site. Pick a table and confirm it: the next guest will see it taken. Nothing reaches the restaurant.

FLO reservation · demo book

Mondays are missing from the calendar because FLO is closed on Mondays.

Open it full screen
The signature

The real room, in 3D.

Modelled from FLO’s floor, table by table. Booked tables fill with diners, so a guest reads a busy Friday at a glance and still finds the quiet corner. On a phone it opens in 2D and loads the 3D model only when asked.

FLO's Red Room on a busy evening, in the booking room
Red Room8 tables by the window, in the hall and at the fireplace
FLO's Bar on a busy evening, in the booking room
Bar4 tables around the bar and its banquette
FLO's Terrace on a busy evening, in the booking room
Terrace6 tables outside, on the embankment
What we built

The whole stack, not a plugin.

01

The website

Near-black and garnet, pulled from the room itself. One idea per screen, the menu with FLO's own dish photography, and the booking a tap away from every page.

02

Booking by the table

A guest chooses the party, the evening and then the seat. A table is only offered to a party it fits, and it is held while they type their name, so two people never book the same one.

03

The room in 3D

FLO's real floor, modelled from the building's geometry and lit like an evening. Taken tables show diners. Phones get a lighter model with smaller textures, so it opens on a train.

04

The back office

Tonight's book, the floor hour by hour and the guest book, in Latvian, on FLO's own data. No portal in between and no commission on a single cover.

The room it sells

Photographed at FLO, not a stock library.

The menu, the rooms and the dishes are FLO’s own photographs, taken in the restaurant.

A table at FLO laid with a spread of plates
FLO's lemon dessert
A domed plate carried to the table
FLO's arched windows on 11. novembra krastmala
Tonka cake with a sugared tomato
The back office

And the panel FLO runs on.

The real one, not screenshots: tonight’s book, the floor hour by hour, the guest book and closed days, in Latvian the way FLO’s hosts use it. It runs on a demo week with made-up guests. Change anything; the reset puts it back.

Demo data only. Reset demo data puts the week back.

Open it full screen
Your room next

Let guests book the seat, not the slot.

Send us your floor plan and we will set your restaurant up the way FLO’s is, before the first call.