Saturday, 9:30pm. The band’s mid-set, the front bar is three deep, and someone leans across to shout a parma order at the bartender pulling their fourth schooner in a row — “and can we get extra chips, no salad!” The bartender nods, keeps pouring, and by the time there’s a second to actually key it in, half the modifier is gone from memory. Or the docket gets written on whatever’s nearest and ends up under a coaster, never making it to the kitchen at all. Forty minutes later, someone’s asking where their parma is, and the honest answer is: it never actually left the bar.
Why “shout louder” doesn’t fix it
The bar isn’t understaffed for pulling beers — it’s understaffed for taking accurate food orders while also running the taps at full noise, which is a genuinely different job. A verbal food order at a loud bar has to survive being heard correctly over a band and a crowd, remembered accurately while three more drink orders come in behind it, and then physically get to the kitchen — on paper, across a room, past every other job the bartender has in the next five minutes. Any one of those steps failing loses the order. All three happening at once, every Saturday night, isn’t bad luck. It’s the setup.
Unlike a dine-in restaurant, where a docket sits on a printer right at the pass, a bar order has to physically travel — through a crowd, past the taps, sometimes down a hallway to the kitchen — before anyone back there even knows it exists. Every metre of that trip is another chance for the ticket to get put down and genuinely forgotten.
What actually needs to happen
Key it once, and let it fire itself
The moment a food order is entered into the POS at the point of sale, it should go straight to a kitchen screen — no docket, no walk to the pass, no relying on the bartender to physically deliver a piece of paper between pulling beers. One entry, one digital ticket, sequenced with everything else the kitchen already has running. That also removes the bartender from the delivery chain entirely: once it’s in the till, getting it to the kitchen is the system’s job, not something a person has to remember between pulling the next three beers.
Put it on a kitchen screen, not a scrap of paper
A KDS shows the order clearly, with every modifier intact — extra chips, no salad, whatever was actually asked for — for as long as the kitchen needs it, instead of a slip that can get lost, wet, or buried under six others during a loud Saturday shift. What’s on the screen is what was actually ordered, not what survived being shouted across a bar. A kitchen running off a screen instead of a paper spike also keeps a record of exactly what came in and when, which turns “did we ever actually get that order?” from a shrug into a real answer.
Let the beer garden and tables order without the bar at all
For groups sitting at tables or out in the beer garden, QR ordering removes the shouted-across-the-bar step completely — they order snacks and another round from where they’re sitting, it lands directly on the kitchen and bar screens, and nobody has to fight their way to the taps just to ask for a parma. That’s fewer orders competing for the bartender’s attention in the first place.
The kitchen can only cook what it actually receives
A busy kitchen on a Saturday night can usually handle the volume — what it can’t handle is food orders that never arrive, or arrive missing the one detail that mattered. Every lost or garbled order isn’t just one unhappy table, it’s a remake, a refund, or an argument at the bar about whether extra chips were ever asked for. Fix how the order gets from the person who said it to the person who cooks it, and the same kitchen, the same bar staff, and the same Saturday night crowd stop generating complaints that were never about the food at all. Get that handoff right and the same kitchen that already runs a packed Saturday bistro service without drama can handle the bar snacks too — because cooking the food was never the hard part. Finding out about it was.