Can freight software run a shipment when all you have is a bill of lading?

Bills of lading guideNov 16, 202617 min read

Can freight software run a shipment from a bill of lading alone?

It is 8:15 a.m. at a plant that makes packaging film. The shipping clerk prints a bill of lading for every outbound load from the warehouse system, signs it and drops a PDF in a shared folder. The ERP order behind it is often incomplete: the ship-to address is the customer's billing address, the pallet count is an estimate from the sales order and the requested date was entered weeks ago. The logistics coordinator ends up retyping each BOL into a carrier portal or an email to get a quote and a pickup. On a busy day, that is twenty retyped BOLs before lunch.

Yes. Freight software can run a shipment from a bill of lading alone when the BOL is complete, because a BOL already holds what a booking needs: who ships, who receives, what moves, how it is referenced and who pays. From that one document, software can create the shipment record, request quotes or book the named carrier, schedule the pickup and set the pickup and delivery appointments. What it should not do is guess. When the BOL is missing something or carries a date that can't work, the shipment should wait as pending while a person supplies the answer.

The idea surprises some teams because they think of the BOL as the last document, printed after the booking. At many plants, it is the opposite. The warehouse prepares the BOL as soon as the freight is staged, and it is the most accurate record of what is actually leaving the dock.

Why the BOL is often better than the order

A sales order describes what the customer bought. A BOL describes what is about to move. Between the two, things change: items are short-shipped, two orders are combined on one pallet, a pallet is split, the ship-to is corrected. The BOL reflects those changes because the person who staged the freight wrote it. Starting from the BOL means the shipment is built from the freight on the floor, not the freight on paper weeks ago.

When the BOL is not enough on its own

A BOL is enough to start a shipment when it is complete and accurate. It is not enough when key fields are blank, when the date is impossible or when the BOL describes a load the company does not ship under its own control, such as a collect shipment the customer's carrier will pick up. Those cases need a rule or a person, and the sections below cover them.

Want to see it with one of your BOLs?

Send one of your BOLs and see the shipment Wilson would create from it. You don't need to prepare anything: Cartage maps the workflow with you on the call.

See it on your own loads. Wilson, by Cartage, is an AI logistics agent that quotes, books, tracks, audits and pays for freight with your approved carriers.

Book a demo →

What does a bill of lading contain that a shipment needs?

A standard straight bill of lading contains the parties, the freight description, the references and the terms that a carrier needs to price and move the load. Read field by field, it maps almost exactly onto a shipment record.

The fields and what each one drives

BOL field What it tells the software What it drives
Shipper name and address Where the freight is picked up Pickup location and pickup contact
Consignee name and address Where the freight is delivered Delivery location and delivery contact
Ship date When the freight is ready Pickup date and quote timing
BOL number The document's own reference Shipment reference on every message
PO, order or customer reference numbers Links to the customer's and the company's systems Matching the POD and the invoice later
Handling units and pieces Pallets, crates or cartons Mode choice and quote accuracy
Weight Total and per line Rate, equipment and mode
Freight class or NMFC item (LTL) How the freight is rated LTL quote accuracy
Commodity description What the freight is Carrier acceptance and any special handling
Hazardous materials indication Whether hazmat rules apply Which carriers can take it
Special instructions Liftgate, inside delivery, appointment required Accessorials on the quote
Freight terms Prepaid, collect or third party Who books and who pays
Carrier name and PRO (if filled in) A carrier may already be chosen Booking with that carrier or quoting others

Creating the shipment

With the parties, freight and references, software can open a shipment record that matches the load on the dock. The BOL number and order references go on the shipment so every later email, rate confirmation, POD and invoice can be tied back to it. If the plant uses one BOL per order, each BOL becomes one shipment. If one BOL covers several orders, the references on it keep each order linked.

Scheduling the pickup

The ship date, the shipper address and the handling units are what a carrier needs to plan a pickup. If the BOL names an approved carrier, the software can tender to that carrier and request a pickup. If the carrier field is blank, it can request quotes from the company's approved carriers, compare them on total cost and book within the approval rules. Either way, the booking should end with the carrier's written acceptance and a rate confirmation.

Setting appointments

