Features

Everything the room needs, in one calm workspace.

A production system for the daily loops of hospitality: service, menu, guests, staff, stock, payments, and the public site.

Run service

Run service

Touch-first POS, kitchen display, ticket state, guest context, and quick payment handoff.

  • Register built for two-second decisions
  • Kitchen state and ticket notes stay visible
  • Payment handoff keeps the closeout path short
Operational proof01

A server can add an item, route it to the kitchen, keep table context, and settle the check without leaving the service surface.

Menu and inventory

Menu studio

Inline category creation, CSV import, photo uploads, out-of-stock state, and publishing controls.

  • Categories, items, prices, and photos in one place
  • CSV import for real menu maintenance
  • Out-of-stock state flows into service surfaces
Operational proof02

Operators can clean up the catalogue during service without breaking register, QR, or public-site menu behavior.

Guest flow

Reservations

Take bookings online and on the floor, then manage status, waitlist, service notes, and seating.

  • Timeline, list, and floor views
  • Waitlist and arrival states
  • Service notes stay attached to the booking
Operational proof03

Hosts see the day timeline, arrivals, waitlist, party notes, and floor context before deciding the next action.

Guest flow

Tables & QR

Generate per-table codes that drop guests into the right menu and service context.

  • Per-table QR links
  • Print-ready table cards
  • Preview links use real guest routes
Operational proof04

Every table code carries table context so guest ordering, previews, and printed packs stay aligned.

Menu and stock

Inventory

Items, par levels, on-hand adjustments, suppliers, recipes, and service-impact visibility.

  • Par levels and on-hand movement
  • Supplier and recipe context
  • Service-impact visibility for stockouts
Operational proof05

Stock changes are designed to be operational, not spreadsheet-only: menu impact and reorder pressure stay visible.

People

Team

Invite employees, manage PINs, schedule shifts, approve requests, and review timesheets.

  • Schedule grid and open shifts
  • Roles, PINs, and permissions
  • Requests, timesheets, and labor guardrails
Operational proof06

Managers can publish a schedule, review coverage, and handle staff requests from the same workforce system.

Revenue

Discounts

Promo codes, percent or fixed rewards, schedules, scopes, and channel controls.

  • Reward, scope, and channel controls
  • Schedule-aware promos
  • Audit-friendly discount setup
Operational proof07

Discount logic is configured once and then respected by service surfaces instead of depending on staff memory.

Closeout

Payments

Take card, cash, and Apple Pay, then reconcile transactions with audit-friendly detail.

  • Multiple tender paths
  • Payment status stays attached to ticket context
  • Reconciliation-friendly transaction detail
Operational proof08

Payments are treated as part of service, with handoff and reconciliation designed around busy-shift reality.

Public site

Public site

Pick a theme and publish a site that pulls from real menu, events, hours, and reservations.

  • Theme and content editor
  • Menu, events, hours, and reservations
  • Domain, SEO, and publish readiness
Operational proof09

The public site uses the same operational source of truth, reducing stale menus, missing hours, and disconnected reservation links.

Features

Start with service, then connect the whole room.

Launch the workspace with the workflows your team uses first. Add the public site, inventory, and team systems as the operation grows.