Keep uncertain output visible
An uncertain submission puts the station on hold. An operator must reconcile the outcome before work continues.
LABEL REPRINTS AND PRINT HISTORY
Another copy.
A clear reason.
A damaged label should lead to an understandable reprint. Select the original copies, record the reason and retain the connection to the output they came from.
AN EXAMPLE COPY HISTORYWO-12345
- 01
Original run
Three copies. The prepared label output is retained.
Copy 01Copy 02Copy 03 - 02
A replacement is needed
The operator identifies damage to copy 02.
- 03
One selected reprint
Copy 02 · original output
Linked to the original run
Reason: damaged during packing
KEEP THE ORIGINAL IN VIEW
A reprint has its own record.
Use the retained original output when replacing a label, even if a newer template has since been published.
- 01
Choose the copies
An administrator selects the specific original copy records. Replacing one damaged label does not need to recreate the whole order.
- 02
Explain the request
A reason is required. The workflow rechecks current eligibility before preparing the reprint, so a previous run alone is not permission to print again.
- 03
Follow the link back
The reprint records its selected originals and preserves their label bytes. The original run and the replacement remain distinguishable in the history.
WHEN THE OUTCOME IS UNCERTAIN
A lost connection
needs a checked answer.
If a browser disconnects during printing, software may not know whether a label emerged. Repeating the send immediately could create an extra physical label.
Acknowledge the duplicate risk
Even when no output is observed, a printer might still deliver a delayed label. The recovery workflow requires that possibility to be acknowledged.
Check the physical result
QZ accepting a send is a submission record. The operator checks what actually printed. Software cannot guarantee exactly one physical copy.
PRACTICAL DISTINCTIONS
A retry, a revision
or a reprint?
Does importing the CSV again print more labels?
No. Importing prepares data and never prints. Repeating an identical import reuses its snapshot. A new source revision does not grant another original print run; additional copies use the reprint workflow.
Can a reprint use an updated layout?
An exact reprint preserves the original output. If the artwork or data needs to change, assess that as a new requirement rather than treating it as an exact replacement.
What if a label was definitely not sent?
A definitely unsent attempt has a separate retry path. An uncertain outcome must be reconciled first. The distinction prevents an ambiguous send from being treated as permission to repeat it.
LET’S START WITH YOUR WORKFLOW
Bring one label.
We’ll start there.
Tell us about your data, customer requirements and printer. We’ll help you assess whether SmartFACT Labels fits.