Modeling bills of lading as data

The bill of lading has been the legal record of a freight shipment for well over a century, and for most of that time it's been a piece of paper. Even today, most BOLs are generated as a PDF, printed, signed, scanned, and emailed — a document pretending to be data.

Why documents aren't enough

A PDF is easy to generate and easy to lose track of. It doesn't have a status. It can't be queried, joined against an order, or validated before it's signed. Every field on it — weight, piece count, carrier, consignee — has to be manually cross-checked against whatever system actually holds the order.

Treating it as a first-class record

In Lading, a bill of lading isn't a rendered document — it's a structured object attached directly to an order, generated from the same line items both partners already agreed on. The PDF still exists, because carriers and drivers need something to sign, but it's a projection of the underlying record, not the record itself.

That distinction matters the moment something needs to be corrected, audited, or reconciled against the order it belongs to. A document has to be re-issued. A record can just be updated, with the change visible on the same timeline as everything else.