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.

Straight Bill of LadingSample · not a real shipment
BOL number header.number
EB-2026-004817
Ship date shipDate
2026-11-16
Carrier SCAC scac
XMPL
Shipper parties.shipper
Lakeshore Supply Co.
1200 W Fulton St, Chicago IL 60607
Consignee parties.consignee
Prairie Hardware DC
88 Commerce Dr, Des Moines IA 50309
PRO number refs.pro
412-889301
PO / Ref refs.po
PO-77193
Freight terms terms
Prepaid
Issue date issueDate
2026-11-14
HUPkgsDescriptionNMFCClassWeight lb
PLT2Shelving components, KD79300851,640
PLT1Paint, flammable liquid UN1263 · 3 · PG III14998055780
Same shipment, two views. Fields map 1:1.

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.

ObjectSectionWhat it covers
headerDocument headerBOL number, type (straight, order), version, issue and ship dates, issuing party.
partiesPartiesShipper, consignee, bill-to, carrier and third parties, with addresses and identifiers such as SCAC, DUNS or GLN.
refsReferencesPRO, PO, shipper and customer reference numbers, load and appointment IDs.
unitsHandling units & line itemsPallets, packages, piece counts, dimensions, weight, NMFC item and freight class.
hazmatHazardous materialsUN/NA number, proper shipping name, hazard class, packing group, emergency contact.
termsTerms & chargesFreight terms, COD, declared value, special instructions and accessorials.
signaturesCustody & signaturesElectronic 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 units or hazmat
  • 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

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.