What happens to kitchen tickets when a printer stops responding?
During the Friday shawarma rush, the grill printer stops halfway through a ticket. The cook needs to know whether the rest is waiting to print or coming out beside the drinks station.
Nexara keeps orders visible and tickets waiting when a printer fails. The restaurant order and operations platform is built in Amman, Jordan. Automatic failover requires a configured backup. Check that printer for the ticket, or re-route the failed station's categories to another working printer from the dashboard.
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.
| What you find | What to check next |
|---|---|
| Order visible, no ticket | Inspect the print queue and check the printer's power, paper and connection. |
| Order missing from the board | Investigate order intake before treating this as a printer fault. |
| Main printer unavailable, backup configured | Confirm the configured backup destination and its availability. |
| No working backup | Track waiting tickets and re-route categories when another printer is available. |
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.
| What has stopped | What Nexara does | What to check during service |
|---|---|---|
| One printer repeatedly fails | Pauses printing to that printer and checks for recovery. | Inspect the failed printer while staff collect tickets from the backup. |
| Branch printing connection is unavailable | Keeps pending tickets waiting for printing to resume. | Check the branch computer, its printing application and its internet connection. |
| Branch internet is down | Keeps incoming orders in the cloud until the branch reconnects. | Check internet access before treating every printer as faulty. |
Unplugging a printer's USB cable creates a different fault from disconnecting the branch computer from the internet. Note which equipment has lost its connection before changing printer assignments.
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.
Set the backup destination before service. Choose a printer the affected cook can reach; if the grill's backup is beside the drinks station, assign a staff member to carry redirected tickets to the grill.
- Identify the primary printer and connect its backup.
- Check the categories assigned to each destination and load paper.
- Record the backup location and ticket-handoff responsibility for the shift team.
- Make sure the person covering the next shift knows these assignments.
Keep category assignments specific. If the backup also prints drinks, staff need to distinguish its usual work from the food tickets redirected during a fault. Record the normal category settings so the manager can check the intended route after the primary printer returns.
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.
- Collect any partial ticket and check the primary printer, backup output and kitchen rail for a complete copy.
- Compare the available paper with the order on the board, including items and modifiers.
- If no complete copy is available, request a manual replacement from the existing order once a printer is available.
- 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, check whether the backup is producing complete tickets and whether work is still waiting. Use the replacement-copy procedure above if paper is missing or incomplete.
- Check the order board and visible print queue for waiting work.
- Confirm that tickets are reaching the configured backup destination.
- Check the failed printer's power, paper, cover and cable.
- Compare the last complete ticket with the waiting orders to identify any gap.
Use the manager's own account when checking the alert during the pre-service test. The person responsible for responding should see how the notification reaches them, rather than relying on a demonstration from the owner's account.
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. Keep the branch computer and backup connected while testing a fault at the primary printer.
- Create a mixed-category test order, such as a shawarma with a modifier and a drink, using Arabic item names and modifiers. Print it through the normal route, check each destination and read the paper for completeness. Set the tickets aside.
- Disconnect the primary printer, keeping the branch computer and backup available.
- Send another test order with the same items and measure the wait until a complete food ticket reaches the backup. Check the drink's destination against its category settings and confirm the Arabic text and modifier are readable.
- Confirm the manager receives the failover notification on their own account.
- Reconnect the primary printer and check that the backup ticket does not print again automatically. Send a fresh test order to confirm the intended route after recovery.
- Record the measured wait and dashboard re-routing procedure alongside the shift team's printer assignments.
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.
You can start at nexaratech.io or message the founder on WhatsApp.
What to remember
- Test printer failure and internet loss separately before service.
- A printer failure leaves the order visible and its ticket waiting.
- Assign backup categories and show the cook where redirected tickets arrive.
- Automatic duplicate protection keeps printed tickets from printing again on reconnect.
- Manager failover notifications have a 5-minute cooldown.
Questions people ask
Why is my kitchen printer not printing orders?
Check whether the order is on the board first. If it is, inspect the print queue, printer power and paper, then the USB or network connection and branch printing application.
Can Nexara switch to a backup kitchen printer?
Yes, through automatic failover where a backup is configured. Otherwise, re-route the failed printer's categories to another working printer from the dashboard.
How long does restaurant printer failover take?
The wait depends on how long failure detection takes and whether the configured backup is available to print the ticket. Measure your branch's actual wait from disconnecting the primary printer to receiving a complete ticket at the backup.
Will tickets print twice when the printer reconnects?
Nexara's automatic duplicate protection keeps printed tickets from printing again on reconnect. A manual reprint produces a replacement copy and should be handled by the person assigned to reprints.
What if I do not have a backup printer?
The ticket waits for a working printer. You can re-route categories when another printer is available, or manually reprint a ticket after the original printer returns.
Do I need a new till to use a backup printer?
Nexara sits beside your existing till as the order and operations layer. It supports standard ESC/POS thermal printers over USB or network; check your existing hardware and backup routing during setup.
Will a backup printer work if the restaurant internet is down?
A second printer does not restore the branch's internet connection. Connect the branch computer through the phone hotspot, then check that waiting tickets reach the intended printer.