A damaged warehouse label may need another physical copy, but pressing Reprint is not a complete control. The project must decide whether the new output represents the same unchanged object, a corrected record or a replacement label with a different business identity. It must also prevent an old readable copy from remaining active beside the new one.
This guide is for warehouse operations, shipping teams and WMS or label-system integrators. Its examples are editorial, not AIDC GO customer deployments or device tests. Relevant commercial handoff points are the handheld-terminal category, warehouse and logistics solutions, Integration Support and Contact. The selected application and label platform define reprint authority, identifiers and audit records.
Separate an exact reprint from a changed label
An exact reprint should reproduce the approved label record for the same business object. A regenerated label is created again from current data and may differ if the order, package, quantity, route or template has changed. A replacement label can deliberately assign a new identifier when the business object itself has changed or the project requires the old identity to be retired.
These actions are not interchangeable. Microsoft Dynamics 365 Supply Chain Management documents both reprinting saved wave-label printer data and, when label details are updated, regenerating a label from current data. Its reprint and void wave labels page is a product-specific example: it does not establish how every WMS stores or regenerates labels.
Before printing, the application should display which action is being requested and why. A user who only sees a printer name and copy count cannot tell whether the output preserves the earlier identifier or creates a changed representation.
| Action | Required check | What the action does not prove |
|---|---|---|
| Exact reprint | Same approved record, identifier, template revision and relevant data | That the earlier physical copy has been removed |
| Regenerate | Current business data and template are approved for a new output | That the result is equivalent to the previous label |
| Replace identity | New identifier is linked to the authorized change and the old one is retired | That downstream systems already know the replacement |
| Print another copy | Multiple active copies are permitted and controlled | That duplicate scanning cannot occur |
Keep the identifier tied to the physical object
A shipping label can contain several identifiers: an internal carton ID, an SSCC, an order or shipment reference and a carrier tracking number. They do not become synonyms because they share one piece of media. Record which identifier selects the package in each application and which one is merely displayed for another party.
GS1's *Logistic Label Guideline*, Release 1.3, describes the SSCC as the mandatory unique identifier of a logistic unit and explains that its original identity should be preserved when a carrier replaces a segment during transport. The GS1 Logistic Label Guideline supports the identity principle; it does not require every internal carton label to use an SSCC or define a WMS reprint screen.
If carton CTN-2048 still contains the same approved goods and the only label is torn, an exact reprint may retain its identifier. If the carton was split, merged or reassigned, the project must decide whether it is still the same logistic unit. Do not copy the old identifier onto a materially different package merely because the printer can reproduce it.
Walk through an editorial reprint decision
Assume shipping task SHIP-7714 has two cartons. Carton CTN-2048 is associated with package record PKG-2048 and label record LBL-9301. The barcode is unreadable after abrasion, but the carton remains sealed and the system shows no change to its contents or destination. All identifiers are invented for teaching.
The operator first selects the physical carton through the approved fallback: a human-readable carton reference, the open packing task or a supervisor-confirmed lookup. The application displays the destination, package record, label status, last print event and whether an exact saved output is available. The operator must not choose a nearby carton simply because it belongs to the same order.
The reprint is authorized for LBL-9301. After printing, the operator compares the human-readable package reference and destination with the application, applies the new label to CTN-2048, and removes or fully obscures the damaged copy. A verification scan must resolve to PKG-2048 in the current shipping task. This proves that the new copy can be read and mapped as intended; it does not prove carrier acceptance or dispatch.
Now change one condition: the carton is reopened and one item moves to a second carton. The earlier package content is no longer current. Reprinting the saved label would create a readable but misleading copy. The packing workflow must update the package records, produce the authorized labels for both cartons and mark superseded label records according to the system's rules. The packing-verification guide covers the item-to-carton relationship; this guide controls label continuity after that relationship changes.
Retire stale copies instead of creating parallel truths
The main risk is not a failed printer. It is two readable labels that point workers or systems toward different outcomes. Define what happens to the former physical copy, the former label record and any queued print job.
Microsoft's documented wave-label flow can void labels when work changes and can maintain label history. That is evidence of one configured product behavior, not a guarantee that every print service automatically invalidates old output. A project should test whether a voided record is rejected at the next scan, only marked in a report, or remains technically readable but blocked by business state.
Remove, destroy or permanently cover superseded physical labels under the site's approved procedure. Do not place a new label over only part of an old barcode, where either symbol could remain decodable. If evidence retention requires keeping a removed label, preserve it away from live packages and link it to the reprint event.
Handle duplicate scans and repeated print requests separately
A scanner can read the same symbol twice in quick succession, while a user can also request the same label again minutes later. These are different controls. Decoder or application deduplication can suppress rapid repeated input; it cannot determine whether a second physical copy was authorized. The duplicate-read guide addresses repeated capture, not print authorization.
Before accepting another print request, show the earlier request state: queued, sent, confirmed by the print service, failed, cancelled or unknown. If the result is unknown, reconcile the printer queue and physical output before submitting again. A network timeout is not proof that nothing printed.
If multiple copies are legitimate, record the reason and intended placement. A pallet may need labels on more than one side, but the labels must represent the same logistic unit and remain consistent. A second copy does not create a second pallet.
Test the full path, not only print quality
Print quality matters, but a clean barcode can still carry the wrong identity. Validate the workflow with an unchanged-package reprint, a changed-package regeneration, a deliberately stale label and an uncertain print result. For each test, retain the user, device, task, label-record ID, template revision, print service response, physical disposition and verification scan result.
The label-media selection guide explains media fit and handling, while the barcode and QR layout guide covers printable area and symbol layout. Neither proves that the identifier and business record are current.
Evaluate the handheld in the real task: locate the correct package, read remaining labels at the expected distance, present the decision clearly, recover from connectivity loss and confirm the new output. Ask the software provider how it distinguishes saved output from regenerated data, how it voids records, and what downstream scan sees. Ask the device and printer suppliers for the exact scanning, printing and connectivity configuration to validate. The control succeeds only when the correct identity survives the reprint and stale copies cannot silently re-enter the workflow.