Skip to content

eBL

Copyright IBM Corporation and GTD Solution Inc. 2020, 2021

Overview

TradeLens eBL (electronic Bill of Lading) scenarios will be delivered in a phased approach. TradeLens currently supports several eBL scenarios, see the eBL Scenario Reference at the end of this page. A TradeLens eBL is a receipt of the goods by the Carrier. This digital asset provides evidence of the contract of carriage between the Shipper and Carrier, and the holder of the eBL has title to the goods listed.

Digitizing the end-to-end process of a Bill of Lading delivers substantial value in terms of direct and indirect cost reduction as well as process improvements. All the parties involved in the transfer save courier fees and avoid delays in the movement of the cargo. The ability to programmatically ingest the information contained in the Bill of Lading also creates opportunities to automate downstream processes.

The eBL flow requires that all parties involved (for example: Carrier, Shipper/Consignor, Doc Receiver, and Buyer/Consignee), must be on the TradeLens platform, have an established business partnership (see Supply Chain Partner Relationships), and be entitled to TradeLens eBL capability (entitlement is done by the onboarding team). The Shipper first requests an eBL through shipping instructions sent to the Carrier. This could be a Shipping Instructions (SI) document submitted through Actionable Doc Flows on the platform. The Carrier accepts the SI and generates a Bill of Lading (BoL) as an eBL ("eBL" :true in the BoL JSON file) and submits it through Actionable Doc Flows to the platform and the eBL flow starts.

The following diagram shows the steps involved for a basic eBL flow and the actions that each party can perform.

ebol_flow1d

  1. Carrier Actions: The eBL is internally issued by the platform once the Carrier submits the Bill of Lading using Actionable Flows. The eBL is assigned to the Shipper/Consignor as the title holder.

  2. Shipper/Consignor Actions: The Shipper/Consignor can check for an issued eBL through a subscription, or by setting up a notification for the Bill of Lading Issued. They can view or download the structured JSON document and a printable copy (pdf, jpeg, or png) if available. They can transfer the eBL to the Buyer/Consignee, surrender the eBL to the Carrier by specifying a release party (this is the Telex process), or choose switchtopaper to transfer the eBL back to the Carrier and change the Bill of Lading from digital to paper.

  3. Buyer/Consignee Actions: The Buyer/Consignee can check for a transferred eBL through a subscription (note that they are not looking for what eBLs have been issued, they are looking for eBLs that have been transferred to them). They can view or download the structured JSON document and a printable copy (pdf, jpeg, or png) if available. They can transfer to another Buyer/Consignee, surrender the eBL to the Carrier, or choose switchtopaper to transfer the eBL back to the Carrier and change the Bill of Lading from digital to paper.

The Carrier is always considered the issuer of an eBL. When you transfer an eBL, you are not the title holder anymore. When you surrender an eBL, the platform registers the last title holder so that the Carrier can start the delivery process. This allows the Buyer/Consignee to receive the goods from the Carrier upon delivery. When you surrender an eBL, you are required to acknowledge and accept the Carrier's BoL Terms and Conditions. The Terms and Conditions are provided by the Carrier in the Bill of Lading document. The eBL operations are recorded on the blockchain ledger as part of the smart contract.

TradeLens supports the Carrier Telex release process. This allows the Consignor (Shipper) to surrender the eBL back to Carrier without a previous transfer. At the time of surrender, the Consignor (Shipper) can define the release party as the Consignee by using an existing partyRef from an established business partnership or use free text to enter the name and address.
Note: If the Consignor uses the free text option to enter the name and address (verses using a partyRef), TradeLens does not do any validation on the name and address fields.

ebol_flow12c

The switchtopaper action can happen when the eBL is in the issue state or the transfer state and can be used in situations where not all of the participants on the eBL flow are using an electronic (digital) bill and they instead need a paper bill. The current holder can request that the electronic bill be switched to a paper bill, and the flow passes back to the Carrier to create a paper bill. Once an eBL is either surrendered to the Carrier or switched to paper, the Carrier will retrieve the Bill of Lading and this marks the terminal state of the eBL flow.

As mentioned above, the issue action is done by the platform as part of the first step in the eBL flow. The transfer, surrender, and switchtopaper actions can be performed through the POST ...​/actionableMessageFlows​/docMessages - Performs Document Action Actionable Flows API (using the actionIdentifiers: eBLTransfer, eBLSurrender, and eBLSwitchToPaper). See the API User Guide for more information on using the TradeLens APIs. The actions can also be performed through the UI.

