WMS - Kitting Flow Process

Kitting Flow Chart

See Also: Glossary

WMS Glossary | Kitting

Create SKU Product KIT

Parent Kit/ KIT SKU

Client will determine which products to Kit together and then Create New SKU for the Product Kit by using iHub Load service.

Load Product Master as Kit

(iHub)File > Upload File > Load Product Master, then upload file.

This process allows the user to create a new “Kit” property to identify a Product as a Kit. The new SKU will be the “Parent” Kit.

Load Product Master Updates

(iHub)File > Upload File > Load Product Master Updates, then upload file.

Used when existing products/SKU needs to be formed as a Kit. This allows the users to update the Product “Kit” property.

kit.png

Kit Components

Load Kit

(iHub)File > Upload File > Load Kit, then load file.

This process allows the user to specify the “Component SKU” and “Quantity” that makes up the Kit.

It includes the Parent SKU and individual SKUs as its components to build the Kit.

This “Load Kit“ service can be used to load a kit OR revise an existing kit.

 

KIT_LoadProduct1.png

 

  • Product Kits that have been uploaded successfully will appear in both the Client and DC Interface.

  • To access them, go to Logistics > Kitting > Kit List.

  • Users should have the necessary access and permissions to view this menu.

ASN/Delivery for Kits

Enter delivery information into the system for Kit (Ready-made or Kit components) Inventory

(DC Interface) Logistics Menu > Select Inventory >Click on Add Delivery

View Kit Inventory via Stock Report

Items Receiving/GRN/Put Away

Same process as standard Inbound Receiving of Inventory in DC

SEE ALSO: https://seko.atlassian.net/wiki/x/9Qp0qQ

Receive Work Order from Clients for Kitting (Optional)

  • Clients can request advance creation of Kits from the components available in Warehouse through Work Order. This process makes Order dispatch and shipping faster and more efficient.

  • Kits are Pre-assembled in the DC before the Sales Order/Dispatch Request.

  • The SO Work Order will be same process as SO Dispatch Request (Pick-PACK-DISPATCH) but will need to be Received (ASN/GRN process) as new SKU KIT or Parent Kit.

  • This will adjust the inventory of the Parent KIT and components accordingly.

  • If no Work Order is requested by Client,  Kits are built on-the-fly from the components available in Warehouse during SO Dispatch Process.

Sales Order and Dispatch Request for KIT

Client creates Kit Sales Order using iHub Load service. CSV file template will be provided.

After the Sales Order (SO) is successfully created, stocks will be allocated based on order quantity. At the same time, Dispatch Request is automatically created for DC to process.

 

Load Sales Orders

(iHub)File > Upload File > Load Sales Order , then upload file.

This process allows the user to create new sales orders with 'On the fly' company code creation function. Includes all Order type.

Load Web Sales Orders

(iHub)File > Upload File > Load Web Sales Order, then upload file.

This process allows the user to create a new Web Sales Order and automatically sets Order type to WEB ORDER.

Compared to the Load Sales Orders service, this service does not include the 'ShipToCompany' field mapping.

Picking

Print Pick Note or Wave Summary Sheet if using wave picking method

The following Picking methods supports the Kit to Order process.

  1. Wave Picking (Mobile scanning)

  2. Fast Dispatch (Mobile scanning)

  3. Order Picking (Mobile scanning)

  4. Pick by SKU (Mobile scanning)

  5. Web Interface Picking/Front End Picking (Desktop)

(Logistics Tab> Dispatch Menu> Dispatch List> “To be Picked” tab )

 

Packing

Assemble Kit Components

Build the Kits on-the-fly (Done if pre-assembled Kits are not available)

Kit components are assembled after Picking based on Dispatch Request/ Sales Order.

Generate Kit to Order Document for packing details.

Pack the Kits

There are two ways to pack a ‘Kit to Order’ using the Desktop Web Interface:

  1. Web Interface Dispatch Packing/Front End Packing- Packing method without scanning individual SKUs

(Logistics Tab> Dispatch Menu> Dispatch List> “To be Packed” tab )

To generate Kit to Order Document, Click “Print Kit to Order Document” button

Pack all components of a single kit into the same dispatch box.

  1. Web Order Packing - Packing method for Wave Picking by scanning Barcode and SKUs

(Logistics Tab> Dispatch Menu> Web Order Packing)

To generate Kit to Order Document, Click “Print Kit to Order Document” button

Short Shipment & Rollback

  • Full Short Shipment: Happens when all lines/items are not available.

  • Partial Short Shipment: Occurs when only some lines/items are insufficient

For Wave Picking with a partial short shipment, users have two options:

  1. Dispatch Quantity Adjustment (Before Picking):

  • Navigate to Logistics > Wave Picking > Dispatch Quantity Adjustment.

  • Decrease the quantity of the kit line. This action will automatically adjust the quantities of all kit components.

  1. Rollback (After Picking)

  • Go to Logistics -> Dispatch -> Rollback

  • Rollback the Dispatch back to “To Be Picked”

  • Then Go to Logistics -> Wave Picking -> Dispatch Quantity Adjustment

  • Decrease the Kit line quantity. This will trigger a recalculation of all component line quantities for the kit.

Users cannot continue packing and must perform a Dispatch Rollback and Dispatch Quantity Adjustment first

Back Order

  • If stock is not enough to fulfill the Kit, as well as the components used to build the kit in a Sales Order, it will become a “Back Order”.

  • On the next Dispatch schedule, system will create a Dispatch Request for the back orders if the Kit or its components are already available to fulfill the order. Otherwise, It remains as back order.

  • If Sales order have multiple Kits to fulfill, Client can decide if complete items will be partially dispatched and incomplete items remain as back order.

See Also: https://seko.atlassian.net/wiki/x/LBV0qQ

Cancellation

Same process as standard Sales Order, SO cannot be cancelled if already in Dispatch status.