Delivery note OCR
Delivery notes in. Quantities out.
Upload delivery notes and packing slips as PDFs, scans or photos, forward them by e-mail or send them to the API. Parsevix returns the order number, every delivered line with its quantity and backorder, batch numbers, the carrier and who signed for receipt, as structured data.
- Every line with delivered and backordered quantity
- The order number to match note, order and invoice
- Your own fields, defined once
No credit card · 20 free pages every month
The fields to define
Your delivery note schema, set up once.
There is no ready-made Delivery Note category: you create one in your project, with fields like these 22. Every delivery note after that comes back in the same shape. Without a category, Parsevix can extract without a schema and use the note's own labels as keys.
Dates come back as ISO dates and quantities as plain numbers. A field the note doesn't contain, such as a batch number, is left out, not guessed.
Delivery note
- delivery_note_numberstring
- delivery_datedate
- order_numberstring
- customer_numberstring
Supplier
supplier_infoobject
- supplier_namestring
- supplier_addressstring
Customer
customer_infoobject
- customer_namestring
- customer_addressstring
Delivered lines
line_itemsarray
- article_numberstring
- descriptionstring
- quantitynumber
- unitstring
- backorder_quantitynumber
- batch_numberstring
Shipment
- delivery_addressstring
- total_packagesnumber
- gross_weightstring
- carrierstring
- tracking_numberstring
- notesstring
Receipt
- received_bystring
- received_datedate
Made for goods receipt
What arrived, what is still open.
Delivery notes come in every layout, one per shipment, and they decide what an invoice may bill. This is what Parsevix does with them.
Partial deliveries, line by line
Each line comes back with the quantity delivered and the quantity still on backorder, as the note prints them. With the order number, your system can set them against the purchase order and see which lines are complete and which are still open.
- 02
Proof of delivery
The name of the person who signed for receipt and the date come back as fields. A handwritten name is read where it is legible; a signature itself is not turned into a name.
- 03
Note, order, invoice
The order and customer numbers link each note to its purchase order and invoice, so your system can check that only what arrived gets paid.
- 04
Batch and serial numbers
Batch, lot or serial numbers come back per line, for traceability and recalls.
- 05
Carrier and shipment
Carrier, tracking number, number of packages and gross weight come back as fields of their own.
- 06
No category yet?
Extract without a schema: Parsevix returns every field it finds, named with the note's own labels. Turn it into a category once you know the fields you need.
- 07
Notes in any language
The language is detected on every page. A note in another language fills the same fields, with ISO dates and plain numbers.
How notes get in
Upload them, forward them or send them from your system.
Dashboard
Upload delivery notes as PDFs, scans or photos. Check each result next to its page, with every value marked where it was printed, and approve it.
E-mail address
Paid plansEvery project gets its own address. Have suppliers send delivery notes to it, and each attachment becomes a document.
API
Send notes from your warehouse or ERP system and get the JSON in the same response, or receive results by signed webhook or through Zapier.
Request
curl https://parsevix.com/api/v1/extract \ -H "X-API-Key: $PARSEVIX_API_KEY" \ -F file=@delivery-note.pdf \ -F category="Delivery Note"
The request stays open until the document is read and answers with the JSON.
- POST /documentsUpload without waiting; the result arrives by webhook or callback.
- POST /extract-autoNo category: every field Parsevix finds, named as in the document.
- POST /classifyOnly the document's category, for 1 credit.
Response · trimmed
Security & compliance
- PII maskedautomatically, before the AI step
- Encryptedin transit and at rest
- No AI trainingon your documents
- API files deletedafter processing
Priced per page, not per feature.
Every plan reads, sorts and masks documents the same way. Picking the category is included, and a document that fails costs nothing.
See pricing- credit per page
- 1
- free pages every month
- 20
- a month for 500 pages
- $39
Delivery note FAQ
Delivery notes,
answered.
What teams ask before they send their first delivery notes.
PDF, Word (DOCX), PNG, JPG and TIFF, up to 10 MB and 30 pages each. Scans and phone photos of signed notes work too; every page is read as an image.
No. Create a category in your project with the fields you need, such as the ones on this page; it takes a few minutes and is used for every note after that. Or extract without a schema and get the note's own labels as keys.
No. It returns the order number and the quantities each note prints. Matching them with your purchase orders and invoices happens in your own system.
No, barcodes and QR codes are not decoded. The numbers printed in plain text next to them are read like any other text.
One credit per page: a two-page delivery note uses two. Choosing the category is included, and if a document fails, its credits are given back.
Notes uploaded in the dashboard or sent by e-mail stay in your project until you delete them. Files sent through the API are deleted after processing unless you turn on keeping them for the project. Your documents are never used to train AI.
Related use cases