A packing slip tells you exactly what is inside a shipment, carton by carton, and Docyield's parser turns that detail into clean rows you can check against a delivery or feed into your warehouse system. Drop in a PDF or a photo and you get the document number, the date, the shipper and consignee, and every packed item — quantities, package counts, net and gross weights, and dimensions — back as CSV, Excel, or JSON, with no line-by-line transcribing.
Where an invoice cares about money, a packing slip cares about contents. It is the document a receiving clerk holds while opening boxes, the reference a warehouse uses to verify a count, and the basis for confirming that what was ordered actually arrived. Docyield reads the item table as a structured list and keeps the totals apart from the individual lines, so the data lands ready to reconcile rather than as a wall of text.
What a packing slip is and what it is for
A packing slip — also called a packing list or bill of parcel — accompanies a shipment and itemises its physical contents. Unlike a commercial invoice, it usually carries no prices; its job is to describe quantities, packaging, and weights so the receiver can verify the goods on arrival. It is normally placed inside or attached to the outside of a package and is referenced the moment a box is opened at the dock.
In the flow of a shipment, the packing slip is produced when goods are packed and sits between the order and the delivery. The warehouse uses it to pick and pack, the carrier may reference it for handling, and the receiving team uses it to confirm the count before signing off. Getting that itemised detail into a system quickly is what lets a receiving team close out a delivery in minutes instead of an afternoon.
Why structured extraction beats raw OCR or manual entry
Receiving teams often check a paper packing slip against a screen by eye, then type discrepancies into a system by hand. That is exactly the kind of repetitive, detail-heavy work where mistakes slip in — a quantity misread, a weight skipped. Pulling the item table out as structured rows lets you compare expected against received automatically instead of squinting line by line.
Plain OCR cannot do that reconciliation for you. It produces the text but not the structure, so you still have to separate item descriptions from quantities and weights, and the packed totals from the per-line figures. Docyield returns each item as its own record with named fields, which means a spreadsheet or warehouse system can match them to order lines without any further parsing.
Who relies on a packing slip parser
- Warehouse and receiving teams verifying inbound shipments against what was ordered.
- 3PLs and fulfilment operators logging contents at goods-in across many clients.
- Importers and exporters cross-checking packing lists against commercial invoices and bills of lading.
- Inventory and ops teams updating stock records from delivered quantities.
- ERP and WMS integrations that need packed item data captured automatically.
- Returns and quality teams reconciling what physically arrived against the paperwork.
Accuracy, missing values, and review
No extraction is right every time, and we will not pretend otherwise. Docyield is built to be accurate on clean packing slips and transparent on the rest. If a field like dimensions or net weight is simply absent from a line, it comes back empty — never invented — because a fabricated weight is worse than a blank one when someone is reconciling a physical count.
Image quality matters most on the item table, where small figures sit close together. A clear scan reads cleanly; a creased, low-resolution photo of a slip stuffed in a pouch is harder. For the minority of documents that arrive degraded, the source stays beside the extracted rows so a quick human pass can confirm the counts before they update inventory.
Reading item tables, package counts, and weights
The heart of a packing slip is its item table, and packing slips vary a lot in how they lay it out. Some show one row per SKU with a quantity; others add separate columns for package or carton counts, net and gross weights, and box dimensions. Docyield reads each row as a structured item carrying all of those attributes, and keeps the document-level totals — total packages, total net weight, total gross weight — as their own fields so summary and detail never collide.
That separation matters when you reconcile. You can sum the per-line quantities and check them against the totals, or compare the total package count to what physically turned up on the dock. Because numbers come back as numbers and weights keep their units, the figures are usable immediately rather than as text that has to be cleaned first.
Output formats, API, and batch processing
Each parse exports as CSV, Excel, JSON, or XML from the same result, and packing slips default to CSV because the item table is naturally row-shaped — ideal for dropping into a spreadsheet or importing to a WMS. JSON suits developers wiring contents into an application, while XML fits older ERP feeds. The free tool processes one slip at a time, which covers ad-hoc receiving checks.
For a fulfilment operation handling many deliveries a day, the same extraction runs through the Docyield API and batch dashboard, with webhooks and your own validation rules. The schema in the free tool is the schema the API returns, so a workflow built against the item fields keeps working unchanged as you scale from manual uploads to an automated pipeline.
Packing slip versus invoice and delivery note
These documents travel together but answer different questions. A packing slip describes the physical contents — what is in the boxes — usually without prices. A commercial invoice states the values and is the document customs and accounting care about. A delivery note confirms a handover and is signed on receipt. Keeping a dedicated parser for the packing slip means the fields match its contents-and-weights focus, rather than forcing a price-oriented invoice schema onto a document that has none.
What the packing slip parser extracts
Each packing slip is returned against a fixed schema. Fields absent from a document come back empty rather than guessed.
- Document number
- The packing slip or packing list number or reference.
- Date
- The date shown on the packing slip.
- Shipper
- The shipper or exporter sending the goods.
- Consignee
- The consignee or receiver of the shipment.
- Items
- Each packed line, with description, quantity, package count, net weight, gross weight, and dimensions.
- Total packages
- The total number of packages or cartons.
- Total net weight
- The total net weight, with its unit where given.
- Total gross weight
- The total gross weight, with its unit where given.
How to convert a packing slip to CSV, Excel, or JSON
- 1Upload your packing slip — drop a PDF, PNG, JPG, or WEBP onto the box above, or click to choose a file.
- 2Wait a few seconds while Docyield reads the document and pulls out the item table.
- 3Review the structured rows and check the quantities and weights against the original.
- 4Choose your output tab — CSV, Excel, JSON, or XML.
- 5Copy the result or download the file, ready to reconcile or import into your warehouse system.
Frequently asked questions
Processing documents at scale?
Batch upload, an extraction API, and webhooks for 100+ documents a month.