Install the macOS print client

The print client is a small macOS menu-bar app that prints labels silently to the right printer — no browser print dialogs, no picking a printer per label. Pair it once and Enter on the pack bench means a label is already feeding out of the Zebra.

Install

Download the DMG and drag the app to Applications. It is code-signed and notarized, and needs macOS 26. It runs as a menu-bar accessory — no Dock icon — with an optional launch-at-login toggle so it is ready when the floor opens.

There is no auto-update, on purpose. The thing that prints your labels should not change itself mid-shift. New versions are a new DMG you install when you choose.

Pair with your browser

Pairing is one shot from the web app on the same Mac — no tokens to copy around. Under the hood, the client runs a local server bound to 127.0.0.1 only. It is never reachable from your network, and connections from anywhere else are rejected outright. The pairing handshake issues a bearer token that the client checks on every print with a constant-time compare. Pairing survives restarts and login cycles.

Route label types to printers

The client fetches the label types your account actually uses — AusPost domestic and international (CN22/CN23), StarTrack, Team Global Express, and A4 customs paperwork for international orders — and you map each one to a printer, with an optional paper size and orientation. Typical floor setup: 100×150 thermal labels to the Zebra, customs paperwork to the office laser.

A built-in test print pushes a small test page through the same pipeline as real labels, so one button validates the rendering, the mapping, and the driver together.

Multi-parcel shipments

A three-parcel shipment arrives as one PDF with three label pages. The client renders and prints every page at full size, one label each — an earlier generation of this pipeline printed only page one, and that bug is fixed for good. How labels stay full-size on thermal stock is covered in ZPL mode & media sizes.

Logs

Every print attempt is logged in the client — timestamp, label type, printer, carrier, success or error — and an audit entry lands in your OrderOps account with who printed what. When a label "didn't print", the log says what actually happened.