IT systems · Practical guide

Validating NiceLabel: from the approved data record to the correct label

A NiceLabel or Loftware Cloud print job may succeed with the wrong expiry date, printer or number of labels. Test the label produced, including what happens when printing resumes after an interruption. The approach helps packaging, QA and IT teams with limited staff select meaningful failure cases for human medicinal product GMP.

Table of contents

At a glance

How do you validate NiceLabel or Loftware Cloud?

Trace the approved source record through the template revision, variable mapping, print component and device to the physical label. Identify the edition, versions, permissions and logging. Test incorrect batch data, multiplied quantities and retries after interruption. The status “Printed” indicates successful transmission to the device. It does not prove that every physical label is complete, legible and correctly assigned.

  • NiceLabel Cloud is called Loftware Cloud; local NiceLabel products should be separated.
  • The release of templates does not automatically validate source data and runtime variables.
  • Transfer status, physical print quantity, and usable labels are distinct attributes.
  • Tariff, client, and configuration determine functions, history, and potential failure paths.

Cloud, on-premise products, and print components differ

NiceLabel Cloud was renamed to Loftware Cloud in March 2024. Local NiceLabel products, according to the manufacturer, retain their original name. Therefore, ensure that more than "NiceLabel" is listed in the system inventory: Cloud Edition or local deployment, Control Center, Designer, Print, Web Client, Automation, and the actual printers in use, including their respective functions.

The cloud documentation includes Designer, Essentials, Business, Compliance, and Enterprise editions. The on-premise products, as outlined in the 10.5 documentation, feature Designer Pro, PowerForms Suite, LMS Pro, and Enterprise. A subscription does not automatically imply SaaS. On-premise components may also require a subscription and connections to the license management system.

The public documents cover NiceLabel 10.5 and patch 10.5.0.11126. The cloud help reviewed is version 25.9. These are the versions of the sources examined. Record the server, clients, drivers, tenant and subscribed options for your installation. An API or test environment is available only if the actual service provides it.

Sources: [1] [2] [4] [5] [3]

Limit the relevant labeling process.

Begin with the use of the label: Does it indicate an intermediate product, a material sample, or a medicinal product packaging? Determine which information constitutes a quality decision or correct assignment. An incorrect batch may be critical, even if the layout and barcode appear formally correct. An internal storage adhesive label may require a different form of evidence.

This guide concerns computerised activities in GMP for human medicines. Annex 11 supports risk-based planning of system evidence. For packaging operations, Chapter 5 addresses matters including correct printing, legibility and quantity discrepancies. Assess applicability separately for warehouse labels, medical devices and other labelling requirements.

Describe a complete approved route including data source, selection rule, layout, output, and control. Define the actions to be taken in the event of interruption, lost connectivity, or incorrect input. The mere installation of an edition named Compliance does not replace this professional delineation. Similarly, successful PDF preview does not validate the output on the intended print medium.

Sources: [16] [17] [19] [13] [11]

Connecting the right template with the right data

A released template may correctly format an incorrect expiry date. Therefore, verify the transition from the approved ERP or production dataset to each utilized variable. Which identifier is assigned to the batch? What occurs in the case of multiple matches, an empty value, an outdated dataset, or a no longer valid assignment?

The cloud help describes print, trigger and document APIs for certain editions. This proves available integration paths, but no technical correctness of your interface. Document field meaning, format, origin and handling of error responses. A transport success and the selection of the correct technical dataset are separate test results.

In applications, the help function explicitly warns that entering values for a non-existent variable name will not trigger an error message. Therefore, a negative test should intentionally use a fictitious variable name and evaluate the actual outcome. Do not assume, without evidence, that every incorrect assignment will be technically detected. If necessary, take a justified additional control decision.

Sources: [15] [10] [17]

Further reading:

Review batch release and approved test exemptions

Cloud workflows integrate revisions, release, and access roles. With appropriate configuration, print users can utilize the approved version, while authors work on a new revision. Essentials is limited to the built-in production release process as described in the help documentation. Therefore, do not implement a custom, multi-stage workflow until your edition and actual capabilities have been fully defined.

In addition, the help provides targeted print permissions for other workflow states, as well as an application option for unpublished files. This can be beneficial for development and testing activities. However, verify which role is actually authorized to print via which entry point. A general statement that drafts can never be printed would be incorrect.

