How to Troubleshoot Orders Missing in the Kitchen: Find the Order, Then Check Who Took It and Where It Went

When the kitchen says it hasn’t received an order, first check whether the order exists. Then find out who has taken responsibility for it and which items should go to which station. Finally, check whether there was a printing issue. No paper ticket doesn’t prove there’s no order, and a customer receipt at the till doesn’t prove the kitchen received a prep ticket. Find where the process broke down and address that step—don’t re-enter the whole table’s order.

Start by checking these possibilities

• Can’t find the order: Check the location, ordering channel, table, submission time, and the front-of-house staff member’s records. If the result is unclear, don’t ask the customer to submit the order repeatedly.
• Order exists, but no one has taken it: The shift lead should assign someone to confirm the request and arrange preparation. Don’t assume the printer is faulty.
• Someone has taken the order, but the station is unclear: Check the specific items with the hot kitchen, cold kitchen, or bar as appropriate. Don’t assume that because the drinks arrived, the hot food did too.
• Print job or print result unclear: Check the ticket rack and the food being prepared or already completed. Confirm whether the ticket printed or was picked up before deciding whether to pass on the information or print again.

Use one troubleshooting record to track the same request

• Order number or staff-assigned identifier: ____; location and table/pickup number: ____; submission method and approximate time: ____.
• Items, sizes/specifications, and quantities not received: ____; front-of-house staff member who handled the order: ____.
• Is there a matching system record: ____; person who took responsibility: ____; intended prep station: ____.
• Items the kitchen has received/started/completed: ____; person who received them on site: ____.
• Ticket purpose and job result, if relevant: ____; next action: ____; person responsible for follow-up: ____.

Assign one front-of-house staff member to follow up while everyone else continues service. Tell the customer which items you’re checking and who will get back to them. Don’t promise a serving time until the kitchen has confirmed it. Only after confirming that the order has not been submitted should you help the customer submit it once. Don’t assume submission failed just because the page has stalled.

Check prep tickets separately from customer receipts

MenuSnap can be used for QR-code ordering and staff-entered POS orders; when the venue is set to browse-only, staff still need to take the order. KDS and kitchen printing work according to the plan, stations, and configuration. Customer bills and receipts serve different purposes from kitchen prep tickets, and use different templates and destinations. A printer making noise only shows that part of the process is working.

The software responsible for printing needs an online device or service to actually send the job; this is the print executor. Troubleshoot by checking the ticket type, whether the rule is enabled, the template, target printer, operating mode, online executor, and job status in turn. First identify the ticket’s purpose and where the process stopped; don’t let every station reconfigure equipment at will.

Before reprinting, ask whether anyone has started on the original order

Confirm with the kitchen using the order number and specific items. A paper ticket may have printed but been left by the machine, picked up, or already put into preparation. If a reprint is necessary, tell the recipient it’s supporting information for the original order, not a second order. If only one dish is missing, hand over just that dish rather than resending the whole table’s order and making the kitchen guess what’s different.

The kitchen lead should fit items not yet started into the current sequence, while anything already prepared stays as planned. Before responding to a request to cancel or change a specification, check the preparation status. Pass special dietary requests directly to the staff member responsible at the venue so they can confirm based on ingredients and preparation conditions; a note alone doesn’t count as acceptance.

If you can’t print temporarily, use a handoff to cover that step

Use the original order number and clearly write what’s being handed over. Ask the recipient to repeat the quantity and key specifications, and note the handoff time. Keep the paper note linked to the original order in the system. Don’t send items already sent to the kitchen again as new orders once the network is back.

QR-code ordering on the website, online payments, cloud syncing, and KDS updates depend on a network connection. A local paper ticket isn’t proof that the whole process works offline. Once the server connection is restored, check the latest orders, what was actually prepared, and payments received, then fill in any missing records. If you’re unsure how to record them, contact support to avoid sending an order to the kitchen or recording a payment twice.

Tell support where the process stopped—not just that the printer is broken

Provide the necessary order identifier, the time of the incident and the venue’s time zone, ticket purpose, device model, connection method, sending software version, and job result. Redact customer information and payment credentials. The owner or an administrator they have explicitly authorized should arrange any device reconfiguration. Don’t interrupt service that is still in progress while troubleshooting.

At closing, sort confirmed findings into orders not submitted, orders no one took, orders sent to the wrong station, printing issues, and unclear ticket handoffs. Don’t label a clue as a product fault before it’s confirmed. On the next shift, address the step that most often breaks down, and check whether any duplicate preparation occurred or temporary records were left unresolved.