Delivery Note and POD Extractor

Read the delivery date, signatory, delivery status, and delivered versus ordered quantities from a delivery note or proof of delivery PDF into structured data.

The full guide: Read a signed delivery note as proof of delivery

How should we start?

Build with Talonic

Need to scale? Create an API key, then run this from your own code or an agent.

Create an API key

Free account required

Start with a document

Upload a file or pick a sample, and see the fields come back.

No signup · nothing stored

Questions about Delivery Note and POD Extractor.

What proof-of-delivery details does it capture?

Who signed for the goods, the delivery status, and the delivery date are read directly, along with the document number and the reference order number and booking reference the delivery relates to.

Can it flag short or over deliveries?

Yes. The line items table returns quantity delivered next to quantity ordered for each row, with the item number, product code, description, and unit of measure, so a mismatch between what was ordered and what arrived is visible per line.

Which parties and locations come out?

Shipper name and address, consignee name and address, notify party, and carrier name with tracking number, plus the place of receipt and place of delivery and the cargo description.

Does it read charges and marks?

Freight and charges, the marks and numbers on the consignment, the currency, and any notes on the delivery are captured alongside the core fields.

What file types are accepted and is the file stored?

PDF only, up to 10MB and 100 pages. The note is processed via the Talonic API for extraction, is not retained for training, and is not shared.

Doing this to one file, or to ten thousand?

The tool reads a single document. The platform reads the whole estate once and keeps it queryable — the same engine, with a memory.

See document data extraction if you run this for freight and customs teams, or the extraction API if you are building it in.