Why CMR waybills are harder than they look
The CMR waybill has a fixed international structure: sender, recipient, loading point, unloading point, weight, number of packages. That sounds straightforward. In practice, however, a transport company receives CMR documents from dozens of different senders, each with their own form. Some are printed and digitally signed; others are handwritten on an old carbon copy form that was then scanned with a phone held at an angle. The same field appears at the top left on form A and in the center right on form B. Then there is the sender who merges five boxes because the goods description does not fit. The structure is standardized. The execution is anything but.
What goes wrong in the first few weeks?
The first batch of CMR documents you run through an automation system immediately reveals which senders deviate from what you expected. Not because the system cannot handle it, but because you did not know beforehand how wide the variation actually is. A reference number appears in three places at once, but which one is yours? A weight is entered as both gross and net, but the system picks the wrong column. A document is so poorly scanned that the back impression of the carbon copy is read along with the front. These are not technical failures; they are document problems that a new employee would also make in the first few weeks. The difference is that a system makes them consistently until you have explicitly identified and corrected the deviation.
What does Cabooter Group teach us?
Cabooter Group processes more than 70,000 documents per year through dottle, including CMR waybills, invoices, and orders. Of those documents, 85% are processed fully automatically, accounting for approximately 110,000 euros in annual savings. The figure that rarely gets mentioned: the first few weeks were not at 85%. That percentage is built by taking exceptions seriously. Every CMR that ends up with a person for approval is a signal. Not of a failing system, but of a deviation that you can identify, record, and handle automatically the next time. The ratio shifts gradually. The person does not become redundant; they simply handle only the cases that genuinely require it.
When does automating CMR documents not pay off?
There are situations where it is better to wait. If you process fewer than a few hundred CMR documents per month, the payback period is long. If the CMR serves purely as an archive document at your organization and the data is still confirmed by phone, you are automating a step that does not solve the real problem. And if source quality is structurally poor, handwritten and poorly scanned, the first investment should be improving the scanning process, not automating the processing. Automation amplifies what is already there: a good process becomes faster, a poor process becomes faster at being poor.
What do you do with the exceptions?
Exceptions are not a residual category to be ignored; they are the only way to make the system better. Every CMR that goes to a staff member for review should be answerable with: which field was unclear, which sender did this document come from, and what was the correct value? If you track that, you build insight. Some senders generate a disproportionate number of exceptions, sometimes due to poor scan quality, sometimes due to a non-standard form. With that insight you can intervene in a targeted way: ask the sender to submit their form digitally, or explicitly define the deviating field so the system recognizes it. That is not self-learning magic; it is management. Controlled, auditable, and predictable.