QR to ordered. Kitchen to served. Seat to settled.
Avyra Dine is a full restaurant front-of-house and kitchen flow — QR-to-order at the table, a real kitchen display, and seat-level billing that splits the way the table actually splits. Pairs with Avyra Voice AI so phone orders land in the same queue.
What it does in production.
QR-to-order
Each table gets a QR. Guest scans, browses the menu in a fast PWA, orders without waiting on a server.
Kitchen display system
Tickets stream in by station. Bumps, recalls, and prep timers — built so the line can actually use it on Friday night.
Seat-level billing
Bills split by seat, by item, or by share. No more 'who had the second beer'. POS-bridge generates the receipts.
Voice AI integration
Phone orders handled by Avyra Voice AI land in the same kitchen queue — Dine doesn't care where the order came from.
Live menu management
86 items in one click. Schedule menus (brunch, lunch, dinner). Categorize, photograph, price — without a redeploy.
PWA-first
Installs to the home screen, works offline for guests on flaky restaurant Wi-Fi, and looks the part on every device.
Hardware-friendly
Pairs with thermal printers in the kitchen and runs the KDS on cheap touchscreens. No exotic terminals required.
Operator dashboard
Owner sees live revenue, top items, wait times, and table turnover. Built on the same Avyra Dashboard the rest of the suite uses.
How it's built.
- Frontend: Vite + React 19 + react-router-dom 7 with framer-motion and Three.js touches.
- PWA-installable; offline-first menu cache for the guest surface.
- Order events stream over WebSocket to the KDS.
- Seat-level billing model is first-class — splits happen in the data, not the receipt.
- Production-tested at independent restaurants; pairs with Voice AI when phones get busy.
- Subdomain-hostable so each restaurant gets its own URL on shared infrastructure.
Guest scans QR ─► PWA menu (Vite + React + R3F)
│
▼
Orders API ──► Kitchen Display (KDS)
│ │
│ ▼
│ Station tickets / bumps
▼
POS-bridge ──► seat-level bills
│
├─► Avyra Voice AI (phone orders)
└─► Avyra Dashboard (operator view)Who runs it today.
Independent restaurants
Owners running 40–120 covers a night who don't want a Toast contract but do want a real KDS and a real ordering surface.
Cafés and counter service
Order-ahead from the table, pickup at the counter. Phone overflow routed through Voice AI.
Multi-location groups
Each venue gets a subdomain and a menu of its own; shared analytics roll up to the operator.
Questions we get asked.
Is this a POS replacement?+
Dine is the front-of-house and KDS. For variety/convenience-style retail, Avyra POS is the till. For restaurants, Dine pairs with a payments terminal of your choice.
Does the KDS need special hardware?+
No — any modern touchscreen plus a thermal printer. We've shipped it on $200 displays.
Can guests pay through the QR?+
Yes, via Stripe Terminal or the payment provider you already use. Settlement flows back into seat-level billing.
How does it work with Voice AI?+
Voice AI publishes orders to the same Orders API the QR uses — same kitchen, same bills, same dashboard. The KDS doesn't know or care that the order came from a phone.
Got a product to build? Tell us what you have in mind.
We kick off in days, not months. Working software in weeks. If we're not the right fit, we'll tell you up front.