Printers & Labels use case

The problem

Print steps live outside automation. Nodlyn Discovery lists Ready printers; workflows print only after approval when needed.

Who it’s for: Shipping desks, warehouses, and offices that print from Windows-installed USB/Wi-Fi printers or Zebra-style labels.

How Nodlyn approaches Printers & Labels

Printers are discovered from the OS (USB/Wi-Fi/Ethernet) and optional serial ports. Workflows submit jobs through Printer → Print with explicit approval because printing is physical and irreversible.

Aviation/IATA printers use dedicated nodes. Everyday packing slips and Zebra-style labels pair naturally with barcode inventory flows linked from this page.

Example workflows

• Order packed → approve → print packing slip
• Barcode confirmed → print shelf label
• Alert checklist → print for night shift

Quick start

1. Discovery → Printers & document devices; accept Ready printers.
2. Use Printer → Print nodes (aviation/IATA printers use dedicated nodes).
3. Combine with inventory/barcode templates for scan→print.
4. Require operator approval — print jobs are non-reversible.

Starter templates in Studio

Open Templates in desktop Studio and search these names — they are real built-in graphs, not placeholder titles.

• Barcode Inventory Scanner

Related protocols

Guides (blog & wiki)

• Warehouse Barcode Scans: Parse, Route, and Trigger Workflows Blog
• Device Discovery in Nodlyn: Matter, Zigbee, Z-Wave, CAN Bus & More Blog
• Zero-Config LAN Discovery: mDNS Browse and Resolve Blog
• Device Discovery Wiki

Are print jobs automatic without confirmation?

You can require operator approval. Printing is physical; aviation/IATA devices use dedicated nodes, not the generic printer action.

Related use cases