Lido extracts delivery date, delivery time, recipient name, signature presence, delivery exception notes, and shipment reference numbers from proof of delivery documents, whether they arrive as signed PDFs, scanned paper receipts, or photos taken by drivers, and produces structured delivery confirmation data for your TMS, WMS, or customer portal.
.png)
.png)
Proof of delivery is the closure event for every shipment, but PODs arrive in the lowest-quality, most inconsistent formats in the logistics document stack. Handwritten signatures, rubber-stamped dates, photographed paper receipts, faxed confirmations. Lido reads all of them and extracts the fields that matter for TMS update and claims management.
Electronic PODs are downloaded from carrier portals or received as PDF attachments. Paper POD receipts are faxed by carriers or scanned by drivers and emailed. In last-mile and direct delivery operations, drivers photograph the signed receipt with a smartphone and upload via a delivery app. Lido processes all four formats in the same extraction pipeline, the extraction logic is the same regardless of how the POD arrived.
From each POD: BOL number, PRO number, carrier tracking number, delivery order number, or purchase order reference, whichever identifier appears on the document. Lido extracts all reference numbers and matches the POD to the originating shipment record in the TMS using the first successful match. Unmatched PODs, where no reference number matches an open shipment, are flagged for manual linking.
Actual delivery date and time as recorded on the POD are extracted and compared against the scheduled delivery window. Early deliveries, on-time deliveries, and late deliveries are classified. Recipient name, the consignee representative who signed for the goods, is extracted from the printed or handwritten name field. Signature presence is confirmed (signed vs. unsigned) as a boolean field.
Consignees frequently annotate PODs before signing — "2 cartons refused," "pallet damaged on arrival," "short 5 units on item 3," "product wrong, see attached note." Lido extracts these handwritten exception notations as a structured exception field and classifies them: shortage, damage, refusal, wrong item, or other. Shipments with damage or shortage notations are flagged for claims review before the carrier's claim filing window closes.
Clean PODs, signed, no exceptions, update the TMS shipment record to delivered status with the confirmed delivery timestamp. Exception PODs trigger a claims workflow: the structured exception notation, the signed POD document, and the originating shipment data are packaged for the carrier claims process. Your claims team receives a pre-filled claim package, not a stack of scanned PODs.
Upload a batch and get structured output in minutes.
Electronic PODs downloaded from carrier portals with structured delivery confirmation fields. Formatted PDF output from carrier systems, all carrier formats extracted without templates.
Paper POD receipts from manual delivery routes, scanned at the warehouse or driver return. Handwritten dates, printed consignee name, and handwritten recipient signatures processed.
Photos taken by drivers or consignees at the point of delivery. Variable image quality, angle, and lighting handled by the extraction engine.
Faxed POD confirmations from LTL carriers and regional truckers. Fax-quality image processing with confidence scoring on extracted delivery fields.
POD data exported from delivery management applications as PDF or image files. Electronic signature images, GPS coordinates, and delivery timestamps extracted.
Delivery receipts with customs clearance stamps for international import deliveries. Customs stamp date, clearance reference, and delivery confirmation fields extracted.
A carrier claims an LTL shipment was delivered clean. The consignee says 4 cartons were damaged on arrival and noted on the delivery receipt. The transportation coordinator needs to find the signed POD, confirm the damage notation, and file a freight claim within the carrier's 9-month window, but finding a specific POD from 3 weeks ago means searching through a shared folder of 400 scanned PDFs, each named something like "scan_0047.pdf." By the time the POD is found and the claim is prepared, 6 weeks have passed and the carrier disputes the damage notation because nothing was logged at the time of delivery.
Lido extracts exception notations from every POD the day it arrives. Damage, shortage, and refusal notations are classified and flagged immediately, not discovered weeks later when a customer files a complaint. The claims package. POD document, exception notation, shipment data, is assembled automatically and routed to your claims team within hours of delivery, while the carrier's claims window is wide open.
| Feature | Lido | Manual processing |
|---|---|---|
| Extract delivery date, time, and recipient from any POD format | ✓ | ✗ |
| Read and classify handwritten exception and damage notations | ✓ | ✗ |
| Match POD to originating shipment in TMS automatically | ✓ | ✗ |
| Flag exception PODs for claims review at time of delivery | ✓ | ✗ |
| Process smartphone photos and faxed PODs in the same pipeline | ✓ | ✗ |
| Search through scanned PDFs to find the POD when a claim is needed | ✓ | ✓ |
Extract delivery confirmation and exception data from every POD automatically, and route exceptions to claims before the window closes.
A 3PL manages last-mile delivery for 8 retail clients. Drivers return scanned PODs via a delivery app at end of shift. Lido processes the daily POD batch, updates TMS delivery status, and flags exception PODs, damage, shortage, refused delivery, for same-day notification to the affected client.
An LTL carrier receives 500 PODs per day from drivers via fax and email. Lido extracts delivery confirmations and routes them to the shipment record. PODs with consignee exception notations are extracted and queued for the freight claims team with the notation pre-classified, reducing claims intake processing time per event from 20 minutes to under 3.
An importer receives 80 container deliveries per month from drayage carriers. Damage and shortage events occur on 3–5% of deliveries. Lido extracts exception notations from signed delivery receipts and packages the claim evidence. POD, exception notation, shipment data, for the carrier within 24 hours of delivery, maximizing claim recovery before the 9-month claims window begins to close.
A freight broker requires POD confirmation before releasing carrier payment and invoicing the shipper. Lido extracts delivery confirmation from carrier-submitted PODs and matches to the originating load record, automating the confirmation step that previously required a coordinator to manually download, review, and cross-reference each POD.
%20(1).svg)
