Printer Setup and Troubleshooting

A printer failure during service can hide orders, delay one kitchen station or create duplicate tickets. Troubleshooting should follow a fixed sequence so staff do not repeatedly restart devices, reprint blindly or change settings without recording what happened.

Record the working configuration first

Before installation, document:

• printer model and serial number;
• purpose and location;
• connection type;
• IP address or port where relevant;
• driver or POS profile;
• paper width;
• station routing;
• cash-drawer connection;
• fallback printer;
• supplier contact.

Save a test print and screenshots of the approved configuration.

Installation sequence

1. Confirm the exact model is supported.
2. Inspect the power supply, cable and physical location.
3. Load the correct paper.
4. Run the manufacturer self-test.
5. Connect by the approved interface.
6. Install the supported driver or POS printer profile.
7. Set paper width, cutter and character options.
8. Assign the printer to the correct station.
9. Print a simple test.
10. Print a realistic long order with modifiers.
11. Test reprint, void and fallback.

First diagnostic: what exactly failed?

Symptom	Likely area	Immediate check
No lights or display	Power	Socket, approved power supply, cable and switch
Self-test works, POS does not print	Driver, port, network or routing	Print queue, selected printer and POS station assignment
Some items do not print	Menu routing	Item-to-station mapping and recent menu changes
Random characters	Driver or print language	Correct model profile and interface settings
Blank or faint thermal receipt	Paper direction, paper type or print head	Reload roll and run self-test
Frequent disconnects	Network, Wi-Fi, cable or power	Connection history and physical stability

Paper feed and jams

1. Stop sending new print jobs.
2. Open the cover according to the manufacturer’s instructions.
3. Remove torn paper without tools that can damage the mechanism.
4. Check roll width, loading direction and feed path.
5. Close the cover fully.
6. Run a self-test.
7. Print one controlled order.

Repeated jams usually indicate unsuitable paper, damaged consumables, debris, cutter trouble or mechanical wear. Do not treat them as a permanent “staff loading” problem without investigation.

Ethernet printer troubleshooting

• Check link lights and cable.
• Confirm the printer’s current IP address.
• Check whether DHCP changed the address.
• Confirm the POS points to the correct port.
• Test connection from the approved device.
• Check network separation and firewall changes.
• Reserve or document the address according to the network design.

Wi-Fi and Bluetooth troubleshooting

• Check signal and interference at the actual station.
• Confirm credentials and network band support.
• Check sleep and power-saving behaviour.
• Remove stale pairings where appropriate.
• Test reconnection after restart.
• Prefer a more stable supported connection for critical kitchen routing if wireless remains unreliable.

USB and serial troubleshooting

• Use the supported cable and port.
• Check whether the operating system reassigned the port.
• Confirm serial speed and communication settings where relevant.
• Avoid unpowered hubs for critical devices unless approved.
• Label cables to prevent accidental swapping.

Queue and duplicate-print control

Before pressing reprint:

1. Check whether the original job is still queued.
2. Confirm whether the kitchen already received a ticket.
3. Clear only the failed job, not the whole queue without review.
4. Mark any reprint clearly.
5. Tell the relevant station.
6. Record duplicate preparation if it occurred.

Menu-routing failures

If drinks print but food does not, the printer may be healthy. Check:

• item station assignment;
• modifier routing;
• location-specific menu;
• new item IDs;
• time-based routing;
• fallback rules;
• recent integration changes.

Controlled restart sequence

Use the supplier-approved order. A typical process is:

1. pause affected order intake if tickets may be lost;
2. record current jobs and order numbers;
3. restart the printer;
4. restart the print service or local controller if required;
5. restart the POS application only if necessary;
6. run a self-test and one POS test;
7. recover missing orders without duplicating completed tickets.

Do not repeatedly power-cycle every device during a live backlog.

Fallback during service

Situation	Fallback
One station printer fails	Route to the approved secondary printer and mark station headings
All POS printing fails	Use KDS or controlled handwritten tickets with order references
Network unavailable	Use supported local or offline route, or pause affected channels
Repaired printer returns	Test before restoring routing; clear old queued jobs safely

Escalation evidence

Provide support with:

• model and serial number;
• time failure started;
• self-test result;
• connection type and IP or port;
• error lights or messages;
• affected order references;
• changes made before failure;
• steps already attempted;
• photos where useful.

Preventive routine

• Daily: paper, visible damage, basic test at opening.
• Weekly: clean according to manufacturer guidance, check cables and repeated errors.
• Monthly: test spare printer, fallback routing and network documentation.
• After changes: test every affected station and menu route.

Close the incident properly

Record the root cause, repair, orders affected, customer impact and prevention action. A printer is not “fixed” if staff must restart it every evening.

Decision tree for a live failure

1. Is the order visible elsewhere? Check POS, KDS or provider dashboard.
2. Can the printer self-test? If not, focus on power, paper or hardware.
3. Can another application print? If yes, focus on POS routing or queue.
4. Is one station affected? Check item mapping and local connection.
5. Are several devices affected? Check network, controller or POS service.
6. Could old jobs print later? Control the queue before switching fallback.

After software, menu or network changes

Run a regression test covering:

• each order channel;
• each kitchen station;
• long modifiers;
• delivery and collection headings;
• reprint marking;
• cash drawer where connected;
• fallback routing;
• restart and reconnection.

A printer that produces one test line is not proof that the complete order flow works.

When to replace rather than repair

Replacement may be more sensible where:

• the model is no longer supported;
• drivers are unavailable for the current POS;
• faults recur after cleaning and approved repair;
• parts and consumables are difficult to obtain;
• network security or firmware cannot be maintained;
• downtime cost exceeds a planned replacement.

Confirm compatibility before replacing with a newer model from the same manufacturer.

Related guides

• POS and Kitchen Systems — the main guide for the wider topic.
• Receipt Printers and Hardware — the broader guide that frames this implementation.
• Kitchen Printers vs Customer Receipts — a closely related operational control to review alongside this page.
• How to Choose a Receipt Printer — a closely related operational control to review alongside this page.