From message snapshots to a shared data state
Traditional air-cargo digitization was built around messaging. Cargo-IMP and later Cargo-XML standardized booking, air waybill, manifest and status messages. Yet each message is still a snapshot. The forwarder keeps one copy, the airline another and the ground handler another; when something changes, a new message is sent and the systems reconcile versions.
ONE Record changes that logic. IATA defines a common data model and secured web APIs that create a single-record view of the shipment. JSON-LD and an industry ontology help systems describe objects consistently; APIs provide direct machine-to-machine access, while the security layer handles identity, authentication and authorization.
The standard is not one centralized industry database. Each company can host and control its own data, granting authenticated partners access only to the objects and fields they need. A forwarder may own booking information, an airline may access selected transport data, and a ground handler may receive delegated access for execution.
Authorized users can retrieve the current state of a logistics object, while publish-subscribe mechanisms notify systems when data changes. By July 2026, the endorsed release included Ontology 3.3.0 and API 2.3.0. IATA also confirmed that Cargo-XML entered containment on 1 January 2026, with no new messages or versions to be developed.
The real value appears in operations, exceptions and compliance
The first operational gain is less re-keying and reconciliation. A shipment can generate data from the shipper, forwarder, airline, ground handler, security provider, customs, trucker and consignee. If every party re-enters pieces, weight, commodity and milestones, mismatches are inevitable. ONE Record allows logistics objects to be referenced and reused across the chain.
Exception management also improves. If a ground handler records an acceptance event or discrepancy, downstream systems can receive a near-real-time notification instead of waiting for a status message, email or portal refresh. The forwarder can protect a connection or resolve customs issues earlier. Visibility matters only when there is still time to act.
Regulatory requirements are another driver. IATA has emphasized that governments need to accept ONE Record data for filings if the standard is to deliver its full value. Advance cargo information, e-commerce house data and pre-loading controls require granular, consistent and early data. Mismatches between house, master and customs records can become delays or compliance issues.
Migration will remain hybrid. Cargo-XML is still widely used in 2026, and IATA's toolkit includes mappings to ONE Record. Forwarders need to consume APIs from ready partners, continue EDI with legacy partners and normalize both flows into one internal shipment model. The real challenge is coexistence without creating another generation of silos.
ONE Record is not a shared file or a centralized database. Its value comes from three layers: a common data model so systems speak the same language; secured APIs so data can be accessed and updated directly; and access control so the data owner decides who may see what. When these layers work together, shipment information no longer needs to be copied repeatedly across emails, EDI messages and portals; authorized parties can work from a controlled, current data state.
Vietnam: From workshops to a cargo community that shares a data language
In Vietnam, the discussion has moved from awareness toward implementation. On 3 July 2026 in Hanoi, Vietnam Airlines and IATA held a workshop on ONE Record and special-cargo handling with more than 100 participants from airlines, freight forwarders, cargo terminals, ground handlers and logistics companies. The breadth of participation reflects the network nature of the standard.
Industry momentum is already material. IATA's 2026 Annual Review says airlines representing more than 70% of global air waybill volume are on track to implement ONE Record, supported by forwarders and technology providers. The Multilateral Data Agreement also reduces bilateral contracting friction by allowing signatories to exchange data under a common confidentiality framework.
Vietnam's timing matters because air cargo is increasingly tied to electronics, high-value components, express traffic and e-commerce. In these flows, a few hours of data delay can mean a missed connection or customs window. When physical cargo moves faster than information, much of air freight's advantage disappears. ONE Record should therefore be treated as operational infrastructure.
For airlines, implementation means connecting booking, AWB, ULD, flight and event data. For TCT, SCSC and ground handlers, the key objects are acceptance, warehouse events, security status, build-up, break-down and handover. For forwarders, the challenge is connecting house-level customer data with airline milestones inside the TMS without returning to email and re-keying.
Customs is the next link. Vietnam can proceed use case by use case: pre-arrival information, e-AWB and house data, dangerous goods or customs-status exchange. Common identifiers and consistent data elements are essential so the same information is not declared repeatedly under different names.
Companies should not begin by buying a platform labelled 'ONE Record'. They should begin with data readiness. Are product and location masters clean? Are events timestamped consistently? Does shipment identity connect house and master records? Who owns each data element and who may change it? An API can move bad data faster as easily as good data.
A practical pilot should use a high-volume lane or partner and measure operational KPIs: fewer manual re-entries, fewer mismatches, earlier exception detection, reuse of regulatory data and better customer visibility. Structured data, shared semantics and clear permissions also create a stronger foundation for AI-based validation, exception prediction and capacity planning.
Air cargo has been digitizing for years, but digitizing documents is not the same as digitizing how parties work together. ONE Record marks a shift from pushing copies of data toward sharing structured, permissioned and continuously updated information.
For Vietnam, the opportunity is not simply to comply with an IATA preference. It is to remove re-keying, reduce mismatches and build a cargo community that describes the same shipment in the same data language. When information can move at the speed of the aircraft, air cargo will truly leave the era of 'sending files' behind.
