# Support Tokenized Electronic Bills of Lading for Global Trade

## About

<table><thead><tr><th width="304">Use Case Category</th><th>Use Case Scope</th></tr></thead><tbody><tr><td>Trade &#x26; Commerce</td><td>This use case explores tokenizing electronic bills of lading (eBL) on multiple blockchain/DLT networks to digitize global trade finance and shipping logistics.</td></tr></tbody></table>

## Description

**Key Stakeholder:**

* Shipping carriers
* Port operators
* Logistics companies
* Import/export companies
* Banks providing trade finance
* Tokenization and interoperability platform

**Story:**

1. Shipping carrier issues eBL for cargo on blockchain/DTL network
2. eBL is inspected and audited for validity
3. Trusted eBL is tokenized on other blockchains by tokenization and interoperability platform
4. Tokenized eBL used for trade finance and logistics
5. Reduces fraud due to validity of tokenized eBL

**Preconditions:**

* eBLs are issued on a blockchain network
* Multiple tokenization platforms exist

**Postconditions:**&#x20;

* eBLs are tokenized on other blockchain/DLT networks
* Reduces fraud in trade finance

**Key Benefits:**&#x20;

* Digitizes global trade documents
* Enables tokenization for trade finance
* Reduces fraud through validity checks
* Provides trust anchors with audits
* Leads to greater adoption of eBL

## Example Solution Provider:

Ant Group

\--------------

Currently, there are many different eBL solutions. That would mean every shipping carrier, logistics company, and bank supporting many incompatible solutions. Also, rulebooks are incompatible.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://qualitax.gitbook.io/interop/use-cases/trade-and-commerce/support-tokenized-electronic-bills-of-lading-for-global-trade.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.