> For the complete documentation index, see [llms.txt](https://i4trust.ishare.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://i4trust.ishare.eu/open-call/e-cmr-hub.md).

# e-CMR Hub

Cross-Platform Handling of B2B Transactions

Goods issuing and reception in B2B transactions have traditionally relied on paper-based processes, leading to a fragmented system with numerous regulatory pitfalls. This has required truck drivers to handle an overwhelming amount of consignment notes (CMRs), which are critical for logistics service providers in ownership transfer, insurance, exception handling, and inspection.&#x20;

The [e-CMR (electronic Customer Relationship Management)](https://collectgo.eu/en/e-cmr-hub-data-exchange-between-e-cmr-providers/) protocols, with a standard data set and guidelines for e-signing, aim to replace this paper-based process. Although numerous e-CMR providers have developed technical solutions for digitalisation, it is still challenging to select an e-CMR provider that ensures the adoption of its solution across the entire supply chain.&#x20;

A neutral [e-CMR data hub](https://collectgo.eu/en/e-cmr-hub-2/), endorsed by businesses and the government, could enable e-CMR providers to perform cross-border digitisation. This is achieved using trusted data exchange through [iSHARE](http://dev.ishare.eu/) and FIWARE components, empowered by robust identity and access management mechanisms.&#x20;

The enablement of cross-platform e-signing and sharing of e-CMR data for inspections by government officials scales up and boosts the acceptance of e-CMR solutions. The development of a trusted service based on the [iSHARE Trust Framework](https://framework.ishare.eu), which is sustainable and interoperable between e-CMR providers, ensures that producers and transporters have their operational business processes supported, regardless of the certified e-CMR provider involved.&#x20;

#### Contributors:

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><img src="https://1503555140-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2jEu4WMcHi3W2Hls1ewh%2Fuploads%2FroD9Fxy7eoD7eG2EbNGh%2FSmart%20Connected%20Supplier%20Network%20(NL).png?alt=media&amp;token=397402f5-f24f-485d-87be-b62cdd548c56" alt="" data-size="original"></td><td></td><td></td></tr><tr><td><img src="https://1503555140-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2jEu4WMcHi3W2Hls1ewh%2Fuploads%2Fy4hq8wSVDKlOwodfAIjj%2FCollect%26Go.png?alt=media&amp;token=46fe328f-72dc-4757-b724-28186f23c62f" alt="" data-size="original"></td><td></td><td></td></tr><tr><td><img src="https://1503555140-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2jEu4WMcHi3W2Hls1ewh%2Fuploads%2FwlRqIl4Xb5Y0kCtfyyIx%2FPionira.jpeg?alt=media&amp;token=c21bcae6-8e17-4d11-bb54-6d3689dd1a15" alt="" data-size="original"></td><td></td><td></td></tr><tr><td><img src="https://1503555140-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2jEu4WMcHi3W2Hls1ewh%2Fuploads%2FobEgKuQrLVZhGqPxHtgz%2FLogistiek%20Zonder%20Papier.png?alt=media&amp;token=5ab69d17-ce21-4cc5-a904-750938a85ad5" alt="" data-size="original"></td><td></td><td></td></tr><tr><td></td><td><img src="https://1503555140-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2jEu4WMcHi3W2Hls1ewh%2Fuploads%2FuoIwWjPvxEOH53ywznar%2FDashdoc.jpg?alt=media&amp;token=2ff0fdfd-7df0-4c8e-ac25-71126e18e24c" alt="" data-size="original"></td><td></td></tr><tr><td></td><td><img src="https://1503555140-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2jEu4WMcHi3W2Hls1ewh%2Fuploads%2FYtb3Pvf5Iy2C7miZfmMV%2FCARGOLEDGER.svg?alt=media&amp;token=9b626bc3-b96a-4fd9-8276-e6176b843ee3" alt="" data-size="original"></td><td></td></tr><tr><td><img src="https://1503555140-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2jEu4WMcHi3W2Hls1ewh%2Fuploads%2Fy93QgBBtZSAP1wccy9p5%2FSensolus.png?alt=media&amp;token=52086f14-1d7b-4ebc-bdee-7286575940d1" alt="" data-size="original"></td><td></td><td></td></tr><tr><td><img src="https://1503555140-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2jEu4WMcHi3W2Hls1ewh%2Fuploads%2FA2luMdQ5jlZVniEU4tNI%2FIntepia.png?alt=media&amp;token=c71bfda3-d2fc-4cce-96f0-4dec22e3754f" alt="" data-size="original"></td><td></td><td></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://i4trust.ishare.eu/open-call/e-cmr-hub.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
