Logistics and freight
Forwarders, 3PLs, and customs brokers know where the week goes. BOL, commercial invoice, customs entry, and POD arrive in different formats, then the desk reconciles them by hand across three tabs. We rebuild that as a packet-level pipeline with the TMS as the system of record.
Where the week sharpens up
These are the patterns we see in discovery for this vertical. If two of the four are recognisable, the pipeline pays for itself inside a quarter.
Dock-signed carbon copies arrive as phone-scanned images: tilted, stamped, partially legible. Operations directors look for rotation correction, stamp-aware classification, and handwriting extraction that is trained on the carriers they actually use.
We build: classification-first intake, trained on your carriers' BOL layouts.
When the commercial invoice and the BOL disagree on pieces or weight, the filer wants a packet-level check before the customs broker files. One flagged field is easier to resolve than three tabs and a calculator.
We build: packet-level reconciliation between BOL, commercial invoice, and customs entry, pre-release.
HS codes work best when they are proposed against the product catalogue your team maintains, not copied from the last shipment. Compliance leaders want a confidence threshold and a flag when a description has drifted from the last few shipments.
We build: HS proposals against your product master, flagged under threshold for filer review.
PODs arrive by email, fax, and photograph. Billing wants them matched against the shipment record and posted inside the hour so invoicing closes on the day of delivery, not the day after.
We build: POD capture across channels, matched to the shipment record, posted to billing on arrival.
Dispatch inbox, carrier portal downloads, dock scanner, EDI feeds. All route into one queue per shipment ID.
Each document tagged and attached to the shipment record before extraction runs.
Handwriting-aware OCR for dock copies, structured parse for portal PDFs.
Weight, pieces, country of origin, HS code consistency across the three documents.
Clean data posted into the TMS with source documents attached. Exceptions named by desk.
The BOL says one weight, the commercial invoice says another, the customs entry carries a third. The pipeline compares all three at the field level, flags the mismatch, and holds the packet until the exception clears. Filers see a single discrepancy, not three tabs.
Case studies in this industry
Each case links to a named client, a named document, and the system of record the data lands in. We publish only what the client signed off to publish.
Customs packet reconciliation before the yard clears, 96% HTS confidence on 28k packets/month.
→Logistics · 2025Regional 3PL · POD capture from dock scansPOD capture from dock scans, verified against the load tender.
→Logistics · 2025Customs broker · HTS classification against product masterHTS classification against a 42,000-line product master.
→Logistics · 2024Mid-market broker · rate confirmation matchingRate confirmations matched to the TMS without the copy-paste round.
→Logistics · 2023Port drayage operator · BOL auto-matchBOL auto-match for a 40-truck drayage operator at the Port of LA.
→Logistics · 2023Freight forwarder · commercial invoice varianceCommercial invoice variance flagging against the packing list.
Free 30-minute call
You'll leave with a clear next step.
