No cargo information visible in Cargo Controller Import

In most cases, the information flow continues as expected when you see a B/L registered in Cargo Controller Import. In some scenarios, the information flow is not (yet) available. In this article we explain a number of scenarios.

Scenario 1: Basic or Extended B/L tracking

A shipping line, a shipping agent or client can grant a commercial release (via the Secure Chain) to your organisation without your organisation tracking the container on the corresponding B/L within Cargo Controller Import. Based on this data, Portbase retrieves information that is available within the Secure Chain, a Basic B/L. Below is an example of a Basic B/L.

A Basic B/L shows only information related to the commercial release. Goods information or the vessel voyage is not shared within a Basic B/L. A Basic B/L is not registered as a paid transaction.

Solution: Adjust the organisation setting.

For most organisation, the main administrator has set B/Ls to always be tracked as Extended . This means that if this scenario occurs, it is immediately fully linked and all available information is retrieved. An Extended B/L is registered as a paid transaction.

Would you like to know more about Basic B/Ls and the extensive, paid Extended B/Ls? Then read more here . 

Scenario 2: Import manifest not yet available

Within Cargo Controller Import, a B/L can already be tracked from the moment you have the master B/L number and at least 1 equipment that is registered on it. If Portbase already has the import manifest from the vessel agent or shipping agent, then this information is available immediately. In this scenario, that is not (yet) the case; we then show 'Pending' on the web screen in various places in the manifest.

If you enter a B/L via web screens or via the API connection, it is immediately indicated if the information is not there yet. On the web screen we then additionally request information about the vessel on which the cargo would have been manifested.

Solution: Wait until the import manifest is available

In most cases you do not need to take any action; Portbase will inform you automatically when the manifest for this cargo becomes available.

Below is a flow chart about how import manifest data works to Cargo Controller Import within the API implementation:

This scenario can also be caused by scenario 3.

Scenario 3: B/L number not known in the manifest

There are three reasons why a B/L will not be updated as expected when tracking a B/L:

1. Typo in the tracked B/L

   Solution: Review the B/L number. Delete the incorrect B/L.

   Via 'Details', press the 'Delete' button and the incorrect B/L will be deleted.

   Track the B/L again to still receive the required data.
    

2. The tracked B/L is not a Master B/L (or a split B/L)

   Solution: Check the B/L number with the shipping line. Delete the incorrect B/L.

   Via 'Details', press the 'Delete' button and the incorrect B/L will be deleted.

   Track the B/L again to still receive the required data.
    

3. The B/L has not been loaded and has not been included on the manifest.

   Solution: Wait until the import manifest is available.

   If the B/L has no typos, is not a split B/L, but was purely loaded on a later sailing, then waiting is the only option.

   Portbase will automatically receive the import manifest that includes the unique combination of B/L and equipment number. We will then immediately send the correct updates. 

   If you had linked a vessel, this will be corrected automatically after the import manifest has been submitted on the correct vessel. 

Would you like to know more about managing your B/Ls within Cargo Controller Import? Then read more here .