Scan-to-print, packaging scan, and scan-dedup all sound like “scan once,” but they are not the same action. They differ on trigger, what they block, and who uses them. Counts and block rates below are drawn from past implementations.
| Capability | Why you scan | Typical station | How it differs from the other two |
|---|---|---|---|
| Scan-to-print | Read a code into a variable and print immediately | Pick / reprint; about 80–200 triggers per hour | Does not keep carton/pallet genealogy; does not run a full uniqueness check before print |
| Packaging scan | Hang unit codes onto inner pack, carton, pallet | Pack station; about 10–60 association scans per pallet | Not “scan once and a label comes out” |
| Scan-dedup | Block the same unique code from printing again | Serialized stations; the block happens before Print | Not print history (history is after print) |
Drawn from past implementations: on unique outbound codes, turning scan-dedup on can cut duplicate-code rework about 50%–70%. Approval and scan-dedup open by edition and can run in LuckDesign.
Print history is the trail after print; keep it separate from scan-dedup.