BistroFlow

Stack

• Next.js
• TypeScript
• Tailwind CSS
• Drizzle ORM
• Neon Postgres
• Auth.js
• Netlify

What to demo

1. Enter as waiter, build an order with modifiers and send it to the kitchen
2. Enter as kitchen in a second window and watch the ticket arrive without a refresh
3. Enter as manager: see stock drop, a reorder list fire, and receive a delivery

Architecture

• Every order deducts its ingredients inside a single database transaction, so stock can never drift from what was sold.
• The menu computes remaining portions from live stock and recipes, so dishes show "Only 3 left" or "Sold out" before an order is taken.
• Netlify Functions cannot hold persistent connections, so one polling hook (every 2 s, no overlapping requests, paused in hidden tabs) drives all live updates.
• Authorization sits next to the data: each server component calls a role check before querying, and the permission matrix is one unit-tested module.
• The demo is resettable: fixed staff ids and a bulk-insert seeder restore the starting state, including two weeks of sales history, in about a second.