TradeLens also supports the case where the Freight Forwarder (or Agent) is the first receiver (Doc Receiver) of the eBL and uses the BoL to ensure the payment from the Shipper. See the eBL Scenario Reference at the end of this page for several Doc Receiver scenarios. The Doc Receiver will be assigned the REQUEST_PARTY role when the eBL is issued and will also be assigned the TITLE_HOLDER role in the consignment until they transfer the eBL. To enable the Doc Receiver eBL feature, the Carrier is required to provide the Doc Receiver information in the structured Bill of Lading document. The partyRole of "docReceiver" must be specified and either a valid organizationId or partyRef must be provided. The following diagram shows three scenarios when a Doc Receiver is involved in the flow.

ebol_flow4a


The example below is a basic eBL flow involving the Shipper/Consignor, Buyer/Consignee, and Carrier. We will show how the UI and APIs can be used to take the appropriate action for each step. You might only be interested in the actions that your organization can perform. So if you are a Shipper/Consignor, for example, you can skip to a particular section by using the navigation links on the right-hand side of the documentation page.


UI Example

In general, the UI section for eBL is a way for you to view eBLs so that you can take action. It is not a historical view, meaning that if you are not the title holder of the eBL, the eBL will be removed from your view in the eBL section of the UI. If (based on your role and the state of the document) you cannot perform any action, there will be no action icons on the UI.

In each of the scenarios below for the UI, you might also choose to set up a subscription or a notification so that you will know when there is a possible action for you to take on the UI. We discuss specific subscription parameters in the API sections below, so we will not repeat the information here. See the Setting Up Subscriptions section for more general information on subscriptions and see the Notifications and Alerts section for more information on the Notifications and Alerts feature.


Shipper/Consignor

Check for Issued eBLs

Navigate to Flows > eBL and find any eBLs that show a Current Status of Issued. You can search on a Bill of Lading Number and use the Current Status filter to help narrow the results on the UI. You will see any Actions (represented by icons) that you can currently take on the eBL, for example: View Document, Transfer, Switch to Paper, and Surrender.

ebol3b

Take Action

In our example, we see all 4 Actions are available: View Document, Transfer, Switch to Paper, and Surrender. In our example, we will choose to transfer the eBL to the Consignee. We click the Transfer icon and our Consignee (from the BoL) is preselected and we can click Transfer to confirm the transfer. We could select a different business partner on the Transfer to a Business Partner dialog box if needed; the ones that are shown are entitled for eBL and have an established business partnership with our org.

ebol5b

Once it has been transferred, the eBL is removed from our view. If we search on the BoL number, it will not show up in our eBL view on the UI.

ebol7b

If we look at the consignment, we can see the Bill of Lading transferred event.

ebol9b

The event details for the Bill of Lading transferred event shows the Action as Transferred and the Destination Organization Name.

ebol11b


Buyer/Consignee

Check for Transferred eBLs

Navigate to Flows > eBL and find any eBLs that show a Current Status of Transferred. You can search on a Bill of Lading Number and also select Transferred for the Current Status to help narrow the results on the UI. You will see any Actions (represented by icons) that you can currently take on the eBL, for example: View Document, Transfer, Switch to Paper, and Surrender.

ebol23b

Take Action

In our example, we see all 4 Actions are available: View Document, Transfer, Switch to Paper, and Surrender. We will choose to surrender the eBL to the Carrier. We click the Surrender icon and our Carrier (from the BoL) is displayed. Review the Terms and Conditions for the Carrier and then check the box to agree to the terms. We can then click the Surrender button. Notice that we could choose to "Add Release Party" if we want to authorize the Carrier to release the goods to the specified party; this would be the case if the party picking up the goods is not the Consignee in the BoL.

ebol25b

Once it has been surrendered, there will be no further actions (except for View Document) on the UI for the Buyer/Consignee, but the eBL will still be displayed on the UI because the platform leaves the title holder as the last org. This allows the Buyer/Consignee to receive the goods from the Carrier upon delivery.

ebol27b


Carrier

Check for Surrendered or Switched to Paper eBLs

