Extract data from packing lists
Unstract reads export packing lists and parcel packing slips, emailed, scanned or photographed on the receiving floor, and returns carton, SKU, quantity and weight data, checked against the PO and ASN, to your WMS or ERP.
| CARTONS · ITEM | QTY | NET KG | GROSS KG |
|---|---|---|---|
| CARTON CONTENTS | |||
| C/NO. 1-60 · TS-2240 Trekking poles, pair | 1,200 | 540.00 | 612.00 |
| C/NO. 61-110 · HB-3150 Hydration pack 15L | 1,200 | 420.00 | 475.00 |
| C/NO. 111-150 · CL-0880 Camp lantern | 1,440 | 518.40 | 566.40 |
| C/NO. 151-180 · SB-5020 Sleeping bag liner | 1,200 | 360.00 | 402.00 |
| TOTAL 180 CARTONS · 14.62 CBM | 5,040 | 1,838.40 | 2,055.40 |
ctn 147 crushed at the door, recount lanterns — Dee
SHIPPING MARKS: TCS / RENO NV / PO TCS-44107 / C/NO. 1-180 / MADE IN CHINA
{ "packing_list_no": "SOG-PL-26-0918", "invoice_no": "SOG-26-0918", "po_number": "TCS-44107", "exporter": "Sunridge Outdoor Gear", "consignee": "Trailcrest Supply", "total_cartons": 180, "total_quantity": 5040, "net_weight_kg": 1838.4, "gross_weight_kg": 2055.4, "volume_cbm": 14.62}
Trusted by logistics and supply chain teams around the globe
Every supplier packs the paperwork its own way
Few packing lists reach the dock as a tidy PDF. A week of inbound freight brings documents like these.
Pulled from the carton pouch, creased, then scanned at the desk
One SKU, three suppliers, three ways of listing the cartons
Counts corrected in pen by whoever opened the cartons
Invoice, packing list and B/L sent as one scan per container
Spreadsheet packing lists and shipping advices with their own columns
Receivers key carton counts and SKUs into the WMS line by line, and a short case that slips through becomes a stock error that surfaces weeks later as a missed order.
Unstract reads each packing list as it arrives, pulls the cartons, SKUs, quantities and weights, compares them with the PO and ASN, and posts the receipt to your WMS or ERP.
Read, extract and receive against every packing list
Parsing, extraction and automation are three products. Each one works on its own, and together they take a packing list from the inbox to a posted receipt.
Parse packing lists with every carton range on its own line
Suppliers lay out packing lists in dozens of ways: a carton range per line, one row per SKU, weights per carton or per line. LLMWhisperer keeps the table as it was printed, so carton 61 stays with the hydration packs and the net weight never slides into the gross column, whether the page came as a PDF, a scan or a phone photo of a slip.
Pass the text to your own LLM as a packing list parser, or make it the first step of a receiving workflow.
Learn more about LLMWhispererTurn each packing list into the same receiving record
Name the fields your receivers need, and data extraction from packing list layouts of every supplier returns one JSON schema: header references, a line per SKU with its carton range, and the totals. A parcel packing slip, an export packing list and a warehouse shipping advice all come back in that shape, with no template per supplier. Quantities and SKUs that disagree with the ASN or the PO arrive flagged, with the other figure shown.
Call it as an API from your WMS, run it as an ETL pipeline from the receiving inbox, or make it one step in an orchestrated intake.
Learn more about Document StudioReceive inbound freight from packing list to posted receipt
Describe how your dock receives against a packing list in plain English, and Flow's agents build the workflow. Packing lists from supplier emails, slips photographed at the door and the ASN already in the WMS are tied to one shipment, read, matched line by line to the PO and ASN, and posted. Receipts land in your WMS or ERP, such as Manhattan Active WM, Blue Yonder or NetSuite. You approve the workflow once, and every shipment runs through it the same way.
Choose where a person steps in: a quantity short against the ASN, a PO that isn't open, a read the extraction isn't sure of. Those shipments wait for a receiving clerk with the reason beside the packing list; the rest post on their own.
Learn more about FlowExtract your packing lists now. Automate receiving after.
Start for free to parse and extract your own packing lists today. Automating shipment intake at the dock starts with a consultation.
Packing lists, slips and the paperwork that travels with them
Documents
- Packing lists
- Export packing lists
- Packing slips
- Material shipping records
- Warehouse shipping advice
- Advance ship notices (ASN)
- Commercial invoices
- Bills of lading
- Purchase orders
- Delivery notes
- Carton content labels
- Weight and measurement certificates
- Return packing slips
- Goods receipt notes
- Proof of delivery receipts
- Any other supplier's packing list layout
Fields captured
Built for the people who open the cartons
Packing lists read before the trailer is unloaded, so receivers count against expected lines instead of typing them in first.
Every client's packing slip format lands in one receiving record, so a new account goes live without a new data-entry routine.
Supplier packing lists checked against the PO on arrival, with short and over-shipped lines raised before the vendor invoice is paid.
Inbound stock from each manufacturer received the day it lands, so listings show what is on the shelf, not what was ordered.
Faster receiving, fewer stock surprises
Supplier terms and customer orders stay private
A packing list names who supplies you and who you ship to, and it shows order quantities and, on commercial copies, unit values. Put together across a season, that shows a competitor your sources, your best customers and how much each one buys.




