The extension lead is in a puddle, the generator coughs, and the card reader shows “waiting for host.” A street-food Saturday does not pause for that. Guests keep ordering. Allergen questions keep coming. The bun tray is already empty. Food truck software that passed a dry run on cafe Wi-Fi either keeps numbered tickets moving offline or the shift falls back to a pad nobody can read in the rain.
You do not have a spare room. You have a van, a menu that changes between pitches, and often one person taking money while someone else plates. Judge the product on that hour. A complete-looking brochure is a different exam.
Freeze the menu for this pitch, not for the year
Before the window opens, the card has to be today’s card. Office lunch is not a street festival and not a Christmas market. Items that are not in the truck should not sit on the screen “just in case.” Hiding a sold-out bun while the line is moving is part of selling, not a Sunday admin task.
Popular items need to sit on the first screen. An add-on or an exclusion has to reach the person at the griddle without a shout across the stall. A short menu does not need a catalogue under four categories. A menu that changes every outing does need a way to build and check the list before you leave the depot.
Run five orders that actually happen at the window: the regular, the regular with an extra, an exclusion, a combo, a group. Count confusion at handoff, not taps. Speed that hands over the wrong burger is not a saving.
Window, cook, and handoff on the length of a vehicle
When the line does not break for ten minutes, the risk is lost sequence. Who takes money, who plates, who calls the number: agree that before you roll onto the site. A kitchen display helps when statuses are decisions (new, cooking, ready), not decorative labels.
A small crew often works better from one shared view than from a “kitchen station” with nowhere to hang. If you look at KDS and restaurant features, ask for the festival path: who changes status, where “no onion” appears, how two similar combos are told apart at the hatch.
After payment, staff still need the number, the items, and the stage. In stage noise, agree how you call ready food. Do not promise guests an app you have not tried in a similar crowd with similar coverage.
When the generator dies or the signal drops
This is the real exam, not a loyalty module. What happens if the screen goes dark for two minutes? Is there an agreed order: keep taking cash with numbered tickets, pause cards, catch sales up when power returns? Who is allowed to tell the queue?
A fallback procedure can matter more than a handsome home screen. Test devices on your power: generator, phone hotspot, a tree that kills LTE. If the product assumes a stable line like a restaurant dining room, the festival will show that in the first hour, not in a weekly report.
OrderNow covers POS, QR menus, KDS, direct online ordering, reporting, loyalty, and coupons within the relevant plan. That is not a reason to load every module onto an event. Solutions for different venue types help you start from the window, not from a bundle.
A second queue in someone’s phone
An owned online channel can help at a regular pitch or a timed collection. At a festival it easily becomes an invisible list: someone paid on a phone while the window is already serving people who ordered out loud. Before you switch it on, complete an order as a guest and as the shift, all the way to handoff. Direct online is not in every plan.
Reports earn their keep when someone asks, after the event, which hour needed a third person. Loyalty earns its keep when you actually return to the same office park. For the first outing, the usual need is take, modify, queue, hand over, and a plan B when power dips.
To walk that on your event menu, book a demo. Module map: features.
Related articles:
- POS system for restaurants: how to choose it without burning your budget
- Restaurant POS prices: system cost components