A rollover test case includes a production operator, a template author, and a deliberately configured test access. Additionally, capture who is authorized to modify logging, variables, or release actions. Re-authentication during a release may support control. Whether a specific action constitutes an applicable electronic signature is assessed separately; a status change or password dialog does not suffice on its own.

Sources: [7] [8] [9] [10] [17] [20]

Further reading:

Check the entire printing chain with targeted documents

The following work aid assigns errors and validations to a specific print path. Fill in your client, customer, driver, and device. Verify the actual production entry point; a successful preview in a different client may mask a different path.

For the described cloud print form, the help specifies its own limits: a database connection, up to 5,000 records and 1,000 labels per print. These limits do not apply to all NiceLabel versions. Furthermore, the printer stored in the template is not automatically selected there. Printer selection and actual output are therefore expressly part of the test.

Work aid: Errors and documentation along the labeling pathway
StepSpecific attitudeTargeted failure scenarioRelevant evidence
Source data Order, Batch, confirmed expiry date Record belonging to an adjacent batch Balance source and pressure values
Template Revision and productive role Draft on alternative entry Used Revision and Authorization
Variables Field mapping and quantity parameters Unknown variable name or incorrect multiplication Data values and calculated expected values
Output Client: Treiber, Device, Material Incorrect printer or different settings Physical label and device status
History Application Logging and Access Logging disabled Actual stored information
Interruption Cache, Order ID, Repetition Resend the entire job Physical quantities and order reference

Sources: [11] [10] [12] [14] [17] [19]

Example: 100 labels following a disruption

The following is a hypothetical example and does not constitute a completed product test. Order J-100 requires 100 usable labels from template version V3 for batch B-26. The professionally verified expiration date is 2027-06-30; this date is not calculated herein. In the considered cloud form, the field Quantity multiplies the value of Copies.

In the event of a disruption, 80 actually produced labels are counted. Five are deemed unusable and are securely segregated. The decision regarding acceptance and rejection is made according to a predefined sample instruction. The table outlines expected outcomes, without any specified automated quantity calculation or built-in duplicate prevention.

Expected results for a data error, print quantity and controlled reprint
Test caseInput or stateIndependently calculated expected resultExpected decision
Incorrect data set V3 correct; expiry 2027-09-30 from adjacent row Deviation from specification 2027-06-30 Identify the incorrect assignment and withhold the output
Quantity correct Copies 25; Quantity 4 25 × 4 = 100 100 requested; additionally verify physical copy.
Incorrect quantity Copies 25; Quantity 100 25 × 100 = 2,500 Investigate errors prior to use; separately verify the formulation boundary.
Interruption 80 batches prepared; of these, 5 unusable. 80 − 5 = 75 available; 100 − 75 = 25 missing "Printed" is not sufficient; inventory reconciliation is required.
Targeted addition 25 additional error-free labels 105 produced = 100 usable + 5 reject Document the basis and reason for the copy.
Blind Repetition Fully printed 100 times without errors 75 + 100 = 175 available; 75 excess Stop further use and investigate excess quantity.

Sources: [11] [12] [14] [19] [17]

Correctly evaluate print status and records

The term "Printed" is defined as successful transmission of the print job to the device. "Restarting" indicates that the entire job is resubmitted. These terms must not be equated with fully functional physical output. Paper jams, material changes, or damaged labels require appropriate monitoring and operational handling.

The logging of print jobs in an application can be enabled or disabled. According to the help documentation, the logged content includes, among other items, label, quantity, printer, and variable values. Therefore, both the configuration settings and actual example printouts should be reviewed. Can the relationship between order, template version, used data, and justified reprint be traced back later?

Loftware Cloud Compliance is described with a history of up to twelve years. This is a product specification, not a general legal retention period, and does not serve as evidence of your current settings. Determine required data, access, and retention based on the process. Additionally, assess which information is retained during export and how it can be recovered following a system migration.

Sources: [12] [10] [13] [18] [17]

Evaluate failure paths and updates based on the client version in use

Offline capability depends on the execution path as defined by cloud support. Enterprise automation requires a configured cache and locally available data; the web client relies on previously loaded content. Desktop designers and print functions do not possess a corresponding cache for cloud documents. Cloud triggers require connectivity for order intake. Therefore, a general statement such as "prints offline thereafter" would be impractical.

Review specifically which template and data are available during a disruption, how new orders are handled, and what occurs upon restoration of connectivity. Relying solely on reloaded history does not prevent duplicate physical dispensing. Clearly assign repetitions to their originating order and establish responsibility for decision-making in cases of unclear print status.

