Build the FWB XML message according to the IATA Cargo-XML schema, populating the WaybillPrefixNumber, DestinationAirport, and ShipmentTotalGrossWeight elements
Include shipper and consignee details in the Consignor and Consignee elements with IATA-format addresses
Populate the RatingInformation element with ChargeableWeight, RateClass, and TotalCharges in the billing currency
Add CustomsOriginCode, CommodityItemNumber (IATA commodity code), and SpecialServiceRequest elements for any special handling (DG, temperature, live animals)
Transmit the FWB to the carrier or GHA system via Cargo Community System (Cargo-IMP over SITA or IATA Cargo-XML over API) and await the FSU/RCF confirmation
Known gotchas
The FWB replaces the paper air waybill only when the carrier, origin country, and destination country have all opted into IATA e-AWB; verify bilateral agreements before transmitting
IATA Cargo-XML and the older Cargo-IMP FWBA/FWBB message formats are different; confirm which format the receiving system accepts
Chargeable weight is the greater of actual gross weight and volumetric weight; using actual weight when volumetric weight is higher will cause invoice discrepancies
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp