How to Create a Bill of Lading (A Compliant 2026 Guide)
Learn how to create a bill of lading that is legally compliant and error-free. Our step-by-step guide covers types, required fields, and automation.
You create a bill of lading in a hurry, send the shipment, and assume the paperwork is fine. Then the cargo reaches port, someone spots a mismatch in the shipping details, and the entire movement slows down while operations, finance, and customs all wait for the same document to be corrected.
That's why this document deserves more respect than it typically receives. A bill of lading isn't just a form to complete before dispatch. It's the document that connects the goods, the transport terms, the parties involved, and in some cases the right to claim the cargo itself.
Understanding the Bill of Lading's Critical Role
A bill of lading is the document that sits at the center of a shipment. Operationally, people use it to move freight. Legally, it does much more than that.
The document has three core functions. It acts as a receipt for goods, evidence of the contract of carriage, and a document of title in the cases where title matters. That foundation didn't appear recently. The bill of lading developed over centuries from medieval maritime commerce into the legally significant shipping instrument still used today, as summarized in this history of the bill of lading.
Why minor errors become major problems
A wrong notify party. A vague cargo description. Freight terms marked incorrectly. These look like admin issues, but they don't stay in admin for long.
Once a shipment is moving, the bill of lading becomes a shared reference point for carrier operations, destination handling, customs review, invoicing, and claims. If the document is incomplete or inconsistent, every downstream team starts working from uncertain data.
Practical rule: If a field affects release, rating, customs review, or payment, treat it as a control point, not a clerical field.
That mindset changes how you create a bill of lading. You stop thinking about “filling the form” and start thinking about “issuing an auditable transport record.”
What the document really confirms
At a minimum, the bill of lading should answer four questions clearly:
- Who is involved: shipper, consignee, carrier, and often notify party
- What is moving: goods description, quantity, weight, packaging, marks
- How it is moving: vessel, voyage, route, or transport mode
- How charges and release work: freight terms, signatures, document status
If one of those buckets is weak, the shipment becomes harder to handle correctly.
In practice, teams get into trouble when they copy old templates without checking whether the trade, mode, or release method is still the same. That's where many “small” mistakes start.
Choosing the Correct Type of Bill of Lading
Before you enter a single field, decide which document you need. Many shipments go off track at this stage. Teams often use one generic template for everything, even though the legal meaning of the bill of lading changes by type and by transport mode.
Straight, order, and sea waybill
Here's the practical distinction:
| Type | Best fit | Main trade-off |
|---|---|---|
| Straight bill of lading | Shipment to a named consignee when ownership transfer during transit isn't needed | Simpler release, but not designed for negotiable transfer |
| Order bill of lading | Transactions where title may need to transfer through endorsement | Stronger control over cargo, but more document handling |
| Sea waybill or express release | Trusted counterparties and shipments where speed matters more than paper title transfer | Faster operational flow, but not the same title function as a negotiable original bill |
A straight bill is usually the least complicated option when the seller and buyer already know exactly who should receive the goods. An order bill is different. It's used when the right to the goods may need to move through endorsement and surrender.
A sea waybill or express release is often chosen when nobody wants originals couriered around the world just to release freight that both sides already agree should move quickly.
Mode changes the document requirements
This is the mistake that creates silent risk. Ocean and road documents are not interchangeable. According to Infoplus guidance on creating and printing a bill of lading, ocean BOLs function as title documents and require vessel and voyage details, while trucking BOLs focus much more on freight class and NMFC information for rating and liability.
That means the right question isn't only “Which BOL type do I need?” It's also “Which mode-specific data fields make this version legally and operationally usable?”
For teams working with retail and warehouse workflows, a more specialized format may apply. If your shipments run through retailer compliance programs, a VICS bill of lading guide is often more useful than a generic freight template.
A short walkthrough can help if your team wants a visual comparison before deciding:
Pick the document type based on how cargo will be released and whether title needs to move during transit. Don't pick it based on whichever template your team used last week.
A simple selection test
Use this quick decision logic:
- Known buyer, no transfer of title needed: Straight bill usually fits.
- Banking, trade finance, or resale while goods are in transit: Order bill is often the safer route.
- Trusted trade lane where speed is more important than handling originals: Sea waybill or express release may make more sense.
- Road freight or LTL workflows: Use a mode-specific freight BOL, not an ocean template with renamed fields.
Required Fields for a Compliant Bill of Lading
When operators create a bill of lading correctly, they don't start with a blank page. They start with structured shipment data, choose the proper BOL type, then validate the required fields before signature and distribution. Core industry guidance consistently includes shipper and consignee details, notify party, mode of carriage, ports, cargo count and weight, freight terms, date, and signatures. Missing or inconsistent information is a common source of customs delays and invoicing disputes, as outlined in this practical guide to creating a bill of lading.
The parties
These fields identify who is sending, receiving, and coordinating the shipment.
Shipper details
Legal name and address need to match the commercial reality of who is tendering the goods. If the wrong legal entity appears here, disputes over responsibility become harder to unwind.Consignee details
This is who should receive the cargo. If the name or address is incomplete, release can stall, delivery can be misdirected, and finance may later find that the shipment paperwork doesn't line up with the sale.Notify party
Teams often treat this as optional admin text. It isn't. The notify party is often the first operational contact at destination, so an error here can delay communication when the cargo is ready, held, or needs action.
The cargo
Many “looks fine to me” drafts fail under real scrutiny.
| Field | Why it matters | What goes wrong if it's wrong |
|---|---|---|
| Description of goods | Supports handling, customs review, and document matching | Vague descriptions trigger questions and manual checks |
| Package count | Confirms what was handed over | Count disputes show up at delivery or during claims |
| Weight and measurements | Affect planning, rating, and documentation consistency | Billing and liability issues follow mismatches |
| Shipping marks | Help identify cargo physically | Warehouse and port handling become slower and riskier |
The cargo description should be specific enough to identify what is moving. “Freight” is not a useful description. “Parts” is often barely better. The right level of detail depends on the mode and trade lane, but the goal is always the same: the bill of lading should support handling and document matching without forcing someone else to guess.
Field check: If a warehouse clerk, customs reviewer, and carrier billing team would each interpret the description differently, it's too vague.
The journey
This part ties the goods to the transport plan.
Mode of carriage
The document should clearly reflect whether this is ocean, trucking, or multimodal movement. That affects both meaning and required data.Vessel and voyage or route details
These matter especially in ocean movements. If they're missing where required, the document may not support downstream handoffs properly.Ports of loading and discharge
These are not decorative labels. They anchor the shipment to specific movement points and help align the bill of lading with the rest of the shipping set.Freight terms
Prepaid and collect have immediate billing consequences. A wrong selection creates arguments later that operations can't solve.Date and signatures
A bill of lading without valid execution is a weak control document. Signatures confirm acceptance and formal issuance.
If your team still prepares documents manually in office files, a bill of lading Word format reference can help as a starting point, but templates only work if the underlying data is validated before release.
The best working method
The most reliable process is simple:
- Collect master shipment data
- Select the correct bill of lading type
- Validate party, cargo, and route fields
- Review mode-specific requirements
- Sign and distribute only after the checks pass
What doesn't work is drafting first and reconciling later. By then, the document has usually already spread to carriers, brokers, and customers.
Common Pitfalls That Derail Shipments
Most bill of lading failures don't come from obscure legal issues. They come from ordinary operational shortcuts. Someone reuses an old file. Someone enters a broad cargo description because the detailed one isn't handy. Someone assumes freight terms are unchanged from the prior booking.
Then the consequences hit later, in a place where fixing the mistake is slower and more expensive.
The data errors that matter most
The most damaging mistakes are usually these:
Declared value entered incorrectly
This directly affects liability and can complicate insurance settlement if something goes wrong.NMFC class entered incorrectly
In road freight, this changes rating and can lead to freight charge disputes.BOL data not matching related documents
When the bill of lading conflicts with the invoice or shipping instructions, downstream teams stop trusting the set.Freight terms selected incorrectly
“Prepaid” versus “collect” looks small until someone issues an invoice the other side refuses to accept.
Industry guidance is clear on the consequences. Inaccuracies such as the wrong declared value or NMFC class directly affect carrier liability, insurance settlements, and freight charges, as explained in this bill of lading automation guide.
Why manual review misses them
Manual review catches obvious blanks. It often misses cross-document inconsistency.
A person looking at one PDF can confirm that a field exists. That same person may not notice that the package count doesn't match the packing list, that the commodity wording doesn't align with the invoice, or that the selected BOL type doesn't fit the release method.
That's the core operational problem. The issue usually isn't writing the document. It's validating whether the document is correct in context.
Teams don't lose time because they can't type a bill of lading. They lose time because they discover bad data after the shipment is already in motion.
What these mistakes turn into
| Mistake | Operational consequence |
|---|---|
| Vague cargo description | More questions, more checks, slower clearance |
| Incorrect charges basis | Billing disputes with carriers or customers |
| Wrong party details | Misrouted communication and release delays |
| Missing or inconsistent shipment data | Rework across operations, finance, and compliance |
The pattern is predictable. Errors created at source don't stay local. They spread across departments.
That's why experienced teams put controls at document creation, not only at exception handling. Once the cargo is delayed, nobody cares that the original error looked minor in the template.
Automating Bill of Lading Creation with AI
Manual bill of lading creation works at low volume, with stable trade lanes, and with people who know exactly what to look for. It starts to break when documents arrive from multiple systems, data is copied across files, and staff have to review exceptions under time pressure.
Traditional OCR doesn't solve that by itself. OCR reads text. It doesn't reliably decide what kind of document it has received, map the right fields into a structured schema, or apply business validation before the data moves downstream.
What an automated workflow should actually do
For bill of lading processing, the useful sequence is:
Classify the incoming document
Distinguish an original B/L from a sea waybill, telex release, invoice, or supporting file.Extract the key fields
Pull shipper, consignee, notify party, vessel or route details, cargo data, freight terms, and document references into structured output.Validate against rules
Check completeness, consistency, and mode-specific requirements before the record is approved.Route exceptions
Send only the uncertain or inconsistent cases to a human reviewer.
That's the gap between OCR and document automation. Reading text is only the first step. Its primary value comes from turning shipping paperwork into validated data that operations and finance can trust.
Where modern tools fit
Tools built for document automation now go beyond scan-and-read workflows. They combine OCR, classification, validation, and orchestration so the system can process mixed shipping documents without relying on a person to inspect every file by hand.
One example is Matil's data extraction API, which supports logistics documents including bills of lading and combines OCR with document classification, validation, and workflow handling. According to the product information provided by the publisher, Matil also offers pre-trained models, rapid customization, API-based integration, security controls including GDPR, ISO 27001, and AICPA SOC alignment, plus a zero data retention option and availability above 99.99%. The publisher also states that its extraction accuracy is above 99% in multiple use cases.
What works and what doesn't
What works:
- Structured extraction schemas that force the same field logic every time
- Mode-specific validation rules so ocean and trucking documents aren't treated the same
- Exception-based review so people focus on doubtful cases, not every case
- API integration with TMS, ERP, or document intake workflows
What doesn't work:
- Generic OCR alone with no field validation
- One universal template for every shipment type
- Manual copy-paste from invoices, emails, and warehouse notes
- End-of-process checking after the bill of lading has already been issued
Operational takeaway: The right automation target isn't “generate a PDF faster.” It's “stop bad shipment data from becoming an issued transport document.”
For teams processing high document volumes, that distinction matters more than the interface. The system has to help prevent errors at source, not just digitize them neatly.
Signing, Issuing, and Transferring Ownership
Completing the fields isn't the end of the process. A bill of lading only starts to matter commercially once it's properly issued and signed.
The signature confirms that the document has been accepted in its transport context. Depending on the movement, that signature may come from the carrier, the master, or an authorized agent. What matters operationally is that the document is executed by the party with authority to issue it in that chain.
Why originals still matter in some trades
For negotiable bills, control of the document can still matter as much as control of the cargo. That legal logic is part of why the bill of lading remains so important in international trade. Its modern legal role was shaped by Lickbarrow v Mason (1786) and later standardized through the Hague Rules (1924), which are summarized in this short legal history of the bill of lading.
That history still shows up in practice. If you're using an order bill of lading, ownership can move through endorsement while the goods are still in transit. If you're using a straight bill of lading or a surrendered release method, the release mechanics are simpler.
Practical release options
A few common operational patterns matter here:
Original paper bills
Often used where negotiability and formal surrender remain important.Surrendered BOL or telex release
Common when the parties want faster release without moving original paper around.Sea waybill
Useful when no transfer of title by document is needed and speed is the priority.
The wrong release method creates avoidable friction. If your commercial arrangement requires document control, don't switch to a faster release option just because it feels simpler. If the shipment is routine and trust is established, forcing original paper through the process can create delay for no real benefit.
Signed correctly, issued correctly, and matched to the right release method, the bill of lading does its job quietly. Most problems begin when one of those three conditions is missing.
If you're evaluating how to automate bill of lading workflows, it helps to look beyond basic OCR. Matil is one option for teams that need OCR plus classification, validation, and workflow automation for logistics documents, with API-based integration and support for high-volume document processing.
