Package classes create a hierarchy of packaging UOMs that describes how items are packed and stored in your warehouse.
Important: Contact your Kenandy administrator before adding or making changes to package classes.
Package classes are usually defined when Kenandy is first set up.
When you create container items, you need package classes set up so you can assign them to the container items. License Plate Numbers (LPNs) can be used to track container items in the top level of the package class hierarchy.
For example: You make t-shirts. In work orders, one t-shirt is measured as an "each" (EA). You sell t-shirts in cases (CS). And you store pallets that can hold a maximum of 10 cases.
Your package classes for your t-shirt business look like this:
Before you create a new package class, you must have the following:
Kenandy creates the package class and ties it to the default container item you specified.
If you need to create a bunch of package classes that all have similar data, you can create one and then clone it to save time.
To clone a package class, follow these steps:
Note: You can complete steps 1-4 for a bunch of packaging classes, then go back and do step 5 for each new packaging class after you finish cloning.
Note: Changing a package class can cause problems in other parts of Kenandy. Before you edit an existing package class, contact your Kenandy administrator or Kenandy customer support.
To edit a packaging class, follow these steps:
The following table lists the fields that Kenandy provides. Your system administrator selects the fields that are displayed on your user interface.
| Field | Description |
|---|---|
| Package Class Name |
The name of this package class. Usually the name is the same as the packaging UOM this class corresponds to. |
| Default Container Item |
The container item you most often use as packaging for this package class. For example, you can create a container item named Brown Cardboard Box and add it as the default container item for the package class CS (case). |
| Level |
The placement of this package class in the hierarchy of package classes. This field is not editable. |
| Parent Package Class |
The next level up in the package class in the hierarchy. For example, if you have EA (eaches) as package class level 1, its parent package class might be CS (cases), which is level 2. |
| Fractional Quantities Allowed |
Select this option only if this package class can be divided into quantities less than one. For example, if you have DZ as a packaging UOM and want to allow fractions of dozens (0.5, 0.25), select Fractional Quantities Allowed. For EA that represent a single item that cannot be stocked in fractions, do not select this option. |
| Description |
Optional. A description of this package class, including information to help Kenandy users understand how to use this package class. |
| Field | Description |
|---|---|
| Action |
Do not use. |
| UOM | The name of a UOM that has this package class assigned to it. |
| Description | The description of the UOM (if it exists in the UOM record). |
| Field | Description |
|---|---|
| Package Class Name |
The name of another package class that has been set as a child to this package class. |
_________________________________
To search the KnowledgeBase and documentation, ask a question, or log a case, please visit the Kenandy Community. To access our online training, visit the Kenandy Learning Center.
Version: Spring 2017