POD photos, PDF bills of lading, “where is it?”

The question this file answersWho is answering “where is my shipment?” at our place — and why is the answer not already in the tracking portal?

Fits: carriers and forwarders whose dispatch documents still arrive as PDFs and photos and get keyed into tracking — a continuous flow over the shipping cycle, no seasonal off-switch

Not for: operators whose drivers scan PODs on a device that already updates the TMS — the retyping is gone, and only the status replies are left to look at

Typical day

What the desk looks like today

Typical, from the logistics playbook. Bills of lading, CMRs and proofs of delivery come back as carrier PDFs and drivers' phone photos — continuously, through the shipping cycle; the playbook gives no daily count and neither do we. A dispatch clerk checks each is complete and signed, types the shipment keys and the event into the tracking system, and answers “where is my shipment?” from the same desk. It hurts at the end of the day, when the paperwork arrives at once and the phone rings for shipments delivered hours ago that the portal still shows in transit.

What changes

What Monday looks like after

Five o'clock, when the drivers' paperwork comes in. The clerk is not typing consignment numbers; the day's PODs with a clear signature and reference are already on the shipments in the TMS, images attached, and the customers who asked have been told from the record. On the screen are the exceptions — a POD with “damaged” scrawled across it, a CMR missing the consignee's stamp, a photograph too dark to read. The clerk's evening is the disputes. You can see, per day, how many documents posted without a person and how many status emails the system answered. The DHL pilot (2022) is the figure in the metric block — their operation, not yours.

Typical, not a measured client result. Every figure here comes from the playbook source named below.

~55%

less time retyping delivery documents — DHL pilot (2022)

Before: a clerk retypes BOLs and PODs from PDFs and photos into tracking. After: a DHL pilot (2022) cut ~55% of that manual handling — their figure, not our measurement.

Where this number comes from

DHL internal case study (2022) reports that AI-powered document processing reduced manual handling by ~55% in pilot operations; Capgemini “Logistics 4.0” (2023) puts automated tracking responses at 60–70% of customer inquiries handled without escalation. Playbook automation range 40–60%. Their operations, not a client KPI of ours.

What we install

What we put in front of the systems you already run

Your tracking stays where it is — project44, FourKites or the TMS that holds status: SAP TM, CargoWise, Transporeon or the one you run. We add a document step:

every BOL, CMR and POD is picked up from the mailbox or the drivers' upload
shipment reference, dates, signatures and any remark — damage, shortage, refused — are extracted, PDF or photograph
complete documents update the tracking event through the TMS or portal API, image attached
incomplete or unreadable ones go to the dispatch clerk with what is missing
“where is my shipment?” emails are answered from the tracking record; anything that is not a status question goes to a person with the thread.

First scope: PODs from your own fleet.

What stays human — and what this will not do

Exception investigation. Carrier disputes. Complex customer inquiries that are not a status lookup.

What can go wrong — and what we do about it

Driver photographs are the weak point — blurred, dark, half a page — and a fair share will fail reading and go to the clerk. If shipment references in the TMS do not match what the carrier prints on the document, nothing can be matched until the master is cleaned. A tracking portal with no API leaves import files, and IT in the loop. Exception investigation, carrier disputes and non-status questions stay with a person; the playbook's 40–60% is about handling the documents, not resolving what they say.

How long it takes, and what we need from you

Audit, about two weeks (€1.5–3K): we sit at the dispatch desk, count a week of BOLs, CMRs and PODs by source — carrier PDF, driver photo, scan — and check what your tracking system or TMS accepts through its API. Pilot (€10–20K), 4–6 weeks — the logistics playbook rates dispatch documents medium complexity: PODs from your own fleet first, status replies drafted but sent by a person. Production: carrier documents, then automatic status replies. From you: mailbox and upload access, a week of documents with their tracking entries.

The path: free 60-second estimate → free 20-minute review → paid audit of this one process (€1.5–3K, typically two weeks) → pilot with your people in the loop (€10–20K, weeks, not quarters). No transformation programme. Prices are public, on the services page →

This is about you if…

Do BOLs, CMRs and PODs still come back as PDFs and phone photos that someone retypes?
Does the same clerk who keys them also answer “where is my shipment?” emails?
Does your tracking system or TMS have an API or import for status events?

What does this mean in euros?

That depends on your volumes and wage costs — this page will not invent the number. The free 60-second estimate runs that calculation from your answers, with every multiplier sourced.

Get your free savings estimate 60 seconds · no sales call Or write first → Map a logistics process like this one — free, 60 seconds →

Not a named Aperanda client. Process file · Logistics.

Deep-dive process file. Volumes, weeks and sources come from the industry playbook; nothing here is a named client.

All process files