EDI

FWB vs AWB: turning an air waybill into an FWB EDI message

A master air waybill is a document meant for people. An FWB is the EDI message a carrier's system reads. Getting from one to the other is an extract-validate-emit problem — not a copy-paste one.

Sep 4, 2026· 5 min read· EDI

turns air waybills into clean, validated shipment records — no keying, no OCR clean-up.

Start here

FWB vs AWB: the AWB (air waybill) is the shipment document; the FWB is the electronic message that carries the air waybill's data from a forwarder to a carrier's system. Converting an air waybill into an FWB means reading every field off the document, validating it against real air-freight rules, and emitting a structured FWB/16 or FWB/17 message — not retyping the waybill into a carrier portal.

An air waybill — the PDF, the scan, the photo from a phone — is laid out to be read by a person. An FWB is the opposite: a positional EDI message a computer ingests, field by field, with no room for a stray character. The distance between those two is the whole job. Bridge it by hand and someone keys fields into a portal or a per-carrier template, one shipment at a time; a single mis-keyed weight or airport code can land downstream as a rejected message or a mis-billed charge.

What "AWB to EDI" actually converts

Three things are in play, and it helps to keep them separate:

  • The source document — the master air waybill, however it arrives: a scan, a PDF, a photo, or an email attachment.
  • The structured record — one clean, validated set of fields extracted from that document. This is the thing everything else reads from.
  • The output message — the FWB/16 or FWB/17 EDI text, generated from the record so it reflects exactly what was validated.

Because every format reads from the same record, they can't disagree with each other: the JSON, the FWB EDI, and the spreadsheet all describe one shipment, not three slightly different versions of it.

With , you can turn a captured MAWB straight into a carrier-ready FWB message.

Start here

Extract, then validate — before you emit

Extraction reads the fields; validation is where a wrong field gets caught before it becomes a wrong message. The air waybill number is checked with the IATA MOD-7 check digit, the airline prefix and airport codes are checked for shape and consistency, and the weights and piece counts are cross-checked against air-freight logic. A field that fails surfaces as an exception rather than flowing silently into the FWB.

extract → validate → emit · 999-12345675
# master air waybill 999-12345675 · CONTOSO FREIGHT · HKG → JFK
awb_number   = "999-12345675"   # prefix 999 · serial 1234567 · check 5
check_digit  = valid            # 1234567 mod 7 = 5
origin       = "HKG"
dest         = "JFK"
pieces       = 12
gross_weight = "480.0 KG"

# one validated record → many formats, all reading from it:
emit FWB/17  ready   # or FWB/16 on request
emit JSON    ready
emit CSV     ready

Validating first means the FWB is built from a record whose fields have already been checked. When something doesn't add up — a check digit that doesn't resolve, a weight that reads implausibly — it's flagged for a person to look at, so it can be fixed before you send a message a carrier would reject.

Generated, not transmitted

AWBGuru returns the FWB/16 or FWB/17 message text; sending it to a carrier is your step, over your own connection. It holds no airline credentials. You get a clean, validated message on your existing rails — the transmission stays entirely in your hands.

Frequently asked

What's the difference between an air waybill and an FWB?

The air waybill is the transport document; the FWB is the EDI message that carries that waybill's data from a forwarder to a carrier's system. One is meant to be read by a person, the other by a computer — converting between them means extracting and validating every field, not just changing the file type.

Does AWBGuru send the FWB to the airline?

No. AWBGuru generates and returns the FWB/16 or FWB/17 message from the validated record; you transmit it through your own rails. It holds no airline credentials.

Which output formats are available?

JSON and XML over the API, EDI FWB/16 and FWB/17, and CSV and XLSX spreadsheets — all generated from the same validated record, so they can't disagree with each other.

How do you turn an AWB into an FWB?

Read every field off the air waybill, validate it against air-freight rules, then build the FWB/16 or FWB/17 message from that one checked record. For a master air waybill, AWBGuru does all three from a scan, PDF, or phone photo; you send the message to the carrier over your own connection.

Turn a waybill into a message.

Start with 30 free scans — no card. Drop in a master air waybill and get back a validated record plus FWB/16 or FWB/17 you can send over your own rails.

← All resources