Printer compatibility
Choose the right connection for your label printer.
Start with the connection your printer actually supports. Match it to the machine that runs the print service, then evaluate one representative label on your media.
Four ways to reach a printer
The Automation Service is called a Runner in configuration and API fields. Local queues belong to that service's machine; a queue installed on your browser's computer is not automatically available to it.
| Connection | Where it runs | What to configure | Successful handoff means |
|---|---|---|---|
Network ZPLzpl-raw | Center directly, or a Windows/Linux Automation Service with network access. | A ZPL-capable device, its host and RAW TCP port, often 9100. No OS printer driver is involved in this path. | sent: the stream was sent without a device acknowledgement. |
Windows RAW queueos-raw | Automation Service on Windows. | The exact installed printer name, usable by the service account. The spooler passes the rendered ZPL through; the device must understand it. | sent: the Windows queue accepted the stream. |
Linux CUPS RAW queueos-raw | Automation Service on Linux with CUPS. | A named queue, working lp/lpstat commands and RAW pass-through. The device must understand the rendered ZPL. | sent: CUPS accepted the stream. |
Windows driver printingos-driver | Automation Service on Windows. | An installed printer and driver visible to the service account. The service renders a bitmap and submits it through Windows GDI. | sent: the spooler accepted the rendered job. |
Network targets use a host and port. Local targets use a printer name. Choose the target type that matches the connection; changing the type does not install a driver or convert a RAW queue into a bitmap printer.
Windows driver output rejects labels with raw printer-command objects and labels whose minimum resolution cannot be met. Unix os-driver output is not implemented; Linux CUPS RAW is a separate path.
PDF is a separate output
Print Center can export a label as PDF. Use it to review or share the document. A downloaded PDF establishes that a file was created; printing it from another application has that application's own scaling, driver and outcome behavior.
What the result can tell you
confirmed requires an acknowledgement-capable protocol. Ordinary zpl-raw, Windows RAW, CUPS RAW and GDI do not supply that confirmation. A simulator receiving a job also does not establish physical output quality.
If transmission becomes uncertain, work can be held with an unknown outcome. Inspect the device and job before deciding to repeat it. See the printer recovery guide.
Evaluate your actual printer
Record the device and media
Note the model, firmware, connection, label size and print density. Match the configured density to the device; for example, 203 dpi · 8 dots/mm. For local printing, include the queue name, driver and service account.
Use a representative design
Include your fonts, artwork, longest expected values and barcodes. For imported labels, review the conversion findings as well as the image.
Request one label
Check the selected target, actual media, alignment and barcode readability. Record both the reported result and what you inspect on the physical label.
Agree on recovery
Establish who investigates a held job and who may request a replacement. Include the service's access to the printer and business data in your rollout plan.
This matrix describes connection support. Device suitability depends on the model, driver, media and workload you evaluate.