Why the CMR waybill is such a difficult document
The CMR waybill is standardized in terms of content, but not in terms of format. Every shipper, freight forwarder, or driver submits it in their own way: a photo of a paper form, a scanned PDF, sometimes a digital version that still arrives as an attachment. Image quality varies. Handwriting sits alongside printed text. Fields are sometimes empty, sometimes crossed out, sometimes filled in twice. Classical OCR software recognizes characters in these cases but does not understand the context. The result is a raw text dump that still has to be corrected manually. That is not automation; it is moving the problem elsewhere.
What dottle specifically does with a CMR waybill
dottle reads the CMR as a document: it not only recognizes the text, but understands which field means what. Sender, consignee, loading point, unloading point, reference number, weight, number of packages, delivery remarks. Those fields are delivered as structured data into the system you work with, whether that is Transpas, WinSped, Dynamics 365, or another TMS. Discrepancies with the corresponding order are flagged so a staff member can review them. dottle does not decide whether a deviation is acceptable; that judgment stays with the employee. What disappears is the typing work: transferring every field, manually, document by document.
Where teams run into problems during implementation
The biggest obstacle is not the technology but the way documents are submitted. CMR waybills that arrive as poorly lit photos of crumpled forms are harder to process than neatly scanned copies. When drivers submit documents through a fixed app or scan function, automation works best. A second pitfall is the expectation that the system will get everything right from day one. In the first few weeks, edge cases surface: a CMR with an extra attachment, a form in a less common language, a sender who fills in the format slightly differently. These cases are surfaced and resolved; they do not fail silently. But the team needs the discipline to assess those exceptions promptly rather than letting them pile up.
When automating CMR waybills is not worthwhile
If you process fewer than twenty to thirty CMR waybills per week, the time savings are small and the investment is hard to recoup. If the processes around the CMR are not yet defined either, for example when it is unclear who checks what and when, automation will speed up the chaos rather than solve the underlying problem. Establish the process first, then automate. And if the quality of incoming CMR documents is structurally poor, due to bad scans or missing fields, that problem needs to be addressed at the source. Automation increases speed, not the quality of the source data.
What it delivers when the foundation is in place
At Cabooter Group, dottle processes more than 70,000 documents per year, including CMR waybills, with 85 percent handled fully automatically. That translates to savings of approximately 110,000 euros per year. CMR waybills that previously arrived by email and were manually retyped are now automatically read and prepared for approval. The staff member reviews, approves, and moves on. The typing work is gone. For transport companies operating at volume, that is the difference between an administration that falls behind and one that keeps up.