Extract data from delivery notes
Unstract reads delivery notes and signed delivery receipts, whether they come back crumpled from the cab, faxed or photographed at the dock, and returns quantities, signatures and damage remarks, checked against the PO, to your WMS or ERP.
olive oil, pallet 2 crushed at the corner, photos sent
WHITE: SUPPLIER · YELLOW: CUSTOMER · PINK: CARRIER
{ "delivery_note_no": "MPS-DN-118204", "delivery_date": "02 NOV 2026", "supplier": "Meridian Pantry Supply", "customer": "Hollis Bay Foods", "po_reference": "HBF-PO-30915", "carrier": "Northfield Freight Lines", "total_delivered": 228, "receiver_remark": "2 cartons damaged", "received_by": "R. Okafor", "received_time": "14:35"}
Trusted by logistics and supply chain teams around the globe
The signed copy comes back in whatever state the cab left it
A delivery note leaves the supplier as a clean print and returns after a day in a truck. These are the copies a receiving office actually files.
Folded in the cab, faxed from the depot, filed as a grey scan
Each supplier prints "delivered" in its own place, or not at all
Quantities corrected in pen and damage written beside the signature
Delivery order, arrival notice and POD scanned together per load
Carrier confirmations exported to a sheet with their own columns
Clerks type delivered quantities and remarks off signed copies days after the truck left, so a damage note in the margin often reaches accounts payable after the supplier's invoice is already paid.
Unstract reads each delivery note as it is scanned, pulls the delivered lines, signature details and remarks, checks them against the PO and ASN, and posts the receipt to your WMS or ERP.
Read, extract and receive from every signed delivery note
Three products do the work. LLMWhisperer reads the page, Document Studio pulls the fields and Flow runs the receiving around them; use one alone or all three from the scanner to a posted receipt.
Parse delivery notes with print and pen kept apart
A delivery note carries two layers: what the supplier printed and what the receiver wrote over it. LLMWhisperer keeps both in place, so the printed 48 stays in the ordered column, the pen count stays under delivered, and "2 cartons damaged" stays beside the signature it was written next to. Faxed dockets, carbon copies and phone photos of a crumpled receipt read the same way.
Feed the text to your own LLM as a delivery receipt parser, or make it the first step of a receiving workflow.
Learn more about LLMWhispererTurn each delivery note into one proof-of-delivery record
List the fields your receiving and freight audit teams need, and Document Studio returns one JSON schema for every supplier's delivery note: references, a line per item with ordered and delivered quantities, the receiver's name, the time signed and any remark. A delivery docket, a delivery order and a carrier's shipment confirmation come back in that same shape. Lines that differ from the PO, and receipts with no signature, arrive flagged with the reason.
Your WMS can call it as an API, an ETL pipeline can sweep the scanned POD folder each hour, or Flow can run it as one step of dock intake.
Learn more about Document StudioReceive against delivery notes from the dock door to a posted receipt
Write down in plain English what your receiving office does with a signed delivery note, and Flow's agents turn it into a workflow. Signed delivery notes scanned at the desk, delivery orders emailed by the forwarder and the ASN already in the WMS are tied to one shipment, read, checked line by line against the PO, and posted. Receipts land in your WMS or ERP, such as Blue Yonder, SAP S/4HANA or NetSuite, and the carrier record in a TMS such as Oracle Transportation Management. You approve the workflow once, and every delivery runs through it the same way.
Choose where a person steps in: a delivered quantity below the PO, a PO that isn't open, a damage remark, a signature the extraction can't read. Those deliveries wait for a receiving clerk with the delivery note open beside the flag; clean ones post on their own.
Learn more about FlowExtract your delivery notes now. Automate receiving after.
Start for free to parse and extract your own signed delivery notes today. Automating proof of delivery and dock intake starts with a consultation.
Delivery notes, proofs of delivery and the notices around them
Documents
- Delivery notes
- Delivery dockets
- Delivery receipts
- Signed proofs of delivery (POD)
- Delivery orders
- Arrival notices
- Dock receipts
- Delivery rejection notices
- Shipment confirmations
- Shipment acceptance notices
- Packing lists
- Bills of lading
- Advance ship notices (ASN)
- Purchase orders
- Goods receipt notes
- Any other supplier's delivery note layout
Fields captured
Processes delivery notes feed
Built for the people who sign for the load
Delivered counts and damage remarks recorded as the copy is scanned, so a claim against the carrier starts the same day.
Signed PODs from every client's carriers filed against the right order, ready when a client disputes a delivery.
Supplier delivery notes reconciled to the PO before the invoice arrives, with refused cartons kept off the payment.
Inbound deliveries from manufacturers confirmed on arrival, so stock counts and listings move when the goods are on the shelf.
Receipts posted on the day, claims raised on time
Customer addresses and signatures stay private
A delivery note carries your customers' delivery addresses, the names and signatures of the people who received the goods, and the damage remarks that every carrier or supplier claim starts from. A leaked copy gives away who you deliver to, and an altered remark weakens the claim.
- Delivery notes and POD scans are encrypted in transit and at rest.
- Signed receipts and delivery paperwork are never used to train any model.
- Access by role, site and client account, with every edited quantity and released hold logged against the delivery note number.
- You set retention: signed delivery notes are kept for your claim window and deleted when your contracts and audit rules allow.
- 3PLs that must keep client delivery records on their own servers can run Unstract self-hosted.
What receiving offices and 3PLs ask about delivery notes
Upload the delivery note to Document Studio as a PDF, scan or photo and name the fields you need, such as delivery note number, PO reference, item lines and delivered quantities. LLMWhisperer reads the page with its layout and handwriting kept, and the extraction returns those fields as JSON. Deploy the same schema as an API or a pipeline once the results look right.
Scan or photograph the signed copies as they come back from drivers, or route the depot's fax and email into one folder. Each POD is read, the receiver's printed name, signature, time and remarks are captured, and the record is filed against its order in your WMS or ERP, so the paper copy is no longer the only proof.
Yes. The delivery note OCR keeps handwriting where it was written, so a pen count sits under the delivered column and a remark such as "2 cartons damaged" stays with the signature beside it. The same delivery receipt OCR reads carrier PODs and dock receipts. A word the reader is unsure of comes back flagged, not guessed.
Yes. A single delivery note parser covers every supplier, because the schema stays fixed and the reading adapts to the page. "Qty delivered", "Rec'd" and a blank column the driver filled in all land in the same field, with no template per supplier.
Document Studio works as a delivery receipt data extractor that reports whether the receipt is signed, who printed their name and when. Flow can hold any delivery with no signature or a missing time, so an unsigned receipt never stands as proof of delivery.
Yes. Each delivered line is matched to the open PO line and the ASN, and the totals are checked against the cartons on the note. A short, refused or extra line holds that delivery with both figures shown, and the matched lines post.
The remark is captured as its own field and the delivery waits for a receiving clerk, who sees the remark next to the signed copy. The clerk accepts the lines, records the damaged quantity or starts a claim with the carrier, and every step is logged.
Delivery dockets, signed delivery receipts, delivery orders, arrival notices, dock receipts, rejection notices and shipment confirmations, plus the packing lists and bills of lading that travel with them. Each type gets its own schema, and Document Studio returns each one in it.
Unstract is SOC 2, ISO 27001, GDPR and HIPAA compliant. Delivery notes are encrypted, never used for training and deleted on the schedule you set. A 3PL that keeps client records on its own servers can self-host, and the Trust Center lists every control.
In a consultation we map intake around your suppliers' delivery notes, your receiving checks and your WMS or ERP, and most teams run live deliveries within days. To test the extraction on its own first, start for free and upload a signed delivery note.
Bring signed delivery notes from five suppliers to the consultation
Delivery dockets, signed PODs and delivery orders, folded and handwritten copies included. Each one is read on screen, its remarks pulled out and its lines checked against the PO while you watch.