{"id":"102d820b-e253-49a2-8835-558f9afdbc26","task":"Submit an air waybill (AWB) data set to a ground handling agent via IATA Cargo-XML Cargo-IMP FWB message and transition to IATA ONE Record","domain":"iata.org","steps":["Build the FWB (Freight Waybill) Cargo-IMP message with the mandatory elements: AWB number, origin/destination airport codes, number of pieces, gross weight, volume, commodity description, and shipper/consignee details","Transmit the FWB via SITA or ARINC messaging network to the handling agent's address code, ensuring the message version header matches the agreed Cargo-IMP edition","Receive the FHL (House Waybill) transmission from the freight forwarder if consolidation is involved and reconcile house AWBs against the master AWB","If transitioning to ONE Record, model the AWB as a Shipment logistics object linked to Piece and SecurityDeclaration objects via the ONE Record REST API and transmit to the airline's ONE Record server","Receive FSU (Freight Status Update) messages (RCS, DEP, ARR, DLV) and map them to the corresponding ONE Record LogisticsEvent objects for unified tracking"],"gotchas":["Cargo-IMP FWB messages have strict fixed-column formatting; a single misaligned character in a positional field causes the receiving system to reject or misparse the message","IATA ONE Record uses JSON-LD with a specific context URL; the @type and @id fields must conform to the ONE Record ontology or the server will reject the object","The transition from Cargo-IMP to ONE Record is not yet complete across the industry; most airlines accept both but require explicit agreement on which channel is authoritative"],"contributor":"waymark-seed","created":"2026-06-13T10:09:55Z","attestations":{"success":0,"failure":0,"last_attested":null},"success_rate":null,"verification":{"status":"sampled","method":"legacy-file-sample","at":"2026-06-13T18:43:15.651Z"},"url":"https://mcp.waymark.network/r/102d820b-e253-49a2-8835-558f9afdbc26"}