Even minor changes can impact data. The documented local patch 10.5.0.11126, for example, affects the configurable handling of leading and trailing whitespaces in PAS variables. Therefore, evaluate updates based on your fields, components, and known defects. A version number does not imply automatic safety nor the necessity to repeat all tests unchanged.

Sources: [14] [5] [17]

Prepare specific involvement and effort in SMEs.

A well-defined start includes a representative label family, its data source, and the production printing pathway. The specialty department provides acceptable values, exceptional cases, and usage criteria. IT defines components and interfaces. The responsible quality function supports assessment of evidence requirements. Decision authorities are established in alignment with organizational structure.

Effort drivers are many template variants, manual inputs, different printer models, multiple locations and inconsistent source data. In addition, roll variants and alternative ways to fail. Therefore, prepare a list of combinations that are actually used. It enables a well-founded selection of test cases without blindly combining any label with any device.

Obtain appropriate supplier documentation covering version, license, support, and provided evidence. The public lifecycle table for NiceLabel 10 currently does not specify a defined end-of-support date; therefore, no unlimited assurance can be inferred. Specifically, clarify local license dependencies and long-term access to required data through contractual agreements. A valid validation plan—including pricing and duration—can only be reasonably developed following this scope definition.

Sources: [6] [4] [17] [19]

Checklist prior to use of the pressure path

This internal checklist consolidates the decision-making framework for the defined scope of use. For each relevant point, provide either validation evidence or a justified evaluation. Any deviation must be assessed based on its impact on correct labeling; a technically successful print does not conceal an open factual data error.

Consider the subsequent operation: New templates, additional printers, modified ERP fields, and other failure scenarios require a change assessment. Clear responsibilities for disruptions and reprinting help particularly when production and IT are not available simultaneously.

  • Product, edition, client, as well as local components and drivers, are documented.
  • Source values and batch assignments are verified against professionally validated target values.
  • Productive roles use the designated released stand; test exceptions are delimited.
  • Variable names, missing values, and quantity parameters include targeted negative tests.
  • The printer, material, and physical readability are verified during the actual dispensing process.
  • Logging, storage, and required export capabilities are appropriately configured.
  • Interruption, rejection, and reprocessing can be clearly matched.
  • Changes, disturbances, and usage decisions are managed by responsible authorities.

Sources: [17] [18] [19]

Project experience and collaboration

Reconcile the print job with the labels actually produced

With the labelling team, we prepare a print order with known source data, template and expected quantity. With IT, we follow it to the physical labels, including interrupted and repeated printing. A fixed local route may need a limited test package. Cloud components, multiple printers or changing data sources first require each handover to be defined. We identify who handles defective or surplus labels. Successful transmission to the printer does not complete the evidence.

Frequent Questions about NiceLabel Printing Paths

Does NiceLabel now mean fully Loftware?

No. NiceLabel Cloud was renamed Loftware Cloud in 2024. Local NiceLabel products are explicitly addressed separately in the renaming document. Therefore, please capture the edition, operating mode, and components of your installation. Even a local NiceLabel deployment may be based on a subscription; the license form alone does not constitute a cloud system.

Sources: [1] [4]

Is Loftware Cloud Compliance already validated for our GMP process?

The system name does not indicate approval of your application. The description references specific features such as separate environments and extended history. Nevertheless, the actual print path, data, roles, and traceability evidence must still be evaluated. Manufacturer documentation may support the availability of appropriate components. Whether your configuration reliably supports the intended labeling requirements requires customer-specific justification and appropriate testing.

Sources: [13] [17]

Can users print only approved labels?

The production pathway may be restricted to approved labels; all actual access paths and user roles must align with this restriction. The guidance also includes print permissions for other workflow states and an application option for unpublished files. Therefore, evaluate these options within your specific setup. A deliberately authorized test print must be handled differently from an unauthorized draft print within the production pathway.

Sources: [8] [9] [10]

Why is a released label template alone insufficient?

The submission alone does not guarantee that the selected batch and its data are correct. An incorrect expiration date may still appear in the correct format. Verify the origin, selection, and assignment of expiry values, as well as the printers and output. In applications, a value for a non-existent variable name may remain without generating an error message. Such cases require explicit expectations and validation evidence.

Sources: [10] [11] [17]

How do Copies and Quantity settings function together in the Cloud Print Form?

