IT systems · Practical guide

Validating BarTender: from the approved layout to the correct label

A well-printed BarTender label can still identify the wrong batch or expiry date. Trace the approved template, source data, output and controlled reprint. The cases distinguish installed on-premises software from BarTender Cloud and identify the versions covered by the supplier documentation.

Table of contents

At a glance

How do you validate BarTender for GMP use?

Demonstrate that the configured labelling process is fit for its intended use. Test template revisions, data mapping, permissions, physical print output and exceptions, including reprints. The BarTender edition and configuration determine the technical controls available. An approved template or completed print job alone does not demonstrate that variable data were correct or the physical label was applied to the right item.

  • On-premises, cloud, edition, and release must be separately documented.
  • Release layout, source data, and actually used labeling require continuous documentation and traceability.
  • Retprints and reprocessing must not generate uncontrolled duplicate markings.
  • Logging, retention, and changes are part of routine operations.

Which BarTender variant is the subject of validation?

The manufacturer distinguishes on-premises editions Starter, Professional, Automation and Enterprise as well as the cloud plans Essentials, Automation and Enterprise. The same terms as "Automation" do not mean that installation, permissions or detection are identical. Therefore, you can collect product, edition, license scope, version number and actually used components together.

On October 6, 2026, the open release page for BarTender On-Premises 12.1.1 from September 2026 is referenced. The detailed function guide for Librarian, data sources, and print logging reviewed herein belongs to category 11.11. This separation is relevant: the function descriptions serve as a basis for your evaluation, not as a general approval for any future version or for the Cloud version.

In addition to the system architecture, it includes print servers, databases, local workstations, printers, drivers, and connected applications. For cloud or hybrid operations, further clarification is required regarding where templates, print data, and histories are stored and how interruptions are managed. BarTender Track & Trace is another product area; its functionalities are not assumed to be natively integrated as part of your labeling process.

Sources: [5] [6] [7] [10]

Separate label requirements and software functions clearly

The guide addresses labeling within the GMP manufacturing of human medicinal products. An internal warehouse label, a status indicator, and a print on the retail packaging serve distinct functions. First, clearly define which identity, decision, or labeling requirement depends on the label. A shipping sticker is not inherently a medicinal product identifier merely because it is printed using a specific printing software.

Annex 11 requires validation of the intended use and appropriate qualification of the supporting IT infrastructure. The current EU overview continues to reference the January 2011 version. Chapter 5 addresses, among other things, prevention of mix-ups and controls during filling and packaging operations. These requirements must be translated into specific processes; a manufacturer's statement of compliance does not substitute for this work.

The professionally acceptable label content is determined by your process and the relevant product specifications. Label printing software does not automatically verify the regulatory completeness of the content. Medical device labeling and serialization require additional, appropriate considerations. FDA Part 11 applies only to electronically recorded data and within the applicable FDA regulatory framework, not universally to every barcode.

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

Link the template revision to production approval

Help for Manufacturer 11.11 describes Librarian as central documentation and revision management. Changes are managed through check-out and check-in processes; revisions and editors remain traceable. Workflows can support review and batch release activities. The open Print Station Help document assigns Librarian to the Enterprise Edition. No identical functionality of a smaller edition or a cloud plan should be inferred.

For your validation, it is essential to determine which revision is actually printed. Describe the pathway from draft through technical review to productive selection. Also assess rejection, rework, and decommissioning. A version number alone does not constitute approval by the intended role.

Investigate potential alternative pathways: locally stored copies, obsolete network drives, or alternative print output devices. If bypassing the approved process is feasible, this option must be evaluated and controlled. A meaningful negative test involves printing a deprecated template using a standard operator role. Expected and handling of acceptable exceptions should be defined prior to execution.

Sources: [7] [8] [1]

Track variable data up to release

BarTender, according to version 11.11 help documentation, can utilize database fields, files, input forms, and named data sources. This enables a single layout to identify multiple products or batches. Here, a distinct validation scope arises: the correct template may display the wrong data set, misinterpret a date, or continue to use an outdated value.

Document for each critical field: origin, selection rule, allowable processing, and output format. Who determines the expiry date: the lead ERP, an approved calculation step, or manual entry? A date from the workstation clock is not automatically the professionally prescribed date. Verify erroneous values, multiple hits, truncated characters, and different date formats.

