Serial numbers
Kristy Sherman
Users can create items with the serial numbers recorded. The item will have one of the following: not serialization, sometimes serialized, or always serialized.
When a sale takes place for an item which is always serialized, a pre-defined prompt will appear and require the cashier to input the mandatory information. (The prompt is defined on CAS)
If the cashier does not enter the mandatory information on a always serialized item, the sale cannot be completed.
Items may be defined as "Always serialized" or "Sometimes serialized" or "Not serialized".
The serialization level is defined on CAS using the Master Item UI, Item Import, the enhanced item detail import, or an entire Classification or Attribute can have the serialization level designated.
"Always serialized" tracking allows you to exercise tight management control over the movement of quantities for the item. Serial numbers must be specified for every transaction (receiving, transfer, sale, etc.). You may only sell serial numbers that are actually in stock. Always serialized tracking ensures that there is a serial number associated with each item on hand.
"Sometimes serialized" tracking provides looser management controls. Recording of serial numbers during receiving (or other transactions) is optional. To ensure that you keep good records, you may specify for each item whether serial numbers are required when selling and returning. The sometimes serialized tracking method is useful for businesses that don't track in-stock serial numbers, but may want to record serial number information at the time of sale.
Serial Prompts
Serial prompts will need to be defined to allow for the collection of additional information. For example, you could define a serial prompt code to be used in receiving’s that requests the classification and optionally requires the user to enter either "New" or "Used." Serial prompt information is retained with the transaction detail. Serial prompts are defined at the time an item/classification/attribute is set for serialization. They can be designated as text box inputs or to display information entered in a field associated with item (description, Classification Attribute etc). Each field can be designated as a mandatory entry (based on transaction type if necessary)