Restaurant module — Reservations & floor plan

Manage your restaurant's reservations, floor and menu

eyeot's Restaurant module brings online reservations, the real-time floor plan and the allergen-declared menu together in a single platform. Covers per time slot, concurrent capacity, anti-no-show deposits, waitlist and kitchen tickets are all run from a single service. Activatable venue by venue, the software couples with your POS and your stock without depending on them.

Restaurateurs, bistros, brasseries and multi-venue chains (small and mid-sized businesses) that want to manage their reservations, floor and menu in one place, cut no-shows and smooth service in both the kitchen and the dining room.

What you can do

Online reservations and service pacing

Public widget with no account creation, computing free slots (covers per time slot, concurrent capacity, lead/cutoff, closures). Full state machine (request → confirmed → arrived → seated → finished), magic-link and idempotent creations.

Interactive real-time floor plan

Zones (dining room, weather-dependent terrace, bar, private lounge), tables positioned on a 2D canvas with live statuses. Table merge/split, direct walk-in seating, one-click zone closing with re-seating, deterministic table suggestion.

Menu with INCO allergens

Chain-wide or per-venue menus, ordered sections, dishes with tax-inclusive prices, surcharge modifiers and dietary tags. Written declaration of the 14 INCO 1169/2011 allergens, multilingual, dayparting and per-venue '86' (out-of-stock) marking.

Anti-no-show deposits and earnest payments

Configurable deposit policies (Flexible/Standard/Strict/Ticketed presets) with a default earnest-payment presumption, cancellation tiers and terms shown before payment. Capture on no-show and tiered refunds.

Walk-in waitlist

FIFO queue with deterministic wait-time estimation, best-effort 'table ready' SMS notification and a grace window. Automatic conversion of a compatible entry when a cancellation or no-show frees a slot.

Connected kitchen (KDS) and coursing

Kitchen tickets per course (starter, main, dessert, drink) grouped by station, cascade firing of the next course and relaying of allergy notes to the pass. Standalone manual entry, independent of the POS schema.

Restaurant steering and intelligence

Module health score, no-show rate, occupancy, real turnover and a 7-day forecast, supplemented best-effort by RevPASH and menu engineering from the POS. Aggregated multi-venue view and allergen coverage.

Compliance & trust

INCO 1169/2011 allergens

Every dish carries the written declaration of the 14 allergens of regulation INCO 1169/2011, in French, English, German and Spanish. A coverage indicator (menu compliance) flags dishes without a declaration.

Deposits: earnest payment vs down payment (French DGCCRF)

Policies distinguish earnest payment (arrhes), down payment (acompte) and card pre-authorization, with a default earnest-payment presumption aligned with the French DGCCRF / Civil Code framework (art. 1590). The general terms of sale are shown before any payment.

Guest data and GDPR

Guest contact details (email, phone, name) are encrypted at rest (Fernet) with a search hash. Anonymization actually removes personal data (art. 17), retention is configurable and marketing consent stays separate from transactional consent.

PCI DSS payments

No card data is stored: only the opaque PaymentIntent reference from the payment provider is kept for deposits and card pre-authorizations.

Works with your other modules

  • POS — table bill & checkout (NF525 receipt)
  • Stock — automatic '86' (out-of-stock) marking on shortage
  • CRM — guest profile & visit history
  • Document management (DMS) — dish photos
  • Finance — tracking of deposits & earnest payments
  • Intelligence — RevPASH, no-show and occupancy

Frequently asked questions

How does the module help reduce no-shows?
You define per-venue deposit policies (Flexible, Standard, Strict, Ticketed presets) triggered by party size or lead time. The deposit or earnest payment is captured on a no-show and refunded in tiers on cancellation. Automatic reminders are sent the day before by email and two hours ahead by SMS then email.
Does the software handle the 14 regulated allergens?
Yes. Every dish carries the written declaration of the 14 allergens of regulation INCO 1169/2011, available in four languages (FR/EN/DE/ES). An allergen-coverage table (menu compliance) identifies dishes without a declaration, and modifiers can add their own allergens.
Can guests book online without creating an account?
Yes. The online menu, the booking widget and the queue tracker are public, with no authentication, protected by rate-limiting, a honeypot, hCaptcha and GDPR consent capture. The guest then manages their reservation via a magic-link.
Does the module work with a POS?
It couples with the POS via the internal event bus: opening the bill on the table, building the check, then checkout that finalizes an NF525 receipt and closes the table round. The module stays standalone: manual KDS entry works even without an active POS.
What happens to customers' personal data?
It is encrypted at rest (Fernet) and indexed by hash for search. A scheduled task anonymizes finished reservations beyond the configured retention period, and anonymization actually removes the data (GDPR art. 17). Marketing consent is separate from transactional consent.
Is a floor plan required to use the module?
No. The floor plan is an optional per-venue setting: you can run on time-slot reservations only, without table management. A chain can enable the plan on certain venues only, each keeping its own zones, tables and services.

Go further

POS / Cash registerInventory managementOnline bookingERPNF525

Try eyeot for free

eyeot is a French all-in-one ERP for small and mid-sized businesses, hosted in France and GDPR-compliant. Free for individuals (1 user, every module); simple team packs for companies.

Create my free accountSee pricing