Case study: the night a pizza place's kitchen printer died at 8 pm.
At 8 pm, a printer failure is rarely a quiet hardware problem. Tickets stop reaching the cooks while the owner tries to establish what the branch can still trust.
Nexara is a restaurant order and operations platform built in Amman, Jordan. It keeps tickets on the live order board and can print them through a configured backup printer or support a manual reprint. The branch needs a powered backup printer and a working connection for those routes to operate.
Figures in this post are illustrative examples, not a client's actual results.
What happened at 8 pm?
Imagine a pizza restaurant in West Amman on a Thursday evening. The branch uses one thermal printer for kitchen tickets and a separate printer for cashier receipts. Orders arrive from the phone, its own website, Talabat and Careem.
At 8:00 pm, the kitchen printer stops responding. The cashier can still see new orders arriving, but the cooks do not receive their usual paper tickets. In this illustrative example, the branch normally handles 12 orders between 8:00 and 8:15 pm. Four are already being prepared when the failure starts. Eight more arrive afterward.
| Time | What happens without a queue | What happens with Nexara |
|---|---|---|
| 8:00 | Printer stops. New tickets have nowhere visible to the kitchen. | The failed printer is marked unavailable and tickets remain on the order board. |
| 8:03 | Staff begin checking phones and order platforms manually. | The configured backup printer receives the kitchen tickets. |
| 8:08 | One order is found twice and another is missed. | The kitchen prints the waiting tickets in order. |
| 8:15 | The manager calls customers and checks bags against screens. | The manager checks the board and sends one ticket for manual reprint. |
How does the night look without a print queue?
Without a print queue, the failure becomes a memory test. A phone order may be written on paper. A Talabat order may remain visible in the partner app. A Careem order may be accepted while the kitchen is unaware of it. The manager sees separate records instead of one working list.
The manager compares incoming orders with prepared food, delivery bags and customer calls. If a ticket was printed before the fault but the kitchen cannot find it, staff may prepare it twice. If an order never printed, the customer may discover the failure before the restaurant does.
- Check every ordering channel separately.
- Write down order numbers and customer names.
- Ask the kitchen which tickets it has received.
- Call customers whose promised times may be affected.
- Rebuild the missing list before restarting production.
This process creates two risks: lost tickets and duplicate tickets. It also takes the manager away from the line when the branch needs a decision.
What changes when tickets wait in a queue?
With Nexara, orders from the phone, website, app, table QR, Talabat and Careem arrive in one live order queue. The failed printer does not erase the order. The ticket stays on the board and waits for a printer route.
Where a backup printer is configured, Nexara can fail over to it. The manager can also re-route that printer's categories from the dashboard. Once the backup printer answers, waiting tickets print in order. A ticket can be reprinted by hand when the original printer returns.
The cooks receive a paper ticket with the order details, modifiers and channel. Nexara prints Arabic kitchen tickets on ordinary ESC/POS thermal printers, with English available on the same ticket.
A year went into Nexara's printing engine. Tickets queue offline and print once, never twice, never lost. The manager configures printer groups and keeps the backup printer ready.
What did the illustrative timeline look like?
At 8:02 pm, the manager sees that the kitchen printer is unavailable. The eight new orders remain in the live queue. The cashier does not need to retype them, and the call-center agent does not need to read them aloud to the kitchen.
At 8:04 pm, the backup printer starts receiving tickets. The kitchen team sorts the printed orders by promised time. At 8:08 pm, the manager notices one pizza modifier was difficult to read and sends that ticket for a manual reprint. At 8:15 pm, all eight new tickets are accounted for.
In this illustrative example, zero tickets are lost. The branch still needs electricity, a working printer, a branch connection and staff who check the board.
| Control | What the manager checks |
|---|---|
| Order board | Every new order has a visible status and order number. |
| Printer route | Kitchen categories are assigned to the intended printer. |
| Backup printer | The configured backup has paper, power and a connection. |
| Reprint | A ticket is reprinted only when the kitchen needs another copy. |
What should a pizza branch check before service?
Printer failover works best when the setup is decided before the rush. The backup printer should be placed where cooks can hear or see it, loaded with the correct paper and assigned to the same kitchen categories as the primary printer.
- Print a test kitchen ticket before opening.
- Confirm the printer group and category assignments.
- Keep the backup printer powered and loaded with paper.
- Make sure the branch computer has a stable connection.
- Show the manager where the live order board and reprint action are.
- Run one controlled failure test during a quiet period.
Nexara is the order and operations layer beside the till. Its Cashier Reconciliation report tab gives the cashier a record for the day's close. Orders can remain in the cloud queue while the connection is down. The board itself needs a connection, so a phone hotspot beside the printer computer is a sensible backup.
Compare the setup with Nexara's printer failover guide, then review how to handle a printer failure before changing a live branch.
How does this compare with a manual recovery plan?
| Situation | Manual recovery | Nexara path |
|---|---|---|
| Order arrival | Check each channel separately. | Orders land in one live queue. |
| Printer failure | Notice it when food or paper is missing. | Tickets remain visible while the printer is unavailable. |
| Backup | Carry tickets or retype them. | Use a configured backup printer or dashboard re-route. |
| Duplicate risk | Staff may print or prepare from two sources. | Use the waiting ticket and controlled reprint. |
| Recovery | Reconcile messages, apps and handwritten notes. | Check the board, printed tickets and order history. |
A manual plan remains useful. Staff need to know how to pause production, protect customer details and contact the manager. Nexara gives the branch one order record and a working printer route, so recovery follows visible orders on the board and in order history.
For the full printing setup, see Nexara's kitchen printing engine overview and the printing features.
What to remember
- A dead printer should stop printing, not erase the order.
- One live queue is easier to check than separate channel apps and handwritten notes.
- Failover depends on a configured backup printer with power, paper and a connection.
- Nexara prints kitchen tickets beside the till and supports the cashier's close-of-day reconciliation.
Questions people ask
What happens to orders when a kitchen printer stops?
In Nexara, the order stays on the live order board and the ticket waits in the print queue. The manager can re-route categories to another printer or reprint the ticket when the printer returns.
Does Nexara automatically fail over to another printer?
Nexara can fail over to a configured backup printer. The branch must have the backup printer set up, powered and assigned to the right kitchen categories.
Can printer failover prevent lost kitchen tickets?
The queue keeps tickets visible and provides a configured backup print path. The branch still needs working hardware, power, paper and connectivity.
Can I reprint a kitchen ticket in Nexara?
Yes. A manager can manually reprint a ticket from the dashboard when the kitchen needs another copy or the original printer becomes available again.
Does Nexara need a special printer?
Nexara drives standard ESC/POS thermal printers over USB or a network. It does not require a proprietary terminal or hardware bundle.
Does the order board work without a connection?
The board needs a connection. Orders can remain in the cloud queue while the branch connection is down, and a phone hotspot beside the printer computer can help the branch reconnect.