Difference between revisions of "Case Label Printing"
From Commander4j Wiki
(Created page with "Case label printing is distinct from Pallet Label Printing in a number of ways. No SSCC (Pallet Numbers) are generated for each label. No record of each label is written to t...") |
|||
| (7 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | Case label printing is distinct from Pallet Label Printing in a number of ways. | + | Case label printing is distinct from [[Pallet Label Printing]] in a number of ways.<br> |
| − | + | <br> | |
| − | No SSCC (Pallet Numbers) are generated for each label | + | * No SSCC (Pallet Numbers) are generated for each label<br> |
| − | No record of each label is written to the Pallet and Pallet History Tables | + | * No record of each label is written to the Pallet and Pallet History Tables<br> |
| − | Data can be printed directly to a labeller from Commander4j or exported to a file for use by an external program. (Logopak Synchro for example) | + | * Data can be printed directly to a labeller from Commander4j or exported to a file for use by an external program. (Logopak Synchro for example)<br> |
| − | Typically data is sent to the labeller at the start of a production run and it remains in the labellers memory without further communications. | + | * Typically data is sent to the labeller at the start of a production run and it remains in the labellers memory without further communications.<br> |
| + | <br> | ||
| + | [[File:Case Label Send to Printer.png|800px|thumb|left|Location Admin]] | ||
Latest revision as of 19:57, 21 December 2023
Case label printing is distinct from Pallet Label Printing in a number of ways.
- No SSCC (Pallet Numbers) are generated for each label
- No record of each label is written to the Pallet and Pallet History Tables
- Data can be printed directly to a labeller from Commander4j or exported to a file for use by an external program. (Logopak Synchro for example)
- Typically data is sent to the labeller at the start of a production run and it remains in the labellers memory without further communications.
