Table of contents
At a glance
How do you test controlled label reprints in BarTender?
Check which template, data and quantity a BarTender reprint actually uses. Link the reprint to an authorised person and documented reason. Include printer interruptions and any labels already produced. A stored print job does not establish the number of correct physical labels present.
Scope and Applicability
BarTender features such as logging or template management depend on edition and configuration. This article outlines evaluation criteria, not a guarantee that every installation includes all required controls.
Digital order and physical label must be consistent.
For a reprint, two questions must be answered: What content is permissible, and how many additional labels are actually required? Both aspects are part of the order release. The following sections address data origin, print log, and physical inventory verification.
Consider reprint as a quality-relevant activity
A reprint is not merely the repetition of a print instruction. Clarify why reprinting is necessary, which original labels are being replaced, and how mix-ups or dual usage are prevented. A visually correct label may still end up on the wrong batch or remain available in an unauthorized additional quantity.
Capture BarTender version, edition, label template, data source, printer, and actually used logging. Manufacturer documentation describes configurable print job logging. It must be separately verified whether the required data are available and accessible for an adequate duration in your operation. The presence of an activated logging switch does not constitute evidence of complete print traceback capability.
Define the technical scope of the reprint. Should the data status be used again or a currently corrected status be printed? Both cases may be justified, but are to be documented differently. A reprint from today's master data can create a different label than the original order.
Link data, documents, and print quantities unambiguously
A print audit trail should enable the required linkage between order, label, data status, and quantity. The information required depends on the label and process. A simple file name may be insufficient if the label has been overwritten. A mere printer identifier does not specify which batch was actually labeled.
Also assess variable data, continuous identifiers, and alternative inputs. If a user can modify values in the reprint dialog, the validity of such modifications must be evaluated. The control must align with the actual workflow. A locked template field provides limited value when the same information is imported from an uncontrolled alternative source.
| Area requiring evidence | Question to investigate | Purpose |
|---|---|---|
| Original order | Which pressure is being replaced? | Compound instead of unclear additional production |
| Template | Which released version was used? | Proper Design and Logic |
| Data | Historical or corrected version? | Legible label statement |
| Quantity | How many additional labels are generated? | Label availability check |
| Use | What happens to damaged or replaced labels? | Address mistaken identity and duplicate use |
| Authority | Who may request a reprint? | Limited and traceable access |
Example: Retract after modification of an expiration date
Order D-14 prints 100 labels for Batch C-14. Ten labels are damaged. Temporarily, a date field within the system has been modified. A reprint of ten labels must now clearly establish which data version is technically correct. "Reprint" does not automatically imply "identical historical content."
Prepare the original instruction with known data. Then modify the relevant field in the controlled test environment. Perform the intended reprocessing route and compare content, quantity, and traceability. The expected rule shall be predefined prior to execution. Document whether historical values, current values, or an authorized correction are to be used.
Include an unauthorized reprint attempt and a discrepancy in quantity. Also verify whether a terminated print job could have generated physical labels. A technical error status is not automatically equivalent to zero usable labels. Handling of partial quantities must align with the actual printing process.
| Test case | Action | Expected finding |
|---|---|---|
| Original print run | Generate 100 labels with known position. | Correct content and traceable instruction |
| Historical Reprint | Request ten items following data modification. | Selected data snapshot rule applies |
| Quantity discrepancy | Attempt to use a greater quantity than justified | Selected quantity and authorization control applies |
| Unauthorized access | Attempt a reprint with a role that lacks permission | Authority limit remains valid |
| Partial breakage | Pressure controlled interruption | Physical quantities and open quantities arising are investigated and clarified. |
| Repetition | Restart an order whose outcome is uncertain | No unexplained additional label quantity |
Assess the print record and physical labels jointly
A software log records a technical process step. It alone does not prove which labels were physically issued, rejected, or used. Therefore, a reconciliation between order quantity, actual on-hand quantity, and further usage must be performed. The level of detail required depends on the potential for mislabeling and process criticality.
Consider printer errors, paper changes, queue delays, and user re-submissions. A user may resubmit a job multiple times because the output appears delayed. Investigate appropriate cases where technical feedback and physical results diverge. The appropriate control may incorporate both organizational and technical components.
You can also regulate damaged, replaced or unused labels. EU-GMP Chapter 5 No. 5.62 expects batch-coded packaging to be destroyed and recorded after completion of the packaging process. Significant or unusual volume deviations must be investigated and satisfactorily clarified before release (5.61). The practical implementation is specified in your procedure. Labels outside this GMP packaging process require their own classification.
Logging, permissions, and retention practically verified
Check which print data is actually stored and whether they can explain a named job later. Configuration, database availability and edition can affect the scope. An existing log table is weak if template level or variable content are not reconstructable, although these are required for your decision.
Assess the impact of logging failure, to the extent it is relevant in operation. If processing continues, the selected protocol must explain how the required evidence remains obtainable. A failed logging database must not inadvertently create the false appearance of a fully documented operation. An appropriate response shall be risk-based.
Limit template modification and reprint rights in accordance with assigned responsibilities. A standard Windows login does not address all application authorizations. Evaluate alternative entry paths and technical print integrations. An integration account may trigger the same print process and should therefore be included in the control model.
Control changes to the template and data source
A changed font size may affect readability or barcode verification. A new data source may alter the correct batch assignment. Therefore, evaluate changes based on their impact, not merely on visual appearance. A visually minor modification can be quality-related if it truncates an identifier or adopts an incorrect value.
For regression testing, known label data, variable length limits, barcode content, and reprint pathways are suitable. Compare actual output against the required machine-readable information. A screen preview does not substitute for physical verification on the actual printer and material. Transferability must be justified for your specific application.
Provide approved template, reprint rules, roles, and audit trail access. The internal team should be able to trace a later-identified print job back to the version in use at the time. This ensures label batch records are investigable, rather than merely being obscured by a subsequent reprint.
Draft: Print instruction, physical quantity, and reason for reprint are linked
For a reprint, run a short volume and content file. In the example, 100 labels have been created and ten of them have been damaged. The new order is intended to replace the justified quantity without making any unclear additional use possible. Write down the handling of original labels according to your procedure.
Link the file to the corresponding work order and test records. This enables a reviewer to trace the decision rationale without having to reconstruct the process from separate documents. The table shows which information items belong together.
If there is a difference, the actual situation will be clarified first. Another emphasis is not automatically the correct correction. Check whether labels have already been used and which data are affected. The conclusion combines technical job and physical process, instead of just recording the last successful message.
| Evidence item | Example entry | Control question |
|---|---|---|
| Origin | Order D-14 with 100 labels. | Is the previous pressure clearly linked? |
| reason | Ten damaged labels. | Is the additional amount substantiated from a technical and scientific perspective? |
| Data version | Historical or approved amended content. | What statement should the reprint convey? |
| Template | Specified approved version. | Is the correct design used? |
| Subset | Actual quantity issued upon termination. | Is there no unresolved duplicate quantity? |
| Closure | Use and handling of replacement labels. | Is the overall process traceable? |
Next steps
- Define template, data source, and quantity responsibility.
- Test normal printing and controlled reprinting.
- Test disruptions, partial datasets, and altered data states as counterexamples.
- Document logging, physical control and release together.
Project experience and collaboration
Control label reprinting after an interrupted print job
After printing stops unexpectedly, which labels already exist and which may be printed again? We walk through the incident with line staff and IT, comparing the template, source data, order and quantities actually printed. We use this to define reprint and reconciliation tests. A documented reason for reprinting and quantity reconciliation may suffice for a limited workflow. Multiple printing routes or changing data sources call for assessment of the whole control process. The choice depends on your labelling operation.
Frequent Questions on Labels and Retouching
Does a pressure protocol suffice as a fill quantity record?
Must the barcode also be scanned?
Can the current draft for an old order be used?
Is every reprint from the old print order automatically identical?
No, not automatically. The reprint may draw upon historical values or current data sources, depending on the method used. Additionally, verify the template version, variable identifiers, and print quantity. Define the subject-matter expected values and test them with a targeted data modification between the original and reprint.
Does the alert "Pressure failure" justify a complete system restart?
Not automatically. Part of the labels can already have been created physically. Determine actual quantity, usability and further handling before additional labels are created. The restart should fit into the concrete printing process and leave no unexplained multiple quantity or conflicting identifiers.
Should we test labels only in the screen preview?
The preview supports design but does not confirm any actual printability or readability. Consider the printer, material, and machine-readable content used, as applicable. A correct screen display may be cropped or inadequately readable in the output. The evaluation is based on the intended use.
Why is the original print reference important during reprinting?
It links the basis, data status, and additional volume to the replaced process. Without this reference, a reprint may appear as an independent new request. Verify that the required relationship is maintained during data modifications, partial system failure, and repetition.
Sources and review date
The sources provide the technical foundation. Tables, checklists, and examples are derived methodological tools, not verbatim regulatory requirements. Manufacturer information must be referenced to the specific version and configuration in use.
- European Commission: EU GMP Annex 11, Computerised Systems (2011)Current version as per EudraLex inventory as of 14.10.2026. Application, risks, operation, and data lifecycle; specific testing proposals are derived independently.
- Seagull Scientific: BarTender Print Job LoggingSupplier source for product functionalities. Availability and behavior depend on version, edition, license, and configuration; no general compliance certification.
- European Commission: EU-GMP Chapter 5 – Production, valid since March 2015Targeted original comparison on 18 October 2026: No. 5.61 and 5.62 for batch-coded packaging materials. Other regulatory areas to be separately categorized.
Sources checked: .
Define reprint rules for BarTender
We support you in assessing the current situation, clarifying responsibilities, and implementing appropriate evidence within operations. The type of support that is most effective depends on your system, your team, and the specific objective.
- Computer system validation →
Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

