The label belongs to the record.

Generate labels from selected record versions, verify their application and reconcile every print run in Seal. Keep reprints, destruction and unresolved quantities visible.

Explore this workflow
Illustration of a seal following a reagent container from storage through identity scanning.

Can this print run be closed?

The run printed 120 labels. Application and destruction records account for 119. One label still needs a disposition.

Print run PR-120

120 labels

Example records. Select a row to inspect its source.

Unaccounted

PR-120-U
Printed
120
Accounted
119
Unresolved
1

120 printed minus 116 applied minus 3 destroyed leaves 1 label unresolved. No return, destruction or application event accounts for it in this example.

What follows

Investigate and record the remaining label’s disposition before closing this reconciliation.

Run the work in Seal.

Select the source.

Choose the record, template version and intended use. Preview identifiers, dates, units and barcode content before printing.

Verify the application.

Capture the print event and confirm that the physical label is applied to the intended container, sample or product.

Close the print run.

Reconcile used, spoiled, returned and otherwise disposed labels. Record the reason and authorisation for any reprint.

Write the handover for the unfinished label run.
neil

One of 120 labels has no disposition. I can prepare the handover with the applied and destroyed counts attached, but the reconciliation stays open.

Every label has a source and a destination.

Reprints keep their reason.

A replacement label is a new controlled print event, not a second invisible copy.

Link the reprint to the original event, identify the reason and quantity, and account for the original label. The workflow should distinguish damaged-label replacement from a change to the underlying record.

Templates and printers stay in scope.

Test the actual label stock, device, layout and scan path used on the floor.

Verify that barcodes resolve to the expected record and that required information remains legible. Where specialised labeling or serialization systems remain in use, scope the interface and responsibility for print, verification and reconciliation.

One record, the appropriate label.

Select the controlled artwork, language and required content for the item and intended use.

Carry sample identity, material lot, equipment reference or batch details from their source records. Keep template approval and effective version with the print event. A change to the source or artwork needs an explicit decision about labels already printed or applied.

Scan at the handoff.

Connect the physical item to its record when it is dispensed, sampled, stored or transferred.

Configure the expected item and destination for each scan. Record mismatches and correction history, not only successful matches. QR or barcode content should resolve to the intended identity and respect access permissions; a readable code alone does not prove correct application.

Connected to the surrounding work.

Sample managementWeigh & dispensePackaging line clearance

Keep specialised systems where they belong. Agree the source of each record, the permitted actions and the reconciliation at each handoff.

Explore integrations

Before you get started.

No. Agree which system owns templates, print events and application verification. Seal can support the connected workflow; the integration must preserve identities and event reconciliation.
No. Printing and applying are separate events. Configure the verification needed to connect the physical item to the intended record.
Not by itself. Market-specific serialization and reporting need their own scope, interfaces and verification. This example concerns print-run accountability.

Try it with your own work.

Bring a label template, representative records and one print-run reconciliation.

Book a demo