Label Issuance
Label Issuance is the controlled authorisation and transfer of identified labels from approved stock or a verified print run to a particular manufacturing job, with actual quantities, custody and issue evidence.

On this page · 12 sections
- 1Label Issuance
- 2Issuance versus neighbouring label records
- 3From authorised request to receiving custody
- 4A label issue ledger that preserves the handoff
- 5LI-260: a supplemental issue with an unresolved count
- 6A partial roll returned and reissued at the same revision
- 7Overprinted excess that never became an issue
- 8Which product and jurisdiction govern the decision?
- 9Connect records without losing transaction identity
- 10Find custody failures before they become count disputes
- 11Cancel or redirect an issue without inventing a return
- 12A practical implementation and review checklist
How does Label Issuance apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01Label Issuance
Label Issuance is the controlled authorisation and transfer of identified label material to a particular manufacturing job, with actual quantities, custody and evidence of receipt recorded. Also called labeling issuance, it concerns the labels handed over—not merely the quantity requested.
What changes when labels are issued?
In the illustrative manufacturing process used here, labels originate from approved stock or a verified print run. Issuance establishes their job-specific custody without becoming a printing instruction. A useful issue record answers:
- Which label identity and revision were transferred?
- Which manufacturing job received them?
- How many actual label units moved, and on what counting basis?
- Who issued them, and who received custody?
- When did the handoff occur, and what evidence records receipt?
Authorisation permits the issue; the physical handoff changes custody. A request, reservation or planned quantity alone does not establish that labels moved. Receipt evidence connects the authorised transaction to the receiving operator, making the chain of custody traceable rather than inferred from a stock deduction.
The unit of control is label material, not the finished device, artwork-development process or product-release decision. Linking the issue to the batch execution history places that material transfer in its manufacturing context without treating receipt as proof of application or acceptance.
02Issuance versus neighbouring label records
Label issuance is the authorised transfer of identified label material, in an actual quantity, into custody for a particular manufacturing job. These operational record boundaries vary by site.
| Activity | Decision answered | Characteristic record | Relationship to issuance |
|---|---|---|---|
| Label identity and artwork control | Which label and revision? | Approved specification and artwork | Establishes the identity to issue. |
| Print-run verification | Does this output match its specification? | Print-run inspection record | Supports eligibility, not transfer. |
| Stock reservation | What stock is allocated? | Reservation against a job | Expresses intent, not actual custody. |
| Label issuance | What changed hands, to whom, for which job? | Authorised transfer with identified material, actual quantity and custody evidence | Records the handoff itself. |
| Label application | Where was the label used? | Application record | Documents use after transfer. |
| Label Reconciliation and closeout | How are quantities accounted for? | Reconciliation and closeout record | Uses issuance as an input. |
Label reconciliation concerns downstream quantity accounting and closeout, using the issue history as an input. UDI assignment, label-content design and printing technique remain outside this article: their outputs inform the identity being issued. A material consumption posting alone does not establish the custody handoff.
04A label issue ledger that preserves the handoff
A label issue ledger preserves linked custody transactions, not one editable issued-quantity cell. The illustrative site design below records each handoff separately; it is not a prescribed legal form. Its process event log retains original entries and links subsequent movements, corrections and review decisions.
| Transaction and event time | Movement type | Job and label identity | Actual quantity and count basis | Issuing and receiving custody | Evidence references | Exception and review state |
|---|---|---|---|---|---|---|
| Unique ID; handoff time | Original issue | Receiving job; item/revision/lot | Labels transferred; counting method | Stock issuer → receiving operator | Count record; receipt event | Transfer recorded; review pending |
| New ID; additional handoff time | Supplemental issue | Same job; actual item/revision/lot | Additional labels only; counting method | Issuer → receiving operator | Supplemental authorisation; count; receipt | Reason recorded; exception linked |
| New ID; return time | Return receipt | Originating job; returned identity | Labels received; recount method | Operator → return custodian | Originating issue; return receipt | Eligibility pending |
| New ID; new handoff time | Reissue | Receiving job; same revision | Eligible labels transferred; count method | Stock custodian → receiving operator | Accepted return; new receipt | Eligibility decision linked |
| New ID; correction time | Correction | Affected job; unchanged identity | Corrected value; supporting basis | No movement unless separately recorded | Original entry; correction reason | Correction review recorded |
| New ID; disposition time | Disposition | Related job; affected identity | Labels affected; count method | Current custodian → documented destination | Disposition decision; execution evidence | Decision and completion distinguished |
Underlying fields are transaction_id, parent_transaction_id, job_id, label_item_id, revision, label_lot_id, carrier_id, quantity_labels, count_basis, from_custodian, to_custodian, event_time and evidence_ids. Record named people or identified custody roles, not an ambiguous department handoff.
A carrier identifier locates the roll, sheet pack or container. It does not establish how many usable label units remain; count_basis explains how quantity_labels was determined.
Keep gross issue history visible after returns, as distinguished in net-versus-gross reconciliation. Link each return to its originating issue and each reissue to eligible returned stock. Neither transaction rewrites either job’s earlier history.
Keep counting, receipt, application, destruction and review evidence separate. Each reference identifies the particular record or event supporting the entry, not merely a folder. Receipt evidence establishes a handoff; it does not establish application or destruction.
Physical location, stock eligibility and QA review state remain distinct attributes. Counted material can remain on hold; a completed transfer can still belong to a job with an unresolved exception.
Issue-to-evidence model
These identifiers let a reviewer navigate from the job to individual transactions, follow their relationships, and retrieve the evidence supporting each event without treating one document as proof of everything.
Manufacturing job
Receives multiple linked custody transactions.
- job_id
- product_id
- required_label_revision
- authorisation_ref
- job_state
Label stock
Preserves identity through carrier splits.
- stock_id
- label_item_id
- revision
- label_lot_id
- carrier_id
- parent_carrier_id
- overprint_status
Custody transaction
Connects the movement and its actors.
- transaction_id
- parent_transaction_id
- job_id
- stock_id
- transaction_type
- quantity_labels
- count_basis
- from_custodian
- to_custodian
- event_time
- evidence_ids
Evidence record
Supports a particular recorded event.
- evidence_id
- transaction_id
- evidence_type
- record_ref
- recorded_by
Review decision
Records assessment separately from movement.
- review_id
- job_id
- transaction_ids
- exception_id
- qa_reviewer
- qa_signoff_state
- decision_time
05LI-260: a supplemental issue with an unresolved count
LI-260 is a hypothetical device-site label issue ledger for job WO-L260, using label item UL-L260, revision C. The unit throughout is one individually counted unit label, not a roll, device or printed sheet. ISS-A is the issuer, OP-B the receiving operator and QA-C the QA reviewer. These illustrative site roles, ledger entries and review states do not establish legal form or signature requirements.
Assume the labels are eligible for the initial issue and that each transfer uses direct individual counting. Each transaction carries the job, label identity and revision explicitly; it does not rely on the previous row to supply them. Evidence references connect the recorded count to the physical handoff.
| Time and transaction | Job and label | Quantity and custody event | Evidence and authorisation |
|---|---|---|---|
| 08:10 — ISS-L260-01 | WO-L260; UL-L260, revision C | 1200 labels; ISS-A transfers to OP-B | Initial authorised issue; direct individual count COUNT-L260-01; receipt RECEIPT-L260-01 |
| 10:25 — ISS-L260-02 | WO-L260; UL-L260, revision C | 80 additional labels; ISS-A transfers to OP-B | Separate supplemental authorisation linked to ISS-L260-01; direct individual count COUNT-L260-02; receipt RECEIPT-L260-02 |
| 13:35 — RET-L260-01 | WO-L260; UL-L260, revision C | 40 unused, unoverprinted labels; OP-B hands to ISS-A into return hold | RETURN-L260-01 records count, condition and receiving custody |
| 13:40 — DSP-L260-01 | WO-L260; UL-L260, revision C | 20 loose labels documented destroyed | DESTRUCTION-L260-01 supports completed disposition, not merely an instruction to destroy |
The supplemental issue increases gross issued quantity to 1280 labels. It does not replace the initial issue with an edited total: both transfers retain their own authorisation, count and receipt evidence. This lets QA-C identify which handoff supplied the additional material without reconstructing an overwritten entry.
RET-L260-01 records physical receipt into return hold, not restoration of stock eligibility. The ledger preserves the gross issue history while recording where those unused labels went. Likewise, DSP-L260-01 points to evidence of completed destruction; a pending destruction request would not support the same accounting status.
The snapshot is not signed off
At 14:00, APPLICATION-L260-01 supports 1210 applied labels: 1195 on accepted devices, 10 on held devices and 5 on sample devices. All remain applied labels regardless of device status. A held device does not turn its attached label into unused stock, and a sample device does not make its label disappear from the issue account.
- Applied: 1195 + 10 + 5 = 1210 labels.
- Accounted: 1210 + 40 + 20 = 1270 labels.
- Unexplained: 1280 - 1270 = 10 labels.
QA-C records NOT SIGNED OFF, with investigation INV-L260 open. This is the site's illustrative review decision for this unresolved account, not a universal legal zero-variance threshold. It neither accepts the unexplained loss nor establishes product release. The investigation links to the individual transactions rather than replacing their evidence with a balancing adjustment.
A later finding adds evidence
Later, OP-B finds 10 loose labels in a segregated tray at the labeling station. FOUND-L260-01 records the finding time, exact location, direct individual count, job and label identity, and OP-B's custody of the labels in identified hold. It links to INV-L260 without rewriting the 14:00 snapshot.
The newly identified tray becomes another location in INV-L260; QA-C can now inspect its count and identity evidence alongside the earlier transactions. A disposition code can describe the eventual outcome; it cannot substitute for evidence that the action occurred. QA-C's earlier state remains part of the history, with any later review recorded separately.
06A partial roll returned and reissued at the same revision
Assume a hypothetical site permits returned labels to be assessed for reuse. Job WO-R41 returns 320 directly counted, unoverprinted unit labels of item UL-R, revision D, on carrier R-41. Receiving job WO-R42 calls for that same identity and revision. These assumptions establish a candidate for assessment, not permission to move the roll straight to the next line.
Create a linked return transaction recording WO-R41’s outgoing custody and the stock custodian’s receipt into return hold. Preserve the original issue reference, carrier R-41, label identity and revision, quantity in label units, direct-count basis, both participants, and each handoff’s event time. Attach the return count sheet and condition evidence to that transaction. Record the physical hold location so the ledger identifies where the remnant actually sits, rather than merely removing it from WO-R41.
Use the assessment record to decide the remnant’s next status. In this example, the site’s designated reviewer assesses identity, condition, exposure during line use and storage, traceable origin, absence of overprinting, and conformity with WO-R42’s specification. Matching revision D alone does not resolve those questions. Record the decision and its supporting evidence before changing the stock status to eligible. This separates the physical return from the restocking decision; an unresolved assessment leaves the material in hold.
After the hypothetical acceptance decision, create a new issue of 200 labels to WO-R42. Identify the issued portion as carrier R-41-B and the retained portion as R-41-A, both linked to parent carrier R-41. Record each child’s quantity and location, plus the new issue’s issuer, receiving operator, event time and evidence reference. Preserve this carrier lineage without leaving the parent available as another undivided stock quantity.
The stock arithmetic is 320 returned and accepted − 200 reissued = 120 labels remaining on R-41-A. Return and reissue remain separate movements, not a net correction to either job. This prevents a partial roll reaching another line while its records still identify WO-R41 or an undivided R-41 carrier.
07Overprinted excess that never became an issue
Assume a hypothetical device-site print run for WO-P73 produces 240 verified unit labels carrying job-specific lot text. The printer custodian transfers 210 labels to the receiving operator; 30 remain under printer custody. Record 240 as print-run output and 210 as the actual issue. The issue entry identifies both people and the handoff time: completing the print run does not establish receipt by the operator.
Later, the operator returns 12 unused overprinted labels from the issued material to a separately identified hold location. Preserve the original issue of 210 and add a return transaction for 12; do not overwrite the issue with a net quantity. The hypothetical evidence references distinguish the two custody origins:
| Held group | Label units | Custody origin | Evidence reference | Hold location |
|---|---|---|---|---|
| Unissued print excess | 30 | Printer custodian; never transferred | P73-EXCESS | Printer hold PH-P73 |
| Returned after issue | 12 | Receiving operator; previously issued to WO-P73 | P73-RETURN | Return hold RH-P73 |
The held total is 30 + 12 = 42 overprinted labels. Only 12 are a return from the job; the other 30 were never issued. Calling all 42 a job return would falsely attribute printer-held material to the operator. Keep the chain of custody tied to each group rather than replacing their histories with the combined hold total.
Neither group enters reusable stock in this workflow. The returns quarantine location records receipt into hold, not acceptance for reuse. Disposition remains pending until the applicable site decision is recorded. A shared disposition decision can reference both groups without merging their origins. For the product-specific legal question, see Which product and jurisdiction govern the decision? This device example is not permission for drug-product returns.
08Which product and jurisdiction govern the decision?
Choose the applicable product regime before deciding whether labels can move back into eligible stock. The custody ledger is a site-defined record pattern, not permission to reuse material across products or markets.
| Product and jurisdiction | Reference and status | Custody decision needing a scope check |
|---|---|---|
| US drug products | 21 CFR Part 211; the archival § 211.125 reference is the 2024 edition, not present-day legal clearance. | Check the current text of 21 CFR 211.125 for scope and the distinct treatment of issuance, excess bearing lot or control numbers, returned-stock storage and reconciliation. |
| US medical-device operations | 21 CFR Part 820; device-specific regulatory reference. | Check current Part 820 and § 820.45 for applicable labeling controls before defining stock eligibility and handoff approvals. |
| US medical-device manufacturers participating in MDSAP | FDA’s MDSAP Audit Approach; audit guidance. | Check how control-numbering procedures connect the label identity to the custody record. |
| US dietary-supplement operations | Product-specific packaging and labeling scope. | Keep operational detail with supplement packaging and labeling, rather than borrowing drug-product rules. |
| Food, chemicals and other markets | Custody-record practice only. | Assess product-specific applicability separately before adopting return, reissue or disposition rules. |
For US medical-device manufacturers participating in MDSAP, FDA’s MDSAP Audit Approach describes written control-numbering procedures as a common traceability element. This is audit guidance, not a standalone US label-issuance law.
ISO 13485:2016, Medical devices—Quality management systems—Requirements for regulatory purposes, concerns medical-device quality management; see QMSR versus ISO 13485 for context. The example ledger format, named QA roles and signatures are site-defined practices. They establish no universal two-person check, loss tolerance or sign-off threshold. Do not transfer drug-product or supplement exceptions into the device examples.
09Connect records without losing transaction identity
A practical integration design assigns each record a distinct role: the authorised job record supplies the job reference; controlled label identity supplies item and revision; stock or print records identify material origin; the issue ledger records the handoff; supporting records retain count evidence, acknowledgements and review decisions. Carry these references together through production context tagging, rather than copying descriptions that can drift apart.
Keep requested transactions, acknowledged transfers and posted stock movements distinguishable. A request expresses intent; acknowledgement records receipt into custody; posting updates inventory. A completed physical handoff can therefore coexist with a delayed stock posting. Retain the handoff time and posting time separately, with the pending posting visible. Neither a request nor a stock deduction alone demonstrates receipt.
Use a stable transaction identifier across messages and records. On retry, check that identifier and the previously recorded result before posting again: retransmission is not another physical issue. Keep transaction type explicit so that issue, return and stock adjustment cannot become interchangeable inventory changes.
Make corrections through linked entries retaining the original value, changed field, reason, author and time. A record correction repairs information; a physical reversal moves custody back and needs its own handoff evidence. Record found labels as a separate event linked to the investigation, discovery circumstances and current custodian—not as a backdated increase or decrease to the historic issue.
For recovery, temporarily capture the transaction and later enter it under controlled review, retaining the temporary record reference and original event time. Check for duplicates before entry. The outage FAQ addresses the operational decision sequence.
10Find custody failures before they become count disputes
A useful diagnostic starts with a mismatch between the record and the physical handoff. The checks below are proposed operational controls, not universal legal requirements.
| Observed signal | Custody ambiguity | Proportionate control | Evidence to inspect |
|---|---|---|---|
| Quantity received differs from quantity entered. | Requested quantity may have replaced actual receipt. | Resolve against actual receipt, not the request. | Actual count basis and receiving evidence. |
| Containers share a carrier identifier after splitting. | Neither portion has a distinct custody trail. | Assign distinct child identifiers linked to the parent. | Parent-child carrier record and both portions’ locations. |
| Issue entry has no receiving custodian. | Transfer is recorded; receipt is unconfirmed. | Confirm receipt before assuming consumption. | Handoff evidence and current physical location. |
| System retry creates another issue entry. | Duplicate posting may resemble another movement. | Compare transaction identifiers before counting another transfer. | Transaction identifiers and message history. |
| Destruction instruction appears as completed destruction. | Material may still be held. | Separate instruction status from execution status. | Execution evidence and material’s current custody. |
Sites can select checks according to label similarity, counting reliability, container handling and the consequences of misapplication. A data integrity risk assessment can guide retry checks; destruction and disposal controls can guide execution confirmation. Focus review effort where an ambiguous record could conceal an incorrect physical transfer.
12A practical implementation and review checklist
Use this suggested site-practice test before adopting or changing an issue ledger. Judge whether it reconstructs custody, not merely whether fields are populated.
- Check every movement for a defined transaction type, actual label-unit quantity, count basis, event time, and identifiable sending and receiving custodians.
- Trace job, item, revision, stock lot and carrier references across the issue record and supporting evidence; investigate conflicting identifiers rather than choosing whichever record looks complete.
- Confirm that supplemental issues, returns, stock-eligibility decisions, reissues and corrections remain distinguishable in the history, without overwriting earlier events.
- Test additional material for an active job, a split same-revision remnant, and overprinted excess originating both at the printer before issue and with the operator after issue.
- Have a reviewer reconstruct a selected handoff from identifiers and evidence, including any open exception and recorded QA state. For exception-based review, keep the underlying transactions accessible.
Hand the reviewed custody history, evidence references and unresolved exceptions to downstream closeout without changing their recorded status.
Frequently asked questions
Q.How should a reservation expire when a job is postponed?+
Define a site rule for reviewing reservations when the planned receiving job is postponed. Identify whether stock is still physically in its original location, whether another job has requested it and whether the applicable label identity has changed. An expired reservation can remove the allocation without inventing a return movement. If handoff already occurred, follow the transaction cancellation decision instead. Record the reservation owner and review outcome in the perpetual inventory context so that stock is neither indefinitely unavailable nor silently allocated to two jobs.
Q.Who holds custody when the issuer and receiving operator work different shifts?+
A useful site convention is that custody remains with the issuer or a named staging custodian until the receiving operator records acceptance. Leaving labels at a workstation does not, by itself, establish who accepted responsibility. Identify the secured staging location, container, quantity and pending recipient, then record the later handoff separately. The shift handover report can reference that pending transaction without replacing it. If nobody can establish custody, hold the transfer open rather than backdating acceptance.
Q.How should an operator record fewer labels than the quantity requested?+
Record the quantity actually transferred as the issue quantity and retain the requested quantity separately. Identify the count basis, shortage reason, issuer and receiving operator; do not book the request as fulfilled and compensate with an unexplained adjustment. If more labels arrive later, create a supplemental issue linked to the original request and job. A receiving discrepancy record can capture disagreement between dispatch and receipt while preserving both observations instead of overwriting either count.
Q.Can an earlier-revision remnant be used after the receiving job’s specification changes?+
Do not treat the remnant’s previous approval as evidence that it remains suitable for the changed job. As a site control, hold it pending a documented comparison with the receiving job’s effective specification and a decision by the designated authority. If use is authorised, reference that decision in the new issue transaction; otherwise retain the hold or record disposition. Link the assessment to change control, keeping revision suitability separate from the physical count and condition check.
Q.How is an issue corrected when the job number is wrong but the physical transfer was real?+
Preserve the original transaction and add a traceable correction identifying the incorrect job, intended job, reason, author and correction time. For this site-practice model, distinguish correcting attribution from reversing a physical movement: a fictional return and reissue would misrepresent what happened. Confirm the actual recipient, location and label suitability for the intended job. Reference the correction from each affected batch execution history, so reviewers can follow the transfer without counting the labels as issued twice.
Q.What changes when labels are transferred to a contract packer?+
The custody model gains an external dispatch-and-receipt boundary. A practical agreement identifies who authorises issue, who controls labels in transit, who confirms receipt, and who decides the fate of unused or damaged material. Record dispatch and receipt separately, retaining quantity differences rather than assuming shipment proves acceptance. Link the manufacturer's job and label identity to the packer’s corresponding identifiers. A chain of custody record can connect those events without treating shipment as permission to use the labels.
Q.How can label custody remain traceable during a network outage?+
Use a predefined contingency record with a unique transaction identifier, job, label identity and revision, actual quantity and count basis, issuer, receiver, event time and evidence references. Keep pending transfers visible to subsequent shifts. When service returns, enter or link the record through a controlled recovery step, distinguishing the physical event time from the later entry time and checking for duplicate postings. A hybrid record system approach can preserve the connection between the contingency record and the restored ledger.
Q.Can a label issue ledger be moved to a new repository without renumbering every transaction?+
A migration can preserve existing transaction identifiers while establishing a clear mapping to the destination repository. Check that each original issue still connects to supplemental transfers, return receipts and evidence attachments, and that original event times remain distinguishable from migration times. Test records with an unresolved investigation as well as closed accounts. If an attachment cannot move, retain an accessible reference and record the retrieval limitation. The disposition decision history should remain attributable to its original reviewer rather than acquire the migration operator’s identity.
Primary sources
Want to see how Label Issuance could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
