Products are items or services that you sell. In Kenandy your company purchases items and sells the product that is made from one or more items packaged or manufactured into those products. Each product can be defined in one or multiple pricebooks that define pricing according to customer parameters, so that when you add product to the sales order line the product is priced appropriately. The product detail includes an item's price, UPC code, weight, selling UOM, and selling price.
Each product price has an effective start date and end date, which is stored in the pricebook. When you add products to the sales order line, Kenandy uses the product's effective date to validate that the sales order reflects the correct version of the pricebook.
Storage Units can be used for storage, sales and shipping. Products that should be sold as complete cases or pallets defined with a number of Units per Layer, the number of Layers per Pallet, and whether they can be stacked For example, for every sold-to customer, you can specify whether you want the order quantity to be in multiples of units per layer or units per pallet.
For manual orders, if the order quantity does not meet the order factor multiple, Kenandy flags the line. For automated orders, you can set Kenandy to adjust the quantity up or down to the nearest even- layer so that order processing can continue.
Note that any changes to the sold-to customer will trigger the order quantity factor validation to be run.
Create a Product
Set Up an Order Quantity Factor
Pallet— from the Order Quantity Factor At drop-down list.Manage Pricing
You can maintain a product price manually or with a pricebook. The default setting is for a product to require a pricebook. This setting ensures that when the sales order is released, Kenandy references the Price Determination Date, Pricing Date, and Bracket Price Field In Use to determine the price.
If the checkbox is not selected, a price book is not used and the sales order line is not repriced when the order is released, aggregated, disaggregated, shipped, or invoiced.
| Order Date | Shipment Date | Manual | |
|---|---|---|---|
| Create a Sales Order | Pricing Date: Sales Order Date | Pricing Date: Sales Order Date | Pricing Date: User entered date |
| Unit Price: Based on Pricing Date | Unit Price: Based on Sales Order Date | Unit Price: Based on Pricing Date | |
| Release Order | Pricing Date: Sales Order Date | Pricing Date: Estimated Ship Date | Pricing Date: User entered value |
| Bracket Price Field In Use: Based on total order weight | Bracket Price Field In Use: Based on total order weight | Bracket Price Field In Use: Based on total order weight | |
| Unit Price: Based on Pricing Date and Bracket Price Field In Use | Unit Price: Based on Pricing Date and Bracket Price Field In Use | Unit Price: Based on Pricing Date and Bracket Price Field In Use | |
| Aggregate Order | Pricing Date: Order Date | Pricing Date : Estimated Ship Date (Estimated ship date can change in the aggregation process) | Pricing Date:User entered date |
| Bracket Price Field In Use: Based on total aggregated weight | Bracket Price Field In Use: Based on total aggregated weight | Bracket Price Field In Use: Based on total aggregated weight | |
| Unit Price: Based on Pricing Date and Bracket Price Field In Use | Unit Price: Based on Pricing Date and Bracket Price Field In Use | Unit Price: Based on Pricing Date and Bracket Price Field In Use | |
| Dis-aggregate Oder | Pricing Date: Order Date | Pricing Date: Estimated Ship Date (Estimated ship date can change in the aggregation process) | Pricing Date: User Entered Value |
| Bracket Price Field In Use: Based on total order weight | Bracket Price Field In Use : Based on total order weight | Bracket Price Field In Use: Based on total order weight | |
| Unit Price: Based on Pricing Date and Bracket Price Field In Use | Bracket Price Field In Use: Based on total order weight | Unit Price: Based on Pricing Date and Bracket Price Field In Use | |
| Ship Order | Pricing Date: Order Date | Pricing Date: Actual Ship Date | Pricing Date: User Entered Value |
| Unit Price: Based on Pricing Date and Bracket Price Field In Use | Unit Price: Based on Pricing Date and Bracket Price Field In Use | Unit Price: Based on Pricing Date and Bracket Price Field In Use | |
| Invoice | NA | NA | Repriced based on the (user entered) Pricing Date |
| Unit Price: Based on Pricing Date and Bracket Price Field In Use | |||
Product Field Descriptions
The following table lists the fields that Kenandy provides. Your system administrator selects the fields that are displayed on your user interface.
| Field | Description |
|---|---|
|
|
Indicates whether the product is active (in use) or not. |
| Attribute Group | Enables you to select the attribute group for the product. |
| Average Lot Size | Displays the average lot size for the product. |
| Billing Category |
Select a billing category for the product. The billing category is visible on sales order lines when the product is included on a sales order. It also is on agreement lines. You can set up invoice grouping rules to group fulfillments for invoicing by billing category. Use the Categories page to set up billing categories. To learn more, see Categories. |
| Bundle | Select this checkbox to flag the product as a bundled product. You can designate a parent product as a bundle so that when the child product lines are fulfilled and the sales order lines are closed, Kenandy automatically creates a fulfillment for the parent and closes the parent sales order line. When you set up products to be bundles, also set up the related item records to be non-inventory. This is to ensure that Kenandy closes a parent sales order line when all of its child lines have been fulfilled. |
|
|
Fraction or portion of a standard case that this product occupies. |
| Company |
Displays the list of companies. |
| Description | Further describes the product. |
| Dimension UOM |
Displays the list of units of measure. |
| Fulfillment Category |
Select a fulfillment category for the product. This category determines how your product is fulfilled (shipment, installation, license key turned out, and so on). You can use fulfillment categories to facilitate integrations with 3rd party products. The fulfillment category is visible on sales order lines when the product is included on a sales order. It also is on agreement lines. Use the Categories page to set up fulfillment categories. To learn more, see Categories. |
| Height | Height of the product. |
| Invoiceable | When selected, this checkbox indicates that the product is invoiceable. |
| Item |
Displays the list of items related to the selected product. |
| Item Identifier | For data loading purposes. Used to link the product to the item during the data load process. |
| Kit Pricing Type | This picklist enables you to select the kit pricing type. |
| Kit Updates Allowed | When selected, this checkbox indicates that kit updates are allowed. |
|
|
The number of product layers per shipping pallet. |
| Length | Length of the product. |
| Lifecycle | Product lifecycle codes include New, Active, Retired. |
| List Price | Displays the product's list price. |
| Lock Price | A checkmark indicates that the product price must come from a pricebook. It also means that the user will not be allowed to override the price for that product on a sales order line. When the lock price box is cleared, the user or a quote line can overwrite the product price on the sales order line. |
| Material Burden | Displays the product's material burden. |
| Material Burden Cost | Displays the product's material burden cost. |
| Next Available Date | Indicates the earliest date the product is available for this customer. |
| Non Taxable | This checkbox indicates when the product does not incur sales tax. It is used by the default Kenandy tax service at the time of invoice creation. External tax services ignore this field and make a determination of taxable status based on definitions made on the tax service. |
| Primary |
A check mark indicates that the product is the primary product in the UPC group (that is, the product is registered for UPC). |
| Product | The name of the product. |
| Product Group | Identifies the group that the product belongs to. |
| Product Group Code | The code is used during the data load process. |
| Product Image | Image of the product, if available. Supported file types are .png, gif, and jpeg. File size is limited to 1 MB. |
|
|
Product specification within the Product Sales Hierarchy. |
| Product Reference (Cross Reference) |
Product reference is not part of the product definition, but every product can have one or many customer specific names (aliases) called product references. Each product reference is specific to a customer and the product reference is used as an alias for the product for that customer. The product reference can be used to specify the product on the sales order line or the agreement line. Product references are defined as cross references. To learn more about product to product reference links, see Cross References. |
| Product Type |
Use the Product Type to specify whether or not the product is a configurable product on agreement lines. If you select Configurable, you can add child products for the product when you set up the agreement lines. Also select the Configurable checkbox on the related item record. This is not an item specification; rather you can define the relationship between products as part of a single solution. If you select Warranty, select the Non Shippable checkbox to identify it as a non-shippable product. |
|
|
The code is used during the data load process. |
| Selling UOM |
The unit of measure used when selling an item. Items are often purchased, stocked, and sold in different units of measure. You can specify a conversion factor to automatically convert from one to the other. Go to the UOM page to manage units of measure and For drop-ship sales orders, the purchasing UOM on the item must be the same as the selling UOM on the product. |
|
|
A code that indicates whether something is sold as open stock or by FCST only, and whether it is assembled at a factory or DC. |
| Stackable | A check mark indicates that the product is stackable on a pallet. |
| Status | Status can indicate whether the product is, for example, active or retired. |
| Tax Code | Tax Codes determine if a product is exempt from sales tax in a given state. If Kenandy calculates sales tax for a transaction that includes an exempt tax code, sales tax is not calculated for that line item. External tax services do not use this field. |
|
|
For products that are stackable, the number of products per layer. |
|
|
Units per pallet. If the product is stackable, units per layer is multiplied by the number of layers per pallet. |
| Usage-Based |
Select this checkbox for usage-based products, for which you want associated sales order lines to remain open even if the quantity fulfilled is greater than the quantity ordered. A usage-based product can be software that is priced based on usage rather than quantity. For non-usage flagged products, their sales order lines automatically close when the quantity fulfilled equals the quantity ordered. You can also select this checkbox on the sales order line. |
| Used | This category allows you to employ special pricing (set through the pricebook) for products that are used, returned, refurbished, or open box. |
| UPC Code | The universal product code (UPC). UPC code is limited to digits. If you use the same UPC codes for multiple products, only one can have the UPC primary flag checked. |
| Weight | The weight of the product. |
| Weight UOM | The unit of measure used to express the weight of the product. |
| Width | The width of the product. |
_________________________________
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