Online ordering with a kitchen display, built by Claude Code on Elements
A photo menu, card checkout and a live order status page, plus a kitchen board with ticket timers and sold-out toggles.
How it's built
Orderhatch needed card checkout, a kitchen board that fills as orders are paid, a live status page for each customer, email receipts, and sold-out items that update on every screen. Each of those is a part of Elements, so the agent spent its 28 minutes on the taqueria app itself.
- A live kitchen board. Orders are a LiveTable, so a paid order appears on the kitchen display the moment it lands, a tap moves the ticket between columns, and the customer's status page moves from received to preparing to ready with it.
- Live sold-out items. The menu is a LiveTable too. Kitchen staff mark an item sold out, it comes back at the end of the business day, and every customer's menu shows it at once.
- Card checkout. Placing an order is one
@rpccall that prices the cart on the server, holds the order off the board and sends the customer to Stripe. The order moves to the kitchen once whether the return page or Stripe's webhook arrives first. Without a Stripe key, a test checkout inside the app records the payment through the same function, and production registers its own webhook. - Email receipts. The payment and the receipt job are recorded in one transaction, and the job emails the receipt.
- Data from SQL files. Migrations define the app and seed the owner, a staff account, twenty items in five categories with photos and options, opening hours, and a lunch rush of seventeen orders timed from when the seed runs.
- Sessions and roles. Kitchen pages check for staff and the owner's pages check for the owner.
Why Elements
Elements is an integrated full-stack app framework and a project server. The project server checks the agent's work as it builds: it type-checks the server and browser code, analyzes the program, applies migrations and runs the tests, then reports the results to the agent. A security mistake, such as calling a server-only function from the browser, is a compile error. The agent reads the report and fixes its own mistakes before it tells you a feature is done. The same checks run on every feature you ask for next.
Run it yourself
- 1 Sign up
Already have an account? Sign in
- 2 Install and run the demo One prompt to paste into your agent.
The prompt
What Claude was given to build this app.
Build an online ordering and kitchen display app named orderhatch for a neighborhood taqueria. CUSTOMER - Menu by category with photos, prices and options (protein, salsa, add-ons). - Cart, pickup time (ASAP or a time slot today), name and phone, pay by card. - An order status page that moves from received to preparing to ready. - An email receipt. KITCHEN (staff account) - Kitchen display: new orders as tickets in columns (new, preparing, ready), oldest first, with a timer on each ticket. Tap to move a ticket. - Mark an item sold out for the day. OWNER (admin account) - Edit the menu and hours. - Today's orders and revenue. Payments by Stripe. Seed the owner, one staff account, a menu of about twenty items in five categories, and a lunch rush of orders across statuses. Show the logins on the sign-in page. New orders, ticket moves and sold-out items update in real time on every screen.