Navigate to Flows > eBL and find any eBLs that show a Current Status of Surrendered or Switched to Paper. You can search on a Bill of Lading Number and also select Surrendered or Switched to Paper for the Current Status to help narrow the results on the UI. There will be no actions to take on the UI since this is terminal state for the eBL flow, but you would perform any appropriate operations on your system. The eBL will still be displayed on the UI, it is not removed from the Carrier's view.

ebol33b

The Carrier can also see the endorsement chain for the eBL flow.

ebol35b



API Example

Similar to the UI, the APIs allow you to perform actions on the eBL, depending on the current state of the eBL flow.


Shipper/Consignor

Here is a basic outline of the process that we will follow to illustrate how you can use the APIs for eBL processing:

  • Create a subscription to receive doc events (you could also set up notifications if you prefer)
    • Optionally, specify docType BILL_OF_LADING and actions for issued, transferred, surrendered, and switchedtopaper as part of the subscription
    • For each docType of BILL_OF_LADING (eventType of documentEvents) received on the subscription
      • If destinationOrgName is your orgName, you have the next action for the eBL
        • If issued - you can transfer or switchtopaper (or surrender if using Telex release process)
        • If transferred - you can transfer, switchtopaper, or surrender
        • Take the appropriate action using Actionable Flows API: POST​ ...​/actionableMessageFlows​/docMessages
      • If senderOrgName is your orgName, this is just a notification of an action you performed
      • Otherwise (you are not the sender nor the destination of the action)
        • This is just a notification that the eBL, for a consignment that you participate on, is “flowing”. You might choose to record that for your purposes depending on your requirements

Create Subscription

We will start by creating a subscription for the Shipper/Consignor organization to receive documentation events so that we can take action when certain events occur. See the Setting Up Subscriptions section for more information on subscriptions. You could also set up notifications if you prefer. We will create an organization subscription and specify docType BILL_OF_LADING and actions for issued, transferred, surrendered, and switchedtopaper as part of the subscription. Subscriptions can be set up through the UI, but we will use the Event Subscription API POST ...​/subscriptions​/org - Create a subscription for your organization in this case. We use the Swagger to create the subscription.

ebol53a

Here is the entire body.

{
  "name": "subscriptionBoLConsignor",
  "orgEventTypes": [
    "documentEvents"
  ],
  "docEventFilters": [
    {
      "action": "issued",
      "docType": "BILL_OF_LADING"
    },
    {
      "action": "transferred",
      "docType": "BILL_OF_LADING"
    },
    {
      "action": "surrendered",
      "docType": "BILL_OF_LADING"
    },
    {
      "action": "switchedtopaper",
      "docType": "BILL_OF_LADING"
    }
  ],

  "webhook": {
    "sharedSecret": "********",
    "uri": "https://mywebhook.com/subscriptionBoLConsignor"
  }
}

Check for BoL Events

When the Carrier submits the BoL through Actionable Flows, the platform will issue the eBL and the event will be sent to our subscription. The following image represents the payload that is sent to our subscription. It has been altered to mask the specific test ids, but we can see the eventName is "Document Events", the action is "issued" and the destinationOrgName is our organization (the Shipper/Consignor), so we have the next action for the eBL.

ebol55b

Take Action

As mentioned in the basic outline above, since the destinationOrgName is our orgName, we have the next action for the eBL. Since the current status is issued, we can transfer or switchtopaper (or surrender if using Telex release process). In our example, we will transfer to the Buyer/Consignee (like we did in our UI example). This will allow us to continue our example with the Buyer/Consignee in the next section. We use the POST​ ...​/actionableMessageFlows​/docMessages - Performs Document Action (that can be found in the Actionable Message Flows section of the Actionable Flows API). Review the Swagger description for the API to become familiar with it. The API can be used for different document actions on different types of documents. For our case, there are several pieces of required information that we need to provide in the payload to identify our consignment, document, action, and party. We need a consignment identifier (we could use the consignmentId, or the combination of carrierBookingNumber and billOfLadingNumber), the action identifier eBLTransfer, the documentId, and the partyRef for the Buyer/Consignee. Our subscription payload for the BoL Issued event contains the consignmentId, carrierBookingNumber, billOfLadingNumber, and documentId. The partyRef is from our established business partnership with the Buyer/Consignee. See the Supply Chain Partner Relationships topic for more details.

ebol65b

The response contains the flowTransactionId 47c64e11-bd85-4349-bc6d-bb39af707dd6.

ebol67b

