Hearth

The brief

What was actually broken

The menu was a PDF. Staff edited it in a designer’s file. The kitchen ticket was a screenshot. Nothing in that chain could survive a lunch rush.

How it shipped

The work, in order

1. 01

   Menu as content

   Staff edit dishes, modifiers, and 86s in a CMS-shaped admin — not a layout file.

2. 02

   Tickets a cook can read

   The ticket is a first-class surface: large type, modifiers in order, no decorative noise.

3. 03

   Pay, then fire

   Checkout posts the order only after payment clears. The rail does not lie.

If the line cook cannot read the ticket, the checkout did not ship.

What changed

After it left the repo

• — The lunch menu changes without a designer in the loop.
• — Kitchen tickets match what the guest paid for.
• — 86ing a dish takes seconds, not a reprint.