Troubleshooting
Easy
Restaurant Admin (Owner) · Manager · Cashier
Updated September 2026
Printer is not working
No KOTs coming out — diagnose device, connection and agent in that order.
What is the problem?
Orders are being accepted but nothing comes out of the printer, or the test print fails.
Why it can happen
- The device is off, out of paper, or off the network (LAN printers listen on port 9100).
- The machine running the print agent was rebooted and the agent did not come back — USB/Bluetooth/LAN devices print through it.
- A LAN printer's IP address changed, so jobs route nowhere.
- Jobs piled up Queued or Failed in the spool while the device was down.
How to check it
- Printers page stats: is the device counted under Offline? Are jobs piling up as Queued or Failed?
- Physical basics: power, paper, lid closed, network cable/Wi-Fi for LAN printers (they listen on port 9100).
- Agent: for USB/Bluetooth/LAN devices — is the machine running the print agent still on? A rebooted till PC that did not restart the agent is the classic cause.
- Test button on the device row — watch where the job stops in Print jobs.
How to fix it
- Queued jobs with an offline device → fix the device/agent, then reprint the failed jobs from the spool.
- LAN printer unreachable → check it is on the same network as the agent and its IP has not changed.
- Everything fine but jobs fail → note the job status and contact support.
- Keep service running: the KDS does not need the printer (Kitchen display).
What NOT to do
Do not
- Do not delete failed jobs to tidy the list — reprint them once the device is back; deleting loses the kitchen's ticket history.
How you know it is fixed
Test print comes out clean, and the next accepted order prints its KOT within seconds.
Still not working?
If the device passes its test elsewhere but jobs still fail here, the agent or spool is the suspect — contact RestoQR support with the printer name, connection type and the failing job's status from Print jobs.
Was this helpful?