You should always check the flowTransactionId using the GET ...​/flowTransactions​/{flowTransactionId} - Fetch a actionable doc flow transaction (that can be found in the Transactions section of the Actionable Flows API) to ensure that every part of the process has completed. See the Document Sharing and Actionable Flows APIs section of the API User Guide for more details.

ebol69b

Our subscription receives the payload for the transfer and shows the destinationOrgName for our Buyer/Consignee.

ebol71b


Buyer/Consignee

Here is a basic outline of the process that we will follow to illustrate how you can use the APIs for eBL processing. The steps are very similar to what we have shown in the Shipper/Consignor section above. We are going to continue with the example that we started in the Shipper/Consignor section. So we will assume that the Shipper/Consignor has transferred the eBL to our Buyer/Consignee.

  • Create a subscription to receive doc events (you could also set up notifications if you prefer)
    • Optionally, specify docType BILL_OF_LADING and actions for issued, transferred, surrendered, and switchedtopaper as part of the subscription
    • For each docType of BILL_OF_LADING (eventType of documentEvents) received on the subscription
      • If destinationOrgName is your orgName, you have the next action for the eBL
        • If transferred - you can transfer, switchtopaper, or surrender
        • Take the appropriate action using Actionable Flows API: POST​ ...​/actionableMessageFlows​/docMessages
      • If senderOrgName is your orgName, this is just a notification of an action you performed
      • Otherwise (you are not the sender nor the destination of the action)
        • This is just a notification that the eBL, for a consignment that you participate on, is “flowing”. You might choose to record that for your purposes depending on your requirements

Create Subscription

We will start by creating a subscription for the Buyer/Consignee organization to receive documentation events so that we can take action when certain events occur. See the Setting Up Subscriptions section for more information on subscriptions. You could also set up notifications if you prefer. We will create an organization subscription and specify docType BILL_OF_LADING and actions for issued, transferred, surrendered, and switchedtopaper as part of the subscription (note that eBLs that are issued might be of interest to know that an eBL for a consignment that our organization is a part of is flowing, but as a Buyer/Consignee, our organization would not have any action to perform at the issue stage of the flow). Subscriptions can be set up through the UI, but we will use the Event Subscription API POST ...​/subscriptions​/org - Create a subscription for your organization in this case. We use the Swagger to create the subscription.

ebol83a

Here is the entire body.

{
  "name": "subscriptionBoLConsignee",
  "orgEventTypes": [
    "documentEvents"
  ],
  "docEventFilters": [
    {
      "action": "issued",
      "docType": "BILL_OF_LADING"
    },
    {
      "action": "transferred",
      "docType": "BILL_OF_LADING"
    },
    {
      "action": "surrendered",
      "docType": "BILL_OF_LADING"
    },
    {
      "action": "switchedtopaper",
      "docType": "BILL_OF_LADING"
    }
  ],

  "webhook": {
    "sharedSecret": "********",
    "uri": "https://mywebhook.com/subscriptionBoLConsignee"
  }
}

Check for BoL Events

As mentioned earlier, when the Carrier submits the BoL through Actionable Doc Flows, the platform will issue the eBL and the event will be sent to our subscription (if we are subscribed to the issue action). Since we are continuing with our example, the Shipper/Consignor has transferred the eBL to our Buyer/Consignee org and the event was sent to our subscription. The following image represents the payload that is sent to our subscription for the transfer. It has been altered to mask the specific test ids, but we can see the eventName is "Document Events", the action is "transferred", and the destinationOrgName is our organization (the Buyer/Consignee), so we have the next action for the eBL.

ebol85b

Take Action

As mentioned in the basic outline, since the destinationOrgName is our orgName, we have the next action for the eBL. Since the current status is transferred, we can transfer, switchtopaper, or surrender. In our example, we will surrender to the Carrier (like we did in our UI example), we could optionally specify a release party at the time of the surrender. This will allow us to continue our example with the Carrier in the next section. We use the POST​ ...​/actionableMessageFlows​/docMessages - Performs Document Action (that can be found in the Actionable Message Flows section of the Actionable Flows API). Review the Swagger description for the API to become familiar with it. The API can be used for different document actions on different types of documents. For our case, there are several pieces of required information that we need to provide in the payload to identify our consignment, document, action, and to agree to the Carrier's Terms and Conditions. We need a consignment identifier (we could use the consignmentId, or the combination of carrierBookingNumber and billOfLadingNumber), the documentId, the action identifier eBLSurrender, and the eBLTCAcknowledgment set to true. Our subscription payload for the BoL Transferred event contains the consignmentId, carrierBookingNumber, billOfLadingNumber, and documentId. Before we call the API for the surrender, we will retrieve the document (using the documentId to review the Terms and Conditions using the GET ...​/documents​/{documentId}​/content - Fetch document content (that can be found in the Documents section of the Document Sharing API).

