MAWB vs HAWB: what a consolidation actually is

A Master Air Waybill (MAWB) is the transport contract between the freight forwarder and the airline for a whole shipment. A House Air Waybill (HAWB) is what the forwarder issues to each individual shipper for their portion of the goods. When one MAWB covers many shippers' goods bundled under a single master, that's a consolidation — and the MAWB references a manifest of the underlying house bills rather than a single shipper's cargo.

The distinction is easy to state and expensive to get wrong when you're extracting data. A straight MAWB — one master, one shipper, one commodity — reads like a single record. A consolidation looks like the same document on the surface, but underneath it stands for many shipments at once. Treat the two the same and you produce a clean-looking record of numbers that were never one shipment's numbers to begin with — the kind of error that surfaces downstream as a mis-billed charge or a customs manifest that won't reconcile.

MAWB vs HAWB, in one breath

Two contracts sit on top of each consolidated shipment, and they answer to different parties:

• MAWB — forwarder ↔ airline. One master per shipment. It's the contract of carriage the airline flies against, and on a consol it covers the whole bundled load as a unit.
• HAWB — forwarder ↔ shipper. One house bill per underlying shipment. Each shipper gets their own, describing only their goods; the forwarder is the one who ties them all to a single master.

So a consolidation is many house bills riding under one master. The house bills carry the per-shipper detail; the master carries the reference to the manifest that lists them. Nothing about that arrangement is exotic — it's how forwarders move small shipments economically — but it means the master and the house bills describe different things and must not be read as if they were the same field set.

Why this matters for data extraction

If your extraction assumes every MAWB is a single-commodity shipment, a consolidation quietly breaks that assumption. Which of the ten shippers' names becomes "the shipper"? Which commodity is "the commodity"? Which HS code? There is no single right answer, because a consol was never one shipment. Force a single-commodity read onto it and you get a confidently wrong record: real values, arranged into a shape the document never had.

That's why the first question AWBGuru asks on any master waybill is: is this a consolidation? That decision runs before any single-commodity logic does. Get it right and the rest of the read follows the correct branch; get it wrong and every downstream field inherits a false premise.

How you can tell a consolidation

A consolidation usually announces itself on the face of the master. The nature-of-goods field often reads something like CONSOLIDATION AS PER ATTACHED MANIFEST instead of naming a commodity; there may be an explicit house-bill count, or CONSOL markings near the description. Take this synthetic master — 999-44881073, CONTOSO FREIGHT as forwarder, ICN → LAX:

# master air waybill 999-44881073 · CONTOSO FREIGHT · ICN → LAX
nature_of_goods = "CONSOLIDATION AS PER ATTACHED MANIFEST"
house_bill_count = 7
markings         = "CONSOL"

# resolves before any single-commodity logic runs:
is_consolidation = true
  → single-commodity identification skipped
  → record flagged as a consolidation master
     (references 7 house bills; e.g. NORTHWIND TRADERS is one shipper of many)

Because is_consolidation resolves to true, the read does not try to collapse seven shippers into one commodity line. The master is recorded as what it is — a consolidation that stands in front of a manifest — rather than a single-commodity shipment that happens to have an odd description.

What AWBGuru does with it

AWBGuru detects consolidation first, at the master level. When a MAWB is a consolidation, it's treated as a consol: the extractor doesn't mis-map it onto a single commodity, shipper, or HS code, and the consolidation flag itself is written into the structured record and factored into the document confidence score. That helps ensure a consol is recorded as a consol — not silently flattened into a shape it never had.

A straight single-shipment MAWB proceeds down the ordinary path: one shipper, one commodity, the usual field checks. The branch is chosen once, up front, from the evidence on the document — and everything downstream reads the correct kind of record.