Page tree

Skip to end of metadata
Go to start of metadata

An incident occurs when some handlings do not match with expectations of the system. For example a quantity deliverd of 490 when the system expected a quantity of 500. 

An incident can be created manually or automatically. 


the following subjects will be described:




Under the tab incidents add a new record and click choose an incident type. The description will be automatically the same as the Incident Type. 

The creation date will be inserted automatically once the incident is saved. 



There are three ways an incident can be created automatically. 

  1. Close a handling unit
  2. Transfer a handling unit
  3. Adjust handling unit

If by any of these three a quantity is changed an incident is created. This could be because some goods of the handling unit is damaged or they are simply lost. 

We are going to adjust a handling unit with status storage. Changing a planned Handling Unit does not create an incident because planned handling units can still be adjusted without problems. 





Once a handling unit is adjusted the info column changes and it shows an eye. It means an incident is created and has status open. Hoover over the eye for more information about the incident. And an email with the HU and incident number is sent to whoever is in charge of this kind of incident. 










In the overview Incidents you can view the automatically created incident. It shows Stock Difference as we changed the quantity that is currently stored. 

Next to it we can see all the differences between original values and actual values. The changed values are highlighted.









The next step is to determine what has to happen with this incident. Right click on an incident shows the actions that can be taken. Contact a customer to ask if the fault may have been caused by them. Process incident changes to either accept or decline the changes that have been made. 

If you cancel the incident all values will be set to original values. 














Incident Dashboard

Automatic Incident types

Incident typeDescription
Stock DifferenceDuring storage quantities of a handling unit changed.
Inbound DifferenceWhen arrived at warehouse the handling unit details do not match with the planned handling unit details. Could be any of the values shown in the image above.
Internal CMR DifferenceThe CMR attached by the Logistic service provider does not comply with the handling units.
Internal Customs goods differenceCustoms filled in by the LSP does not comply with handling unit goods.
External CMR DifferenceThe CMR attached to handling units by an external party does not comply with the handling units.
External Customs goods differenceCustoms filled in by an external party does not comply with handling unit goods.
Damage StockStock has been damaged, could be the issue if a quantity is changed.
Damage on outboundOutbound handling units are (partly) damaged
Damage on inboundInbound handling units are (partly) damaged



Status of incidents

OpenAfter an incident has been created it is assigned the status open
Partially approvedIf more than one value has been changed and only one or a few of these is approved
ApprovedAll changes have been approved
Partially declinedIf more than one value has been changed and only one or a few of these are declined
DeclinedAll changes have been declined
CancelAn open incident can be cancelled, if it has any other status it cannot be cancelled.


  • No labels