Difference between revisions of "Case Label Printing"
From Commander4j Wiki
| 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.</br> | No SSCC (Pallet Numbers) are generated for each label.</br> | ||
No record of each label is written to the Pallet and Pallet History Tables</br> | 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).</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).</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.</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.</br> | ||
Revision as of 02:22, 19 April 2015
Case label printing is distinct from Pallet Label Printing in a number of ways.
No SSCC (Pallet Numbers) are generated for each label.</br>
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).</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.</br>
