Freight guide

What Is an Electronic Bill of Lading?

Learn what an electronic bill of lading is, how an eBOL works in commercial LTL shipping, what it must contain, and what to verify before pickup.

By: Shipocity Editorial
Published: Jul 22, 2026
Updated: Jul 22, 2026
Reading time: 8 minutes

A blank tablet on a shipping stand beside a prepared pallet at an unbranded loading dock.

The direct answer

An electronic bill of lading, usually shortened to eBOL, is a bill of lading whose shipment information is created, sent, accepted, updated, and retained as an electronic record instead of moving only on paper. In commercial less-than-truckload shipping, that record can carry the same core shipment details as a paper BOL while allowing the shipper, carrier, and logistics provider to exchange structured data through compatible systems.

An eBOL is not simply a photograph or PDF of a paper form. A scan can be useful evidence, but a true electronic workflow generally keeps the underlying fields as data that authorized parties can transmit and process. NMFTA’s current LTL eBOL API standard, Version 2.1, supports creating, updating, and deleting eBOL records through a common interface.

The word electronic does not make the shipment information correct, prove that the carrier picked up the freight, or force every carrier to accept the same technology. The parties still need an agreed workflow, accurate shipment data, appropriate acceptance at pickup, and a record they can retrieve later.

What information belongs in an eBOL?

The format may change, but the underlying shipment facts do not disappear. For a covered for-hire, non-exempt motor carrier, 49 CFR 373.101 lists five baseline categories for a receipt or bill of lading:

The names of the consignor and consignee.
The origin and destination points.
The number of packages.
A description of the freight.
The weight, volume, or measurement when it applies to rating the freight.

A practical commercial LTL eBOL commonly carries more operational detail, such as handling-unit type and count, packaged dimensions, commodity and classification information when applicable, payment terms, requested services, shipment identifiers, and pickup instructions. Which fields are required depends on the carrier, the transportation agreement, the freight, and the system used.

Accuracy still begins with the freight as it is actually tendered. A structured field can prevent illegible handwriting and reduce repeated data entry, but it cannot correct a guessed weight, an incomplete address, a vague commodity description, or a missing service request.

How does an electronic bill of lading work?

An eBOL workflow usually has five stages. The exact screens, acknowledgments, and document names vary by carrier and technology provider.

1. Shipment data is gathered

The shipper or its authorized logistics provider collects the origin and destination details, final packaged piece count, dimensions, weight, commodity description, and required services. The data should match the freight that will be available at pickup.

2. The electronic record is created

A transportation management system, carrier portal, or connected logistics platform creates the eBOL. In an API-based workflow, the fields are sent as structured data rather than copied manually onto a new form.

3. The carrier receives the information

The record is transmitted according to the carrier’s supported process. NMFTA’s Digital LTL Council publishes a common API standard intended to make this exchange more consistent across LTL participants, but use of that standard does not mean every carrier has the same integration, cutoff time, or acceptance procedure.

4. Pickup acceptance is recorded

The carrier follows its own process to acknowledge the freight and document the pickup. That may involve a signature, authenticated user action, status event, or another electronic acknowledgment. Creating an eBOL before the truck arrives is not, by itself, proof that the carrier received the freight in the stated quantity or condition. For covered transportation, 49 U.S.C. 14706 says a carrier’s failure to issue a receipt or BOL does not erase the liability otherwise imposed by that section; that liability rule still does not turn a pre-pickup record into evidence of receipt.

5. The record is retained and used downstream

Authorized parties can retain the origin record and related status history for later reference. The shipment may also produce separate records, including a delivery receipt or proof of delivery and a carrier invoice. Those documents are related to the eBOL, but they are not automatically the same record.

Electronic BOL versus paper BOL

The useful difference is how the information moves and is controlled, not a promise that every digital shipment is paperless from end to end.

Question	Paper BOL	Electronic BOL
How is information entered?	Written or printed on a form	Entered in a system and often exchanged as structured data
How is it shared?	Physical copies, scans, email, or manual re-entry	Portal, system integration, or API supported by the parties
How are corrections handled?	A revised form or documented correction	An authorized update in the system, subject to carrier rules and timing
How is acceptance shown?	Commonly a physical signature or notation	The carrier’s supported electronic acknowledgment or signature process
How is it retained?	Paper files and scanned copies	An accessible electronic record that can be reproduced later
What can still go wrong?	Illegible entries, missing pages, conflicting copies	Bad source data, failed transmission, access problems, or incompatible systems

Federal electronic-commerce law provides an important limit and an important protection. Under 15 U.S.C. 7001, a signature, contract, or record in interstate or foreign commerce generally cannot be denied legal effect solely because it is electronic. The same section does not require a person to agree to use electronic records. When retention is legally required, the electronic record must accurately reflect the information and remain accessible in a form that can be reproduced later.

That is why “we have a PDF” is not a complete compliance or operations test. The relevant questions are whether the parties agreed to the electronic process, whether the record preserves the required information, whether authorized people can access it, and whether it can be reproduced when needed.

What an eBOL does not do

Several common assumptions can cause trouble at the dock or after delivery.

It does not schedule the pickup by itself. Creating or transmitting an eBOL and requesting a truck can be separate steps. Confirm the carrier’s booking and pickup-request process.
It does not prove pickup before acceptance. A pre-pickup record describes what is intended to move. Preserve the carrier’s completed origin acknowledgment.
It does not validate every field. A system may catch missing or malformed data without knowing whether the packaged weight, dimensions, commodity description, or location details are true.
It does not erase the governing terms. Moving the record from paper to data does not automatically change carrier rules, agreed liability terms, payment instructions, or special-handling requirements.
It is not automatically a delivery receipt. Delivery condition and receipt are ordinarily recorded later, even when one platform links the records.
It is not one universal global document. A domestic commercial LTL eBOL should not be treated as interchangeable with a negotiable ocean bill used in a trade-finance transaction. Governing law, transfer-of-title issues, and platform rules can differ materially.

If a shipment involves hazardous materials, cross-border documents, letters of credit, negotiable title, or a live dispute, use the carrier’s instructions and obtain qualified compliance or legal advice for that transaction. A general eBOL workflow is not a substitute for shipment-specific requirements.

What should you verify before submitting an eBOL?

Review the electronic record against the packed freight and the booking confirmation. A concise pre-submission check should cover:

Confirm the legal or operating names and complete addresses for the shipper and consignee.
Count the final pallets, crates, cartons, or other handling units.
Measure and weigh the shipment after packaging, including the pallet or crate.
Use a specific commodity description and include freight class or NMFC information only when applicable and supportable.
Confirm the services required at both locations, such as liftgate, appointment, residential, or limited-access service.
Check payment, valuation, release, and special-instruction fields before accepting them.
Make sure the carrier supports the chosen electronic submission method and determine whether a paper copy is still required at pickup.
Save the carrier’s acceptance record and later delivery documentation in a retrievable format.

If the freight or service details change after submission, do not assume that editing your local copy updates the carrier’s record. Follow the carrier or platform process, confirm that the revision was accepted, and retain the resulting version history or acknowledgment.

Prepare accurate data before booking

Shipocity is backed by a team with more than 40 years of combined logistics experience. Through established industry relationships, the platform helps businesses compare competitive freight rates for their specific shipment.

Gather the final packaged dimensions, weight, handling-unit count, commodity description, origin and destination details, and required services before you begin. Then book a shipment and let Shipocity prepare the paperwork using the details that will carry into booking and shipment documentation.