Lido reads signed, scanned, and photographed PODs and extracts delivery confirmation data. Recipient, timestamp, condition notes, and signature status.
.png)
.png)
Lido reads any POD format and extracts delivery confirmation and exception data for TMS update and claims.
Electronic PODs come from carrier portals or email. Paper receipts are faxed, scanned, or photographed by drivers. Lido processes all formats in the same extraction pipeline.
BOL number, PRO number, tracking number, delivery order, or PO reference are extracted and matched to the originating TMS shipment record. Unmatched PODs are flagged for manual linking.
Actual delivery date and time are compared against the scheduled window. Recipient name is extracted from printed or handwritten fields. Signature presence is captured as a boolean.
Handwritten consignee notations like "2 cartons refused" or "pallet damaged" are read and classified: shortage, damage, refusal, wrong item. Exception PODs are flagged for claims review.
Clean PODs update the shipment to delivered status. Exception PODs trigger a claims workflow with the structured notation, signed POD, and shipment data packaged for the carrier claims process.
Upload a batch and get structured output in minutes.
Electronic PODs with structured delivery fields. All carrier formats extracted without templates.
Paper receipts scanned at the warehouse or driver return. Handwritten dates, names, and signatures processed.
Driver or consignee photos at point of delivery. Variable image quality and angle handled.
Fax-quality POD confirmations from LTL and regional carriers with confidence scoring on extracted fields.
PDF or image exports from delivery apps. Electronic signatures, GPS coordinates, and timestamps extracted.
Receipts with customs clearance stamps. Stamp date, clearance reference, and delivery confirmation extracted.
| 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)