Appointment needs are usually on the BOL itself, in special instructions such as "delivery appointment required" or "call before delivery." The pickup side often has its own dock schedule. With the dates, addresses and instructions from the BOL, software can request the delivery appointment from the receiver and reserve the pickup slot in the company's dock calendar if that calendar is connected.

A hypothetical BOL, step by step

Consider a hypothetical BOL from the packaging film plant in the opening. It lists eight pallets of film, 6,400 pounds, class 70, shipping prepaid on Wednesday to a converter's receiving dock two states away. The special instructions say "delivery appointment required, no liftgate needed." The carrier field is blank. The customer PO and the plant's order number are both on the form.

Here is what software can do with that page alone:

  1. Open the shipment. It creates a record with the plant as shipper, the converter's dock as consignee, the BOL number as the main reference and the PO and order number attached.
  2. Choose the mode. Eight pallets at 6,400 pounds is a typical LTL load, possibly a volume LTL or partial truckload candidate. The quote request goes to approved carriers for the mode that fits.
  3. Quote and book. Quotes come back from approved carriers. The best usable quote inside the lane limit is booked, and the carrier's written acceptance and rate confirmation are collected.
  4. Schedule the pickup. The pickup is requested for Wednesday at the plant's dock, within the dock hours on record.
  5. Request the delivery appointment. Because the BOL says an appointment is required, the receiver is contacted for a slot that fits the carrier's transit time.
  6. Send the paperwork. The BOL goes to the carrier with the booking, and it is attached to the shipment with the rate confirmation.

Nothing in those six steps needed the ERP order. Every input came from the BOL. If one of them had been missing, such as the consignee's dock address or the weight, the shipment would have stopped at that step and waited for an answer.

The fields that most often cause trouble

Three BOL fields cause most bookings to go wrong. The freight class on an LTL load, when it does not match the density of the freight, leads to reclassification charges later. The weight, when it is an estimate, changes the rate. The special instructions, when they are missing, lead to a driver arriving without a liftgate. Software should read those fields carefully and raise anything that looks inconsistent instead of booking around it. For a related comparison of documents built before and after booking, see a BOL maker versus a BOL built from the booked load.

How does BOL intake compare with ERP, email and CSV intake?

BOL intake is one of four common ways to get orders into freight software, and each fits a different kind of plant. Most companies end up using two or more.

The four intake routes

Intake route What arrives Strengths Weak points
ERP connection Sales or transfer orders as they are released Structured fields, no retyping, links back to the ERP Orders may not reflect what actually staged
Email Orders, requests or documents sent to an inbox Works with any system and any sender Free text and attachments vary in quality
CSV or XLSX files A batch of orders exported from any system Simple to set up, no integration project Only as current as the last export
Bill of lading The document prepared for the load Reflects the actual freight at the dock Arrives later than the order; depends on BOL quality

When the BOL is the best starting point

The BOL tends to be the right starting point when:

  • The warehouse already creates a BOL for every outbound load.
  • ERP orders are often changed or combined before shipping.
  • The company has no ERP connection yet and wants to start without one.
  • The team today retypes BOL details into carrier portals or emails.
  • Inbound shipments arrive with a supplier's BOL that is the only record the team has.

When the ERP or a file is better

An ERP connection is better when the company needs to quote earlier than the BOL is ready, for example on truckloads that need a rate days before the freight is staged. A CSV or XLSX file works when a team wants to hand over a batch of orders without building any connection at all. For a deeper look at that choice, see whether you need an API integration or can work from email and files.

Combining routes

Many teams use the ERP order to quote early and the BOL to confirm the final details before pickup. When the two disagree, for example a pallet count of 12 on the order and 14 on the BOL, the BOL usually wins because it describes the staged freight, but the difference should be raised with the team, not overwritten in silence. If the change affects the rate, the carrier needs the corrected details before the truck arrives.

What still needs a person when software runs a shipment from a BOL?

A person should still own anything that changes the cost, the date or the carrier, and anything the BOL does not answer. Running a shipment from a BOL takes the typing out of the work. It does not take away the decisions.

