Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.firstresonance.io/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

ION can print barcode labels for any traceable entity in the system — parts, part inventories, runs, locations, and more. The Print Label modal lets you pick a label template, choose a printer, set the number of copies, preview the rendered label, and submit the print job. Labels are barcode-encoded so operators can scan them downstream during installation, kitting, receiving, and inventory operations. Print exactly the format your downstream scanners expect — ION supports multiple label templates per entity type.

​
Printing modes

ION supports three printing paths. Which one you’ll use depends on how your org’s print infrastructure is set up. The mode is configured at the org level, not per-print.
ModeWhen to useSetup
Browser (Zebra Browser Print)Operator’s workstation is directly connected to a Zebra printer over USB.Install Zebra Browser Print on the workstation. ION talks to it over localhost:9101.
Server (Print Server)Printers are shared across the floor and managed centrally.Configure ION’s print server setting and register printers in the Admin area.
Third-party (e.g. PrintNode)A third party fulfills print jobs from a queue.Enable third-party printing in org settings; ION emits print requests instead of driving the printer directly.
If you’re not sure which mode your environment uses, ask an admin or check Organization Settings. The Print Label modal will only show the printer picker that matches the configured mode.

​
Prerequisites

  • Permission to print labels for the entity type you’re working with.
  • A printer reachable from the printing mode your org uses (see above).
  • At least one barcode template configured for the entity type. ION ships defaults for parts, part inventories, and runs; custom templates can be added by an admin.

​
Open the Print Label modal

The Print Label modal opens from the entity you want a label for — for example, from a part inventory page, a run page, or any context with a “Print” action. The modal shows three controls and a preview:
  • Label Template dropdown — picks the barcode format and field layout. Templates are scoped to the entity type, so only valid templates appear.
  • Printer Selection — picks which printer to send to. The picker varies based on org print mode.
  • Label Copies — number of duplicate labels to print (minimum 1).
  • Print Preview — renders the first label exactly as it’ll print, so you can verify format before submitting.

​
Steps

​
1. Pick a label template

Open the Label Template dropdown and select the format you want. ION pre-selects the first available template — adjust if your downstream process expects a different one.

​
2. Pick a printer

Open the Printer Selection picker and choose the destination printer. The picker pulls printers from the active mode (browser, server, or third-party). If no printers appear, see Troubleshooting below.

​
3. Set the number of copies

Use the Label Copies input. Default is 1. Use copies when you need multiple identical labels — for example, one per kit container or one per face of a packaged unit.

​
4. Verify the preview

The Print Preview area renders the label exactly as the printer will produce it. Check that the barcode and any human-readable fields look right before submitting.

​
5. Print

Click Print. The button is disabled while a job is in flight or when copies = 0. On success ION shows a confirmation toast (Print job submitted with id=<id> for server mode, or a generic success for third-party). For browser mode, the print is dispatched directly to Zebra Browser Print.

​
Barcode formats

Each label template defines its own barcode format (Code 128, QR, DataMatrix, etc.) and the data fields encoded into it. Common patterns:
  • Part Inventory labels encode the inventory ID so scanning identifies a specific lot or serial.
  • Part labels encode the part number for kit and bin labeling.
  • Run labels encode the run ID for run-step kiosk scanning.
If your scanners need a specific encoding (e.g. a lot-coded GS1 DataMatrix), have an admin configure a custom template — don’t try to reformat ad-hoc.

​
Troubleshooting

​
”Failed to connect to printers”

If the modal shows a red Failed to connect to printers alert:
  • Browser mode — Confirm Zebra Browser Print is running on the workstation. Click the Check Printer Status link in the alert (it opens https://localhost:9101/available in a new tab) to verify the local print service is responding. If the page errors, restart Zebra Browser Print and reload ION.
  • Server mode — Confirm the print server is reachable and the printer is registered. Check Check Printer Status the same way; on persistent failure, escalate to an admin to verify print server health.
  • Third-party mode — Failed connections here usually indicate the third-party service is down. Print requests are still queued and will fulfill when service is restored.

​
Labels print but barcodes won’t scan

Most often this is a template mismatch — the template encoding doesn’t match what your scanner expects. Try a different template; if no template scans correctly, request a custom template from your admin. In server mode, ION shows Print job submitted with id=<id> even before the printer renders. Check the print server’s job queue for that ID to see whether the job is queued, printing, or errored.

​
Tips

  • Print one before printing many — Use Label Copies = 1 for a verification print, then re-open and print the full quantity. Saves wasted stock when a template is wrong.
  • Scan-test before deploying — Whenever a new template is added, scan a printed label with the actual scanner the floor uses. Encoding compatibility isn’t always obvious from the preview.
  • Keep the modal narrow — Print one entity at a time. If you need bulk-print across many parts, an admin can configure a print queue or batch flow rather than opening the modal repeatedly.