In the office
- Day and week reservations, in the restaurant's time
- Guest profiles, tags, check history, duplicates
- GDPR export and anonymisation, marketing consent
In-house or Zenchef reservations, waitlist, profiles linked to checks, anonymisation when needed.
Request a demo
Booked, confirmed, seated, no-show. Table, covers, notes. The floor plan turns amber as the time approaches; after midnight the evening stays on the plan.
Two-way sync: create, statuses, table mapping. A badge separates a Zenchef booking from an in-house one.
Guests without a table wait in a list shared by the floor and the office; a tap seats them when a table frees up.
The profile follows the checks, with tags and marketing consent. Duplicate merge, data export, anonymisation: no eternal guest file “just in case”.




TheFork and a public booking widget on the restaurant site are not on the roadmap yet. Zenchef and in-house booking are.
FAQ
No. In-house reservations are enough. Zenchef is a sync, not a requirement.
Checks stay for food cost; identity goes.
Pilot
Leave your email: we review the request, then you get personal access to the demo, the restaurant running in these screenshots.
Request a demo