How to Combine Packing Slips and Delivery Notes
from Any Supplier into One Receiving Spreadsheet
A logistics provider described their daily receiving routine on LinkedIn: "Every order required someone to manually read through a packing slip, pull out the PO number, weight, carton count, figure out freight class, type it into a spreadsheet, crop the shipping labels to size, and email everything to the warehouse. Multiple times a day. Every day. None of it was hard. All of it was tedious. And all of it lived inside one person's head." That's the packing slip problem in one paragraph: low cognitive difficulty, high volume, zero automation. And when that one person is out sick, the receiving dock slows to a crawl.
Why Packing Slips Are Harder to Automate Than Invoices
Invoices have financial stakes driving automation investment — AP departments have budgets, software vendors build for them, and the ROI math is clear. Packing slips sit in a dead zone between logistics and finance. They're not invoices (so AP automation doesn't cover them). They're not inventory transactions (so the WMS doesn't ingest them automatically). They're the document that says "this is what's in the box," and for most warehouses and receiving docks, getting that information into a system still means someone standing at a desk with a stack of paper and a keyboard.
The format problem is worse for packing slips than for almost any other business document. Invoices and POs are typically generated by ERP systems — they have structure, even if the structure varies. Packing slips are often printed on thermal paper from a warehouse printer, handwritten annotations added at the loading dock, scanned at 150 DPI three years ago, and stored as a compressed attachment in an email forwarded twice. Every supplier's packing slip looks different because every supplier's warehouse workflow is different. One uses a 4-column item table with SKU and carton numbers. Another uses a vertical list with no table structure at all. A third bundles the packing slip with the commercial invoice on the same page.
Template-based extraction — which works by memorizing the pixel positions of fields — fails completely here. You'd need one template per supplier, and templates break the moment a supplier changes their packing slip layout (which they do, without warning you). The only viable approach is one that reads the document by field meaning, not field position.
The cost of staying manual: Industry data indicates that manual receiving creates quantifiable losses. Workers spend 15-20 minutes per shipment verifying product codes, quantities, and lot numbers, with error rates of 1-3% per data entry field. These errors lead to inventory discrepancies — misplaced products, delayed customer orders, unprocessed goods clogging storage. The cumulative cost has been estimated at $390,000 annually per warehouse. And that's before accounting for the human cost: the key person who knows the process calls in sick, and the receiving dock stops processing.
The Core Packing Slip Field Set
Packing slips and delivery notes share a common set of fields that matter for receiving, inventory update, and PO reconciliation. Define these columns once and use them across every supplier:
| Field | Why it matters | Naming tip |
|---|---|---|
| Slip Number / Packing Slip ID | Unique identifier for the shipment — links to carrier tracking | Use "Packing Slip Number" — distinguishes from PO and invoice numbers |
| PO Number / Order Reference | Links the shipment back to the originating purchase order | Use "PO Number" — standard across all document types |
| Ship Date | Verifies on-time delivery and supports carrier performance tracking | Use "Ship Date (YYYY-MM-DD)" for consistent output formatting |
| Supplier / Shipper Name | Identifies who sent the goods — may differ from the billing entity | Use "Supplier Name" — matches PO terminology |
| Carrier Name | Enables carrier performance comparison across suppliers | Use "Carrier Name" — distinct from supplier/shipper |
| Tracking Number | Links to carrier portal for real-time status and POD | Use "Tracking Number" — universally understood |
| Item Code / SKU | Matches received goods to inventory records for putaway | Use "Item Code" — the AI maps "SKU" and "Part Number" to this |
| Item Description | Visual verification for receiving inspection | Use "Item Description" — standard terminology |
| Quantity Shipped | Core reconciliation value against PO ordered quantity | Use "Quantity Shipped (Number)" — distinguishes from quantity ordered |
| Carton / Pallet ID | Physical location reference for warehouse putaway | Use "Carton Number" or "Pallet ID" depending on your unit |
| Package Count | Total cartons/pallets in the shipment — dock-level verification | Use "Total Package Count (Number)" |
Not every packing slip will contain every field. Define the columns you consistently need; blank cells for missing fields are cleaner than omitting columns and having inconsistent output structure across batches.
The Three-Way Match: Packing Slip + PO + Invoice
The real operational payoff of digitizing packing slips isn't just saving data entry time — it's enabling a proper three-way reconciliation before payment. Here's what that looks like when all three document types are extracted into structured data using the same column-name approach:
| Document | What it tells you | Key reconciliation field |
|---|---|---|
| Purchase Order | Quantity ordered, agreed unit price, requested delivery date | Quantity Ordered |
| Packing Slip | Quantity actually shipped, carton count, carrier, tracking | Quantity Shipped |
| Invoice | Quantity billed, unit price charged, total amount due | Quantity Billed |
With all three data sets in spreadsheet format, discrepancies surface immediately. A line item with 100 ordered, 80 shipped, but 100 billed is caught before payment — not discovered three months later during a reconciliation project that consumes half a week. A shipment where the packing slip says 12 cartons but the receiving team only counted 11 is flagged before the carrier leaves the dock. This is the difference between proactive discrepancy management and reactive firefighting — and it only works when packing slip data is digital.
Why most teams don't do this: The three-way match is procurement 101 in theory but rare in practice for one reason — packing slip data is almost never digitized. POs live in the ERP. Invoices get processed by AP. Packing slips sit in a filing cabinet or an email attachment folder. Closing that gap — getting packing slip data into the same spreadsheet format as PO and invoice data — is the bottleneck that column-name extraction removes.
Batch Processing: From Dock Receipts to Receiving Report
The batch packing slip workflow follows the same pattern as PO and invoice batch processing, with one difference: the source documents are often lower quality. Here's the end-to-end flow:
Define your receiving columns. Set up your field set once — Slip Number, PO Number, Supplier, Ship Date, Carrier, Tracking, Item Code, Qty Shipped, Carton Count. Save as a template. This works across all suppliers regardless of their packing slip format.
Upload the day's packing slips in one batch. Scan paper slips at the receiving dock, collect PDF attachments from supplier emails, photograph thermal-printed labels — upload everything at once. The AI processes mixed formats in a single batch.
AI extracts and aligns. Each packing slip is processed against your column definitions. Header fields (Slip Number, PO Number, Supplier) repeat into every line-item row. Line-item fields (Item Code, Qty Shipped) are extracted row by row from the slip's item table.
Review and reconcile. The merged spreadsheet shows every line item from every packing slip in the batch. Filter by PO Number to see what's been shipped against each PO. Cross-reference with your PO spreadsheet to flag partial shipments and backorders before inventory hits the dock.
For a typical receiving operation processing 30-50 packing slips per day, the manual workflow consumes 2-4 hours. The batch extraction workflow — upload, process, review — completes in under 15 minutes. The time savings compound: 2-4 hours per day is 10-20 hours per week, which is a quarter to half of a full-time position recovered for higher-value work.
Files are processed securely and not stored.
Remove the Collection Bottleneck Too
Even with automated extraction, you still need to get the packing slips into the system. If your current workflow is "check supplier email → download PDF attachment → save to receiving folder → upload to extraction tool," you've automated the reading but not the collecting.
Collection Link closes this gap for packing slips the same way it does for POs and invoices. Share a unique URL with suppliers as part of your shipping instructions or vendor onboarding — "upload your digital packing slip here." The slip lands directly in your processing queue without touching email. For drop-ship suppliers where you never see the physical packing slip, this is the only reliable way to get that data into your system before the customer receives the goods.
The full loop: supplier uploads packing slip via Collection Link → AI extracts item and shipment data → data merges into your receiving spreadsheet → you cross-reference against your PO spreadsheet → discrepancies are flagged before goods receipt is finalized. The only human step is the one that requires judgment: reviewing flagged discrepancies and deciding what action to take.
Frequently Asked Questions
Can the AI read thermal-printed packing slips — the kind that fade over time?
Partially. Thermal print fades because the chemical coating degrades, reducing contrast between text and background. A fresh thermal print extracts similarly to laser-printed documents. A six-month-old thermal print with visible fading will produce lower accuracy — the AI can still read most characters but may miss faint sections. For archival packing slips, scan them while the print is still legible. For incoming slips, photograph them on arrival if they'll be needed for later reference.
What about packing slips with handwritten quantity changes — e.g., "shipped 8 of 10, 2 backordered" written in the margin?
Handwritten annotations reduce accuracy compared to printed text. The AI will attempt to read legible handwritten notes, but scribbled or heavily stylized writing may be missed. For mixed printed/handwritten slips — common in warehouse environments where staff annotate at the dock — expect to spot-check the output for handwritten fields. The AI handles printed fields reliably; handwritten fields may need manual verification.
How does this work with international packing slips that include customs fields (HTS codes, country of origin, commercial value)?
Add custom columns for the customs fields you need: "HTS Code," "Country of Origin," "Declared Value," "Net Weight (kg)," "Gross Weight (kg)." The AI extracts these alongside standard receiving fields. International packing slips are often more structured than domestic ones because customs requirements enforce standardization — which actually improves extraction accuracy.
Can packing slip data feed directly into our WMS or inventory system?
The extracted XLSX output can be imported into most WMS and ERP systems via their standard import tools. For automated integration, the data can also be exported as CSV or JSON and fed into systems through their API or file-watch directories. The extraction layer produces structured, consistently formatted data; the integration layer is where you connect that data to your specific systems. If your WMS supports XLSX or CSV import for goods receipt, the output is ready to use without transformation.