Kitchen printing when the internet drops

Will my kitchen printer still work without internet?

Yes, a ticket already held on the branch PC can print if the print agent is running and the printer is reachable. A ticket still waiting in the cloud reaches the branch after its internet connection returns. The ticket's location determines what can happen next.

Nexara uses a desktop print agent at each branch to send tickets to standard ESC/POS thermal printers through USB or the local network. The branch's internet link and the PC's connection to the printer can fail separately.

• Check received tickets: the agent holds them in the branch's local print queue until a printer is available.
• Check paper already printed: the agent remembers tickets printed in the last 48 hours, preventing another automatic copy if the same ticket arrives again.

Ask to see a waiting ticket during the outage test. Check that the desktop print agent is running on the branch PC as well as checking the browser. An open dashboard page cannot take the desktop agent's place.

What does the Nexara local agent hold?

The agent holds tickets that have reached the branch, including received tickets still waiting for the printer. New orders arriving in the cloud during a disconnection remain there until the branch reconnects. A local print queue therefore covers received work, rather than every order the restaurant might receive during an outage.

When checking a missing ticket, start with whether it reached the agent. If it did, check the assigned printer. If it is still cloud-held, restoring the branch connection is the next step. Reprinting an order before locating its first copy can give the kitchen two pieces of paper for the same meal.

Tickets also have an assigned destination. A working printer may be quiet because the expected ticket belongs at another station. The Nexara kitchen printing engine explains printer assignments and category routing if that check points to setup rather than an outage.

What still needs the cloud when the internet drops?

Orders can keep arriving in Nexara's cloud queue while the branch connection is down. A quiet kitchen printer can therefore sit beside a growing list of customer orders. Once the branch reconnects, waiting tickets appear on its print agent and printing can resume.

This is the recovery path for a branch connection failure while cloud services remain available. During your test, use a separate connected device to check whether an order has reached the cloud board. That separates a ticket waiting for the branch from an order that has not arrived.

A phone hotspot next to the printer PC provides a backup internet link. For a network printer, check that switching connections still leaves the PC able to reach the printer on the local network. A restored browser connection alone does not establish that the printer is reachable.

The restaurant internet outage guide covers the wider service procedure. Include the hotspot changeover in your branch test, then check the cloud board for orders received while the kitchen was disconnected.

What resumes, and how does a ticket print once?

After reconnection, waiting cloud tickets appear on the branch's print agent. Printing catches up with the agent running and the assigned printer available. A printer without power or paper still needs attention even after internet access returns.

Check the ticket rail before pressing reprint. If a ticket printed just before the connection dropped, its paper copy may already be with your cook. Recovery can send the same ticket to the agent again, which makes automatic duplicate protection useful at exactly this point.

The agent remembers tickets printed in the last 48 hours and suppresses automatic duplicates during that period. Staff can still request a manual reprint when a paper ticket is lost or damaged.

Use manual reprint for a replacement you have identified, rather than for every order visible after reconnection. Tell the cook which paper is a replacement. Automatic duplicate protection permits deliberate reprints, so the kitchen needs to distinguish a replacement copy from another order to prepare.

Is the internet down, or is the printer unreachable?

A USB printer connects directly to the PC. A network printer needs a working local network path. Both need power, paper and a running print agent. Nexara supports standard ESC/POS thermal printers over USB or network; Bluetooth printers are not supported.

For an unavailable printer, a connected dashboard lets you redirect its menu categories to another printer. Nexara can also use automatic failover where a backup printer is configured. Test the backup destination separately from internet recovery.

• For an internet fault, restore the branch's cloud connection or use the tested hotspot backup.
• For a local network fault, check the connection between the printer PC and the network printer.
• For a printer fault, check its power and paper, then use the configured backup or dashboard rerouting.
• For a stopped print agent, restore the agent before expecting received tickets to print.

Use the printer failover guide to check the backup-printer setup and category destinations. During the test, collect the paper at the backup station and confirm that it contains the items assigned to the unavailable printer.

How should you test offline printing before service?

Test the actual branch PC and printer outside service. Disconnect the internet link without turning off the PC or printer. If you unplug the router that also connects a network printer, you will be testing two failures together and will not know which one stopped the paper.

Start with a clearly marked test order while everything is connected. Confirm that the ticket reaches its assigned printer and keep the paper for comparison. Use distinguishable test orders for the local-printing and cloud-recovery checks.

1. Arrange for a test ticket to be held locally, then disconnect only the internet link. Leave the PC, agent and printer running. Check whether that received ticket prints.
2. While the branch is disconnected, submit another test order from a separate connected device through a configured channel. Confirm it reaches the cloud board. Restore the branch connection and check that the waiting ticket appears at the agent and prints, without an automatic duplicate of work already printed.
3. Switch the printer PC to the phone hotspot. Check cloud access and, if you use a network printer, whether the PC can still reach it. Record the connection changes needed for this setup.
4. With internet access restored, test printer failure separately. Confirm that the configured backup or dashboard rerouting sends the ticket to the intended printer.

Record the outcome against each test order: whether it was received locally before disconnection, where its paper appeared, and whether an extra automatic copy printed during recovery. These observations show which part of your branch setup needs attention.

For the Nexara printing test below, have your printer model and connection type ready. The WhatsApp contact is Nexara founder Issa Al-Dalu, who answers in Arabic or English; company details are at nexaratech.io.