DocuOCR reads every document that moves with a shipment, classifies it, and pulls the freight data your team needs, straight from bills of lading, proof of delivery, packing lists, freight invoices, and customs forms. No template to build, no keying by hand.
Built for US 3PLs, freight brokers, forwarders, carriers, and customs brokers that move shipment documents at volume and need accuracy their billing and tracking can trust.
Upload a document to extract
Drop files here or click to upload
Up to 50 files
Uploading...
Drop in a bill of lading, POD, or packing list to watch DocuOCR read it and pull out the data, free, no signup required.
Freight runs on paperwork, and a single shipment generates a stack of it. The bill of lading, the packing list, the carrier's rate confirmation, the customs declaration, the proof of delivery that comes back with the driver, the freight invoice that follows. A single international load can pass dozens of documents among the shipper, the carrier, the broker, and the consignee. Someone has to read all of it, find the reference numbers and amounts that matter, and key them into the TMS or billing system. That work is slow, it repeats on every load, and it is where billing and tracking fall behind.
Logistics document processing software takes that job off your team. It reads each document, identifies what it is, and extracts the fields ops and billing depend on, the BOL number, the shipper and consignee, the carrier and PRO number, the weights and piece counts, the freight charges, then checks the values before they move forward. Instead of keying data, your team reviews what the software already pulled.
The change that makes this practical is AI. Older tools needed a separate template for every carrier's form and broke the moment a layout changed. Modern extraction reads a document by understanding its structure, so an unfamiliar carrier's bill of lading or a faxed POD does not stop the line. That is the difference between software that adds work and software that clears it.
DocuOCR classifies and extracts the shipping and customs documents that fill an ops inbox and fax line, however they arrive.
Reads BOL number, shipper, consignee, carrier and SCAC, PRO number, piece count, weight, and freight terms from straight, master, and house bills in any carrier format.
Captures delivery date, receiver name, signature presence, piece count, and noted exceptions or damages from PODs, including driver photos and faxed receipts.
Extracts SKUs, quantities, carton and pallet counts, weights, and dimensions so warehouse and ops systems get a structured line-item list.
Pulls carrier, invoice number, charges, accessorials, and references to match invoices to loads and speed freight bill audit and payment.
Reads commercial invoices, customs declarations, certificates of origin, and arrival notices, capturing HS codes, values, and party details for clearance.
Extracts agreed rates, lane and load details, and air or ocean waybill numbers from rate cons and waybills so dispatch and billing stay aligned.
Freight bills and commercial invoices often need their charges and line items broken out on their own for freight bill audit. If you want those invoices specifically pulled into structured line-item data outside the shipment workflow, a dedicated invoice data extraction tool handles that one task, while DocuOCR processes the whole shipment file end to end.
Classify, read, extract, validate. Drop a shipment file in and the whole sequence runs on its own.
The engine reads a mixed stack of pages and sorts them by document type, bill of lading, POD, packing list, freight invoice, customs form, so the right extraction runs on each.
OCR and ICR convert scans, photos, faxes, and image-only PDFs into machine-readable text, including hand-completed fields and driver signatures on PODs.
DocuOCR pulls the freight fields tied to their labels, so you get named values, reference numbers, and tables instead of a wall of text.
Values run through your rules and cross-document checks, low-confidence reads route to review, and clean data exports to your TMS or billing system.
# bol_004812.pdf -> extracted data { "document_type": "bill_of_lading", "bol_number": "SCAC-004812", "shipper": "Cedar Ridge Mfg, Dallas TX", "consignee": "Harbor Foods, Newark NJ", "carrier": "Estes Express", "pro_number": "0421-779302", "pieces": 12, "weight_lbs": 3480, "confidence": 0.98 } # classified, read, validated, ready for billing
Reading a clean BOL is the easy part. These are the capabilities that decide whether the software actually clears your ops and billing queues.
Sorts a multi-document load package by type automatically, so no one separates BOLs, PODs, and invoices by hand before processing can start.
Reads straight, master, and house bills of lading from any carrier without a per-carrier template, so a new lane or partner does not break the flow.
Reads hand-completed fields, driver notes, and degraded faxed PODs with intelligent character recognition, routing low-confidence reads to review.
Pulls BOL, PRO, PO, container, and load numbers as named fields, not buried text, so billing and tracking match documents to the right shipment.
Compares values across the BOL, POD, and invoice and flags mismatches, like a weight or piece count that does not agree across the file.
Exports clean data as JSON, Excel, or CSV, or pushes it straight into your TMS, ERP, or freight billing system through the API, no rekeying.
The cost of manual processing is not just time. It is the rekeying errors, the freight bills that cannot be matched to a load, and the detention and delay claims that pile up while paperwork waits.
| Factor | Automated (DocuOCR) | Manual handling |
|---|---|---|
| Time per file | Seconds to read and extract | 15 to 30 minutes of keying |
| Sorting the file | Classified automatically | Pages separated by hand |
| Reference-number errors | Flagged at capture | Caught after a billing dispute |
| New carrier BOL formats | Read on the first pass | Re-learned by each handler |
| Peak-season volume | Scales without headcount | Backlogs build, loads stall |
| Data into TMS or billing | Exported or pushed by API | Retyped at the handoff |
DocuOCR is built on intelligent document processing: it classifies the file, reads any carrier layout, extracts the data, and validates it across documents, so ops and billing keep pace with your freight volume instead of falling behind it.
Any team that reads freight or customs documents to move a load forward gets time back.
Classify mixed shipment files across clients, extract BOL and POD data, and feed clean records into the TMS instead of keying every load by hand.
Read rate confirmations, BOLs, and carrier invoices to match loads, speed carrier settlement, and cut the reference-number errors that delay billing.
Capture PODs and BOLs from drivers, including faxed and photographed receipts, and turn them into billable, structured records in seconds.
Process bills of lading, packing lists, and arrival notices across air, ocean, and ground to keep shipment files complete and current.
Read commercial invoices, customs declarations, and certificates of origin, capturing HS codes, values, and parties to prepare entries faster.
Call the API to add document classification and freight data extraction to your own TMS, visibility, or freight audit product.
Run documents by hand in the dashboard, or call the same engine from your TMS, freight audit, or visibility platform with one REST request. Post a document and get back the classified type, the recognized text, and the extracted fields, with a confidence score on every value.
# classify + extract a freight document curl https://api.docuocr.com/v1/extract \ -H "Authorization: Bearer $KEY" \ -F "file=@bill_of_lading.pdf" \ -F "classify=true" # -> document type + fields + confidence
No seat licenses and no setup fees. Start free to check accuracy on your own bills of lading and PODs, then pay per page as your volume grows. Higher volumes move to committed plans with lower per-page rates and priority throughput.
The questions ops and billing teams ask most before they automate freight document processing.
Logistics document processing software reads the freight and shipping documents tied to a shipment, identifies what each one is, and extracts the data your team needs into structured fields. It handles bills of lading, proof of delivery, packing lists, freight invoices, and customs forms, then validates the values before they post. Instead of staff keying data from scans, faxes, and emails, the software pulls it and routes anything uncertain to review.
OCR turns the paper and PDFs that move with every shipment into data your systems can use. In logistics it reads bills of lading, PODs, packing lists, and customs forms, then pulls shipper, consignee, carrier, container, weight, and reference numbers into structured fields. That removes manual keying, speeds billing and tracking, and keeps a single shipment from stalling across the many stakeholders who touch its paperwork.
Logistics runs on a long list of documents: bills of lading, proof of delivery, packing lists, commercial and freight invoices, customs declarations, rate confirmations, arrival notices, delivery receipts, air waybills, and dock receipts. A single international shipment can pass dozens of these among shippers, carriers, brokers, and consignees, which is why classifying them automatically is the first step to processing them.
Freight OCR works in four steps: it captures each document from a scan, fax, photo, or PDF, reads the text with OCR, extracts the fields tied to their labels, and validates them. The engine pulls shipment IDs, container and PRO numbers, ports, weights, and shipper and consignee details, then sends clean data to your TMS or billing system so loads move without manual entry.
Bill of lading OCR is software that reads a BOL and extracts its key fields automatically: BOL number, shipper, consignee, carrier, pieces, weight, freight terms, and the line items. Because bills of lading arrive in every carrier format and often by fax or scan, layout-aware extraction reads them more reliably than fixed templates, turning a paper BOL into structured data in seconds.
You extract data from a bill of lading with AI that reads the document, finds each value next to its label, and returns structured fields. It captures the BOL number, shipper and consignee, carrier and SCAC, PRO number, piece count, weight, and freight charges. Because it reads by understanding layout rather than a fixed template, it handles straight, master, and house bills from any carrier.
Yes. OCR reads proof of delivery documents, including the delivery date, receiver name, signature presence, piece count, and any noted damages or exceptions. PODs often arrive as photos or faxed scans from drivers, so the dependable approach pairs automatic extraction with a review queue for low-confidence reads. That lets billing match a POD to its load and invoice without someone keying every receipt.
Modern AI logistics OCR commonly starts around 95% field-level accuracy on clean documents and climbs toward 99% with tuning and validation. Accuracy varies with scan quality, handwriting on PODs, and document type. The safe pattern is straight-through processing for high-confidence values and a short human review queue for anything the engine flags, so a misread weight or reference number never posts on a guess.
Yes. Good logistics document processing software exports clean data as JSON, Excel, or CSV, or pushes it into your TMS, ERP, or freight billing system through an API, so extracted values land where ops already work. That removes the rekeying step between a scanned BOL or POD and the load record, which is where most billing delays and reference-number errors come from.
The best logistics document processing software classifies a mixed shipment file, reads printed and handwritten documents accurately, extracts the freight fields your team relies on, validates them, and exports to your TMS or billing system through an API. DocuOCR does this across bills of lading, PODs, packing lists, freight invoices, and customs forms, and lets you test it on your own documents first.
How to read shipper, consignee, carrier, and line items off a BOL without retyping.
The paperwork behind every shipment, from BOL to commercial invoice, and what each one holds.
The end-to-end IDP workflow that classifies, reads, extracts, and validates documents in one pipeline.
The full platform behind the freight workflow, with a dashboard for teams who want document data without code.
The focused tool for reading a single BOL: number, shipper, consignee, carrier, weight, and line items.
How the engine sorts a mixed shipment file by document type before extraction runs.
How DocuOCR reads structured forms like customs declarations and packing lists, including hand-completed fields.
The developer endpoint that classifies, reads, and extracts freight documents inside your own app.
Upload a bill of lading, POD, or packing list, watch DocuOCR read it and pull out the data, then connect the API to process every shipment file that follows on its own.
