Overview
Restaurants need speed: menu, modifiers, table status, kitchen tickets, and stock that moves with recipes.
Problem statement
Paper KOTs and mental table state slowed turns and hid voids.
Requirements and constraints
Table map, order fire to kitchen, manager void rules, recipe consumption, shift close report.
Proposed architecture
Waiter UI lightweight; kitchen display or print; admin for menu and stock.
Database design
Orders, line items, modifiers, payments, and stock movements linked.
API design and authentication
Local network deployment common; API optional for handhelds.
Security
Manager PIN on voids and discounts.
Performance
Kitchen queue sorted by station when menu tagged by kitchen section.
Testing and deployment
Peak-hour order burst on staging hardware.
Challenges and lessons
Split bills and merged tables without losing audit.
Verified results
Service staff and kitchen share one live order state.