Restaurant POS Receipt Printer Troubleshooting Checklist (kitchen, bar, and expo printers)

A receipt printer that stops mid-shift feels like a locked door in a busy hallway. Tickets pile up, expo starts guessing, and the kitchen gets loud for the wrong reason.

When I’m doing receipt printer troubleshooting for restaurants, I stick to a simple rule: fix what’s safe and fast on the floor, then collect clean evidence before calling support. This checklist is written for managers and shift leads who need answers now, not a tech lecture.

The 60-second triage (do this before anything else)

1. Identify the printer and station

• If it’s printing food tickets, label it Kitchen.
• If it’s printing drink chits, label it Bar.
• If it’s printing order summaries or runner tickets, label it Expo.

2. Check the obvious, on purpose

• If the printer has no lights, then confirm the power switch is on, the power brick is seated, and the outlet strip is on.
• If the printer light is red or blinking, then open the cover, reseat the paper, and close the lid until it clicks.
• If paper feeds but prints blank or faded, then swap in a fresh roll (correct thermal side) and try again.

3. Run one safe test

• If the printer has a built-in feed button, then hold it briefly to feed paper.
• If it prints a self-test (some models do), then the printer can print, the problem is likely connection or POS routing.

4. Decide: printer problem or POS problem

• If the printer self-test works but POS tickets don’t, then focus on connection, IP, or POS settings.
• If self-test fails, then focus on paper, lid, cutter, or hardware fault.

For brand-specific examples, I sometimes reference the vendor’s own guides, like the Toast kitchen printer troubleshooting FAQ.

Kitchen vs bar vs expo printers (why the same “fix” doesn’t always work)

Station	Typical symptom	Most common cause	My fastest safe fix
Kitchen	Stops printing mid-rush	Paper not seated, lid not latched, cutter jam	Reseat paper, relatch lid, power-cycle printer only
Bar	“Offline” in POS	Network drop, Wi-Fi weak, cable bumped	Check link lights, reseat Ethernet, confirm correct SSID
Expo	Partial tickets or delays	Print queue stuck, routing mis-set	Clear queue, test print from POS, confirm station routing

Kitchen printers also take heat, grease, and vibration. Bar printers take spills and cable tugs. Expo printers take constant volume. Different wear, different failures.

Symptom-based receipt printer troubleshooting (If/Then quick fixes)

Symptom: Not printing at all

• If the printer has power but no tickets, then confirm the POS is sending to the right destination (Kitchen vs Expo confusion is common).
• If it’s USB-connected, then reseat the USB on both ends and try a different USB port on the terminal.
• If it’s networked, then check the Ethernet port for link lights. No lights usually means cable, port, or switch.

Safe action: power-cycle the printer (off 10 seconds, then on). Avoid opening sealed panels or removing screws, that can void warranties.

Symptom: Offline in POS

• If the printer is networked and shows offline, then verify the printer is on the same network as the POS.
• If someone recently rebooted the router or switch, then the printer may have a new IP address (DHCP change).

If you’re on Toast hardware, their TP200 troubleshooting and FAQs is a good example of the floor-safe checks most teams can do.

Symptom: Garbled text or random symbols

• If the ticket looks like “Greek letters” or junk, then the POS is usually using the wrong printer driver or language setting.
• If it started after swapping hardware, then you may be sending jobs to the wrong model profile.

If/Then: if a self-test prints cleanly but POS output is garbled, then it’s software configuration, not the print head.

Symptom: Paper jam or cutter stuck

• If paper won’t feed, then open the lid and remove the roll gently.
• If the cutter area is blocked by torn paper, then remove only what you can see and reach without tools.

If/Then: if you need tools to clear it, then stop and escalate. Forcing a cutter can turn a small jam into a replacement.

Symptom: Partial print, light print, or blank spots

• If the print is faint, then use a new roll and confirm it’s thermal paper (not bond paper).
• If only part of each line is missing, then the print head may be dirty.

Safe action: clean only as the manufacturer allows. Most thermal printers support gentle cleaning with approved materials. Don’t scrape the print head.

Symptom: Slow printing or delayed tickets

• If tickets arrive in bursts, then the print queue may be backed up.
• If only one terminal causes the delay, then that terminal’s print service may be stuck.

If/Then: if a single terminal is the problem, then restart the POS app or the terminal’s print service (if your POS support guide allows it), then re-test with one ticket.

For a quick visual on reconnecting an order printer workflow, this Clover POS order printer video is a practical reference.

Network checks you can do without breaking anything

For Ethernet and Wi-Fi printers, I keep it simple:

• If link lights are off, then swap the Ethernet cable with a known-good cable.
• If link lights are on but it’s offline, then collect the printer’s IP address from its status page (or POS device list).
• If the IP changed recently, then the POS may still be pointing to the old address.

Don’t change advanced settings like ports (RAW 9100 vs LPR) mid-shift unless your POS vendor tells you to. That’s the kind of “quick fix” that becomes a two-hour outage.

What I collect before calling Restaurant POS Support (so the fix is faster)

When you escalate, clean details cut your downtime. Here’s what I ask teams to capture:

• Printer model (photo of the label is best)
• Station name (Kitchen, Bar, Expo) and where it sits
• Error lights status (solid, blinking, color)
• Connection type (USB, Ethernet, Wi-Fi)
• IP address (for network printers)
• POS terminal name (the one sending tickets)
• Last ticket time (when it last printed correctly)
• Photos (lights, cabling, paper path, and the bad print sample)

Prevent repeats (the stuff that saves Saturday night)

I treat printer uptime like plumbing: boring when it works, a disaster when it doesn’t.

• Label everything: printer name, station, and cable tags. It stops accidental swaps.
• Use surge protection: especially for kitchen outlets shared with warmers or microwaves.
• Set stable addressing: static IP or DHCP reservations for network printers.
• Schedule cleaning: quick wipe-down, keep paper dust out, and follow vendor rules.
• Keep spares: paper rolls, one spare power brick, one spare Ethernet cable.

When I’m acting as a Business Technology Partner, this ties into more than printers. Good Restaurant POS Support and Kitchen Technology Solutions often connect to Small Business IT foundations like Cloud Infrastructure, Cloud Management, and even Office 365 Migration planning. For multi-site groups, Data Center Technology, Infrastructure Optimization, and Secure Cloud Architecture matter too, because outages rarely stay “just a printer.” I also push Cybersecurity Services, Endpoint Security, and Device Hardening because a compromised terminal can break printing and payment flows. That wider view is part of my Technology Consulting approach, with Innovative IT Solutions, Tailored Technology Services, IT Strategy for SMBs, Managed IT for Small Business, and strong Business Continuity & Security that supports real Digital Transformation.

Printable Incident Log (copy and use during a shift)

Date/Time	Station	Printer model	Symptom	Error lights	IP address	POS terminal name	Steps tried	Last ticket time	Photos taken (Y/N)	Resolution

Conclusion

Receipt printers fail in predictable ways, even when the shift feels chaotic. I use this receipt printer troubleshooting checklist to get a safe win fast, then escalate with details that actually help. If your team keeps losing time to the same printer issues, tighten the labels, lock down IPs, and document every incident. The goal is simple: fewer surprises, faster fixes, and more tickets landing where they should.