Shared access to documents
Transport details, confirmations and updates will be kept in a single document that every party can access.
01 / DOCUMENT WORKFLOWSDK AND API FOR TMS PROVIDERS
Add e‑CMR to your TMS
We are building an SDK and API for consignment notes, proof of delivery and pallet records. You will be able to integrate them into your system and offer them to customers under your own brand.
✳An SDK for TMS and ERP providers building their own products.
POZNAŃ, PL BERLIN, DE
DIGITAL DOCUMENT
Consignment note
CMR / 2026 / 0842
LOADING LOCATIONPoznań, Poland PLDELIVERY LOCATIONBerlin, Germany DE
270kmCargo24 pallets · 12,400 kg
Document preparedEverything in one place
Ready for the roadEXAMPLE
Shared documentAvailable to every party
PRODUCT CONCEPT PREVIEW · SAMPLE DATA
THE DOCUMENT'S JOURNEYe-CMRProof of deliveryPallet recordsAPI integration
01 / DOCUMENT MANAGEMENT
Manage transport documents in one system
We are designing a shared document workflow for the office, driver and recipient, from entering transport details to settling the delivery.
Delivery confirmation and history
Drivers will be able to collect signatures, photos and recipient notes at delivery, with a record of who added them and when.
02 / CONFIRMATIONS AND HISTORYIntegration with your system
The SDK and API will let you add document handling to your existing TMS or ERP and offer it under your own brand.
03 / SDK AND API02 / FROM OFFICE TO RECIPIENT
OUR PLANNED WORKFLOWFrom creating a document to confirming delivery
01
Prepare
Send transport details from your TMS through the API to create a document.
02
Share
Send the document to the driver and other parties through a link.
03
Confirm
Collect receipt confirmations, notes and pallet exchange details.
04
Keep it handy
Return to the complete documentation when it is time to settle up.
03 / FOR TMS DEVELOPERS
Transport documents built into your product
You do not need to build document handling from scratch. We are preparing a shared data model and API to connect it to your system.
- Planned REST API and webhooks
- A shared document model
- Preparing eFTI TestBed integration
Your TMS / ERPYOUR PRODUCT
REST API
✳ eCMR hub.
Documentse-CMR · e-POD · pallets
eFTI TestBedIntegration in preparation
04 / GOOD TO KNOW
Questions about the product and integration
Find out who the SDK is for, what is in development and how we plan to handle integration.
Who is eCMR Hub for?
Primarily for TMS and ERP providers who want to add digital transport documents to their own product. A standalone app for carriers is planned as a separate product built on the same technology.
Can I use the platform already?
We are developing the product and talking with partners. The previews show the planned experience. We agree the scope and timing of pilots individually with interested companies.
Is eCMR Hub eFTI certified?
Not yet. We are preparing integration with the eFTI test environment. Technical testing and certification are separate stages; we do not currently claim certification or readiness for production eFTI data exchange.
Do I need to change my TMS?
No. We are designing the SDK and API to integrate with existing TMS and ERP systems. A standalone workspace for transport companies is planned as a separate product using the same technology.
BUILDING ECMR HUB
Tell us about your system
If you develop a TMS or ERP, we would like to hear which documents your customers need. These conversations will help us define the first integrations.
Information about joining the pilot is coming soon.
Product in development · Poland / Europe