Freight-native answers, in depth
Air waybill data export: History, re-export, and FWB EDI
Air waybill data export from History — a searchable record of every processed document. Re-export any slice, any time, as CSV, XLSX, JSON, XML, or FWB v16/v17 EDI.
Air waybill data extraction, explained
Air waybill data extraction turns a scan, PDF, or phone photo of an AWB into a structured, validated record. What it means, why validation — not OCR — is the hard part, and what comes out.
Confidence calibration: what AWBGuru's confidence score really means
Every field carries a confidence score the model self-reports. Here's what that number means, how the auto-export threshold uses it, and why calibration here watches real corrections instead of rescaling the score.
Team workspace roles: how owner and member work in AWBGuru
One workspace is one company — your team shares the same air waybills, history, and settings. Two roles, Owner and Member, and usage-based pricing, so you can invite the whole team without a seat cap.
Benchmarking straight-through processing: the KPIs for a cargo capture desk
Four numbers tell you whether a capture desk is working: STP rate, touch time, exception rate, and cost per AWB. What each one means, how to baseline it in a week, and what good looks like.
ULD codes explained: how to read a Unit Load Device identifier
A ULD code packs a container or pallet's type, size, and shape into three letters, then adds a serial and an owner code. Once you can read AKE or PMC on sight, the loading data on a manifest stops being a jumble.
Prepaid vs collect air waybill charges: PP, CC, and the charge fields
Every charge settles one of two ways — prepaid at origin or collect at destination. The Charges Code, the weight and other-charges fields, and each line's PP/CC entitlement decide who gets billed and whether the FWB reconciles.
The e-AWB mandate: what going paperless actually changes
The e-AWB made the electronic record the contract of carriage on enabled lanes. Going paperless removes the paper original — not the job of getting clean, validated data into the FWB behind it.
FHL vs FWB: the house-manifest message and when you need both
FWB carries the master air waybill; FHL carries the house waybills under it. A direct shipment needs only the FWB — a consolidation needs both, and customs wants the house level.
Special Handling Codes (SHC): the three-letter codes on the air waybill
PER, AVI, ICE, CAO — the Special Handling Codes in the air waybill's handling box tell everyone downstream how the cargo must be treated. Reading one wrong is a safety miss, not a typo.
What is AWB data capture, and why OCR alone isn't enough
Turning an air waybill PDF, scan, or photo into a structured, validated shipment record — the full path from intake to output, and why OCR is only the first step.
AWB data explained: every field on an air waybill
AWB data is the set of fields on an air waybill — the AWB number, parties, routing, pieces and weights, charges, and handling text. A field-by-field reference.
AWB capture software compared: OCR vendors vs a validating engine
How to compare AWB capture software across three categories on eight criteria — from MAWB field coverage and freight-rule validation to output formats and pricing.
Air waybill to EDI: turning a MAWB into an FWB message
An air waybill is a document; an FWB is the message a carrier's system reads. Getting from one to the other is extract, validate, emit — with worked examples.
FWB 16 vs FWB 17: which message your carrier wants
Two versions of the same Cargo-IMP message carry air waybill data to a carrier. The one you send has to match the version the receiver accepts — here's how to tell.
How MAWB data extraction works, end to end
Intake, extraction, validation, output — the four steps that turn a master air waybill into a structured, validated record, and why validation is where the value is.
Chargeable weight vs gross weight: what a waybill is billed on
Air freight is billed on the greater of actual weight and volumetric weight. How the ÷6000 rule works, and the mis-keys that turn into billing disputes.
Exceptions-only review: a short list, not a full inbox
Straight-through processing means clean waybills clear on their own. A person only sees the ones that failed a check — here's what routes a document to review.
Cargo-IMP vs Cargo-XML: the two languages air cargo speaks
The legacy positional EDI, IATA's modern XML replacement, and why both coexist today — so your data has to be ready for whichever the receiver reads.
API-first extraction: the happy path has no screen
Most documents should never touch a UI — data comes in by API or email, clears validation, and goes back out as structured data. The screen is for the exceptions.
Validation that catches what OCR confidence misses
A confidence score proves the model read the field. It says nothing about whether the value is right. Here's the second layer that closes the gap — with worked examples.
Reading the IATA check digit: how MOD-7 works
Why an air waybill number carries its own proof inside it, how the modulo-7 check digit is computed, and the mis-key errors it catches on sight.
MAWB vs HAWB: what a consolidation actually is
Master versus house air waybills, why a consolidation has to be recognized before single-commodity logic runs, and what that means for your data.
Put the checks to work on your own waybills.
Start with 30 free scans — no card. Watch a caught error route to review while the clean ones clear.