CMR-JET is built for organisations that draft CMR documents without running a full Transport Management System. Fit depends on the workflow — not just on company size.
The key question isn’t how large your business is, but whether you draft CMRs without running a full TMS. If CMR work is a gap next to ERP or accounting, CMR-JET fits.
Organisations that regularly draft CMR documents alongside ERP or accounting, without running a full Transport Management System.
Companies with outbound shipments where they draft the CMR themselves, often combined with collection arrangements or regular carriers.
Operators in materials, construction or industry who organise transport, needing signed proof-of-delivery and a searchable archive.
Alongside the primary audience there are two profiles where CMR-JET also works.
Carriers that need CMR documents and evidence, but don’t want or need a full TMS.
Users of the current desktop app moving to the cloud, with a migration path for supported formats.
For the following profiles a different kind of solution will take you further — not because of company size, but because of workflow and scope. Better clear up front than disappointed afterwards.
If you already run a carrier-oriented Transport Management System, CMR functionality lives in that system or via a TMS integration. CMR-JET does not replace a TMS.
CMR-JET does not plan trips, does not do fleet management and does not handle customs declarations. For those needs, other systems are a better fit.
Those who only draft a handful of CMRs per year are often better served by a template or a simple form tool.
Typical scenarios
Four recognisable scenarios that show where CMR-JET does its work.
CMRs are drafted in the morning and handed to the driver with a QR. On delivery the recipient signs and confirms through the QR code; the photo of the signed CMR and the archive are findable straight away.
Saved parties and references are set up in advance, so repeat work disappears and CMRs are ready faster.
Proof of delivery is tied to the right document, no matter which depot or driver handles the shipment.
Existing customers import supported formats and continue the workflow in the cloud without losing historical context.