Skip to content
English
File Service Request Customer portal
Go to Riege Status page
  • There are no suggestions because the search field is empty.

Reliable automatic tracking for air freight main carriage

Tracking the main air freight leg is often challenging: the availability of events via airline interfaces is inconsistent and ranges from “not available” to “occasional” to “good” With an additional feature, manual follow-up work is no longer required, and automatic event processing is fully supported by a dependable, near‑real‑time data connection to specialized portals: Airline Messaging Premium.

To ensure that airline events are supplied as comprehensively, reliably, promptly, and with as much coverage as possible, Scope uses the “Airline Messaging Premium” feature to process corresponding data from selected external commercial data providers.

Shipment coverage

Airline Messaging Premium covers approximately 200 airlines and automatically subscribes to event updates after entering the IATA AWB number for

  • consolidation shipments,

  • back-to-back shipments, and

  • IATA direct shipments,

in each case for

  • air freight export,

  • air freight import,

  • simple shipments (air freight type).

Airline Messaging Premium does not require IATA/CASS agent registration and is also fully available to non-IATA forwarders without any impediments.

Order

If you are interested in the “Airline Messaging Premium” feature, please contact us by email at sales@riege.com.

Pricing and contract model

To ensure the most comprehensive possible coverage of the main air freight leg, we rely on external commercial data providers. Based on the cost structure of these providers, Riege Software charges a fee per unique IATA AWB number for which main-leg events are subscribed. A separate contractual agreement between the forwarder and these data providers is not required.

Which events are covered and which milestones are completed automatically?

Airline 

Airline Messaging Premium provides with event data from airlines for the main airfreight leg. Such events are identified by a “CIMP” prefix. The key events are

  • CIMP_BKD: Consignment booked on a given flight
  • CIMP_FOH: Consignment is on hand at export airport ground handler
  • CIMP_RCS: Consignment received from Shipper / Consignment Ready for Carriage
  • CIMP_MAN: Consignment manifested (usually by GHA) on a given flight
  • CIMP_DEP: Consignment has departed on a given flight and location
  • CIMP_ARR: Consignment has arrived on a given flight and location
  • CIMP_RCF: Consignment physically received from a flight (unloaded into WHS)
  • CIMP_NFD: Consignee or his agent informed of arrival of shipment
  • CIMP_DLV: Consignment has been physically delivered to consignee or his agent

The level of detail and the number of events may vary depending on the airline.

It is recommended to use a template type in the milestones of tracking templates. Template types for milestones have predefined triggering events that automatically complete the milestone based on the CIMP events listed above. Triggering events can be configured individually for each milestone.