Drop-in replace Lodop with printHtml?
No—prepare HTML/CSS layouts and call printHtml; Lodop templates need a separate rework scope.
Running web-print-pdf in parallel with Lodop
Many teams keep Lodop while adding an optional parallel HTML print path for reports, browser upgrades, or domestic desktops. This guide covers inventory → PoC → parallel run → phased rollout—not a drop-in Lodop API replacement. See Lodop comparison and C-Lodop notes.
How to read this guide
Lodop has a long track record in overlay and intranet printing. If your Lodop deployment is stable, no change is required because of this page. This guide is for teams evaluating an additional HTML + npm path alongside Lodop.
Pre-migration inventory
Document the current state before choosing PoC candidates or keeping Lodop forms.
| Item | Record | Why |
|---|---|---|
| Forms list | Name, page, daily volume | Prioritize PoC / HTML work |
| Layout type | A4 / thermal / overlay | HTML fit assessment |
| Printers | Driver name, paper | printOptions |
| OS / browser | Windows / domestic OS, versions | Client package |
| Lodop entry points | API calls, C-Lodop usage | Parallel switches & rollback |
Implementation mapping (reference)
Typical integration differences—not a drop-in API map. Verify with official product docs.
| Step | Typical Lodop | Typical web-print-pdf |
|---|---|---|
| Layout | Lodop commands / overlay | HTML/CSS template |
| Trigger | LODOP APIs | printHtml |
| Silent output | Local control / service | Web Print Expert client + npm |
| Browser | Includes C-Lodop deploy | Standard Web + local WebSocket |
| Domestic OS | Per Lodop vendor docs | deb client (Linux deploy) |
Phased path (Lodop may run in parallel)
Phases may overlap. Lodop can handle forms not yet moved to HTML throughout.
Phase 1: PoC (about 1–2 days)
- Install the client
npm install web-print-pdf- Pick a simple HTML report (not the hardest overlay first)
- Call
printHtml; preflightgetConnectStatus() - Compare sample output with Lodop side by side
- Sign off with business owners before parallel run
Phase 2: Parallel run (about 2–4 weeks)
- Feature flag: new modules use web-print-pdf
- Keep legacy Lodop forms on Lodop
- Document rollback (disable flag, restore Lodop calls)
- Remote push: WMS remote labels
- Review volume and errors after 2–4 weeks
Phase 3: HTML rollout by priority
- Prioritize by volume × HTML effort
- Migrate A4 / order reports first
- Overlays: case-by-case; keep Lodop where needed
- Domestic desks: Kylin / UOS
- Update ops docs and error handling
Parallel run & rollback
Keep Lodop services, licenses, and templates during parallel run. Rollback = disable the web-print-pdf flag and restore Lodop calls—do not uninstall Lodop before PoC sign-off.
Risks & mitigations
- Overlay drift: calibrate HTML; keep Lodop for misfits
- Dual pipelines: document which form uses which path
- Client offline: use getConnectStatus; see error handling
- Licensing: follow each vendor's terms independently
FAQ
When to keep Lodop?
Stable precision overlays and forms that cannot be HTMLized soon can stay on Lodop.
PoC examples?
Try invoice or order table demos, or extract HTML from your page.
Rollback during parallel run?
Disable the web-print-pdf flag and restore Lodop calls; keep Lodop services installed.
vs C-Lodop / Chrome page?
Browser/C-Lodop notes: C-Lodop guide. This page focuses on phased parallel rollout.
Notice & trademarks
Technical integration reference only. Lodop and C-Lodop are independent products; names are used for identification and route comparison—trademarks belong to their owners. Whether to continue Lodop or adopt web-print-pdf is your organization's decision based on official docs, licensing, and IT policy. This page is not commercial advice about any third party.
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.