Resto

Experimental beta. This module may change, have bugs, or incomplete data. Requires Pro plan and enabling it under Settings → Company. Use it to try the dining-room flow; it is not a critical production floor replacement yet.

The Resto module (/restaurant) runs the dining room alongside retail POS: floor plan, tickets, kitchen, reservations, takeaway, and table payment.

What’s in beta

• Floor / layout: tables by zone, layout editor (admin), join/move tables, bar seats.
• Tickets: per table or seat, catalog attributes (same products.attributes as POS) plus free-text notes, send to kitchen.
• Kitchen (KDS): one board with 3 columns (new → preparing → ready); priority; “Served” archives the ticket.
• Reservations: agenda and table assignment; the floor highlights bookings in the next 2 hours.
• Takeaway / delivery: no-table orders with statuses new → kitchen → ready → picked up.
• Checkout: precuenta, partial or full charge via POS, tips; closing is blocked while a balance remains.
• Realtime: floor, kitchen, and payments stay aligned across devices for the same store.

Routes

Alias: /resto redirects to /restaurant.

Minimum permissions

See Roles and permissions.

Demo

Demo company 5, store 2 (resto seed).

Not in this release

Resy-style waitlist/host stand, priced modifiers / ingredient removals as structured SKUs, multi-station KDS, hospitality CRM, and WhatsApp from reservations are deferred.