Labels and printing

Label templates live in Operations Studio → Labels. A template defines the physical layout and data bindings. A print job resolves that template for particular data and a printer target. A preview, a queued job and a confirmed physical print are different outcomes.

Design the label

1. Create a Label and give it a recognisable name.
2. Set width, height, unit, DPI and orientation for the actual label stock and printer.
3. Use Add to insert text, a QR code, barcode, bitmap image, box, line, ellipse or inverted text block.
4. Select an element and adjust its position, size and relevant text/code settings.
5. Insert dynamic data fields where required, then supply representative Preview Data.
6. Generate the preview and review its resolved values and measurements.
7. Save the draft and publish the reviewed template.

Units include millimeters, inches, pixels and dots. Barcode settings offer Code 128, Code 39 and EAN-13, with optional human-readable text. Check that the chosen code can represent the value you plan to print. Text that looks readable on screen can still be too small on the real stock; check one physical test label.

Bind operational values

The editor offers fields such as production order number, scan value, material number/name, quantity, batch and work-center name/code. Custom-field bindings use the configured keys.

A parameterized element can use a value such as {{productionOrder.orderNumber}}. Check Used Parameters and the resolved preview for every binding. Preview sample data is for testing; it is not the future job's live order. A label cannot obtain an unavailable value merely because its field name is present.

For an order-selection code, use the offered Production order scan value, and test it with the target Scan Input. A displayed order number and the value required by a scanner can differ.

Generate output and queue a test

In Printer Code, choose the supported output platform and generate the resolved code. The label service provides ZPL, TSPL and resolved JSON output. Resolved JSON is useful for inspecting data and layout; it does not prove that a printer accepted a job.

In Print Flow, select a registered printer and number of copies, then choose Queue Test Print. The test uses the current draft after saving and needs the relevant print permission; publication is a separate action. Recent Jobs shows the job; use its refresh control to inspect later progress.

A physical printer uses the standalone Print Bridge and its locally approved connection policy. Configure the destination in Operations Studio → Printers and the host in Print Bridges. The full machine Edge Runtime is independent. See the complete Printing chapter.

Physical jobs reject missing data instead of using preview samples. ZPL supports bitmap output. TSPL image printing is rejected until a compatible binary-image adapter is available; choose a supported layout or a ZPL printer.

Print through an Automation

Add a Print label action to a supported non-Form Automation. Select the published Label, configure its printer and copies, and map the data the template needs. Publish and activate the workflow, then test one agreed event. The action queues a job; inspect both the Automation run and the print job.

Interpret the result

State	Meaning
Queued	A print job exists and awaits dispatch.
Dispatched	The assigned Print Bridge was offered the job.
Sent	Raw printer data was transmitted. This does not prove physical output.
Unknown	Output may have happened; inspect the printer before reprinting.
Failed	Printing was reported unsuccessful; inspect the target and error before another attempt.

Queued work can be cancelled; reprints require a reason and create a linked new job. Job expiry prevents stale output after an outage. See Jobs and recovery for every state and recovery procedure. Raw TCP does not establish the reserved printer-confirmed Printed state.

Change a template safely

Use version history to inspect prior layouts or restore content for a new publication. Check dimensions, DPI and the scan result again after a change. Editing the draft does not change the existing publication, and a saved job contains its already resolved output.

If a preview is blank, verify valid JSON sample data and field paths. If jobs stay queued, check the assigned Print Bridge, local policy and current printer connection. If text is clipped or codes cannot scan, check physical stock, dimensions, DPI, printer language and barcode contents before repeating a batch.