Workflow — BOL Processing

BOL data into your TMS in seconds, not minutes.

Carrier-format BOL PDFs and faxes — shipper, consignee, commodity, weight, NMFC, freight class, special instructions — extracted, validated, and pushed into MercuryGate, Oracle TMS, Blue Yonder, Manhattan Active, or McLeod LoadMaster. Replaces dispatch / ops-team BOL keying and offshore ops-center labor at a fraction of the per-BOL cost.

Take the AI Assessment Get a Per-BOL ROI Model

$0.40–$2.00

Per BOL at offshore ops centers

$11–$22

Per hour, BPO ops associate (billed)

60–85%

Volume off the BPO line after AI cutover

What This Replaces

The Ops Center Keying Every Carrier-Specific BOL Format

The work the ops-center associate does on every BOL — and the cost of leaving it there.

The labor

BOL data extraction today moves through 3PL dispatch teams plus heavily offshored ops centers — Genpact, WNS, Cognizant BPS, Accenture Operations, EXL, plus Flexport's Manila and Eastern Europe ops centers and Expeditors' in-house ops shops. Per-BOL cost runs $0.40–$2.00 fully loaded depending on carrier-format complexity, special-instruction parsing, and downstream-routing requirements. Each carrier has its own BOL format — there is no industry standard, and templates change without notice.

The cycle time

Real-time BOL processing is the table stakes for shipment visibility. When ops-center capacity backs up during peak season or carrier-format changes, BOL queues create downstream tracking gaps — proof-of-pickup records lag, customer EDI 214 status messages slip, and customer-service calls spike. The constraint isn't the per-BOL time; it's the cumulative volume across thousands of BOLs per day at a mid-size 3PL.

The Workflow

Input · Analysis · Output

What goes into BOL processing, what we do to it, and what shows up in the TMS.

Input

BOL submission from carriers and shippers

BOL PDFs from major carriers (each with their own format)
Inbound fax (eFax, RightFax, Concord)
Driver-supplied BOL photos via mobile app
EDI 211 / 204 messages
Carrier portal exports
Mixed-quality scans, mobile photos with skew
Special-instructions content (HazMat, temp-controlled, expedite)

Analysis

Extract, classify, validate

Shipper and consignee identification
Commodity description and NMFC class lookup
Weight, pieces, and dimensional data
Freight class and special-handling codes
Pickup and delivery dates and times
Special instructions (HazMat tags, temperature, expedite)
Confidence score per field; exceptions to dispatch queue

Output

Shipment record into the TMS

MercuryGate (REST APIs)
Oracle TMS (Cloud Integration)
Blue Yonder TMS (REST APIs)
Manhattan Active (REST APIs)
McLeod LoadMaster (REST APIs)
Proof-of-pickup record creation
Per-BOL audit trail with field-level extraction basis

Side by Side

BOL Processing Today vs. With Last Rev

The numbers that matter: cycle time, per-BOL cost, accuracy, and TMS-integration depth.

Dimension	Dispatch + Offshore Ops Center	Last Rev BOL Processing
Cycle time, BOL received to TMS record	Minutes-to-hours, depending on queue	Seconds per BOL
Per-BOL unit cost	$0.40–$2.00 fully loaded	Per-BOL, benchmarked at 25–45% of BPO unit cost
Carrier-format coverage	Trained on the formats the team has seen	All major carrier formats with template-drift detection
NMFC class lookup accuracy	Manual NMFC reference, drift on commodity edge cases	NMFC lookup with commodity-description match cited per BOL
Special-instructions parsing	Free-text scanning, HazMat / temp / expedite often missed	Structured tagging with downstream-routing logic
TMS integration	Manual entry into MercuryGate / Oracle / McLeod	Direct via documented MercuryGate / Oracle / Blue Yonder / Manhattan / McLeod APIs
Renegotiation leverage at next BPO renewal	None — you're locked in	60–85% of routine BOL volume off the contract

How It Works

From Carrier BOL to TMS Shipment Record

Five steps. Every one logged. Every one reversible if your confidence threshold isn't met.

Submission Lands

BOL PDF or fax from the carrier, driver-supplied photo via mobile app, EDI 211 / 204 message, or carrier portal export. Customer / lane / commodity context pulled from the order management system.

Extraction & Classification

Shipper and consignee identification. Commodity description and NMFC class lookup. Weight, pieces, dimensions. Freight class. Pickup / delivery dates and times. Special instructions (HazMat, temperature, expedite) with structured tagging.

Validation Against Customer Rules

Findings validated against the customer's lane and commodity rules. Anything below your confidence threshold per field is routed to the dispatch exception queue — your call which queue, ours or yours.

Push to TMS

Shipment record into MercuryGate, Oracle TMS, Blue Yonder, Manhattan Active, or McLeod LoadMaster via the documented integration. Proof-of-pickup record creation. EDI 214 status message updates queued.

Audit Log Persisted

Every field extraction, NMFC classification, and special-instruction tag logged with the source BOL, model version, prompt, and confidence score. Customer-audit-ready, FMC-complaint-ready, and yours.

