CMR notes, PODs and carrier invoices, off your desk
You handle CMR notes, bills of lading, packing lists and POD photos that arrive by WhatsApp from a driver in the cab. The SayFocus pipeline reads what comes in, checks carrier invoices against the rate you agreed, and flags what needs a decision.
What eats the hours
Four things we hear from people who do this work.
POD photos arrive by WhatsApp, one at a time
A driver sends a photo of a signed delivery note from the cab, often blurry, sideways or missing a page, and someone has to match it to the right shipment by hand.
Carrier invoices rarely match the quote
Fuel surcharges, waiting time and demurrage get added after the fact, and checking a carrier's invoice against the rate you agreed means pulling out the original booking every time.
Enquiries turn into quotes too slowly
A rate request by email sits in the inbox behind everything else, and a slow quote loses the booking to whoever answers first.
Customs paperwork has to be exactly right
A CMR, invoice or packing list with a mismatched weight or reference number holds up a shipment at the border, and catching that means a careful read of documents that all look similar.
The streams we take over
Each one links to the page that describes exactly how it is built.
A rate request is read, checked against your tariffs and lane data, and answered with a draft quote fast enough to keep the booking in play.
Shipment paperwork is read as it arrives, whatever the format, and the reference number, weight and consignee are pulled out and matched to the booking.
A photo sent over WhatsApp from the driver's cab is matched to the right shipment and filed as proof of delivery instead of sitting in a chat thread.
Fuel surcharges, waiting time and demurrage are checked line by line against the rate you agreed, and only a matching invoice is passed for payment.
Weight, reference numbers and consignee details are checked across the CMR, invoice and packing list before submission, so a mismatch is caught before the border does.
What the pilot measures here
Share of one document stream, such as carrier invoices, processed without a manual correction during the pilot.
Time from a CMR, POD or invoice arriving to being filed or checked, against your current manual process.
How many documents per 100 need a person's decision on a mismatch or an unreadable file.
Systems in this line of work
Processed in the EU. Original files and extracted data stay in your own systems; a data-processing agreement is available on request.
Proof
111 dairy SKUs online with stock levels that are never more than 15 minutes old
111 SKUs, two languages, stock refreshed every 15 minutes from MoySklad, 222 product pages and a shopping feed — for a dairy distributor in Kazakhstan.
Our closest proof: a distributor's storefront reads messy stock data from several sources and keeps a live link to its inventory system, not a freight case.
What we have not done yet
We have not yet run a pilot for a freight forwarder or carrier, and we are not going to imply otherwise. Our published cases are from an accounting firm and a distributor; what carries over to logistics is the intake-and-validation half of the pipeline, not a finished template for a CMR or a POD. A pilot on your documents would be the first of its kind for us in that specific type, and the free audit tells you plainly what is realistic before anything is agreed.
From audit to autopilot
Audit
We map one document or enquiry stream end-to-end, count volumes and name the systems it touches. You get a written scope and a fixed pilot price.
Free · 3 working daysPilot
One stream goes live on your real documents. Acceptance is measured, not felt: straight-through rate, minutes per document, exceptions.
About two weeks · fixed priceRollout
The remaining streams follow the proven pattern. Monthly report, support, and changes as your systems change.
Stream by streamFrequently asked questions
Have you built this for a freight forwarder before?
Not yet. Our published pipelines run for an accounting firm and a distributor. The document-reading and validation logic transfers; the specific fields for a CMR, a bill of lading or a POD would be built and tested against your own documents during the pilot.
Can it read a photo of a CMR taken in a truck cab?
Reading a photograph rather than a clean scan, including a tilted or partly obscured shot, is the kind of document our pipeline is built to handle. Accuracy is checked against your own documents in the pilot before you commit to a rollout.
How does it check a carrier's invoice against what we agreed?
The invoice is read and its lines, including fuel surcharges and demurrage, are checked against the rate and terms on file. Anything that does not match is flagged for a person rather than approved automatically.
What happens to a document it cannot read?
It goes into a review queue inside a tool your team already uses, such as Telegram or email, with a note on what could not be read. Nothing is guessed and nothing is silently dropped.
Where does our shipment and customer data go?
Processed in the EU. The original files and extracted data stay in your own systems, and a data-processing agreement is available on request.
Start with the free audit
Three working days, one stream mapped end-to-end, a fixed pilot price on paper. No commitment.
Get a free automation audit