Online ordering with a kitchen display, built by Claude Code on Elements

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.

View the code on GitHub →

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 @rpc call 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 the integrated stack for building apps with AI: a TypeScript project server, build system, app framework and deployment system, engineered from the ground up as one. Your editor, tools and one or many agents all connect to the same always-on project server, which runs type checking, program analysis, migrations and tests as the agent builds. Built-in guardrails keep the app structured correctly and secure as it grows from prototype to production.

Run it yourself

Paste this into a terminal. It installs Elements, creates your copy of this app and starts it.

curl -fsSL 'https://elements.dev/install?create=orderhatch&scaffold=demo-orderhatch' | sh
View script