AWB data is the set of structured fields printed on an air waybill: the 11-digit AWB number, the shipper, consignee and agent, the routing and flights, the piece count and weights, the description of goods, the charges, and the handling and execution details. It is the information a carrier, a forwarder and a customs system each use to move, bill and clear one air shipment.
An air waybill (AWB) is the transport document and contract of carriage for goods moving by air, laid out to the IATA standard form so the same box means the same thing on every carrier's paper. A Master Air Waybill (MAWB) is the forwarder's contract with the airline; a House Air Waybill (HAWB) is the forwarder's contract with each shipper, and several house bills under one master make a consolidation (see MAWB vs HAWB). The field set below is the same on both; only the parties differ.
The AWB number
The AWB number is 11 digits in a 3–7–1 layout: a 3-digit airline prefix, a 7-digit serial, and one check digit. The prefix identifies the issuing carrier (a carrier can hold more than one). The check digit equals the serial modulo 7, so the number can be verified by arithmetic alone.
# 999 is a stand-in prefix, not a real carrier prefix = 999 serial = 5720493 check = 2 5720493 mod 7 = 2 ✓ equals the printed check digit → valid
On the form the number is printed top-right as the prefix, a dash, then the 8 digits of serial plus check: 999-57204932. Systems usually store the prefix and the 8-digit block separately. A misread or transposed digit almost always changes the remainder, so a bad number is caught before it reaches a carrier; the rule and its limits are covered in Reading the IATA check digit.
With , you can turn every field on your waybills into clean, structured data.
Start hereField-by-field reference
Grouped the way the form is laid out. The tag on the right is the usual printed format; the note flags what breaks when a field is misread.
Where AWB data flows
AWB data starts life on paper or as a PDF: the forwarder's system prints the form, the parties sign it, and copies travel with the cargo. The same fields then have to reach carrier and customs systems, which is where capture comes in: reading the boxes off the document into one structured record. That record is what gets encoded as an FWB message, the IATA Cargo-IMP message that carries air waybill data to a carrier's system. Two revisions circulate, FWB/16 and FWB/17, and the receiving party decides which it accepts; Cargo-XML's XFWB is the newer encoding of the same message, still mid-migration. The carrier builds its own AWB record from that message; customs consumes the same data through the manifest and the declaration.
An electronic air waybill (e-AWB) replaces the paper contract with the electronic record: the FWB message becomes the contract of carriage, and a paper AWB need not accompany the shipment. IATA made the e-AWB the default on enabled trade lanes in 2019, though paper still circulates where a party, a lane or a customs authority requires it. For the data itself nothing changes; the e-AWB shifts which copy is authoritative, not which fields exist.
Common AWB data errors
Most bad waybill data is not illegible. It is legible and internally inconsistent, which is why the fields are checked against each other rather than read in isolation:
- Check digit fails. The serial mod 7 does not equal the printed check digit; usually a transposed or misread digit.
- Prefix and flight disagree. The prefix belongs to one carrier and the 2-letter code at the front of the flight number to another. Carriers hold prefix sets, so this is a membership check, not equality.
- Routing that cannot be right. An airport code not in the IATA location table, or a departure equal to the destination.
- Chargeable weight below gross. Impossible by definition, since chargeable is the greater of gross and volumetric. Almost always a misread or transposed value.
- Format slips. A rate class that is not one valid letter (the K/L unit taken as a rate class), an HS code with the wrong digit count, a currency that is not ISO 4217, a piece count that is not a positive integer, or a blank shipper, consignee or gross weight.