Skip to content
LionPOS

Receipt printer

What you’ll find here

Section titled “What you’ll find here”
  • Pick the right printer model for the lane.
  • Pair it from the dashboard or the POS workspace.
  • Print a test slip and read the activity log.
  • Recover from “printer offline” without losing receipts.

I. Supported printers

Section titled “I. Supported printers”

The receipt printer pairs over the POS bridge running on the lane PC / Vendor Desktop. It works with any ESC/POS or StarPRNT compatible thermal printer that the bridge can reach.

Common picks:

  • 80mm thermal (most retail lanes) — Epson TM-T88, Star TSP143, Xprinter XP-Q200.
  • 58mm thermal (small lanes / kiosks) — smaller slip, fits on a 5cm roll.
  • Network printers (RJ45 / Wi-Fi) — most common in stores; the bridge uses the printer’s IP.
  • USB printers — bridged through the lane PC.

If you don’t have a real printer yet, the bridge ships with a PDF/HTML preview so you can train cashiers without hardware.

II. Pair the printer

Section titled “II. Pair the printer”

From the dashboard: Settings → Devices → Receipt printer → Add.

From the POS workspace: Settings → Devices → Receipt printer → Add.

Fields:

FieldWhat to enter
NameFriendly name (e.g. “Lane 1 receipt”).
ConnectionNetwork / USB / Bridge preview.
AddressIP:port for network, device path for USB.
Paper width80mm or 58mm.
Characters per lineAuto-detected; usually 42 (80mm) or 32 (58mm).

Tap Test connection before saving — the system sends a one-line ping to the printer.

The endpoint is GET/POST /api/v1/vendor/settings/devices (see API catalog → “Vendor: Settings”).

III. Test slip

Section titled “III. Test slip”

Open the device card → Print test. The bridge emits a slip with:

  • Store header.
  • Test line “RECEIPT PRINTER TEST — ”.
  • QR code linking to the device detail page.

If you see the slip, pairing is correct. If not, check the POS Bridge status (next guide).

IV. Offline behavior

Section titled “IV. Offline behavior”

When the bridge loses contact with the printer:

  • Receipts queue in the lane (SQLite via Vendor Desktop).
  • Once the bridge reconnects, queued receipts print in FIFO order.
  • The device activity log shows the gap and the auto-resume.

The dashboard never blocks checkout over a printer issue.

V. Activity log

Section titled “V. Activity log”

Open the printer card → Activity tab:

  • Last connect / disconnect timestamp.
  • Number of receipts queued.
  • Recent print errors with retry count.

Use this when investigating “did this order actually print?”

VI. Common pitfalls

Section titled “VI. Common pitfalls”

Pairing succeeds but no slip prints. The bridge URL is reachable but the printer is not on the same network. Confirm the IP / port, then re-test.

Slips print garbled characters. Wrong characters per line or wrong character set. Pick 42 for 80mm, 32 for 58mm; set charset to UTF-8.

Slips print on the wrong store header. The store selector is on the wrong store. Switch and re-test.

Slips get cut off mid-line. Paper width mismatch. Try 58mm if your printer is 58mm, or vice versa.

Section titled “Related”