The following work aid represents an independent review plan, not a description of automated BarTender control checks. Even seemingly simple table imports require a clear mapping to the respective order. A successful database connection does not necessarily indicate adequate validation.

Work aid: Critical label data and appropriate error scenarios
Item under testExample: Test failure scenarioExpected result to define before testing
Articles and Batch Order and imported dataset belong to different batches. Detect deviation prior to use; no unverified labeling.
Expiry date Source provides 2027-03-04, the release swaps day and month. Play agreed date uniquely and unchanged in text and code.
Required field The batch number is missing or contains only spaces. Handle errors instead of retaining a previous or arbitrary standard value.
Quantity and unit Data source provides pieces; template expects cartons. The unit and, where appropriate, the conversion are clearly coordinated in a technical manner.
Dataset selection A search provides two matching lines. Unique selection or controlled rejection instead of random first match.

Sources: [9] [1]

Further reading:

Record printer, material, and barcode in the inspection.

The screen preview is only part of the traceability chain. Verify the printed label using the intended printer, material, and relevant settings. Changes in size, misalignment, inadequate print quality, or cut-off text may affect usability, even if the file remains unchanged. Document the relevant combinations for your process and justify any applied grouping.

For a barcode, separately verify content and readability. A scanner may read a code whose stored batch is still incorrect. Therefore, compare the actually decoded content against the independent expected value and the legible printed text. If a specific quality inspection of the code is required, establish the procedure separately; a single successful scan does not automatically substitute the required verification.

On-site usage considerations: Which printer is assigned to the line? How are leftover labels and roll changes managed? How is it ensured that the correct label is applied to the right product? Chapter 5 covers the packaging process including print checks. Therefore, the review does not end with the Windows print status. Software validation and appropriate testing of the printing equipment must be aligned.

Sources: [3] [1] [6]

Secure reprocessing and retry against double labeling identification

A reprint may be required when a label is damaged. It may simultaneously generate additional identical labels. Therefore, define who is authorized to perform reprints, the allowable quantity, and how the reprint remains traceable to the original order. The handling of damaged or excess labels should be part of the same process.

Section 11.11 describes configurable settings for the storage of post-print relevant data as well as copies of documents and associated images. A comment may be requested during printing through the described interfaces. These options must be configured and aligned with the specific edition scope. A comment does not constitute professional approval, and a stored document copy does not serve as evidence of consumed labels.

Also verify the retry: connection interrupted, order accepted, no feedback. A retransmission must not be unreviewed and treated as the first print. Define how operators shall determine the actually achieved state. This applies particularly to interfaces, queues, and backup printers. Whether an automatic retry is appropriate depends on the verified behavior of your entire print chain.

Sources: [10] [3] [1]

Which history must actually be available later

Historical records, print job logs, and change histories address distinct questions. The first supports batch preparation, the second supports traceability during print events. For evaluating a defective batch, additional critical insight may be provided by identifying the source data used and whether post hoc changes are traceable. Establish this required linkage, rather than merely noting "Audit trail available."

The print logging in Help 11.11 is configurable. Separate options are provided to determine whether print-relevant data, document copies, or images of individual print positions are stored. Review a representative order based on the actually stored information. A stored image may support the generated representation, but it does not prove the state of the physical label.

Database maintenance may involve deleting or archiving older protocols. Therefore, align settings with the required retention requirements. Verify access, readability, and recoverability, including necessary relationships. A backup and a long-term understandable archive serve distinct functions. Additionally, determine which quality-related changes or exceptions are reviewed and identify who conducts the review.

Sources: [10] [12] [11] [1]

Test example: Correct layout, incorrect expiration date

This example is not a completed product test. A pharmaceutical company prints internal labels for packaging. The approved template is correct, but a data query incorrectly assigns the expiration date of one batch to another batch. A simple visual inspection of the layout would not reveal the root cause.

For test planning, the following serves as an independent input: Batch TEST-A has the date 4 March 2027, and Batch TEST-B has the date 30 November 2027. The data originate from a controlled test source. The expected release is determined prior to printing; it is not derived from the same query being currently assessed.