ebol94b

Since we are using Swagger for our API examples, we click the link to download the document and review the Terms and Conditions.

ebol96b

ebol98b

Now we will call the API for the surrender with the eBLTCAcknowledgment set to true.

ebol95b

The response contains the flowTransactionId 4e1b9712-f5bb-4869-b237-012bed53fd85.

ebol97b

You should always check the flowTransactionId using the GET ...​/flowTransactions​/{flowTransactionId} - Fetch a actionable doc flow transaction (that can be found in the Transactions section of the Actionable Flows API) to ensure that every part of the process has completed. See the Document Sharing and Actionable Flows APIs section of the API User Guide for more details.

ebol99b

Our subscription receives the payload for the surrender and shows the destinationOrgName for our Carrier.

ebol101b


Carrier

Here is a basic outline of the process that we will follow to illustrate how you can use the APIs for eBL processing. The steps are very similar to what we have shown in the Shipper/Consignor and Buyer/Consignee sections above. We are going to continue with the example that we started in the previous section. So we will assume that the Buyer/Consignee has surrendered the eBL to our Carrier.

  • Publish eBLs using Actionable Flows API: PUT ...​/actionableDocFlows​/billOfLading
  • Create a subscription to receive doc events (you could also set up notifications if you prefer)
    • Optionally, specify docType BILL_OF_LADING and actions for issued, transferred, surrendered, and switchedtopaper as part of the subscription
    • For each docType of BILL_OF_LADING (eventType of documentEvents) received on the subscription
      • If destinationOrgName is your orgName, you have the next action for the eBL
        • If surrendered or switchtopaper - perform appropriate operations on your system
      • If senderOrgName is your orgName, this is just a notification of an action you performed
      • Otherwise (you are not the sender nor the destination of the action)
        • This is just a notification that the eBL, for a consignment that you participate on, is “flowing”. You might choose to record that for your purposes depending on your requirements

Submit eBL

Note: This step would be done at the very start of the eBL flow, but it is mentioned here in the Carrier section since it is a function that the Carrier performs.

The Carrier starts the eBL flow when a Bill of Lading (BoL) document is submitted using the PUT ...​/actionableDocFlows​/billOfLading - Bill of Lading actionable doc flow Actionable Doc Flows API and the BoL JSON file contains "eBL" :true. See the Actionable Doc Flows section for more details on a typical SI (Shipping Instructions) to BoL flow.

Create Subscription

We will start by creating a subscription for the Carrier organization to receive documentation events so that we can take action when certain events occur. See the Setting Up Subscriptions section for more information on subscriptions. You could also set up notifications if you prefer. We will create an organization subscription and specify docType BILL_OF_LADING and actions for issued, transferred, switchedtopaper, and surrendered as part of the subscription. Subscriptions can be set up through the UI, but we will use the Event Subscription API POST ...​/subscriptions​/org - Create a subscription for your organization in this case. We use the Swagger to create the subscription.

ebol123a

Here is the entire body.

{
  "name": "subscriptionBoLCarrier",
  "orgEventTypes": [
    "documentEvents"
  ],
  "docEventFilters": [
    {
      "action": "issued",
      "docType": "BILL_OF_LADING"
    },
    {
      "action": "transferred",
      "docType": "BILL_OF_LADING"
    },
    {
      "action": "surrendered",
      "docType": "BILL_OF_LADING"
    },
    {
      "action": "switchedtopaper",
      "docType": "BILL_OF_LADING"
    }
  ],

  "webhook": {
    "sharedSecret": "********",
    "uri": "https://mywebhook.com/subscriptionBoLCarrier"
  }
}

Check for BoL Events & Perform Operations

