Give each order a recognisable reference
A table number, guest reference or takeaway reference helps people talk about the same order. Agree how your team writes these references before service. Avoid free-form abbreviations that only one operator understands. When a guest asks for an update, use the recorded reference rather than describing an order as the one with the coffee.
Keep preparation notes with the order
A note recorded in the order is easier to review than a note in a separate chat. State the requested change plainly, such as no onion or sauce on the side. Dietary and allergy handling still requires your kitchen’s own safety process; software notes do not verify ingredients or replace staff confirmation. Check that the kitchen sees the note before preparation starts.
Agree what each status means
Queued should mean accepted for preparation. Preparing should mean someone has taken responsibility for cooking. Ready should mean the food is ready for handover, not already delivered. Served should mean the handover is complete. Use the same definitions at the counter and in the kitchen so a status change does not create a false expectation.
Make ready-for-handover an explicit step
A prepared dish can still wait if nobody knows it is ready. Assign responsibility for checking ready orders and completing the handover. During a rush, the operator taking new orders may not be the person collecting finished food. A visible ready status helps separate those responsibilities without promising that the system itself will deliver the dish.
Build refresh into the current workflow
Menuji’s present kitchen view uses manual refresh. Set a practical refresh habit and check that the latest order state is visible before acting. Automatic real-time updates are planned, but should not be assumed during your pilot. If several people share a display, agree who updates statuses to prevent parallel work on an outdated view.
Review one handover issue after service
Choose a single delayed or unclear order and inspect its notes and status changes. Ask what information was missing and whether it belonged in the order. Keep the review specific and useful rather than attributing every delay to software. Small changes to references, ownership and note wording can make the next service easier to follow.