Skip to content
  • There are no suggestions because the search field is empty.

Why is the FWB/FHL  different from the printed AWB or the shipment data in Scope? 

There are different scenarios as to why the shipment data might be different to the printed AWB and/or the FWB that is sent to the airline. For example, the value of the SLAC filed in the shipment and the FWB/FHL could be different. 

General procedure

  • Scope always transmits data from the AWB, not from the shipment.
    An exception is a Coload-in, where Scope doesn't have an AWB object.
  • In general the shipment data is in sync with the AWB data, if no changes are made in the AWB editor. In that case the AWB and the FWB will reflect the information entered in the shipment. This not only holds for SLAC but for any other values as well. 
  • Not all AWB data is shown in the FWB message - here is why: 
    Why don't I see all AWB data reflected in the FWB message?

Changes that lead to deviating data

  • Checkbox in partner profile activated
    In the partner profile roles Forwarding Customer and Agent you have the option to alter the default address for the AWB as well as for e-AWB by editing the “custom AWB address” and “custom e-AWB address”.
         In case these are different from the default partner address, then this would be used for the printed AWB and the FWB.
  • Changes made to shipment data in the AWB Editor
    In addition to the above-mentioned change to the default address, you also have the option to alter information in the AWB editor itself. These changes will have priority over the shipment data and also over the custom address set in the partner profile.