Decisions that stay with the team

  • Rates outside approval limits. If the best usable quote is above the lane limit, a person approves or declines it.
  • A carrier that can't make the date. If the only available carrier can pick up a day late, the team decides whether to accept it. The agreed date should not change without a person.
  • A carrier the company has not approved. New carriers are approved by the company before anyone books them.
  • A permanent rule change. If the team changes a carrier or time on one load, that is a change to that load. Whether it becomes a rule is the team's call.
  • Customs clearance on cross-border loads. A customs broker clears the freight. Software can prepare and pass on information, but it is not the broker.

When the BOL is incomplete or wrong

The worst response to a bad BOL is a guess. Consider a hypothetical BOL for six pallets of resin with a ship date of February 30 and a blank lot number line on a customer that requires lot numbers. A careful system does three things:

  1. It does not book the load.
  2. It holds the shipment as pending and asks the sender for the correct date and the lot number.
  3. It tells the team what is missing and what it asked.

If the pickup deadline approaches and the answer has not come, the team should be told again, plainly. For more on this case, see what should happen when orders arrive with missing details or an impossible pickup date.

Common mistakes when starting from BOLs

Mistake 1: Trusting the freight class without a check. A class copied from an old BOL may not match the freight. Compare weight and dimensions to the class on LTL loads before booking.

Mistake 2: Ignoring freight terms. A BOL marked collect usually means the customer's carrier picks up and the customer pays. Those loads may belong outside the shipper's booking scope entirely. Write a rule for them.

Mistake 3: Losing the BOL version. If the warehouse reprints a BOL after a change, the carrier must get the new one. Keep the latest version attached to the shipment and send it again when it changes.

Mistake 4: Scanning a BOL nobody can read. A blurry phone photo of a handwritten BOL is not a reliable source. Ask for a clean PDF or a printed copy from the warehouse system.

Mistake 5: Forgetting the delivery appointment. An "appointment required" note buried in special instructions is easy to miss. Make appointment instructions a field that is always read and acted on.

Which checklist makes a BOL good enough to run a shipment?

A BOL is ready to run a shipment when every field below is filled in and believable. Use this checklist with the warehouse team before sending BOLs to any software.

Item What "ready" looks like Owner
Shipper address Full street address of the dock, not the head office Warehouse
Shipper contact Name or role and phone for pickup questions Warehouse
Consignee address Delivery dock address, not the billing address Customer service
Consignee contact Phone or email for appointments Customer service
Ship date A real date the freight will be staged Warehouse
BOL number Unique for the load Warehouse system
References PO and order numbers the customer expects Customer service
Handling units Pallet or piece count that matches the staged freight Warehouse
Weight Scale weight or a reliable total Warehouse
Dimensions Pallet dimensions for LTL density Warehouse
Freight class Matches the commodity and density (LTL) Logistics
Commodity Plain description, hazmat flagged if relevant Warehouse
Lot numbers Present when the customer requires them Quality or warehouse
Special instructions Liftgate, appointment, inside delivery noted Customer service
Freight terms Prepaid, collect or third party marked Logistics

How to roll out BOL intake

Start with one dock or one group of customers where BOLs are already clean. Send those BOLs to the software for a few weeks and compare the shipments it creates with the BOLs themselves. Were the appointments right? Did any freight class get questioned? Did any BOL get held as pending, and was that correct? Fix the BOL template where the same gap keeps appearing, then add the next dock.

What to keep on the shipment

Keep the original BOL, any reprinted versions, the carrier's acceptance, the rate confirmation, the appointment confirmations, the POD and the carrier invoice on the same shipment. When a customer disputes a delivery or finance questions a charge, the answer should take one search, not a hunt through the shared folder. For a broader view, see how to organize BOLs, PODs and freight documents.

How does Wilson, by Cartage, run a shipment from a bill of lading?

Wilson, by Cartage, is an AI logistics agent that can create a shipment, schedule the pickup and set appointments from a bill of lading alone, because everything it needs to start is on a BOL. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward. Think of it as a free logistics department: what big shippers build over years, Wilson does from day one, in four parts.

