freight-doc-processor

Extract POD and BOL fields from freight documents via OCR and NLP.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/wasay1200/freight-broker-ai --skill freight-doc-processor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freight-doc-processor
Source: https://github.com/wasay1200/freight-broker-ai/tree/main/skills/freight-doc-processor
Command: npx skills add https://github.com/wasay1200/freight-broker-ai --skill freight-doc-processor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires docling, pdfplumber, Pillow, pytesseract, requests, ocrmypdf, imagemagick, tesseract-ocr, and includes scripts (resource) components.

What problem does it solve?

Automatically detects POD and BOL documents from email attachments, OCR-parses key fields, and verifies delivery details by matching to loads, reducing manual review and speeding invoicing.

Core Features & Use Cases

  • OCR-based extraction of POD and BOL fields (e.g., bol_number, shipper, consignee, delivery dates, receiver, units, weight) from PDFs and images.
  • Document matching to loads to surface discrepancies and trigger invoicing or settlement workflows.
  • Use Case: A broker receives multiple PODs; this Skill extracts fields, links them to the correct loads, and flags missing PODs or discrepancies for quick action.

Quick Start

Process a new POD or BOL attachment by passing its file path to the doc_pipeline script to extract fields and surface matches.

Frequently Asked Questions about freight-doc-processor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract data from POD and BOL freight documents using OCR?

You can extract data from POD and BOL freight documents using OCR by passing PDF or image file paths to the processing pipeline. The system identifies documents, parses key fields like bol_number and delivery dates, and matches them to loads.

Can I automate matching BOL documents to loads and flagging discrepancies?

Yes, you can automate matching BOL documents to loads by extracting OCR fields and verifying delivery details. The system surfaces discrepancies and missing PODs, enabling quick settlement actions and triggering invoicing workflows.

Does this document processing pipeline support both PDFs and image attachments?

Yes, the document processing pipeline supports both PDFs and image attachments. It uses dependencies like pdfplumber and Pillow to handle OCR extraction across different file formats from email attachments.

What is the best way to automate freight document detection for invoicing workflows?

The best way to automate freight document detection for invoicing is using an OCR and NLP pipeline that identifies POD and BOL attachments, extracts critical fields, and verifies load details to trigger automated settlement workflows.

Do I need Tesseract OCR and Docling installed to process freight documents?

Yes, you need Tesseract OCR and Docling installed along with other dependencies like pdfplumber and pytesseract. These tools provide the foundational OCR and document parsing capabilities required for robust error handling.

Why does OCR fail to extract fields from low quality BOL scans?

OCR can fail to extract fields from low quality BOL scans due to poor image resolution or skewed text. The pipeline uses ImageMagick and ocrmypdf to preprocess images, improving extraction accuracy from degraded freight documents.