What happens to kitchen tickets when a printer stops responding?

Where does the order go when the printer stops?

Start by checking whether the order exists on the board. If it does, inspect its printing status before entering anything again. Retyping the customer's order risks duplicate preparation while the original ticket is still waiting to print. A half-printed ticket needs attention because the cook may be missing a modifier or an item.

Nexara sits beside the till as the order and operations layer. Its order board and printing features let staff check missing paper against the existing order.

How is a printer failure detected?

After repeated printing failures, Nexara pauses printing to the affected printer and checks for recovery. It also tracks whether the branch printing connection is available. The time needed to detect the fault and the availability of the configured backup affect how long staff wait for redirected paper.

A failed printer affects its assigned station. A disconnected branch computer can interrupt printing to every printer it serves, even when those printers have power and paper. Connecting another printer to that same computer will not restore the computer's connection.

Record which connection failed during a branch test. Unplugging a printer's USB cable tests a different fault from disconnecting the branch computer from the internet. Keep the computer and backup available when measuring printer failover.

Which printer receives the ticket next?

Nexara routes tickets by branch, printer group and location, and can distribute printing across same-type printers. Each printer also has menu-category toggles, so the destination depends on the categories assigned to it.

A spare needs an assigned role before service. A drinks printer is little help to the grill if nobody knows that grill tickets are now coming out there. Choose a destination that the affected cook can reach, or assign someone to carry the paper.

• Identify the primary printer and connect its backup.
• Check the categories assigned to each destination and load paper.
• Print a test ticket with modifiers and Arabic text.
• Agree who carries redirected tickets to the affected station.

Include a mixed-category test order, such as a shawarma with a modifier and a drink. Follow the food ticket to the grill's backup and check the drink's destination against its own category settings. Read the modifier on the paper rather than checking only that a ticket appeared.

The Nexara kitchen printing engine guide explains category routing and Arabic thermal printing in more detail.

What prevents lost or duplicate tickets?

Pending tickets remain available for printing after a connection interruption. Nexara's automatic duplicate protection keeps a printed ticket from printing again on reconnect, including after the branch printing application restarts.

Paper can come out just before a connection drops. Recover missing paper from the existing order rather than asking the cashier to type the meal again. A manual reprint is a deliberate replacement copy, so one person should decide whether it is needed.

1. Collect any partial ticket and check the primary printer, backup output and kitchen rail for a complete copy.
2. Compare the available paper with the order on the board, including items and modifiers.
3. If no complete copy is available, request a manual replacement from the existing order once a printer is available.
4. Give the cook the complete ticket and identify the partial paper to discard.

How is the manager alerted?

Nexara sends managers failover notifications with a 5-minute cooldown. That limits repeated notifications during the fault while the manager deals with the affected station.

When the alert arrives, establish where tickets are printing and tell the affected cook. A ticket sitting beside the drinks station still needs to reach the grill. Use the replacement-copy procedure above if paper is missing or incomplete.

1. Check the order board and visible print queue for waiting work.
2. Confirm the active backup destination and tell the affected station.
3. Check the failed printer's power, paper, cover and cable.
4. After recovery, test the intended route before returning to normal service.

During a demonstration, have the manager use their own account and confirm how they receive the failover alert. Include the person covering the next shift, so the response does not depend on the owner standing beside the printer.

How should you test failover before service?

Test the printers installed in your branch, using the kitchen's assigned template and categories. Nexara supports standard ESC/POS thermal printers over USB or network. Include Arabic item names and modifiers so the test checks readability as well as delivery.

1. Print a test order through the normal kitchen route and set its paper aside.
2. Disconnect the primary printer, keeping the branch computer and backup available.
3. Send another test order and measure the wait until a complete ticket reaches the backup.
4. Confirm the manager receives the failover notification.
5. Reconnect the primary printer and check that the backup ticket does not print again automatically.
6. Record the measured wait, backup location and dashboard re-routing procedure for the shift team.

Test an internet interruption separately. Orders keep arriving in Nexara's cloud queue while the branch connection is down, and printing catches up after reconnection; the order board itself needs a connection.

The offline printing guide covers waiting tickets during connection loss. The restaurant internet outage guide covers the wider branch response.

Keep a phone hotspot beside the printer computer and practise connecting the computer and board device to it before service. Include that separate connection test in the shift handover.