The labor. Wilson does the work from the first quote to the final POD. From the BOL, it creates the shipment, requests quotes from the company's approved carriers and compares them on total cost, negotiates toward the company's rate targets within approval limits and books with written acceptance and a rate confirmation. It checks carrier availability before booking. If a carrier can only pick up a day later, Wilson presents that option to the team and updates the expected date, while the agreed date stays unchanged until the team decides. It can read and create appointments in a connected dock calendar and request delivery appointments from receivers. It tracks the load, follows up with carriers by phone and email until it gets an answer, and requests and files the POD.

When a BOL is missing a detail or carries an impossible date, Wilson does not book it. It holds the shipment as pending, asks for the missing detail, tells the team and never invents the value. If a deadline passes while the order is still incomplete, Wilson flags it to the team.

The data. Wilson keeps every order, load, quote, rate, document and contact on record as it works, connected to the company's ERP. Wilson replaces the TMS for freight execution and connects to the company's ERP. Orders can also reach Wilson by email, an ERP connection or CSV/XLSX files, so a BOL can sit alongside other intake. Wilson generates and sends the BOL when it builds one itself, attaches it to the shipment, and records who wrote what and when. Every message, confirmation and change is kept in the shipment's change history.

Wilson works with SAP, NetSuite, Microsoft Dynamics 365, Oracle, Infor, Epicor, Sage, Acumatica and other ERP environments, with the exact connection depending on the customer's data flow and scope.

The network. Wilson gets better freight rates on every lane because the shipper's volume counts with every other Wilson customer's. The network includes carriers and brokers, and the company still approves who hauls its freight.

The payments. Wilson audits every carrier invoice against the rate confirmation and the POD before money moves, then pays carriers from the Wilson Wallet. Invoices over the agreed rate or outside the rules wait for a person.

Control stays with the company. Wilson starts with assisted execution, the company sets approval limits, and routine actions can run automatically within those rules as the workflow is proven. The company can also exclude loads by rule, such as collect or third-party shipments.

Pricing

Wilson is free on Wilson's network: the shipper pays the freight rate and nothing on top. When a shipper keeps its own carriers, the fee is 2% to 0.5% of what Wilson pays them, falling with volume. There are no seat fees, no setup cost and no contract. Timing depends on scope: most teams start on a few lanes and expand from there.

FAQs

Can Wilson move a shipment if we only send it a BOL?

Yes. Wilson, by Cartage, an AI logistics agent, can create a shipment, schedule the pickup and set appointments from a bill of lading alone, because everything it needs to start is on a BOL. It then quotes or books with approved carriers, tracks the load and collects the POD. If the BOL is missing a detail or has an impossible date, Wilson holds it as pending and asks for the answer.

Can freight software run a shipment from a bill of lading alone?

Yes, when the BOL is complete. A BOL names the shipper, consignee, freight, references and payment terms, which is what a booking needs. Missing or impossible details should stop the booking until a person supplies them.

What if the BOL does not name a carrier?

The software should request quotes from the company's approved carriers, compare them on total cost and book within the approval rules. Quotes above the lane limit go to a person.

What if the carrier can't pick up on the BOL date?

The team decides. Wilson presents the carrier's later date as an option, updates the expected date on the shipment and leaves the agreed date unchanged until the team chooses.

Does Wilson guess a missing freight class or lot number?

No. Wilson never invents a missing value. It holds the shipment as pending, asks the sender for the detail and tells the team.

How do we send BOLs to Wilson?

A BOL can reach Wilson by email. Orders can also arrive through an ERP connection or as CSV/XLSX files, and the routes can be combined.

Can Wilson receive orders by EDI?

Not today. Orders reach Wilson by email, an ERP connection or CSV/XLSX files.

Can Wilson book dock appointments?

Wilson can read and create appointments in a connected dock calendar. It is not integrated with third-party dock-scheduling portals.

What about collect or third-party BOLs?

The company decides. Many teams exclude collect and third-party shipments by rule, because the customer or a third party books and pays for those loads.

Does Wilson clear customs on cross-border BOLs?

No. Wilson is not a customs broker. It can generate shipping documents such as the commercial invoice and packing list, help run the customs paperwork under a customer-specific SOP and send the information to the customer's customs broker.

Sources

Send one of your BOLs and see the shipment Wilson would create from it. You don't need to prepare anything: Cartage maps the workflow with you on the call.

Add Cartage as a preferred source on Google