- Packing lists are encrypted in transit and at rest.
- Shipment paperwork is never used to train any model.
- Access by role, site and client account, with every corrected quantity and released hold logged against the packing list number.
- You choose retention: packing lists and their attachments are deleted when your client contracts and audit rules say so.
- 3PLs and distributors that must keep client data on their own servers can run Unstract self-hosted.
What receiving teams and 3PLs ask first
One that returns the same receiving record from any supplier's layout. Document Studio deploys an endpoint for your packing list schema: POST the PDF, scan or photo and get the header references, a line per SKU and the carton, quantity and weight totals back as JSON. The same extraction also runs as an ETL pipeline over a shared inbox or bucket.
Unstract, in three layers. LLMWhisperer turns the page into text with the table intact, Document Studio uses LLMs to pull the SKUs, descriptions, quantities and weights you named, and Flow's agents run the receiving checks around them. The OCR layer is not an LLM, so the text the extraction reads stays faithful to the page.
LLMWhisperer reads PDFs, scans, faxes and phone photos of packing lists and keeps their columns in place, and Document Studio returns the shipment details as JSON: PO, invoice and ASN references, shipping marks, cartons, net and gross weight and volume.
Document Studio finds each field by what it means, not where it sits, so "C/NO.", "Carton #" and "Box range" all fill the same field. A new supplier's packing list needs no template and no training before the first one is read.
Yes. The same packing slip OCR reads the slips that ride inside parcel cartons, return slips and drop-ship slips, including creased pages pulled from a pouch and photographed at the bench, with handwritten counts read alongside the print.
No. One packing slip parser handles every supplier, because the schema stays fixed and the reading adapts to the layout. Add a field to the schema once and every supplier's slips start returning it.
Both, in layers. On its own, Document Studio acts as a packing slip data extractor and hands your developers JSON. Flow adds the receiving around it: collecting the paperwork per shipment, matching to the ASN and PO, holding exceptions and posting the receipt.
Yes. Each SKU's quantity is matched to the ASN line and the open PO, carton totals are compared with the bill of lading, and net and gross weights are footed. A mismatch holds that shipment with both figures shown, and the matched lines carry on.
A receiving clerk sees the flagged line beside the spot on the packing list it came from, then accepts it, corrects the count or sends it back to the supplier. Every decision is logged, and other shipments keep moving.
Unstract is SOC 2, ISO 27001, GDPR and HIPAA compliant. Packing lists are encrypted, never used for training and deleted on your schedule. Teams that must keep client data in-house can self-host; the Trust Center lists every control.
In a consultation we set up intake around your suppliers' packing lists, your receiving checks and your WMS or ERP, and most teams receive live shipments within days. To test the extraction first, start for free and upload a packing list.
Bring packing lists from five suppliers to the consultation
Export packing lists, parcel slips and warehouse shipping advices, creased and handwritten copies included. Each one is read on screen and matched to its PO and ASN while you watch.