A follow-up scenario is planned: Out of 100 issued labels, three are demonstrably nonusable. Three approved replacement labels result in 103 physically produced labels, but only 100 labels are intended for use. The operation determines how the approval, reprinting, and actual usage are documented for its process.

Example: Test matrix for data assignment and reprinting
TestPrerequisite and ActionExpected result
Normal case Select TEST-A; compare text and decoded barcode. Both contain the approved identity and the defined date.
Confused source For TEST-A intentionally provide the TEST-B dataset. The specified control detects a deviation prior to use.
Empty date Remove date from test source. Expected error response; no uncontrolled access to old values.
Old Revision An operator attempts to use a superseded template. The defined release process permits no unauthorized use.
Replacement print run Three unusable labels are documented and three replacement labels are requested. Authorization, quantity, and order reference are traceable; no additional usable labels are available.
Unclear communication Interrupt the connection after acceptance of the order. Status controlled and verified; repetition does not generate unnoticed duplicates.

Sources: [1] [9] [3] [10]

Plan small team changes and effort realistically and manageably

The main drivers of effort are primarily the number of distinct templates, data sources, print pathways, and exceptions. Ten variations from the same controlled data logic may require different handling compared to two templates with independent calculations. Grouping requires a clear, justifiable rationale and representative validation; the mere number of files is not decisive.

QA or the responsible function defines required contents and release criteria. Production covers printing, rejects, and re-run activities. IT documents components, access, and backup procedures. The implementation partner provides details on configuration and interfaces. Approved sample data, available printing equipment, and time for joint acceptance inspections are required. Manufacturer certificates may be utilized if they align with the actual scope.

Assess the impact of changes to layout, data query, drivers, printers, and software. The current Release Notes 12.1 include, for example, modifications to print interfaces and print position control. This necessitates a targeted evaluation of affected workflows, without automatically re-running every template. Maintain traceability of version status, selected regression tests, and open deviations following updates.

Sources: [6] [1]

Further reading:

Checklist for the Start of BarTender Validation

Prepare the evaluation using a real process run and controlled test data. The following list serves as a guidance document for your intended use. It neither replaces the definition of label content nor constitutes a justified decision regarding existing evidence.

  • Product, edition, release, and on-premises, cloud, or hybrid operation are documented.
  • Label type, intended use, and professionally responsible release are defined.
  • Template revision, batch release, and possible local copies are considered.
  • Critical data have definitive sources, selection rules, and release formats.
  • Printer, material, charge content, and actual label usage are included in the inspection scope.
  • Out-of-specification values, incorrect assignments, and alternative printing paths are reviewed.
  • Retprints, audits, and unclear feedback have impacted controlled procedures.
  • Stored histories align with investigation, retention, and restoration.
  • Rotations, exceptions, and quality-related reviews are governed.
  • Changes and regression testing are associated with ongoing operations.

Sources: [1] [3]

Project experience and collaboration

Link source data, label template and printed label

More than the template can change between approval of a label layout and printing. With your owners, we trace variable source data, the print job and evidence of the version used. A specific label change may permit a narrow scope. For a new labelling process, IT and process owners establish approvals and handovers first. The tests check whether the agreed relationship between data, template and printed label is preserved.

Frequently asked questions about BarTender

Does every label printed with BarTender require a GMP validation?

No. The key factor is whether the labeling process is GMP-related, for example, because the label carries information on material identity, status, or quality-related product information. In such cases, the required functions and controls for this specific application are defined and validated. An internal organizational label without such a connection does not justify the same level of scrutiny solely based on the software used.

Sources: [1] [3]

Must we exclusively use BarTender Enterprise for GMP compliance?

The regulatory framework does not specify a particular edition. Appropriate controls must be implemented to meet your requirements. The open vendor guidance assigns Librarian to the Enterprise edition; therefore, other editions cannot be described with the same functionalities. Compare required template controls, roles, and histories against the actual feature scope provided. If any required control is missing, a suitable alternative solution must be demonstrated.

Sources: [8] [5] [1]

Can our desktop validation remain valid for BarTender Cloud?

