Restaurant Ordering
Connecting the customer at the table with the team taking the order.

The problem behind the project
Customers need a clear way to order, while the store needs to track what has arrived, what is being prepared and what has been settled. This project explores both sides of that workflow.
Follow the workflow
Enter from the table
A signed table code opens the menu for the relevant table.
Browse and order
Choose dishes, quantities and notes, then confirm the cart.
Accept and serve
The store handles incoming orders and updates their status.
Settle the table
After offline payment, the store records the bill as paid and clears the table.
My role, with AI
I specified requirements and directed Codex to implement the application. I read and debugged generated code, checked features against the intended workflow and directed revisions.
AI assisted implementation. My contribution was shaping the requirements, reviewing the result and checking whether it worked for the intended use.
Decisions visible in the product
Confirm changes before ordering
The manual describes price-change confirmation and removing sold-out dishes before submission. This makes the reason for a blocked order visible.
Keep order and bill views distinct
A customer sees orders from their own device; the store handles the whole table bill. The interface explains that final payment is handled at the counter.
A closer look at the workflow
For now, explore the screenshot above. Recorded walkthroughs will be added here as they become available.
Current scope & limitations
The application runs locally and has no public demo yet. This screenshot uses mock data; the later manual describes database-backed flows. Online payments, kitchen printing and a full multi-staff permission system are not presented as completed features.