Back to blog

    Guides & Resources

    From the Table to the Pass: Why Your Kitchen Shouldn't Be Reading Your Handwriting

    Wrong orders, cold food and a waiter walking into the kitchen every four minutes to ask 'is table six ready?'. Here's how the floor and kitchen stop guessing.

    M

    MerxumOS Team

    Aug 1, 2026

    From the Table to the Pass: Why Your Kitchen Shouldn't Be Reading Your Handwriting

    Every busy restaurant has the same two arguments. The kitchen says the order was written wrong; the floor says the kitchen didn't read it. Both are usually right, and neither is really at fault — the order was passed between them on a piece of paper, in handwriting, during a rush.

    A wrong plate costs you twice: the food you throw away and the customer who waits again while you remake it. Do that a few times a service and you've eaten a whole table's margin.

    The order has to leave the table complete

    Most kitchen errors are actually order-taking errors. The customer asked for something ordinary — extra shito, no pepper, well done, a different side — and it either didn't get written down or got written somewhere the kitchen didn't look.

    • Build modifiers into the menu so the common requests are a tap, not a note in the margin.
    • Price the ones that should cost more, so an extra portion isn't quietly given away.
    • Capture it against the specific item, not the whole table.
    Warning — If a request has to be remembered rather than recorded, it will survive the walk to the kitchen roughly half the time.

    Put the order on a screen the kitchen can actually read

    A kitchen display replaces the docket. The order appears the moment it's sent, in the same format every time, with the modifiers attached to the item they belong to. The kitchen marks each item as it's cooked, and the floor sees that on their own screen — which ends the four-minute trip to ask whether table six is ready.

    1. Send the order the moment it's taken, rather than carrying it.
    2. Show only what the kitchen has to cook — drinks and packaged items don't belong on a kitchen screen.
    3. Let the kitchen mark items done so the floor knows without walking in.
    4. Keep the timing visible, so an order that's been sitting too long stands out.
    Tip — The best sign a kitchen screen is working: the pass gets quieter, not busier. Nobody is shouting to find out what's next.

    Tables, walk-ins and the ones who won't wait

    Knowing the state of every table — free, seated, ordered, bill requested — is what lets you seat people quickly on a Friday night. Reservations hold the tables you've promised, and a waitlist handles the walk-ins you can't seat yet, so the host isn't managing a crowd from memory at the door.

    Delivery is the same kitchen

    Once orders flow through one system, an online or delivery order is just another order into the same kitchen, off the same stock, at the same prices. That's the whole point: your menu exists once. Whether the customer is at table six or on their phone shouldn't change how the kitchen sees the order.

    Wrong orders aren't a kitchen problem or a waiter problem. They're a handwriting problem.

    MerxumOS runs restaurant floors and kitchens together — tables, modifiers, kitchen display screens, reservations and delivery on one menu and one stock pool. See it at merxumos.com/industries/restaurant.