Compliance & Defensibility

Built to Meet the Quality Bar 3PL Operations Already Run On

NMFC and freight-class accuracy

NMFC commodity classification per the National Motor Freight Classification with commodity-description matching cited per BOL. NMFC publication updates flow into the classification engine within days of effective dates.

EDI 211 / 214 / 204 conformance

EDI 211 (Motor Carrier Bill of Lading), EDI 214 (Transportation Carrier Shipment Status Message), and EDI 204 (Motor Carrier Load Tender) message generation supports the carrier-shipper EDI exchange. Per-trading-partner EDI mapping configurable per onboarding.

Customer-audit defensibility

When customers dispute a freight charge, raise an OS&D claim, or request shipment-history audits, the audit log produces what BOL data was extracted, what NMFC class was applied, and what the basis was. Cleaner chain of custody than the dispatch reconstruction post-event.

Customer data and lane confidentiality

BOL data contains customer pricing, lane structure, and commodity volume information. Deployable in your VPC or our SOC 2 environment. Encryption in transit and at rest; retention policies tied to your customer contracts and FMC recordkeeping rules.

Common Questions

What 3PLs and Shippers Ask About BOL Processing

Those are the systems where shipment records and BOL data live. The competitor on this page is the dispatch + ops-center labor that does the actual BOL keying — typically dispatch teams onshore plus offshore ops centers at Genpact, WNS, Cognizant BPS, Accenture Operations, EXL, Flexport's Manila ops, or Expeditors' in-house ops at $11–$22 per hour translated to $0.40–$2.00 per BOL. We undercut that labor cost, integrate directly into your existing TMS, and deliver shipment records into the system of record.

Most 3PLs and shippers keep the ops-center arrangement in place during pilot and early production — we route exceptions, complex multi-stop BOLs, and any case that genuinely requires senior-dispatcher judgment to the team you already have. Volume to the ops center drops 60–85% on routine BOL processing once cutover completes. You renegotiate at the next renewal from a much better position.

Our pilot success threshold is BOL field-extraction accuracy at parity with or above your incumbent ops process, measured on the same shadow-data sample of historical BOLs. Anything below your defined confidence threshold per field is routed to the dispatch exception queue — your call which queue, ours or yours.

There is no industry-standard BOL format — each major carrier (FedEx Freight, XPO, Estes, Old Dominion, Saia, ABF, R+L, Yellow, T-Force) has its own, and templates change without notice. The extraction layer adapts to the carrier-specific format with template-drift detection so format changes surface as exception findings rather than silent extraction errors.

Special-instruction content is parsed into structured tags so downstream routing rules fire correctly. HazMat shipments route to the hazmat / DG declaration validation workflow; temperature-controlled shipments flag the carrier-monitoring requirements; expedited shipments trigger the customer-SLA tracking. Each tag carries the basis citation so dispatch can verify on a richer file than free-text scanning produces.

Yes — through the documented integration surface each platform supports. MercuryGate via REST APIs; Oracle TMS via Cloud Integration; Blue Yonder via REST APIs; Manhattan Active via REST APIs; McLeod LoadMaster via REST APIs. Your IT and operations teams review and approve service accounts. We do not require platform-side custom development.

BOL-processing pilots typically run 4–6 weeks: 1 week of integration and per-carrier-format calibration with the dispatch team, 2–3 weeks of shadow-mode running on real BOLs with no TMS-side writes, 1–2 weeks of supervised cutover on a constrained scope (one carrier, one customer tier). Production rollout is staged after the pilot meets your accuracy and operations sign-off.

We benchmark against your current per-BOL fully-loaded cost — typically $0.40–$2.00 at offshore ops centers. Our target is 25–45% of that per-BOL cost at higher accuracy and faster cycle time. Pricing structures around volume tiers and outcome SLAs, not hourly billable rates.

Two Ways to Start

Take the AI assessment for a structured read on BOL-processing feasibility. Or talk to us if you already know the ops center is your largest 3PL line item.

Self-serve · 8 minutes

Take the AI Assessment

A short structured assessment that maps your monthly BOL volume, TMS, and current dispatch / ops-team arrangement to AI feasibility and ROI.

Talk to a specialist

Get a Per-BOL ROI Model

Send us your monthly BOL volume, your TMS, and your current dispatch / ops-team arrangement. We'll come back with a per-BOL unit-cost comparison and a 6–8 week pilot plan in 5 business days.

Other Workflows

More Logistics & Trade Workflows We Replace

The same approach, applied to the other document-heavy labor lines on your operations and trade-compliance budget.

Freight Bill Audit

Carrier invoices line-by-line audited against contract rates, fuel surcharge, accessorials.

POD Processing

Signed PODs, manifests → OS&D categorization and freight-claim-letter draft.

Detention & Demurrage Tracking

Container event data → FMC-reasonableness analysis and dispute-letter draft.

Hazmat / DG Declaration

Shipper's declaration → 49 CFR / IATA DGR / IMDG validation. Bad paperwork stops before the carrier.