How to Automate the Air Waybill (eAWB)
Author:
Pamela
Published On:
1 min read

How to Automate the Air Waybill (eAWB)
Automating an air waybill connects your freight software to carrier systems and IATA standards, so the Master and House AWB populate from your booking and transmit electronically, instead of being typed by hand and couriered as paper.
TL;DR
What it is: producing and transmitting the air waybill electronically (eAWB), so the MAWB and HAWB come from your booking and go to the airline as data, not paper.
Three approaches: auto-populate from freight software (TMS/ERP), extract inbound data with AI/OCR, and transmit via an IATA e-AWB integration.
The workflow: sign the IATA agreement and set up carrier codes, populate the shipment, run validation, then file the MAWB to the airline first and the HAWBs after.
The messages: the master waybill goes as an FWB message, the house manifest as FHL.
Why it matters: eAWB is the default on feasible trade lanes, yet a large share of the industry still handles paper, so the laggards lose speed at origin.
With CargoEZ: the HAWB generates from the shipment, AWB stock is managed by airline prefix, and the eAWB transmits from the same ops file.
Why this matters
eAWB has been the default contract on feasible trade lanes since 2019, yet IATA put global penetration at about 58.5% in 2018, with adoption held back by customs rules and the limits of small and mid-size forwarders' tools. The forwarders still on paper lose time at origin and risk running out of AWB stock mid-week.
Penetration via IATA / CAAS; adoption barriers via Air Cargo Week. Figures are dated; confirm current IATA data.
The air waybill is the contract of carriage for air cargo, and for a forwarder it comes in two layers: the Master AWB (MAWB) the carrier issues for the consolidation, and the House AWB (HAWB) the forwarder issues to each customer. Automating it means the data is populated from your booking, validated, and transmitted to the airline as an electronic message, instead of being typed onto a paper form and couriered. This guide covers the three approaches, the step-by-step filing workflow, the tools, the benefits, and what trips forwarders up.
eAWB automation tools at a glance
These are the platforms forwarders use to file eAWB. We explain how automation works below; confirm features and pricing with each vendor, and see our best eAWB software roundup for the full buyer's guide.
Platform | Best for | eAWB automation strength | Note |
CargoEZ | Small–mid forwarders | Generates the HAWB from the shipment, manages AWB stock by prefix, transmits the FWB | One record, forwarder-built |
CargoWise | Enterprise forwarders | Auto-populates MAWB/HAWB from booking records | Global TMS |
Magaya | Forwarders that also run a warehouse | eAWB filing from the forwarding file | TMS + WMS |
Logitude World | Forwarders | Dedicated eAWB module | Forwarder TMS |
Riege Scope / Descartes eAWBLink | Multi-airline messaging | eAWB/FWB to airlines and CASS | TMS / network |
SmartAWB / AWBEditor | Low-cost or ad-hoc | Browser-based AWB/FWB editor | Standalone (print/transmit only) |
Directional comparison for US freight forwarders. Verify current capabilities and pricing with each vendor.
What is an eAWB?
An electronic air waybill (eAWB) replaces the paper AWB with an electronic record exchanged between the forwarder and the carrier, under IATA Resolution 672, which made eAWB the default contract of carriage on feasible trade lanes. Instead of a bilateral agreement with each airline, forwarders sign the multilateral e-AWB agreement once. The master waybill is transmitted as an FWB message and the house manifest as an FHL, and the same AWB number serves as the shipment's tracking key.
58.5% eAWB penetration (IATA, 2018); a large paper tail remains
2019 eAWB the default on feasible lanes (IATA Resolution 672)
FWB + FHL the master waybill and house manifest messages
MAWB / HAWB carrier's master vs the forwarder's house waybill
The three ways to automate the air waybill
Approach | What it does | Tools |
Freight software (TMS/ERP) | Auto-populate the MAWB and HAWB straight from booking and customer records | CargoWise, Magaya, CargoEZ |
AI & OCR extraction | Pull weight, dimensions, shipper details, and commodity codes from incoming invoices or PDFs | Vision Parser, custom OCR pipelines |
IATA e-AWB integration | Sign the multilateral agreement and use carrier plugins or direct API to transmit digitally | IATA multilateral e-AWB, airline links/CASS |
Most forwarders lean on the first and third together: the software builds the waybill from the shipment, and the IATA integration transmits it to the airline. OCR extraction is for when the data arrives from outside as a PDF or invoice.
Step by step: filing an eAWB from your software
Establish agreements & set up the system: Sign the IATA e-AWB agreement, enter carrier codes, and enable the AWB/eAWB module.
Populate shipment data: Import booking details, flight schedule, routing legs, and piece/weight/dimensions; pick shipper and consignee from the address book.
Run validation checks: Let the validation engine flag missing compliance fields, weight discrepancies, and customs errors before you send.
Submit electronically: For consolidations, file the Master AWB to the airline first, confirm acceptance, then file the House AWBs. Send to transmit the eAWB and receive a transaction ID and status.
The flow, end to end:
Booking → Populate MAWB / HAWB → Validate → File MAWB (FWB) → Confirm → File HAWB (FHL) → Status
How CargoEZ does it: CargoEZ generates the HAWB from the shipment record, tracks AWB stock by airline prefix so the export desk never runs dry mid-week, validates the data, and transmits the FWB to the airline, all from the same file that runs the booking and customs. The AWB number then carries into tracking.
eAWB vs paper AWB
Paper AWB | eAWB | |
Transfer | Physical document, couriered | Electronic FWB message to the airline |
Timing | Waits on paper at origin | Transmitted at booking, ahead of cargo |
Data | Re-keyed by hand | Mapped from the shipment file |
Tracking | Manual | AWB number is the tracking key |
Basis | Bilateral, per airline | One multilateral IATA agreement |
The benefits of automating the air waybill
Faster at origin. The waybill transmits ahead of the cargo, so handover does not wait on paper.
Fewer errors. Data mapped from the shipment beats re-keying a form, and validation catches weight and compliance gaps before send.
No AWB stock-outs. Managing stock by airline prefix keeps the export desk from running dry mid-week.
Lower admin cost and faster clearance. IATA cites reduced administrative cost and faster clearance from the shift to eAWB (Brazil eAWB milestone, 2025).
One record. The HAWB, AMS, and tracking all draw on the same shipment, so nothing is entered twice.
The cost of paper and manual AWBs
Slow release. Paper originals hold up handover at origin and destination.
Re-keying errors. Hand-typed weights and party details drive airline rejections and corrections.
AWB stock-outs. Running out of pre-assigned AWB numbers mid-week can ground an export desk.
No live tracking key. Without the electronic AWB, status updates stay manual.
What trips forwarders up (and how to avoid it)
eAWB is more an implementation project than a feature switch. The common snags:
Agreement and codes. You need the multilateral e-AWB agreement signed and the right carrier/CASS codes configured before anything transmits.
Per-airline, per-station activation. eAWB has to be enabled airline by airline, and sometimes station by station, not switched on globally.
Message quality. Poorly formed FWB/FHL messages get rejected; validation before send is what keeps acceptance rates high.
Lanes that still want paper. Some routes or customs regimes still require a physical document, so keep the ability to print.
How CargoEZ automates the air waybill
CargoEZ treats the eAWB as part of the shipment, not a separate editor. The House AWB generates from the shipment record, AWB stock is tracked by airline prefix, the data is validated, and the FWB transmits to the airline, then the AWB number carries into tracking. Because the same record also runs the AMS filing for air cargo and the rest of the document set, the waybill data is entered once and reused.
See the eAWB software overview, its ocean sibling on bill of lading automation, how it fits your wider freight forwarding workflow automation, or book a demo to file an eAWB straight from a shipment.
How do I automate the air waybill?
Use freight software to auto-populate the MAWB and HAWB from your booking, validate the data, and transmit it to the airline through an IATA e-AWB integration. Sign the multilateral e-AWB agreement and configure carrier codes first.
What is the difference between MAWB and HAWB?
The carrier issues the Master AWB (MAWB) for the whole consolidation; the forwarder issues a House AWB (HAWB) to each underlying customer. For consolidations you file the MAWB to the airline first, then the HAWBs.
What are FWB and FHL messages?
FWB is the electronic master air waybill message sent to the carrier; FHL is the house manifest message listing the house waybills under a master. Automation builds and transmits both from the shipment data.
Is eAWB mandatory?
eAWB is the default contract of carriage on feasible trade lanes under IATA Resolution 672, but some lanes and customs regimes still accept or require paper. Keep the ability to print where a route demands it.
Do I need a separate agreement with each airline?
No. Forwarders sign the IATA multilateral e-AWB agreement once instead of a bilateral agreement per carrier, then activate eAWB airline by airline (and sometimes station by station).
Does the AWB number work for tracking?
Yes. Once the eAWB is filed, the AWB number serves as the shipment's tracking key across the carrier's milestones.
Author
Author information unavailable
Don't forget to share this blog!


