Körber WMS - Daily Check Guide

This guide provides detailed instructions on the daily checks required - use the Qlikview Order Tracking WMS To Mantiki report to perform these checks: Report

1. Orders cancelled in Mantiki but not cancelled in Korber

When orders are cancelled in Mantiki, the status of the order should be updated in Korber. There are occasions where this does not happen, and a check is required to update orders when this is the case.

To find orders that have been cancelled in Mantiki but not cancelled in in Körber, select the Cancelled option from the Order Status Mantiki filter as shown below. This will return orders and their corresponding status in Körber in the Körber Status filter. Any orders at a cancelled status in Korber require no further action.

Any orders that have been cancelled in Mantiki but have a Shipped status in Korber and have a carrier scan confirming shipment/delivery require further investigation, as per the example orders shown further below.
An IT – Support (HELP) ticket should be created for these orders and investigation undertaken to understand why they have not been dispatched in Mantiki. The CS Management team should be e-mailed with the order numbers so payment can be taken from the customers.

Any remaining orders that have been cancelled in Mantiki but are not showing as cancelled in Korber will need to be investigated and manually cancelled in Korber. The table below shows the different Korber statuses and whether they can be cancelled. If the order to be cancelled is at a status that either cannot be cancelled or requires an update before it can be cancelled, the CS Management team should be e-mailed with the order details.

2. Orders with a carrier scan that are not Shipped in Körber

When orders are physically shipped from the warehouse, the order will be updated with a carrier scan and a consignment reference which can be used to track the status of the delivery. There are occasions where orders are physically shipped with a carrier scan, but the status of the order is not updated to shipped within Korber. A check is required to investigate and update orders when this is the case.

To find orders with a carrier scan, select the Scanned option from the Scanned filter as shown below. This will return orders and their corresponding status in Körber in the Körber Status filter. In the example below, there are orders with a carrier scan and at a Korber status of Cancelled, Shipped, and Waved Error.

Orders with a carrier scan confirming delivery and Korber status of Cancelled and Mantiki status of on picklist (as per the example orders shown further below) need to be investigated further.
An IT – Support (HELP) ticket should be created for these orders and investigation undertaken to understand why they have been cancelled in Korber but physically shipped and received by the customer. The CS Management team should be e-mailed with the order numbers so payment can be taken from the customers.

Orders with a carrier scan confirming delivery and Korber status of Waved Error and Mantiki status of on picklist (as per the example orders shown further below) need to be investigated further.
A Service Request ticket should be raised to Balloon One requesting the order is shipped in Korber. An IT – Support (HELP) ticket should also be created requesting the order is dispatched in Mantiki so payment can be taken from the customer.

Orders at any of the following statuses in Körber can be manually shipped:
o Loaded
o Staged

3. Orders shipped in Körber but not shipped in Mantiki

When orders are physically shipped from the warehouse, the status of the order will update to Shipped in Korber and should update to dispatched in Mantiki, but there are occasions when this doesn’t happen. A check is required to investigate and update orders when this is the case.

To find these orders, select Shipped in the Korber Status filter, this will return orders and their corresponding status in Mantiki in the Order Status Mantiki filter. In the example below, there are orders at a Mantiki status of Cancelled, Dispatched, and On Picklist. Any orders at a Dispatched status in Mantiki require no further action.

Orders with a Korber status of Shipped, Mantiki status of Cancelled and a carrier scan confirming delivery (as per the example orders shown further below) need to be investigated further.
An IT – Support (HELP) ticket should be created for these orders and investigation undertaken to understand why they have been cancelled in Mantiki but shipped in Korber. The CS Management team should be e-mailed with the order numbers so payment can be taken from the customers.

For orders with a Korber status of Shipped and Mantiki status of On-Picklist, check the Korber ship date (as highlighted below). If this is today’s date this relates to a timing factor and data within Qlikview not updating in real time with Korber and Mantiki. These jobs can be left and will be updated at the end of the day when the orders are physically shipped from the warehouse.

For any remaining orders that need to be dispatched in Mantiki (e.g., orders at a On Picklist status and not today’s date as per the examples below), export the results to Excel.

The file should then be updated for each order to contain the shipment information as per the example image below.

The shipment information can be found for each order using the Outbound Orders screen in Körber (Menu > Supply Chain Advantage > Advantage Dashboard > Shipping > Outbound Orders). Note the format of the consignment reference for each courier:
o Yodel – 18-character value starting ‘JD…’
o DHL – 14-digit reference starting ‘601…’

Note the column headers should be in the exact same format as shown and the file should be saved with the same naming convention as per the below including the date (ddmmyy) and as a CSV (Comma delimited) file type.

Once the file has been updated, raise an IT – Production CAB ticket attaching the file to get the orders dispatched on Mantiki.

4. Orders at a sent_to_warehouse status in Mantiki but no record in Körber

There are some occasions when orders created in Mantiki do not successfully transfer across to Korber. A check is required to investigate and update these orders when this is the case.

Select the NPrint tab at the top of the dashboard and any orders at a sent_to_warehouse status in Mantiki but have no record in Körber will be shown in the table highlighted below.

Further investigations will be required to understand why any orders have not gone across to Korber from Mantiki. Initially, check the status of the orders in Mantiki to see if they have been cancelled and if so, the orders should clear from this table once Korber has updated, otherwise it will need to be manually cancelled in Korber.
To resolve any orders that have not been cancelled in Mantiki and do require a Korber record, an IT – Production CAB ticket will need to be created requesting the orders are resent to Korber.