ERP/WMS pushes jobs
Server queue sends printHtml-compatible JSON; client listens and prints.
WMS/OMS pushes label HTML/URLs to warehouse PCs via WebSocket/HTTP; the local client runs printHtml without browser dialogs. See remote print setup.
Typical stack: WMS/OMS builds label HTML → pushes via WebSocket/HTTP to warehouse PCs → local Web Print Expert client runs printHtml. No client on the server—each workstation installs and configures the remote URL.
Server queue sends printHtml-compatible JSON; client listens and prints.
Set pdfOptions size; see batch labels demo.
printOptions.printerName per workstation; same API on Win/Mac/Linux.
await webPrintPdf.printHtml(
receiptHtml,
{ width: '80mm', height: '120mm', printBackground: true },
{ printerName: '热敏打印机', copies: 1 }
);
| Mode | Best for | Notes |
|---|---|---|
| WebSocket push | Peak batch, low latency | Client listens on a long connection |
| HTTP polling | WebSocket blocked | Pull pending jobs on an interval |
| Front-end printHtml | Clerk clicks Print | Still dialog-free, not unattended |
printOptions.printerName matches workstation thermal driverbatchPrint or queue throttlingNo—only on warehouse print PCs; server pushes jobs.
Yes—client auto-prints on remote messages without dialogs.
See <a href="../window-print-alternative/">window.print alternative</a>.
Yes—<a href="../kylin-print/">Kylin</a> / <a href="../uos-print/">UOS</a> deb clients.
Each workstation sets a different printerName; WMS jobs may include station IDs. See print options.
The same web-print-pdf front-end runs on Windows, macOS, and Linux/domestic OS—install the matching client on each desktop.