IN Brief:
- CargoCONNECT Track & Trace now feeds standardised shipment events from more than 260 airlines into Scope.
- A 2026 pilot achieved up to 91.3% export event coverage and 90.2% import coverage.
- The integration supports IATA and non-IATA forwarders across direct, consolidated, back-to-back, import, and export shipments.
Riege Software has expanded its CargoAi partnership by integrating CargoCONNECT Track & Trace into Scope, bringing standardised shipment milestones from more than 260 airlines directly into the transport management system used by freight forwarders.
The new connection forms part of Scope’s Airline Messaging Premium capability and supports import, export, consolidated, back-to-back, and direct air shipments for both IATA and non-IATA forwarders. Events are retrieved and normalised inside Scope rather than requiring operators to search individual airline sites and copy updates into the forwarding record.
Riege and CargoAi say the 2026 pilot achieved event coverage of up to 91.3% for exports and 90.2% for imports. Coverage varies according to the airline and the underlying shipment data, so the integration does not remove every gap, but it expands the proportion of milestones that can be handled automatically.
The supported event set includes FWB, RCS, MAN, DEP, ARR, RCF, NFD, and DLV messages, covering stages from booking and cargo receipt through departure, arrival, notification, and delivery. That gives the forwarder a shipment view extending beyond the aircraft movement itself.
The distinction is operationally important. A flight can arrive on time while the cargo remains unavailable because of unloading, handling, customs, or breakdown delays. Forwarders need to know when the shipment has moved through each usable milestone, not simply when the aircraft reached the destination airport.
Incomplete event data has traditionally created manual work. Operations teams may have to check a carrier website for actual departure or arrival, compare that status with the transport management system, and then update the record before answering a customer query. Repeating that process across hundreds of shipments turns a visibility gap into a labour problem.
Embedding the feed inside Scope removes some of those repetitive checks and keeps the operational record closer to the external data source. The same shipment can move from rate search and booking into execution monitoring without staff shifting between several platforms, because Riege and CargoAi already cooperate on digital airfreight rates and booking.
Import flows are a particular focus. Shipment information often becomes more fragmented once cargo leaves origin and responsibility passes between airline, ground handler, destination forwarder, customs, and consignee. Missing arrival or cargo-availability milestones can disrupt truck planning even when the international flight itself operated normally.
More complete import data allows collection planning to start from the same system used to manage the forwarding job. If a shipment is delayed or a milestone fails to arrive, the missing event becomes an exception rather than the default condition requiring somebody to search manually.
The commercial value will depend on data quality as well as carrier count. Coverage across more than 260 airlines gives the integration breadth, but forwarders will judge it on the routes they actually use and on how quickly key events arrive. A late or inconsistent milestone can still leave the operation making decisions on stale information.
Standardisation is therefore as significant as aggregation. Airlines and handling partners can expose data through different formats and processes, while a transport management system needs a consistent event structure if it is to trigger workflows reliably. CargoAi’s API acts as the translation layer before the data reaches Scope.
That can support more than customer tracking. Reliable events can feed exception management, warehouse planning, truck scheduling, performance reporting, and internal service metrics. The useful outcome is not another map showing where a shipment might be, but a cleaner operational record that downstream processes can use without rekeying information.
The 90%-plus pilot figures also show the limit of automation. Some shipment events will still be unavailable because the originating airline or handler has not produced them, the data is delayed, or the shipment record cannot be matched correctly. Operations teams still need procedures for those exceptions rather than assuming API connectivity guarantees complete visibility.
Measurement after rollout will be more revealing than the number of connected carriers. Forwarders can compare the share of shipments requiring manual status checks, the time spent resolving missing milestones, and the speed of customer updates before and after activation. Those are mundane operational measures, but they determine whether the integration removes work or merely changes where staff look for the same information.
Riege’s latest integration pushes airfreight software further towards a single operational environment spanning commercial and execution data. The technical step is an API connection; the practical measure is whether staff spend less time hunting for milestones and more time managing the smaller number of shipments that genuinely need intervention.
