Your guest browses the menu, calls the team and sees the relevant bill. One POS, the same features — in the cloud or on the Box at your venue.
Explore the workflows
The guest scans the table’s QR code and opens the menu in a browser. They choose their language and see the dishes and descriptions maintained in Nova. Translated item text requires the corresponding language versions to be provided.
The guest chooses items and sends an order request. Currently, the selection goes straight onto the table bill; the team checks it there and sends it to the kitchen. Prior waiter confirmation is planned but is not yet part of the current flow.
The guest calls service or asks for the bill or payment. The team sees the request with its table reference at the till and on the waiter’s phone and can handle it. Alert sounds are configurable. Buzzer and smartwatch delivery has not been established.
For direct payment of an AI waiter order, the personal guest link shows only that order. The regular table QR code shows the shared table bill; personal AI payment bills remain separate. Each access link therefore has its own relevant items and outstanding amount.
The guest can pay through a configured card terminal at the table or with the team at the counter. Online payment is available only with a configured payment provider. Only confirmed payments count as paid; when configured accordingly, confirmation releases the order to the kitchen.
The customer display shows the items and total of the current till bill. It also shows any recorded tip; after payment, the guest can open the receipt by QR code. Choosing a tip directly on the display is not currently available.
LidoOS Copilot
Nova AI · handover to the POS
The guest talks to the AI waiter in Nova. Nova hands the order to the POS, where the bill, payment and kitchen follow the configured rules.
For direct guest payment, the link belongs to the guest’s own bill. The kitchen waits for full payment if that release mode is selected.
No AI model runs in the POS itself. An AI answer replaces neither payment confirmation nor a service check.
Nova ↔ POS
Maintain menus, tables and staff in Nova. The POS handles orders, payments and receipts.
The limits
Table access, the published menu and language versions must be ready. The browser needs a connection to the POS server; online payment needs a configured provider. A shared table bill is not a personal bill. Prior waiter confirmation and tip selection on the customer display are currently missing.
Availability
LidoOS POS — coming soon. Terms in the shop; we will plan the introduction together.
Talk to us about how LidoOS POS fits your venue’s workflows.
Short answers
No. Currently the request goes straight onto the table check; the team reviews it there and sends it to the kitchen. An upstream waiter approval is planned but does not exist yet.
Via “Pay online” only when a payment provider is set up. Only a confirmed payment counts as paid — the button is not available in every venue.
No. The display shows the items, the total and the recorded tip of the current check; there is currently no way to enter it yourself.
The captures show the demo venue Via Palermo with own transactions: table access, order request, service call and customer display. The online payment ran on the sandbox; the online payment button and the permanent paid block are not proven.
Tell us how you work: dining room, terrace, counter or self-service. Together we will define your operating mode, devices, Nova modules and terms.