Not without evaluation of the changed environment. When transitioning to BarTender Cloud, assess data retention, print path, user management, updates, and responsibilities. From this, determine which existing justifications remain valid and which require new validation. A visually identical label does not imply identical operational environments. Assign the specific Cloud implementation plan and its documentation to historical records, retention policies, and failure response procedures; desktop settings do not constitute valid Cloud functionality evidence.

Sources: [5] [6] [1]

Does the release of a template in Librarian suffice?

It covers only the specifically defined portion of the workflow. Additionally, the data assignment, version used, print configuration, and actual output must match. Verify whether operators can access outdated copies via alternative paths. A meaningful release review links the released template to a known dataset and the resulting label. The workflow status alone does not confirm a correct batch.

Sources: [7] [9] [1]

How do we verify an expiry date from SAP or a CSV file?

Track a uniquely identifiable test dataset from the released source through audit trail to clarity and, if applicable, code. Additionally, verify incorrect mappings, missing values, and inconsistent date representations. Expected values must be independently defined. If calculations are involved, their rules and edge cases must also be included. A functional connection and a plausible-looking date are insufficient as evidence of correct mapping.

Sources: [9] [1]

Is a successful scan evidence of a correct barcode?

He confirms initially that the scanner could read the specific printed output. Compare the decoded content against the technical specification and the clear print. Depending on the required standard and intended use, further quality verification may be necessary. These should be defined separately. A legible code may still contain incorrect identity or date information.

Sources: [3] [1]

How do we prevent uncontrolled duplicates during reprinting?

Associate authorization, rationale, quantity, and origin order with the handling of defective labels. Additionally, assess the action taken in the event of missing print confirmation. The described BarTender options can store reprint data and comments; they do not replace a predefined decision on replacement quantities. Test the actual reprocessing including interface and printer functionality before automatic reprints are considered controlled.

Sources: [10] [3] [1]

Does the pressure history suffice as an audit trail?

A print history is not sufficient proof of changes for templates and source data. Print events, template revisions, and modifications to source data are not equivalent. Define which linkage you will require later for an investigation. Verify the actually activated logging and readable availability. A general manufacturer feature "Audit Trail" does not address your specific configuration or the required review.

Sources: [10] [7] [1]

Must we retest all labels following a printer replacement?

Assess the impact of the change: printing method, dissolution, drivers, materials, dimensions, and used codes. From this, determine the appropriate testing scope. A justified selection of representative and critical reference samples can be beneficial. Simple model similarity is insufficient as a justification. Document which attributes remain unchanged, which new risks have emerged, and which actual expressions were evaluated.

Sources: [3] [1]

What preparations reduce the duration of a BarTender validation?

Useful are a structured template list, clear data sources, pre-approved required contents, and known print pathways. Provide test printers, materials, and responsible personnel from QA, Production, and IT. Pre-define the reprint process and existing manufacturer certifications. Unclear sources and approvals often lead to excessive coordination compared to the mere test execution; therefore, reliable time estimates require a clearly defined and limited scope.

Sources: [1] [9]

Sources and review date

Sources of manufacturers and authorities were opened on 6 October 2026. Current release notes concern BarTender On-Premises 12.1/12.1.1; detailed functional documents are from the manufacturer's help 11.11 and have to be compared separately for other stands or cloud. Tables and test examples are own test aids, no executed tests.

  1. EU GMP Annex 11: Computerised Systems
  2. European Commission: EudraLex Volume 4
  3. EU GMP Chapter 5: Production
  4. FDA: Part 11, Electronic Records; Electronic Signatures – Scope and Application
  5. Seagull Software: BarTender Editions and Features
  6. Seagull Software: BarTender On-Premises 12.1 / 12.1.1 Release Notes
  7. BarTender Help 11.11: Librarian
  8. BarTender Help 11.11: Using Librarian with Print Station
  9. BarTender Help 11.11: Data Sources Pane
  10. BarTender Help 11.11: Print Job Logging Page
  11. BarTender Help 11.11: System Database
  12. BarTender Help 11.11: Performing Database Maintenance

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Data source, template, and label to be jointly evaluated

Daniel Herrmann Consulting supports you in defining the GxP scope of your labeling activities and linking existing controls to the required validation evidence.

  • 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.

Send a project enquiry Customer testimonials →