Zenchef, SevenRooms, Tock: how we pick a restaurant reservation system in 2026

Every restaurant project we work on starts with the same conversation. Should we use OpenTable? Resy? TheFork? Someone told us about SevenRooms. Six platforms, three markets, and most operators end up overpaying for a system that does not fit their format.

Here is how we actually pick, after five years of restaurant and hospitality work across Paris, London and beyond.

We use three systems, almost always

For a new restaurant client we recommend one of three platforms.

• Zenchef for French independents.
• SevenRooms for UK groups and premium operators.
• Tock for chef tables and prepaid formats.

That is it. The other names you may know (OpenTable, Resy, TheFork) we rarely recommend, and we will say why at the end.

Zenchef · the French market default

Zenchef is the leader in France for a reason. It does the basics well. A widget that drops cleanly on your site. No-show management. Distribution through TheFork as a discovery channel. French support. GDPR clean. Pricing sits in a range most independents can absorb (around 100 to 250 euros per month per site).

Best for

• French bistros, neo-bistros, mid-tier independents.
• One to five sites in France.
• Operators who want a widget on a custom site and a clean back office.

Where Zenchef is weaker

• CRM and guest history (functional, not a strategic tool).
• International expansion (you will not run a London site on Zenchef).
• Premium gastronomic positioning (it works, but feels generic).

In our portfolio : Double Dimanche (hospitality + restaurant, Paris) or L'Atelier Entrecôte & Volaille. Both run Zenchef widgets on Webflow.

SevenRooms · the UK and group standard

SevenRooms is built for groups. The CRM is deep, the marketing automation is real, and guest profiling drives everything. Birthdays, dietary preferences, lifetime spend, table preferences, VIP flags, retention campaigns. Operators who care about repeat revenue choose it.

In the UK specifically, SevenRooms is the de facto standard for any hospitality group above three sites. If you are opening in London and you talk to a group operator, the chances are high that they run SevenRooms.

Best for

• UK hospitality, especially pub and resto groups (3+ sites).
• Premium independents and fine dining.
• Restaurants inside hotels that need to talk to a PMS, particularly MEWS.
• Operators with a marketing function and a CRM mandate.

Where SevenRooms costs you

• Setup is heavier (training, data migration, integration time).
• Price is higher (figure 400 to 1000 dollars per month per site, plus setup).
• Overkill for a 30-cover bistro.

In our portfolio : The Culpeper Family (London hospitality group, multi-site pubs and restaurants, Webflow + SevenRooms) or the Green Clerkenwell. The CRM is what justifies the cost. Knowing that a guest spent £400 last quarter and prefers a corner table by the window is operational gold.

Tock · chef tables and prepaid only

Tock changed the game for fine dining with one design choice. Prepayment is the default. You charge the card when the reservation is made. No-shows drop to near zero. For chef tables, omakase, kaiseki, and tasting menus, this is the right model.

Best for

• Chef tables and tasting menus.
• Fixed-price experiences.
• Wine bars with a small number of seats per service.
• Pop-ups and limited residencies.

Where Tock is wrong

• Walk-in restaurants and casual formats (the prepay model adds friction).
• Operators who want a flexible CRM (Tock is reservation-first, not CRM-first).
• Markets where prepaid culture has not landed (still tricky in parts of continental Europe).

We have not deployed Tock with a client yet, but it is the only honest answer for a chef-table client. If you are launching one in 2026, talk to us before you sign.

What we do not recommend, and why

OpenTable. Vendor lock-in is the polite term. Cover fees (1 to 2 dollars per seated guest) compound fast. The marketing channel is real, but you pay forever for it. Most importantly, you do not own the data. When you leave OpenTable, the guest history stays behind.

Resy. Strong in the US, especially in fashion-adjacent and Amex-aligned brands. Weak in the EU. If you are not opening in New York, do not bother.

TheFork. It is a discovery channel, not a reservation system. Pair it with Zenchef as your back office. Do not use it as your back office.

The decision grid

If you are choosing right now, the short answer is :

• Bistro or independent restaurant in France, 1 to 3 sites → Zenchef.
• Group operator in the UK or premium independent → SevenRooms.
• Restaurant inside a hotel running MEWS → SevenRooms (it talks to MEWS).
• Chef table or fixed-menu format → Tock.
• US fine dining only → SevenRooms or Tock.
• Maximum discovery and you accept the marketing tax → Zenchef + TheFork as a channel.

What our role is as a studio

We are a design studio, not a reservation platform. Our work in this stack is the integration. Where the widget lives on the page. How the booking flow connects to your CMS. What data flows to your CRM. What the experience looks like on mobile.

We ship three patterns :

1. Native widget embed. Fastest, least flexible. Zenchef and Tock support this well.
2. Custom-styled iframe with brand layer on top. Used on most of our Webflow restaurant builds.
3. Full API integration with custom UI. Most flexible, more expensive. Required when the booking flow is a key part of the brand experience or when the site speaks to a PMS in the background.

We are publishing a follow-up article on the technical side of these three integration patterns. If you are early in a project, ping us before you sign with a vendor. The choice locks more of your stack than you think.

‍