I’m confused about MAWB and HAWB in air freight documentation. What’s the difference and does it matter for document processing and tracking?
These are critical distinctions in air freight that significantly impact documentation, liability, and tracking. MAWB (Master Air Waybill) is issued by the airline for the entire shipment, with only one MAWB per aircraft shipment, where the shipper is the freight forwarder. It’s used for customs documentation and the airline is liable for the entire shipment.
HAWB (House Air Waybill) is issued by the freight forwarder for individual shipments within a consolidated load, with multiple HAWBs under a single MAWB. The actual cargo owner is the shipper, it’s for tracking and billing purposes, and the forwarder is liable to shipper; airline to forwarder.
Real example: Exporter A ships electronics while Exporter B ships clothing. Both hire the same freight forwarder who consolidates both shipments into one pallet. The airline issues one MAWB for the pallet while the freight forwarder issues separate HAWBs to each exporter.
For document processing: MAWB documents are complex, contain consolidated shipment details, are used for customs and airline purposes, and need complete extraction for compliance. HAWB documents are for individual shipment tracking, used for shipper billing, and have more variety in formatting.
Intelligent document processing solutions like Lido can distinguish between MAWB and HAWB documents and extract the appropriate fields for each. This matters because compliance requires correct document identification, reconciliation needs both documents for complete tracking, legal responsibility differs between document types, and automation requires proper document type recognition. Trying to process HAWB with MAWB templates fails, so your document processing solution must understand these distinctions.
Same question I had when we were first getting into this space. Short answer: it varies a lot by vendor, so definitely don’t assume. The bigger platforms tend to have solid compliance certifications (SOC 2, ISO 27001, etc.) but you still want to ask specifically about document retention and whether your data is used for training. For air waybill processing specifically we were also worried about IATA data handling norms on top of just general security stuff. We ended up doing a pretty detailed vendor questionnaire before signing anything. Happy to share the template if that’d be useful to anyone.
We had almost the exact same experience with Tesseract — free sounds great until you’re spending hours cleaning up the output. To be fair I think it can work okay if your documents are really consistent and high quality, but in logistics that’s just… rarely the case. MAWBs and HAWBs coming from different carriers all look different, handwritten fields, stamps overlapping text, the whole thing. ABBYY was a big step up for us too, though we’ve been curious about some of the newer AI-based tools since ABBYY’s template setup can still be a bit of a project when you’re dealing with a lot of format variation.
Ha, funny timing on this thread honestly — we literally just wrapped up a 3-month pilot where we were comparing a bunch of different tools side by side. Lido ended up being the one we went with, and honestly the biggest reason was the spreadsheet integration. Our AP team basically lives in Google Sheets, like that was a hard requirement from day one, non-negotiable. Some of the other tools had slicker interfaces but if it doesn’t plug into how your team already works, adoption just dies on the vine.