Every make

One console for every label printer you own.

Zebra, Honeywell, SATO, Toshiba, TSC and the rest: PrinterVision talks to each in its own language, over open protocols, and puts them all in one list - without a vendor cloud in between. Zebra, Honeywell and SATO are managed; every other make is monitored.

How each printer connects
  • Zebra Link-OS WebLink, direct · managed
  • Honeywell · Intermec · Datamax-O'Neil SNMP + HCD, via collector · managed
  • SATO Interface commands, via collector · managed
  • Toshiba TEC, TSC, Brother, Epson… SNMP, via collector · monitored
  • Vendor cloud needed None

Illustration of the connections PrinterVision uses.

Why

Mixed fleets are the rule, not the exception.

Most sites run more than one make of printer. Each make comes with its own tool, its own cloud or gateway, and its own way of telling you something is wrong.

For the site manager

What it costs your operation
  • One make is monitored, the others are not - until one of them stops the line.
  • The same label prints darker on one printer than on the next, because each make is set up in its own tool.
  • Nobody has one list of what is on the floor, where, and in what state.

For IT

What actually keeps you up at night
  • Every vendor tool is another server, another agent, another account to keep up to date.
  • Vendor clouds and gateways mean printer data leaving your network to places you do not control.
  • Opening inbound ports at every site to reach printers is a conversation with security you would rather not have.
How

Zebra connects itself. The rest goes through one small collector.

No server to run, no inbound ports to open: Zebra printers on WebLink need nothing on site, the other makes one small collector per site. Everything connects out to PrinterVision.

1

Point Zebra printers at PrinterVision

Link-OS printers keep a secure WebLink connection open to PrinterVision, with mutual TLS. No agent, nothing on site.

2

Install the collector

One small service per site or VLAN, on Windows or Linux, enrolled with a one-time code. Outbound HTTPS only.

3

Discover and approve

The collector finds the printers on its network. Approve them, and they land in the collector's site.

What this looks like in practice

A new site with three makes.

Onboarding readout Monday · New distribution site

09:00 - The site's Zebra printers are pointed at PrinterVision and come online over WebLink.

09:40 - IT installs the collector on a machine on the printer VLAN and enrols it with a one-time code from PrinterVision.

09:55 - The collector discovers Honeywell and SATO printers on its network. They wait as New until someone approves them.

10:10 - Approved and placed in the site, every printer is in one list, and one common-settings change sets darkness and speed on all three makes.

Without PrinterVision

Three vendor tools to install, three ways to configure, and still no single view of the site.

The features behind it

Everything that example runs on.

Zebra

Zebra over WebLink, with nothing in between.

Zebra Link-OS printers keep a secure connection open to PrinterVision, so their state and alerts arrive the moment they happen. Full management: settings, files, firmware, certificates, Wi-Fi and network, profiles and batteries.

  • Link-OS 5.0 and later, mutual TLS with certificates
  • No agent on the printer, no server on site
  • Supply levels are not reported over WebLink yet
  • Zebra printers not on WebLink are polled over SNMP and SGD through the collector
DOCK-01 · Zebra ZT411Online
  • Connection WebLink
  • Certificate Valid
  • Agent on site None

Illustration.

Honeywell and SATO

Honeywell and SATO, managed in their own language.

Through the collector, PrinterVision speaks each make's own management protocol: settings, files, firmware and restarts, as for Zebra.

  • Honeywell, Intermec, Datamax-O'Neil: SNMP plus HCD - settings from the printer's own schema, files, firmware, profiles, restart
  • SATO: its interface commands - status, settings, files, restart, and firmware (except the EP18)
  • Common settings - darkness, speed, media, label size - across Zebra, Honeywell and SATO
Common settings · 3 makes
  • Darkness 60 %
  • Speed 152 mm/s
  • Applied to Zebra, Honeywell, SATO

Illustration.

Every other make

Every other network printer, monitored.

Toshiba TEC, TSC, Brother, Epson, cab, Godex, Citizen, Printronix, Bixolon, Avery Dennison and other SNMP printers are monitored over standard SNMP, in the same list as the rest.

  • Status, alerts, identity, counters and supplies where the printer reports them
  • Files and label formats sent to the printer, and a restart
  • No settings, profiles or firmware for these makes
PACK-03 · Toshiba TECMonitored
  • Connection SNMP, via collector
  • Alerts None
  • Label count 184,220

Illustration.

The collector

One small service per site, outbound only.

The collector polls the printers of its network for PrinterVision, runs the work it is sent, and discovers new printers.

  • Windows service with an installer; also on Linux, for example a Raspberry Pi
  • Outbound HTTPS only - no inbound ports to open
  • Enrolled with a one-time code; printers behind it land in its site
Collector · Warehouse 2In contact
  • Platform Windows service
  • Connection Outbound HTTPS
  • Printers behind it 23

Illustration.

Security & hosting

Your printers, your data, no vendor cloud.

PrinterVision is a cloud service by CaptureTech in Belgium. Printers talk to it directly over open protocols, never through a manufacturer's cloud or gateway.

  • Hosted in Azure West Europe, each customer its own database
  • Sign in with Microsoft work accounts; roles limited to sites
  • Approval of new printers and an operation log of every change
Your environment
  • Hosting Azure West Europe
  • Database Your own
  • Sign-in Microsoft work account

Illustration.

Frequently asked

Common questions about mixed printer fleets.

Which label printers does PrinterVision support?

Three levels. Full management for Zebra Link-OS printers (Link-OS 5.0 and later) directly over Zebra WebLink: settings, files, firmware, certificates, Wi-Fi and network, profiles and batteries. Management for Honeywell (including Intermec and Datamax-O'Neil) and SATO through the collector: settings, files, firmware and restart. Monitoring for other network printers - Toshiba TEC, TSC, Brother, Epson, cab, Godex, Citizen, Printronix, Bixolon, Avery Dennison and more - over SNMP: status, alerts, supplies, counters, file sends and restart, without settings or firmware.

Do I need to install anything for Zebra printers?

No. Zebra Link-OS printers (Link-OS 5.0 or later) connect directly to PrinterVision over WebLink: the printer keeps a secure connection open, with mutual TLS and certificates. There is no agent on the printer and no server on site.

Does PrinterVision show supply levels?

For printers that report them, such as most printers monitored over SNMP. Zebra printers on WebLink do not report supply levels to PrinterVision yet; their alerts, such as ribbon or media out, do arrive.

What is the PrinterVision collector?

A small service you install on one Windows machine per site or VLAN (it also runs on Linux, for example a Raspberry Pi). It polls the printers that are not on WebLink, discovers printers on its network and runs the work PrinterVision sends it. It only makes outbound HTTPS connections and is enrolled with a one-time code.

Do I need a printer manufacturer's cloud or gateway?

No. PrinterVision talks to printers over open protocols - WebLink, SNMP, HCD, SATO's interface commands and the print port - without a vendor cloud, gateway or agent.

Bring every make into one list.

Tell us which printers you run and on how many sites. We show you PrinterVision with several makes side by side.