ERP/WMS pushes jobs
Your server maintains a job queue; desk clients connect to your exposed API to receive and print.
WMS remote shipping label silent print
WMS/OMS: print job JSON is fixed; build your server to receive, store, and expose WebSocket/HTTP. Desk PCs enter that URL in the client. See remote print setup.
WMS remote print architecture
Stack: WMS/OMS enqueues fixed-format jobs → your receive/store/expose consumer API → desk client with that URL → local print. No client on server; remote path does not call webPrintPdf.printHtml (npm is format reference only).
Typical scenarios
100×150mm etc.
Set pdfOptions size; see batch labels demo.
Named thermal printers
printOptions.printerName per workstation; same API on Win/Mac/Linux.
Integration steps
- Learn the fixed message format (remote print guide)
- Build receive/store + WebSocket/HTTP expose on WMS server
- Install client on desk PCs; enter that URL in Remote Print settings
- Zero label margins; match paper width
- Errors: error handling
Label print sketch
Unattended remote print does not call webPrintPdf.printHtml. Below: server-side enqueue in the fixed format; map fields using printHtml API or client test tasks (call npm only for local PoC).
// WMS server: enqueue fixed-format jobs (remote path — do not call printHtml)
const task = {
id: crypto.randomUUID(),
timestamp: Date.now(),
type: 'printHtml',
content: labelHtml,
pdfOptions: { width: '100mm', height: '150mm', printBackground: true },
printOptions: { printerName: stationPrinter },
extraOptions: { requestTimeout: 15 }
};
queue.push(task);
// Desk client: set Remote print URL to your WebSocket/HTTP endpointChecklist
- Remote: WebSocket or HTTP polling
- Paper: pdfOptions match printer
- Silent: requires local client
- Compare: Lodop comparison
Push vs pull
| Mode | Best for | Notes |
|---|---|---|
| WebSocket push | Peak batch, low latency | Client connects to your WS API |
| HTTP polling | WebSocket blocked | Client polls your HTTP API |
| Browser local print | Manual reprint | npm printHtml in admin UI—not unattended remote |
Troubleshooting checklist
- Remote URL matches WMS push endpoint
- Label HTML margins zeroed (avoid blank pages)
printOptions.printerNamematches workstation thermal driver- Peak load:
batchPrintor queue throttling - Failures: error handling & retries
How this page fits with related guides
- This page: WMS push + warehouse PC output
- Remote print setup: client URL & channels
- Receipts & labels: 80mm / 100×150 HTML layouts
- Print.js comparison: why browsers cannot run unattended
FAQ
Client on WMS server?
No—only on warehouse print PCs; server pushes jobs.
Unattended?
Yes—the client pulls from your consumer API without dialogs—no webPrintPdf.printHtml on the remote path (npm is for local print or format reference).
vs window.print?
Domestic OS warehouses?
Multi-warehouse printer binding?
Each workstation sets a different printerName; WMS jobs may include station IDs. See print options.
Client deployment by platform
The same web-print-pdf front-end runs on Windows, macOS, and Linux/domestic OS—install the matching client on each desktop.