Point of Sale (POS)

POS printer not printing

Troubleshoot printer connectivity and configuration issues at the point-of-sale register.

Jul 11, 2026

Problem

When you complete a sale at the POS register, the receipt should print automatically, but the printer does not produce output. There are no error messages, or the system claims the print succeeded but nothing appears on paper.

Causes and solutions

Cause 1: Printer is not connected or powered off

The most common reason for printer failure is a loose or unplugged connection, or the printer itself is turned off.

Fix:

  1. Check that the printer power cable is plugged in and the printer is switched on (look for a power indicator light).
  2. Verify the USB or network cable connecting the printer to your POS computer is firmly seated on both ends.
  3. If the cable is loose, reseat it (unplug and replug firmly).
  4. Restart the POS register or refresh the page in your browser.
  5. Try printing a test receipt.

Cause 2: Printer is not configured in Usystems

Even if the printer is connected to your computer, Usystems must know which printer to use for POS receipts.

Fix:

  1. Go to Settings → POS Settings (or POS Configuration) Open in Usystems.
  2. Look for a field labeled "Printer" or "Receipt Printer."
  3. Click to select your printer from the list of available printers. The list is populated from printers installed on your computer.
  4. If your printer does not appear in the list, see "Cause 3" below.
  5. Save the settings and test printing again.

Cause 3: Printer is not installed on the computer

If your printer does not appear in the Usystems printer list, it is not recognized by your computer's operating system.

Fix:

  1. On your computer (Windows, Mac, or Linux depending on your system), install the printer driver from the manufacturer's website or the disc that came with the printer.
  2. After installation, restart your computer or the POS application.
  3. Go back to Settings → POS Settings Open in Usystems and verify that your printer now appears in the printer dropdown.
  4. Select it and save.

Cause 4: No paper in the printer

A simple but easily overlooked cause: the printer is out of paper.

Fix:

  1. Open the printer's paper tray or cover.
  2. Load a new roll or stack of receipt paper (check your printer's manual for the correct paper size and orientation).
  3. Close the tray and test print again.

Cause 5: Printer driver is outdated or corrupted

Printer drivers can become outdated after operating system updates, or files can become corrupted.

Fix:

  1. Go to your computer's device manager or printer settings (varies by operating system).
  2. Find your printer in the list and right-click (or use the menu) to uninstall the driver.
  3. Restart your computer.
  4. Reinstall the printer driver from the manufacturer's website or use your operating system's automatic driver search.
  5. Restart the POS register and test printing.

Cause 6: Firewall or security software is blocking printing

On some computers, particularly those with strict security settings, a firewall or antivirus software may block Usystems from communicating with the printer.

Fix:

  1. Check your firewall or antivirus settings to see if Usystems (the browser or application) is blocked from accessing local devices.
  2. Add Usystems to the firewall's allowed applications list, or temporarily disable the firewall to test.
  3. If printing works after disabling the firewall, work with your IT support to add a proper exception.

Tips

  • Test the printer independently: Try printing from a different application (e.g., Notepad or your web browser) to confirm the printer itself is working. If it prints elsewhere, the issue is specific to Usystems.
  • Check the browser console for errors: If you are using Usystems in a web browser, open the browser's developer tools (F12 or right-click → Inspect) and check the console for error messages related to printing.
  • Contact your IT support: If the printer is connected and installed on your computer but Usystems still cannot find it, your IT team may need to check the computer's system settings or network configuration.

Was this helpful?

More like this