...
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
...
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
...
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.
...
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.