Low-resource shop PC?
Client handles render; browser sends jobs only.
Manufacturing ERP shop-floor print case (anonymized)
Anonymized discrete manufacturing: shop-floor work orders and office ERP statements via printHtml / batchPrint, including authenticated URL reports.
What decision-makers care about
| Role | Concern |
|---|---|
| Production | Slow tickets, line waits |
| IT / ERP | Web report changes, auth URLs |
| Finance | Month-end batch, duplex A4 |
| Procurement | Shop PC specs, license count |
Background
15 shop-floor Windows PCs plus office desks; ~400+ work orders/day; month-end statements 200–500 pages per run.
Key challenges
- Frequent work-order print
- Wide A4 tables
- Some authenticated URLs
Architecture
ERP web → printHtml or printHtmlByUrl with auth extraOptions → shop client → floor printer. Finance uses batchPrint for statements.
Solution
- Windows client on shop PCs
- printHtml from report HTML
- printHtmlByUrl + extraOptions for auth URLs
- batchPrint for month-end statements
Stack & deployment
Implementation timeline
| Phase | Work |
|---|---|
| Day 1–2 | One A4 work-order PoC |
| Week 2 | 3 shop-floor lines live |
| Week 4 | Two authenticated URL reports |
| Month 2 | Month-end batchPrint + Lodop parallel review |
Measured outcomes (pilot)
| Metric | Improvement (pilot) |
|---|---|
| Work order print | ~15s → ~3s |
| 200 statements batch | ~45min → ~18min |
Outcomes
Silent shop tickets; faster month-end batch.
Procurement checklist
- License = shop PCs + office silent stations
- Accept: silent tickets, auth URL, batch sample audit
- Document Lodop retention scope
Risks & rollback
- Wide-table pagination vs ERP preview → CSS page-break tuning
- Auth token expiry → refresh before printHtmlByUrl
- Shop PC reboot → client autostart policy
Read next
FAQ
SAP URL reports?
printHtmlByUrl with cookies/headers.
Linux shop terminal?
deb client—linux-deploy guide.
vs hiprint?
HTML + printHtml when no designer templates.
PoC start?
One A4 report + demo—about one day.
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.