# e-CMR Hub

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="/files/ZjFlvs0KglJekS0zxQ0p" alt="" data-size="original"></td><td></td><td></td></tr><tr><td><img src="/files/NlUaPwFU5qMDg8p0rix1" alt="" data-size="original"></td><td></td><td></td></tr><tr><td><img src="/files/AdCiPWg2kWG5GoKGrLfr" alt="" data-size="original"></td><td></td><td></td></tr><tr><td><img src="/files/aLMrLAHq7Ae0Iw93GSSR" alt="" data-size="original"></td><td></td><td></td></tr><tr><td></td><td><img src="/files/efXgeEeVm9xgxMxj7gd7" alt="" data-size="original"></td><td></td></tr><tr><td></td><td><img src="/files/gyhSQJSKBETnDPFjiczv" alt="" data-size="original"></td><td></td></tr><tr><td><img src="/files/QpYWlyC9N1enaRAnjwsa" alt="" data-size="original"></td><td></td><td></td></tr><tr><td><img src="/files/odZ3RcbSZVIL7dP5kOd6" alt="" data-size="original"></td><td></td><td></td></tr></tbody></table>


---

# 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://i4trust.ishare.eu/open-call/e-cmr-hub.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.
