Restaurants

Keep table bookings and the current food and wine offer understandable for both service staff and guests.

Illustrative screens with sample data.

The operational problem

A full terrace can overload a service even when indoor seats remain free. Booking capacity, the kitchen offer and the wine list need separate owners and a shared pre-service check.

Who this is for

The manager owns the daily handover, HR confirms staffing, employees check assigned work and guests use only the intended public information.

NOVUZA
NOVUZA

Daily workflow

Illustrative scenario — not a customer case study

A guest books a table; the manager checks capacity; service directs the guest to the digital menu or Vini. Any guest overview depends on verified links and permissions: do not assume a QR visitor is identified.

Preparation checklist

  1. 01

    Review bookings by service period and identify parties requiring manual confirmation.

  2. 02

    Check dishes and wine prices with their editors before staff test both QR destinations.

  3. 03

    Brief employees on terrace changes and who may resolve a capacity conflict.

Illustrative role handover — not a customer case

Illustrative Friday: the manager moves a terrace request to manual review because of rain; an employee checks the food QR; HR verifies the evening roster. A guest reads the menu while staff confirm the table separately.

Why this starting combination

Compare the Restaurant package with standalone reservations, digital menu and Vini. The package is a starting combination for table and content needs, not a promise of POS synchronization.

Suggested starting point in pricing, not a promise that extra modules are included: Restaurant

Pricing

Questions before you decide

How do we prepare for a terrace closure?

Bring the terrace plan and identify which requests need a staff decision if it closes. Test the supported change process with your team; retain a named person for contacting guests instead of assuming automatic reallocation.

Where can I verify the price and billing unit?

Use the published pricing page for listed modules and packages. HR is per organization; other listed modules are per establishment. Unlisted scope and integrations require a quotation, not an assumed package inclusion.

Availability and scope

Listed in the public offering. Confirm actual availability, permissions and your exact workflow in a demo before ordering.

Limits to check

These are restaurant tables, not accommodation bookings. Demonstrate zones, time slots and guest-record access; QR browsing does not identify a person.

Start simply.

Restaurants

Discuss this workflow by emailPricing