A submission is recorded
QZ accepting the request means the send was accepted. It does not establish that a usable label emerged.
BROWSER LABEL PRINTING WITH QZ TRAY
Review labels in SmartFACT, then send them through QZ Tray on an attended workstation. Keep the printer choice and the physical check with the person doing the work.
QZ Tray installation and a checked printer setup are required.
Review and accept the prepared label.
Connect to the selected local printer queue.
Print one label, then inspect the result.
SET UP THE WHOLE PATH
The workstation, driver, queue and label stock all affect the result. Check them together before using the station for production.
Install and run QZ Tray. The site needs HTTPS and server-side signing configured, with the QZ certificate trusted on the workstation.
Select the intended printer explicitly. The current PDF path needs a compatible pixel-printing driver, 203 dpi resolution, 100 × 150 mm stock, zero margins and no scaling.
The operator prints a calibration label, measures it and scans the barcode. Keyboard-input scanners fit this check. Recheck the setup when the printer, driver or stock changes.
ONE DELIBERATE ACTION
Accepting a run prepares the output. Each “Print one label with QZ” action sends at most one queued copy, keeping the attended workflow explicit.
QZ accepting the request means the send was accepted. It does not establish that a usable label emerged.
Check the size, content and barcode on the physical label. A browser preview alone cannot qualify the hardware.
An ambiguous send needs operator reconciliation. The app does not automatically repeat it and risk a duplicate label.
CHECK YOUR SETUP
The workspace runs in the browser, but attended local printing needs QZ Tray installed and running. QZ provides the connection between a web application and local printers. See QZ’s getting started guide.
Bring the exact model, operating system, driver and label stock for assessment. The current SmartFACT path sends PDFs through QZ; it does not send native ZPL. QZ notes that some printers need a pixel-capable driver for this path. A brand name alone does not establish compatibility. See QZ’s pixel-printing documentation.
Unattended background printing, arbitrary label sizes and a native raw-printing path are outside the current early-access profile. Discuss those requirements before planning a rollout.
QZ uses certificates and signed messages to establish trust in print requests. SmartFACT signs authorised requests on the server. Certificate provisioning is a setup requirement; see QZ’s signing documentation.
LET’S START WITH YOUR WORKFLOW
Tell us about your data, customer requirements and printer. We’ll help you assess whether SmartFACT Labels fits.