The documented function multiplies Quantity by Copies. Thus, when Copies is 25 and Quantity is 4, a request for 100 labels is generated; a Quantity of 100 would theoretically result in 2,500. This is not a simple repetition of the same quantity field. Additionally, verify the form field limits and the actual behavior at elevated values; the described form has a limit of 1,000 labels per print.

Sources: [11]

Proves "Printed" that all labels are available?

No. After assistance, the status indicates successful transmission of the print job to the device. The physical output may differ. Accordingly, verify the actual quantity, readability, and usable inventory based on your process. In the example provided, 80 manufactured labels with five defects yield only 75 usable pieces, even though the software shows a successful transmission status.

Sources: [12] [19]

Can a complete order be simply restarted after an interruption?

A repeat requires clarity regarding the initial state. The status description "Restarting" includes resending the entire job. If acceptable labels are already available, an excess output may result. Compare existing output and reject batches and document the required additional volume. The required release or control depends on your specific process.

Sources: [12] [14] [19]

Does Loftware Cloud remain operational during an internet outage?

This depends on the client used and the locally available data. Automation can be configured in the Enterprise Edition with an enabled cache to continue printing upon task receipt if the task includes all variable data and no online source is required. The Web Client can leverage previously loaded applications and limited cached data. Desktop Designer and Print, however, do not have an offline cache for cloud-managed files. Cloud-triggered tasks require connectivity for new orders. Review your failover procedure and recovery to normal operations: offline capability does not guarantee access to up-to-date source data nor protection against duplicate printing.

Sources: [14] [17]

Do we need to retain pressure histories for a period of twelve years?

No. Up to twelve years is a stated feature of the Compliance Edition, not an absolute regulatory deadline. Define the retention purpose, required information, and retention period for your records. Additionally, verify actual logging, access, and export capabilities. Extended storage duration is of no benefit if critical parameter values or the link to a reprint are missing.

Sources: [13] [10] [18] [17]

Is a re-registration during the dossier release a Part 11 signature?

A single re-authentication alone does not constitute a Part 11-compliant electronic signature. First, determine the applicable FDA record-keeping and signature scope, and then assess the significance, function, and configuration within the specific process. The cloud support describes re-login as a feature; this does not demonstrate fulfillment of all regulatory and operational requirements associated with your usage.

Sources: [8] [20] [17]

Sources and review date

As of October 6, 2026. Supplier reference: Loftware-Cloud-Help with visible version 25.9 and NiceLabel 10.5 documentation and Patch 10.5.0.11126. These source versions do not constitute a statement regarding the most current available customer build. Editions, clients, and configurations must be verified separately. Regulatory focus: Human medicinal product GMP, Annex 11 and Chapter 4; Chapter 5 for the applicable packaging process. Examples and invoices are standalone reference materials, not executed print tests. Targeted source reconciliation on October 18, 2026: Loftware "Offline printing" to client, cache, local data, and cloud triggers.

  1. Loftware Licensing Policy – NiceLabel Cloud and Local Products
  2. Loftware Product Range Rebranding – Edition Comparison
  3. Loftware Cloud – Lifecycle Schedule
  4. NiceLabel 10.5 – Changes to the Local Product Portfolio
  5. NiceLabel 10.5.0.11126 Patch
  6. NiceLabel – Product Lifecycle Schedule
  7. Loftware Cloud – Workflows
  8. Loftware Cloud – Approval Process
  9. Loftware Cloud – Assign workflow steps
  10. Loftware Cloud – Creating and Sharing Applications
  11. Loftware Cloud Print Form
  12. Loftware Cloud – Job Statuses
  13. About Loftware Cloud Compliance
  14. Loftware – Offline printing
  15. Loftware Cloud – Cloud Integrations
  16. European Commission: EudraLex Volume 4
  17. EU GMP Annex 11: Computerised Systems, January 2011 revision
  18. EU GMP Chapter 4: Documentation, January 2011
  19. EU GMP Chapter 5: Production, Revision 2014/2015
  20. FDA: Part 11, Electronic Records; Electronic Signatures — Scope and Application

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Make the actual labeling route verifiable

We support you in linking the data source, template release, and physical distribution to a traceable inspection workflow and selecting relevant error and recurrence cases.

  • Cloud and SaaS validation →

    Maintain the validated state of cloud and SaaS systems as suppliers issue new versions. We define the boundary between your responsibilities and the supplier’s and agree how each release will be assessed.

Send a project enquiry Customer testimonials →