Extract data from bills of lading

One that returns the same record whatever the carrier's layout. Document Studio deploys an endpoint for your B/L schema: POST the PDF or image, get the shipper, consignee, routing, containers, seals and weights back as JSON. The same extraction runs as an ETL pipeline if you would rather drop files into S3 or a shared drive.

Parse first, then extract. As a bill of lading parser, LLMWhisperer turns each page into layout-preserved text so a container number stays beside its seal, and Document Studio then maps that text to your fields. For volume, run it as a pipeline or let Flow pick B/Ls up from the shipment inbox as they arrive.

Flow turns extracted B/L data into a running process: it ties the B/L to the booking, packing list and ASN, checks quantities, containers and seals, and posts the result to your TMS or ERP and your WMS. Exceptions stop for a person; clean shipments go straight through.

Yes. LLMWhisperer handles skewed phone photos, fax noise and pen marks, and reads handwritten driver counts alongside the printed fields. A value it cannot read with confidence goes to a person with the page, so a guess never reaches your TMS.

Yes. Master and house ocean B/Ls, straight bills, sea waybills, multimodal bills and truckload or LTL BOLs all come back in one schema, along with shipping request and information forms. Fields are found by meaning, not position, so a new carrier's layout needs no set-up.

Both, in layers. For BOL digitization alone, LLMWhisperer and Document Studio act as the bill of lading data extractor and hand you JSON. Flow adds the intake around them: collecting the documents, running the checks, routing exceptions and posting to your systems.

Yes. Package counts and weights against the packing list, container and seal numbers against the booking and pickup log, PO numbers against open orders, and any other check your team does by eye. A failed check holds that shipment with the reason attached.

The shipment waits in a review queue where a clerk sees the field next to the box it came from on the B/L, then approves, corrects or sends it back. Each decision is logged, and the other shipments keep moving.

Unstract is SOC 2, ISO 27001, GDPR and HIPAA compliant. B/Ls are encrypted, never used for training, and kept only as long as you choose. Teams that need cargo data to stay on their own servers can self-host; the Trust Center lists every control.

Not for Flow. In a consultation we set up the intake around your carriers' B/Ls, your checks and your TMS or ERP, and most teams run live shipments within days. To try extraction now, start for free and upload a bill of lading.