As mentioned earlier, when the Carrier submits the BoL through Actionable Doc Flows, the platform will issue the eBL and the event will be sent to our subscription. In our example, the Shipper/Consignor has transferred the eBL to our Buyer/Consignee org and the event was sent to our subscription. Once the Buyer/Consignee surrendered the eBL to the Carrier, the surrendered event is sent to our subscription and the Carrier would perform any appropriate operations. The following image represents the payload that is sent to our subscription for the surrender. It has been altered to mask the specific test ids, but the destinationOrgName is what you would check to determine if your org has the next action for the eBL. In this case, we see it is our Carrier org. If the Carrier receives switchedtopaper on the subscription, the Carrier would perform any appropriate operations, including changing the BoL from the digital eBL form to a paper form.

ebol125b

eBL Scenario Reference

The following examples are eBL scenarios that TradeLens currently supports.

Regular eBL

  1. Carrier issues an eBL to the Consignor/Shipper.
  2. Consignor/Shipper (TITLE_HOLDER) transfers eBL to the Consignee.
  3. Consignee (TITLE_HOLDER) surrenders eBL to the Carrier.

Non Consignee eBL

  1. Carrier issues an eBL to the Consignor/Shipper.
  2. Consignor/Shipper (TITLE_HOLDER) transfers eBL to any valid entitled business partner onboarded in TradeLens (This might not be the defined Consignee in the Document).
  3. The entitled business partner (TITLE_HOLDER) surrenders eBL to the Carrier.

Multi Transfer with Banks

(Business Scenario: No Letter Of Credit )

  1. Carrier issues an eBL to the Consignor/Shipper.
  2. Consignor/Shipper (TITLE_HOLDER) transfers eBL to any valid entitled business partner onboarded in TradeLens.
  3. The entitled business partner (TITLE_HOLDER) transfers eBL to the Consignee.
  4. Consignee (TITLE_HOLDER) surrenders eBL to the Carrier.

Multi Transfer with Banks (multiple banks)

(Business Scenario: Letter Of Credit )

  1. Carrier issues an eBL to the Consignor/Shipper.
  2. Consignor/Shipper (TITLE_HOLDER) transfers eBL to any valid entitled business partner onboarded in TradeLens (Advicing Bank).
  3. The entitled business partner (TITLE_HOLDER) transfers eBL to any valid entitled business partner onboarded in TradeLens (Issuing bank: Trade Finance).
  4. The entitled business partner (TITLE_HOLDER) transfers eBL to the Consignee.
  5. Consignee (TITLE_HOLDER) surrenders eBL to the Carrier.

Doc Receiver Regular eBL

  1. Carrier issues an eBL to the Doc Receiver.
  2. Doc Receiver (TITLE_HOLDER) transfers eBL to the Consignee.
  3. Consignee (TITLE_HOLDER) surrenders eBL to the Carrier.

Doc Receiver Non-Consignee eBL

  1. Carrier issues an eBL to the Doc Receiver.
  2. Doc Receiver (TITLE_HOLDER) transfers eBL to any valid entitled business partner onboarded in TradeLens (This might not be the defined Consignee in the Document).
  3. The entitled business partner (TITLE_HOLDER) surrenders eBL to the Carrier.

Doc Receiver Multi Transfer eBL

  1. Carrier issues an eBL to the Doc Receiver.
  2. Doc Receiver (TITLE_HOLDER) transfers eBL to any valid entitled business partner onboarded in TradeLens (This might not be the defined Consignee in the Document).
  3. The entitled business partner (TITLE_HOLDER) transfers eBL to the Consignee.
  4. Consignee (TITLE_HOLDER) surrenders eBL to the Carrier.

Switch to Paper eBL

(Business case is where an Agent is involved and does not want the Consignor and Consignee to know each other. The Consignor does a SwitchToPaper and this ends the current eBL lifecycle. A new BOL is issued where Consignment is created with Agent as Consignor and the regular Consignee).

  1. Carrier issues an eBL to the Consignor/Shipper.
  2. Consignor/Shipper (TITLE_HOLDER) does SwitchToPaper to the Carrier.

eBL Surrender with Release Party (Telex)

(Consignor Release)

  1. Carrier issues an eBL to the Consignor/Shipper.
  2. Consignor/Shipper (TITLE_HOLDER) surrenders eBL to the Carrier by specifying ReleaseParty.

(Consignee Release)

  1. Carrier issues an eBL to the Consignor/Shipper.
  2. Consignor/Shipper (TITLE_HOLDER) transfers eBL to the Consignee.
  3. Consignee (TITLE_HOLDER) surrenders eBL to the Carrier by specifying ReleaseParty.

Back to Top