CMR-JET is built around proof: the photo of the signed CMR, extra photos, scans and events stay tied to the right CMR document. We use precise language because compliance claims only matter when they hold up.
The evidence file makes every delivery traceable, searchable and invoice-ready: the photo of the signed CMR, extra photos and events stay with the right document. Below you read exactly what we capture today and how the archive works.
Why proof matters
A scribble on paper only makes a delivery robust if it ties to the right document, the right moment and the right context.
Who signed what, when and with what remark? A structured evidence file prevents endless email chains after a disputed delivery.
A signed proof of delivery on the right document makes invoicing and AR follow-up easier.
Documents, signatures and evidence are kept linked, so when customers or audits ask, you find what’s needed quickly.
What we capture
The evidence capabilities below are in the release scope. What falls outside it is further down this page.
The recipient confirms through the QR code and captures a photo of the signed CMR, tied to the correct document with timestamp and context. No account required on the recipient side.
Add photos or scans as supporting evidence — packing lists, packaging, recorded damage.
Creation, changes, confirmations and archive actions are recorded chronologically as events.
Documents are kept in a per-organisation isolated archive, searchable by reference, date and party.
Archive integrity
Evidence stays tied to the CMR via an event model, so the full history of a document remains readable — recognisable, traceable and searchable, and isolated per organisation.
The event and evidence model makes later edits recognisable. We don’t claim statutory immutability — we make divergence visible.
The photo of the signed CMR, extra photos and scans stay tied to the CMR they relate to, even after the document is closed.
The archive runs on infrastructure in the EU. Each organisation gets its own isolated archive, separate from other customers.
Security & GDPR
Shippers want clear, verifiable statements before entrusting documents and signatures. Below is what we do today — no ISO/SOC seals we don’t hold, no customer logos we may not show.
Production and archive run on Hetzner in Nuremberg (nbg1). No third-country transfer for storage. Full list at /subprocessors.
All connections run over HTTPS/TLS. Uploaded files and backups are stored encrypted. Access controls and logging are part of the standard configuration.
The app and this marketing site use no advertising or tracking cookies. Usage analytics runs via a cookieless, EU-hosted solution — no consent banner needed.
Every organisation gets its own isolated archive. Access to another tenant’s data is contractually forbidden and technically shielded.
What CMR-JET is
CMR-JET drafts your CMR, captures the signed proof of delivery and keeps everything in an evidence file. The paper CMR remains the transport document: CMR-JET is not an e-CMR and not an exchange platform. What falls outside it is below.
CMR-JET does not issue electronic consignment notes (e-CMR) and does not exchange consignment notes between parties. The CMR travels on paper; CMR-JET keeps the evidence with it.
CMR-JET is not a Peppol access point and not a customs platform. For that kind of exchange you work with a separate provider or service.
Honest about the limits
CMR-JET does not replace a Transport Management System — route planning, fleet management and driving/rest times belong in your TMS. It is also not a Peppol access point and not a customs platform; for that exchange you work with a separate provider.
CMR-JET does not apply an electronic signature: the signature is on the paper CMR, and CMR-JET keeps the photo of it with timestamp and events. We do not claim statutory incontestability of that evidence or of the archive. The event and evidence model makes proof structured and traceable; legal assessment remains the user’s responsibility.