For every load that leaves the dock, someone builds a bill of lading, prints it, collects the signed copy, finds the packing list and any certificates, emails the customer and files the lot. Almost none of that requires judgment. The data is already in your ERP, your warehouse records and your carrier booking. What is missing is the plumbing between them.
Start with what a BOL actually needs
Before automating anything, list every field on the BOLs you issue today and where each one comes from. A typical BOL carries:
- Parties and references: shipper, consignee and ship-to address, the BOL number, customer PO numbers and any customer reference fields.
- Carrier details: carrier name, SCAC code and the PRO or tracking number.
- What is on the truck: handling units, piece count, weights and, for LTL freight, the NMFC freight class.
- Hazardous materials, if any: US DOT rules (49 CFR 172) require the basic shipping description, including the UN number, proper shipping name, hazard class and packing group, plus an emergency response telephone number.
- Instructions and signatures: special handling, seal numbers and the shipper, carrier and consignee signatures.
Many retail and distribution customers expect a standardized format such as the VICS bill of lading, and some add their own fields. Write those requirements down per customer; they become rules the automation follows rather than knowledge in one clerk’s head.
Find where the data lives, and where it does not
Most fields map cleanly: the order and ship-to come from the ERP, handling units and weights from pick and pack data, carrier and PRO number from the booking. The gaps are where automation stalls. The usual ones are weights that are never recorded, freight classes missing from the item master, and ship-to addresses typed differently on every order. Fixing those gaps is part of the project, and it pays back on its own because the same errors cause billing disputes.
Step 1: generate the BOL from data
Once fields are mapped, the BOL and packing list can be generated the moment an order is marked shipped, using your existing templates. Keep the template content under the control of the shipping lead: when a customer changes a requirement, they should be able to update the rule, not file a ticket.
Step 2: capture the signed copy
The signed BOL is the document customers and auditors ask for, and the one most often missing. A scan station at the dock, or a phone camera, is enough. Two things make matching reliable:
- Print the BOL number as a barcode, so a scan can be tied to the right load without reading handwriting.
- Check for a signature and for handwritten changes, such as a corrected piece count. Anything unusual goes to a person with the image attached, instead of being guessed.
Step 3: assemble and send the customer’s documents
With the BOL, packing list and any certificates of analysis linked to the order, the shipment email can be drafted automatically, with every document attached and the right contacts for that customer. At first, the shipping clerk approves each email. Once the drafts are consistently right, you can agree pre-approval rules for standard customers, in writing, and keep anything outside those rules waiting for a person.
Step 4: file everything against the order
Attach every document to the order and shipment record. Invoicing can then start from a complete shipment, proof of delivery can close the order, and the next audit request takes a search instead of a binder.
Where people stay in control
- The clerk approves customer emails, or the pre-approval rules that replace that step.
- The shipping lead owns BOL templates and customer requirements, including hazmat content.
- Scans that cannot be matched with confidence wait for a person.
What to measure
Measure a baseline before you change anything, for two weeks or so, so the result can be checked rather than estimated:
- Clerk minutes per shipment, from shipping to filed paperwork.
- Missing-document follow-ups per month: calls and emails from customers asking for a BOL or COA.
- Time from shipment to customer notification.
- Share of loads with a complete document set on file.
A short readiness checklist
- Every BOL field mapped to a source system, with gaps listed.
- Customer-specific BOL and document requirements written down.
- A scanner or phone at the dock, and a BOL number that can be printed as a barcode.
- A named person who approves customer emails.
- A baseline for clerk time and missing-document follow-ups.
These steps match the bill of lading creation workflow in our library; and the assessment works through this checklist on site with your shipping team.
