Must change WMS server?
Push or poll tasks in npm-compatible JSON.
Logistics WMS remote label print case (anonymized)
Anonymized summary: server push + desk clients for 100×150 labels at peak.
Background
Regional warehouse with 20+ label stations; browser print caused wrong printers.
Key challenges
- Peak batch labels
- Named thermal per desk
- Unified task JSON
Solution
- Client on each Windows desk
- WebSocket push from WMS
- Zero-margin HTML templates
- batchPrint for local reprints
Stack & deployment
Outcomes
Removed browser dialogs; stable peak queues.
Read next
FAQ
Client per desk?
Yes—one client per PC.
Mac warehouse?
Yes—same API.
vs Puppeteer PDF?
Client direct print lower latency at desk.
Network outage?
Plan reconnect/queue with WMS; see WebSocket troubleshooting.
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.