Print history
Print history keeps trace data after labels print for reconciliation, audits, and disputes. Policy may be none, local install, or enterprise data service (e.g. via LuckData) when licensed and configured.
It differs from scan deduplication, which blocks duplicate business requests before print: history answers who printed what and when; dedup answers whether this print is allowed. Enablement, storage, and retention follow Versions & permissions and your contract. Often planned together with Scan to print labels on the floor.
What it does
- Timing: records land after print—who printed what and when.
- Policy: none, local install, or enterprise data service (e.g. LuckData)—per edition and contract.
- UI guard: the dialog blocks double submit during a job; that is not the same as business dedup or retention policy.
Vs. scan dedup and data write
- Scan deduplication: pre-print blocking of duplicate business keys. See Scan dedup.
- Data write (LuckData): post-print formula-driven writes to business tables—can coexist with history for different purposes. See Label printing software · Data write.