Air waybill data export: a searchable record, re-exportable any time

Air waybill data export is how the structured data AWBGuru pulls off a document actually leaves the system — as a file you download or a feed another system reads. It isn't a single moment at the end of processing. Every document AWBGuru handles is kept in History, and from there you can export any record, or any slice of records, whenever you need it and in whatever format the next system expects.

That matters because the data outlives the moment it was captured. A shipment gets re-billed, a partner asks for a resend, an EDI message needs regenerating in a newer version — and the record is still there to export again. History is the durable copy; export is how you get it back out.

The History surface

History is a searchable record of every document AWBGuru has processed. Each row shows the source file, the AWB number, the model's confidence in the read, the status — Pass or Review — and whether the record was already emailed or sent onward.

You can search History by AWB number, by filename, or by date, and reopen any document to see the extracted fields exactly as they were captured. Nothing is discarded after a document clears, so the record you need next week or next quarter is the same record that was processed today.

Because every processed document stays in History, it doubles as the audit trail and the resend source. The confidence and Pass or Review status on each row tell you at a glance how a document was handled — whether it cleared on its own or went to a person — and the sent flag tells you whether its data has already gone out. When someone asks for a record you handled a month ago, you search for it, reopen it, and export it again; you don't go hunting for the original file or re-running anything.

Export is not a one-shot

In a lot of capture tools, export happens once — at the moment a document is processed — and if you need the data again you re-run or re-upload. AWBGuru treats export as something you do from the record, not from the pipeline. From History you can re-export any document at any time, even one that was already exported or already sent, and you can do it for a single record or a whole filtered slice.

So air waybill data export here is really a replay against the stored record: filter History down to what you want — a date range, one AWB number, everything with a Pass status — and export that set in the format the next system needs. No re-processing, no re-upload.

The slice is the useful part. Because History is searchable, you're never forced to export one record at a time or dump everything at once. Narrow to a single AWB number for a one-off resend, a date range to hand a period to accounting, or every Pass record to feed a downstream system — then export just that set. And because a document that was already exported or already sent can be exported again, a resend costs nothing extra: the record is still there, and the export is repeatable as many times as you need.

One export, five formats, two jobs

Export serves two different readers, so the formats fall into two groups. CSV and XLSX are for people and spreadsheets — open the data in Excel or Google Sheets, hand a batch to accounting, reconcile by eye. JSON, XML, and FWB are for systems — JSON and XML feed an API or an internal tool, and FWB is the Cargo-IMP electronic air waybill EDI message, available in both v16 and v17.

That JSON, XML, and FWB set is what makes this more than a spreadsheet export. It's the API and EDI story: the data comes out machine-ready, in the shape the receiving system already speaks, rather than as a one-off dump someone has to re-key. That's the real difference between air waybill data export here and exporting a CSV from any capture tool — the same record can leave as a human file or as a system message, from the same History row.

CSV and XLSX flatten the record into rows and columns anyone can open, which is exactly right when a person is the reader — a batch to reconcile, a report to hand off, a quick sanity check in a spreadsheet. JSON and XML keep the structure intact for a program to consume, and FWB packages the shipment into the exact EDI message an airline or forwarder's system expects. It's the same underlying record in every case; you pick the shape that fits whoever, or whatever, reads it next.

# illustrative — field names shortened
{
  "awb":         "020-12345675",
  "status":      "pass",
  "confidence":  0.98,
  "origin":      "HKG",
  "destination": "LAX",
  "pieces":      12,
  "gross_kg":    248.0
}
# the same record also exports as CSV, XLSX, XML, or FWB v16/v17

FWB EDI, in one line

FWB is the IATA Cargo-IMP electronic air waybill message — a widely used EDI format airlines and forwarders exchange. AWBGuru can export a processed waybill straight to FWB in either v16 or v17, so the data lands in the receiver's system as a message it already understands. The mechanics — segments, versions, when to send which — are their own topic; the air waybill to FWB EDI guide covers them in depth.

Where export sits in the pipeline

AWBGuru is automation-first. Clean, high-confidence documents clear straight through and deliver their data on their own; only the exceptions — a failed check or a low-confidence critical field — wait for a human, in an exceptions-only review queue. Export from History is the layer underneath all of it: whatever happened at processing time, the record is kept and stays re-exportable.

There's a difference worth drawing between delivery and export. When a clean document clears, it delivers its data automatically as part of straight-through processing — that's the pipeline doing its job with no one watching. Export from History is the deliberate, on-demand version of the same thing: you, later, choosing a record or a slice and pulling it out in the format you need. One is automatic and happens once; the other is manual and repeatable — and both draw on the same stored record.

If you're new to how the data gets pulled off a document in the first place, AWB data capture is the place to start. History and air waybill data export are what you use afterward — the searchable record of everything that ran, and the way to get it back out in any format, at any time.