PerfectParser Docs
User GuidesParser Setup Guides

Set Up Cargo and Shipper Fields for Bills of Lading

Configure bill of lading fields in the dashboard — extract shipper, consignee, cargo tables, and hazmat flags from shipping documents.

Ready to set this up? Sign up for PerfectParser and get 20 free credits — no credit card required.

What this guide helps you do

This guide shows how to configure a bill of lading parser in PerfectParser, define shipper, consignee, and cargo fields, run a test batch, and export logistics data. After you upload a sample, field detection runs automatically. Compare the Schema tab with the recommended fields below so party and cargo names stay distinct.

Why bills of lading are hard to parse

Bills of lading mix party blocks, routing metadata, and cargo tables in formats that vary by carrier and trade lane. Shipper and consignee names sit in labeled boxes that OCR often reads out of order, especially on scanned ocean BOLs. Origin and destination may be labeled "Port of Loading" and "Place of Delivery" on one form and "Pickup" / "Delivery" on another. Cargo tables split weight, piece count, and description across columns with inconsistent units (kg vs lbs). Hazmat declarations appear as checkbox flags, marginal notes, or UN numbers embedded in description text. Multi-stop shipments attach rider pages with additional cargo lines. Vessel name and voyage number are frequently confused with BOL number during detection unless field descriptions are explicit.

We suggest configuring the following schema fields for your Bill of Lading Parser to capture all essential logistics and cargo data.

Field NameTypeDescription
bol_numberTextThe unique Bill of Lading reference number.
shipper_nameTextThe company or exporter shipping the goods.
consignee_nameTextThe buyer or company receiving the goods.
carrier_nameTextThe freight line or transport carrier (e.g., DHL, Maersk).
ship_dateTextThe date the cargo was shipped.
origin_portTextPort of loading or pickup location.
destination_portTextPort of discharge or delivery destination.
total_weightTextThe overall gross weight of the cargo.
cargo_itemsTableTable containing package_count, weight, description, and hazmat status for each cargo unit.

Set up this parser in the dashboard

Create a parser

Go to Parsers → New Parser in the dashboard. Give it a name like "Bill of Lading Parser". You can set the parser name while detection runs.

Upload a sample document

Drag and drop a representative bill of lading (PDF, PNG, or JPEG). Use a real BOL from your freight workflow — the AI uses it to learn party block and cargo table placement. Field detection and sample extraction start automatically.

Review detected fields

Field detection and sample extraction start as soon as the upload finishes. Open the Schema tab and compare detected fields with the Recommended Fields table above. Rename, remove, or add fields, and edit each field's instructions. Check sample values on the Results tab.

Review and save your schema

Check that shipper and consignee are separate fields and that cargo_items includes a hazmat column if you handle regulated freight. Confirm bol_number is not confused with booking or container numbers. Click Save parser. You can edit fields later on the parser Fields tab.

Run a test batch

Open Run Extraction, choose how your files are organised, upload a small test set of BOLs, and click Start batch extraction. Review the run on the Results tab and export to CSV or Excel.

Common mistakes

  • Swapping shipper_name and consignee_name because both appear in similar boxed regions on the form.
  • Omitting the hazmat column from cargo_items when compliance workflows depend on UN number or hazmat flag extraction.
  • Mapping vessel name or voyage reference into bol_number — add explicit field descriptions to disambiguate.
  • Skipping cargo_items and capturing only total_weight — you lose piece-level detail needed for customs or warehouse receiving.

Next steps

Test your first extraction free — sign up for PerfectParser, no credit card needed.

FAQs

Do I need a sample bill of lading to set up this parser?

Yes. Upload a BOL that matches your freight mode — ocean, air, or domestic trucking layouts differ. Include a sample with a cargo item table and hazmat notation if your workflow handles regulated goods.

Should shipper and consignee be separate fields?

Always define shipper_name and consignee_name as separate Text fields. They appear in adjacent blocks on most BOLs and are easy to swap if field descriptions are vague. Never merge them into a single 'party' field.

How many credits does setup and a test extraction use?

Parser setup is free. Each BOL page costs 1 credit. Single-page domestic BOLs use 1 credit; multi-page ocean bills of lading with attached rider pages cost 1 credit per page.

Looking for product features and use cases?

See the Bill of Lading Data Extraction solution page.

On this page