Kitting is a process that allows putting two or more different products in one product code to create a new product. Sales Orders can be loaded with kits. If the kit is in stock, the system will allocate this, but if the Kit is not in stock then the system will attempt to assemble the kit automatically from the kit components if stock is available for all the components that make up the requested kit.

This process allows the user to create a new “Kit” property to identify a Product as a Kit.

Logged in to Hub, the user must go to the side menu and click on File > Upload File > Load Product Master, then upload file.

Please note that the below .csv file screenshot is only a sample.

Note: Kitting is assigned per client, if no setup, ask our support for assistance.

Click the “Select file” button to upload the created .csv file.

If no error is encountered on the uploaded file, the user must click the “Submit” button to proceed.

Once the file successfully uploaded, the user must wait for the products to be uploaded to the system before uploading the Kit Components in the “Load Kit” service.

This allows the users to update the “Kit” property used to identify a Product Master as a Kit.

Notes:

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

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

Please note that the below .csv file screenshot is only a sample.

Go to the side menu and click on File > Upload File > Load Kit, then load file.

If no error is encountered on the uploaded file, Click the “Submit” button to proceed.

To check the status of the uploaded file, Go to the Activity to check if the upload was successful or not.

This menu allows the user to view the Kits loaded in Seko 360 and the Components that build Kits.

Go to Logistics > Kitting > Kit List, and this is only visible if the user has access to the “KitListView“ permission.

Note: If no permission or login details please ask our support members for assistance.

Both DC and Client users can be given access to the menu item:

After loading Kits on the hub, the user can now add delivery (ASN) for the Kit and components.

Note: After putting stocks on the loaded kit/s, the user can now proceed with Loading Sales Orders or Load Web Sales Orders of Kits via iHub.

If a Client has the “Kit to Order” setting enabled, Seko 360 will:

Note: If no permission or login details please ask our support members for assistance.

If a client is enabled to use back orders and there is NOT enough stock to fulfill the Kit line as well as the components used to build the kit, then the order will remain in back order.

E.g.

(Samples are out of stocks on Stocks Report) Orders will reflect to the Back Orders List but still needed to wait for the next schedule of the Order Process.

As soon as stock is available to fulfill either the kit line OR enough stock for the components to build the kit on the fly, then Seko 360 will attempt to create a Dispatch for this.

If a Client has the “Kit to Order” setting enabled, Seko 360 will attempt to use the components that make up the kit if stock is available for all these components when processing Back Orders.

When a dispatch is created with kits to be built on the fly, the components that make up the Kits to be built will be displayed as follows:

When the Kit has enough stock, the dispatch lines will be displayed as follows:

Excludes updating pricing of the components required to build the kits as it is the pricing of the Kits lines that will be sent to the TMS.

Includes all Kit lines sent to us by the client. This includes any Kit lines that need to be built on the fly.

Weights and Pricing work off Kit lines, excludes any Component lines required to build the kits.

Update weight of Kit lines sent to us by the client including Kit lines that need to be built on the fly.

Excludes updating weight of the components required to build the kits as it it is the weight of the Kits lines that will be sent to the TMS

Users have the ability to create Client Wave Configurations and set a “Build Kit” option.

This will group waves with Dispatches that require kits to be built on the fly.

Users can print the “Kit to Order” document as soon as the waves are created.

If any dispatches within the wave require kits to be built on the fly, then the “Print Kit to Orders” button will be enabled.

To adjust the Kit quantity, the user must go to Logistics > Wave Picking > Dispatch Quantity Adjustment.

This process will allow a user to decrease dispatch line quantity to force a dispatch to fit in a wave.

When adjusting the quantity of a Kit line, ALL the components that make up the kit will be reduced.

Wave Pick Release

Users can print the “Kit to Order” document as soon as the waves are created.

If any dispatches within the wave require kits to be built on the fly, then the “Print Kit to Orders” button will be enabled.

After creating Pick Waves, the user can now proceed to mobile Wave Picking

After clicking the “Pack” button, the users will be redirected to another page and will work as the usual process.

Note: Users cannot pack components that make up one kit into different dispatch boxes. If they do they will receive an error: “You cannot pack components that make up a specific kit in different dispatch boxes. Please repack.”

Note: Kit to Order Document can be printed on the Packing Screens for both “Front End Packing” and “Web Order Packing” modules.

The following modules supports the Kit to Order process and the users can pick a dispatch that requires a kit to be built on the fly:

However the following modules do NOT currently support Kit to Order and users will be blocked if they attempt to pack a dispatch that requires a kit to be built on the fly:

Users should instead use the “Front End Packing” or “Web Order Packing” modules for this as these support the Kit to Order document that users need to print so they know what components make up the kit to be built on the fly.

On the “Front End Packing” and “Web Order Packing” modules, a “Print Kit to Order” button will be visible when there is a kit to be built on the fly.

This document details the components that make up the kit and what needs to be packed. Users will refer to this document when assembling the kits at the packing benches.

Web Order Packing

If a dispatch is short-shipped and this results in insufficient stock to build a kit in progress.

The user will encounter a message on both “Front End Packing” and “Web Order Packing” modules:

“Due to a short shipment there is now insufficient component products to build the requested Kit.
Please perform a Dispatch Rollback and ensure there is sufficient component SKU’s picked to build the kit.”

E.g. Web Order Packing

Note: Users cannot continue packing and must perform a “Dispatch Rollback”. Once the dispatch rollback is completed they can use the “Wave Picking > Dispatch Quantity Adjustment“ process to decrease KIT line quantities.

Note: If the Kit doesn’t have enough stock, that’s the only time the SKU components that build a kit will be listed in the pick note.

Seko 360 developed a bespoke “Product Label” for the client EquiLife containing order information, product information, and a QR code (coded as a web address), which will be affixed to each unit during the pack process.

This label allows the ship-to (consignee) to scan the QR code and easily register their product.

Print Packing List

After a client cancels a Sales Order with Kit lines that need to build on the fly, Seko 360 will update the Stock Report with the lines that were canceled.

The Component line totals will be updated in the Stock Report to reflect the cancellation.

Kit lines that are built on the fly are NOT updated in the Stock Report as it is the Component lines that are picked and packed.