Skip to content
  • There are no suggestions because the search field is empty.

Barcode & label printing with Loftware Cloud/Nicelabel

The  Loftware Cloud/Nicelabel integration enables AlisQI to trigger professional label printing, including barcodes and regulatory symbols, while keeping full flexibility in label design. This makes it possible to print for example labels for QC  samples, complaint samples or product identification labels. 

The Nicelabel integration enables:

  • Centralized quality data in AlisQI

  • Professional label formatting in Loftware Cloud/Nicelabel 

  • Flexible template management

  • Automation of printing workflows

  • Traceable print logging

  • Support for regulatory labeling (e.g. GHS)

The Loftware Cloud/Nicelabel integration is available as a template in AlisQI. This article explains how the integration works, how responsibilities are divided, and how to configure label printing from within AlisQI.

Overview: Clear Role Division

The integration is built on a simple principle:

  • AlisQI provides the data for the label and triggers the printing

  • Loftware Cloud/Nicelabel contains the layout for the label and does the printing

What AlisQI Does

  • Stores and manages all inspection, sample, and product data

  • Triggers the print action via workflow

  • Sends data, selected label template, and printer information to Nicelabel

What Loftware Cloud/Nicelabel Does

  • Formats the label (layout, barcodes, graphics, GHS symbols, etc.)

  • Converts data into printable barcode formats

  • Sends the print job to the correct printer

This separation ensures that customers can manage all data in AlisQI, and control label layout in Loftware Cloud/Nicelabel . Changes to formatting do not require any changes in AlisQI.

How the Printing Workflow Works

The integration uses a two-step workflow model.

Step 1 – Trigger from any analysis set in AlisQI

From any analysis set (e.g. incoming inspection, process control, final inspection, complaint handling), a workflow can be triggered to print a label.

This workflow:

  • Collects the required data fields

  • Assigns a label definition and a printer name

  • Sends the data to a dedicated Nicelabel Print Queue

The workflow can be triggered manually (via the workflow button) or automated (based on field values or conditions).

Step 2 – Print Queue Sends Data to Nicelabel

The Nicelabel Print Queue acts as the centralized point for all label print requests across the system. It contains a second workflow that sends an HTTP POST (webhook) to the Nicelabel server. In that webhook, the relevant data, selected label template and selected printer are transferred to Nicelabel.

Loftware Cloud/Nicelabel then processes the request and executes the print job.

 

Technical implementation

Label Templates and Printer Selection

To print labels correctly, two elements must always be provided:

  1. Label Definition (Template)

  2. Printer Name

These must match exactly with the configuration inside Nicelabel. If a customer has multiple printers, they must all be configured on both sides. Similarly, the label template name used in AlisQI must correspond exactly to the template defined in Loftware Cloud/Nicelabel.

Inside AlisQI, these two elements can be defined in several ways:

  • Hardcoded in the workflow that sends data to the print queue

  • Derived from a field value (for example a a dropdown that contains printer names)

  • Using dynamic variables (e.g. product-dependent labels)

This allows full flexibility while keeping configuration structured.

Data Payload: What Is Sent?

The workflow in Step 1 determines which fields from a result are sent to  Loftware Cloud/Nicelabel . It ignores any data fields it does not require, as long as required fields are present.

Feedback from Loftware Cloud/Nicelabel 

Loftware Cloud/Nicelabel can return a response confirming successful printing, the printer used and a status message. This response can be logged in the print queue for traceability.

Best Practice

The print queue should primarily act as a log, similar to a Windows print queue.

If a label needs reprinting:

  • Retrigger it from the original analysis set

  • Avoid retriggering directly from the print queue

This ensures clean traceability and audit history.

 

Support for GHS Symbols

The integration supports sending GHS hazard codes (e.g. corrosive, flammable, toxic).

  • GHS codes can be included in the data payload

  • Nicelabel translates these into standardized hazard symbols

  • Symbols are printed automatically if configured in the label layout

This enables compliant chemical and hazardous material labeling.