Must change WMS server?
Enqueue tasks in the fixed message format; build receive/store + WebSocket or HTTP expose on your server.
Logistics WMS remote label print case (anonymized)
An anonymized regional warehouse story: peak-season push printing on 20+ desks without browser dialogs. For warehouse ops, WMS engineers, and procurement.
What decision-makers care about
| Role | Concern |
|---|---|
| Ops | Missed/wrong labels at peak |
| WMS team | Server receive/store/expose workload |
| Procurement | Per-desk cost vs cloud SaaS |
Background
20k–40k 100×150mm labels/day at peak across 20+ Windows desks. Browser print needed manual confirm; wrong thermal printer caused rework. Goal: unattended push print with status feedback to WMS.
Key challenges
- Peak batch labels
- Named thermal per desk
- Unified task JSON
Architecture
WMS enqueues fixed-format jobs → your receive/store/expose consumer API → desk client with that URL → local print. Manual reprint: admin UI may use npm locally (remote path itself does not call APIs).
Solution
- Client on each Windows desk
- WebSocket push from WMS
- Zero-margin HTML templates
- batchPrint for local reprints
Stack & deployment
Implementation timeline
| Week | Work |
|---|---|
| W1 | 1-desk PoC: push one label |
| W2 | 5-desk load test + printer binding |
| W3–4 | All 20 desks + HTML template sign-off |
| W5–6 | Peak drill + reconnect playbook |
Measured outcomes (pilot)
| Metric | Before | After |
|---|---|---|
| Human steps/label | ~8s | Push-triggered |
| Wrong print rate | ~1.2% | ~0.15% |
| WMS effort | — | ~8–12 dev-days |
Outcomes
Removed browser dialogs; stable peak queues.
Procurement checklist
- License per label-station PC
- Enqueue jobs in the fixed message format; build receive/store/expose server
- Acceptance: 1h load test without manual clicks
- Keep browser print as emergency fallback
Risks & rollback
- Push storms queue up → server throttle + batch limits
- Bad margins waste labels → preview sampling before go-live
- Network outage → client queue + WMS retry policy
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.