Logistics – Delivery notes from PDFs and scans as a table

In short: Tiro reads delivery notes and packing lists from PDFs, scans and photos and returns them as a table – header fields such as delivery note number, PO number, carrier, consignment number, packages and weights once per document, every line item as its own row with article number, ordered, delivered, back order and batch. No template, no training – the example is a delivery note with 14 header fields and 11 line items, 2 of them back-ordered.

Below is the complete example: the delivery note, the extracted data and the result in the app.

Who this is built for

Whoever ships the goods prints the delivery note – whoever receives many shipments has to record it. Goods receiving at builders' and trade merchants, at manufacturers with hundreds of suppliers, the warehouse of an online retailer, dispatch at a freight forwarder: dozens of delivery notes a day, every supplier with its own layout, as PDF in the dispatch notification, as paper on the pallet, as a photo from the shop floor. The line items then have to be checked against the order, posted in the ERP and the back orders followed up – row by row. That retyping is what disappears.

What else logistics teams use it for

• Delivery notes and packing lists (the example below; scanned or photographed documents work as shown on the PDFs & scans page): one row per line item with ordered, delivered, back order and batch – for the goods receipt posting and the back-order list.
• Freight invoices from parcel carriers and forwarders: consignment number, weight, zone, toll and fuel surcharges – as rows for freight cost control per shipment.
• Consignment notes and bills of lading: shipper, consignee, carrier, packages, weights, pickup and delivery date – for shipment tracking and proof of delivery.
• Customs documents and commercial invoices for import: commodity code, country of origin, value, quantity – as a table for the customs declaration or the preference check.
• Loading lists, advance shipping notices and damage reports: what was announced, what arrived, what was damaged – one row per shipment for the claim to the supplier.

Why not just a PDF-to-Excel converter?

A PDF-to-Excel converter copies the page layout into cells. For a delivery note that means shipper, consignee and carrier blocks side by side in one row, the two-line article description split across two cells, "1,200" as text, and a different column order for every supplier. Parseur and Airparser solve this with fields instead of layout, but their examples are invoices and e-mails – neither of them shows goods receiving with a partial delivery and a back order. Tiro takes the field approach into logistics with one difference that matters at the match: quantities, weights and dates are normalised by default – ordered, delivered and back order as real numbers, the delivery date as a date, the position with quantity 0 kept as a row. What comes out of Tiro, Excel can check against the purchase order right away; the bank statements page shows the same idea applied to payments.