Version 3 · In use with partners
The open standard for the electronic Bill of Lading.
eBOL is a system-agnostic format for exchanging bill of lading data in real time between shippers, carriers, logistics providers and the people waiting on the freight. Version 3 is in use today with a group of shippers and carriers working directly with Advanced Solutions. We are refining it with them on the way to an open-source release.
header.numbershipDatescacparties.shipper1200 W Fulton St, Chicago IL 60607
parties.consignee88 Commerce Dr, Des Moines IA 50309
refs.prorefs.potermsissueDate| HU | Pkgs | Description | NMFC | Class | Weight lb |
|---|---|---|---|---|---|
| PLT | 2 | Shelving components, KD | 79300 | 85 | 1,640 |
| PLT | 1 | Paint, flammable liquid UN1263 · 3 · PG III | 149980 | 55 | 780 |
{
"ebolVersion": "3",
"header": { "number": "EB-2026-004817", "type": "straight", "issueDate": "2026-11-14", "shipDate": "2026-11-16" },
"parties": {
"shipper": { "name": "Lakeshore Supply Co.", "address": { "line1": "1200 W Fulton St", "city": "Chicago", "region": "IL", "postal": "60607", "country": "US" } },
"consignee": { "name": "Prairie Hardware DC", "address": { "line1": "88 Commerce Dr", "city": "Des Moines", "region": "IA", "postal": "50309", "country": "US" } },
"carrier": { "name": "Example Freight Lines", "scac": "XMPL" }
},
"refs": { "pro": "412-889301", "po": ["PO-77193"] },
"terms": { "freight": "prepaid" },
"units": [
{ "type": "PLT", "count": 2, "description": "Shelving components, KD", "nmfc": "79300", "class": 85, "weight": { "value": 1640, "unit": "lb" } },
{ "type": "PLT", "count": 1, "description": "Paint", "nmfc": "149980", "class": 55, "weight": { "value": 780, "unit": "lb" },
"hazmat": { "un": "UN1263", "properShippingName": "Paint", "hazardClass": "3", "packingGroup": "III" } }
]
}
01
Why an open standard
The bill of lading is the one document every party in a shipment touches. When each company digitizes it differently, the paper comes back. eBOL is already used to exchange shipping data between partners. Once the requirements settle, publishing it openly will let anyone implement it without asking permission.
Headed for open source
Today the specification is shared with partners. The goal is to publish the spec, schema and examples under an open license.
System-agnostic
Works with whatever TMS, WMS or ERP each partner runs. eBOL defines the data, not the software.
Real-time
Status events link to the eBOL by its BOL number and travel separately, so partners see pickup and delivery as they happen.
Small on purpose
A required core that fits on one page, with optional extensions for hazmat, customs and specialty freight.
02
The specification
Version 3 is organized into seven sections. The full specification, JSON Schema and example files are available to partners.
| Object | Section | What it covers |
|---|---|---|
| header | Document header | BOL number, type (straight, order), version, issue and ship dates, issuing party. |
| parties | Parties | Shipper, consignee, bill-to, carrier and third parties, with addresses and identifiers such as SCAC, DUNS or GLN. |
| refs | References | PRO, PO, shipper and customer reference numbers, load and appointment IDs. |
| units | Handling units & line items | Pallets, packages, piece counts, dimensions, weight, NMFC item and freight class. |
| hazmat | Hazardous materials | UN/NA number, proper shipping name, hazard class, packing group, emergency contact. |
| terms | Terms & charges | Freight terms, COD, declared value, special instructions and accessorials. |
| signatures | Custody & signatures | Electronic signatures at pickup and delivery, proof of delivery, exceptions noted on receipt. |
Status events are part of the eBOL standard and are exchanged separately, linked to each eBOL by its BOL number. Tendered, picked up, in transit, exception and delivered updates flow in real time.
03
How the standard evolves
Each version is shaped by partners using eBOL on real shipments. Their feedback decides what changes in the next release.
Use
Partners exchange eBOLs on live shipments with their trading partners.
Report
Gaps, edge cases and integration problems are logged as they come up.
Propose
Partners submit change requests describing the problem, the change and who it affects.
Review
Advanced Solutions reviews each request with input from the partners it affects.
Release
Accepted changes ship in the next version with a changelog entry.
Partner feedback
Partners can send questions, corrections and change requests. A useful request includes:
- The section it applies to, such as
unitsorhazmat - The problem you hit in a real shipment or integration
- What you would change, and who it affects
Follow the open-source release
Not a partner yet, or interested in eBOL as a standard? Tell us who you are and we will keep you informed as the specification moves toward public release.
- Notice when the public draft opens for comment
- Invitation to the open working group
- Release notes for each new version
Partners discuss changes in the eBOL Standards Forum.
04
Road to open source
eBOL is maintained today by Advanced Solutions and used within a closed group of customers and carriers. The plan is to settle the requirements with them, then hand the standard to an open working group and release it as open source.
Done
Versions 1 and 2
eBOL is built and put into production exchanging shipping data between shippers, logistics providers and data recipients.
Now
Version 3 with partners
A closed group of customers and carriers uses eBOL on live freight while the requirements are worked through.
Next
Public draft
The specification is published for open comment, and an open working group forms.
Then
Open source
Spec, schema and a reference implementation released under an open license.
05
Logistics glossary
Terms used throughout the specification.
Bill of Lading
The document a carrier issues to a shipper acknowledging receipt of freight. It serves as a receipt, a contract of carriage and, for some types, a document of title.
eBOL
An electronic bill of lading. Also the name of this standard for structuring and exchanging that data.
Shipper
The party tendering the freight, usually the seller or the facility the goods leave from.
Consignee
The party the freight is delivered to.
Carrier
The company that physically moves the freight.
3PL
Third-party logistics provider. Arranges or manages transportation and warehousing on behalf of a shipper.
SCAC
Standard Carrier Alpha Code. A two-to-four letter code identifying a carrier.
PRO number
The carrier’s tracking number for a shipment, assigned at pickup or pre-printed on the BOL.
NMFC
National Motor Freight Classification. Item numbers that describe a commodity for LTL pricing.
Freight class
A rating from 50 to 500 under NMFC, based on density, handling, stowability and liability.
Handling unit
The unit a carrier handles as one piece, such as a pallet, crate or drum.
LTL
Less-than-truckload. Freight that shares trailer space with other shippers’ freight.
POD
Proof of delivery. The consignee’s signed confirmation that the freight arrived, with any exceptions noted.
Straight BOL
A non-negotiable bill of lading consigned to a named party.
Order BOL
A negotiable bill of lading that can transfer title to the goods by endorsement.
UN number
A four-digit number identifying a hazardous substance for transport, such as UN1263 for paint.
Accessorial
A charge for a service beyond standard pickup and delivery, such as liftgate or inside delivery.
Freight terms
Who pays the freight charges: prepaid by the shipper, collect from the consignee, or a third party.
06
Partner access
eBOL is currently available to shippers and carriers working directly with Advanced Solutions or one of its customers. Request access with the partner code you were given. No code? Ask your Advanced Solutions contact.
For shippers
Request shipper access
For vendor partners referred by an Advanced Partner. Have your partner code ready.
For carriers
Request carrier access
For carrier partners working with Advanced Shippers. Have your partner code and SCAC ready.