Services

Shanghai Air Cargo Control Tower & AWB Monitoring

Within an agreed written service scope, UDB Shanghai coordinates booking and AWB milestones for commercial air cargo, including booking confirmation, airport handover, departure, arrival and document milestones. The team consolidates status updates from identified carriers, airports, handlers, customers and other responsible parties, follows up missing information and escalates exceptions to designated contacts at the agreed reporting frequency. The public Tracking page only validates reference formats and links to available public tracking channels; it is not a carrier or airport system, and UDB does not create or guarantee live carrier data.

What UDB Shanghai monitors and coordinates

  • Define the agreed milestones, reporting contacts, update frequency and escalation path in writing.
  • Consolidate status updates and document requests received from identified carriers, airports, handlers, customers or other responsible parties.
  • Follow up missing information, handover issues and milestone deviations, and coordinate the relevant responsible parties.
  • Issue scheduled status reports and escalate exceptions within the written service scope.

What this service does not provide or guarantee

  • The website Tracking page is not a live carrier or airport tracking system.
  • UDB Shanghai does not create, infer or alter a status that has not been provided by an identified responsible source.
  • UDB Shanghai does not guarantee live data, carrier milestone timing or a response SLA beyond the written service scope.

Primary Shanghai air gateway

  • Shanghai Pudong International Airport (PVG)

Information required to set up monitoring

  • A valid booking reference or AWB, and a UDB reference if one has been assigned.
  • Shipper, consignee, route, carrier or handler if known, and planned departure and arrival timing.
  • Milestones to be monitored, designated contacts, reporting frequency and escalation thresholds.
  • Relevant documents, known exception details and responsible-party contacts.

Control-tower setup and monitoring process

  1. Confirm the booking or AWB reference, route, baseline milestones, contacts, reporting frequency and escalation path.
  2. Record the baseline plan and latest status supplied by identified responsible sources.
  3. Monitor the agreed milestones, follow up missing information and coordinate exception escalation.
  4. Issue scheduled status updates and close the monitoring record when the written service scope is complete.

Content responsibility

Responsible team
UDB Shanghai Operations
Last reviewed
2026-08-28

FAQ

Does the website Tracking page show live carrier or airport data?

No. It validates reference formats and links to available public tracking channels. Operational status comes from the carrier, airport, handler or another responsible operating party.

Which references can be included in control-tower monitoring?

A valid booking reference or AWB is normally required, together with a UDB reference if one has been assigned. The shipment must also be within an agreed written monitoring scope.

How are reporting frequency and escalation response times agreed?

They are defined in the written service scope for the shipment, including designated contacts, reporting frequency, escalation conditions and the escalation path. The website’s general response target does not replace the shipment-specific monitoring scope.