How to Extract Key Fields from Packing Slips into Excel
Even When Every Supplier Format Is Different
Manual receiving data entry errors cost warehouses an estimated $390,000 annually. A Grainger packing slip looks nothing like a Fastenal delivery note, which looks nothing like a Uline thermal-print sheet. Yet the receiving clerk still needs to pull the same five fields from each one — PO number, SKU, quantity received, lot number, and date — into a spreadsheet or WMS. Template-based OCR can't handle this format diversity. But an approach that reads fields by what they mean rather than where they sit on the page can.
Why Format Differences Break Traditional Extraction — and What Works Instead
Every supplier prints packing slips differently. Grainger uses a multi-column table with part numbers on the left and carton counts on the right. Fastenal might list items vertically with hand-written annotations at the loading dock. Uline thermal prints have no table structure at all — just line after line of text with item codes embedded mid-paragraph. MSC Industrial nests packing information inside a combined invoice/packing-slip document where shipping fields and billing fields share the same page. One logistics coordinator described the daily routine: "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."
Traditional OCR extraction fails here because it works by position. A template records that "PO Number" appears 2.3 inches from the top edge and 1.1 inches from the left — and if it moves, the extraction breaks. You'd need one template per supplier. Worse, templates break silently when a supplier changes their layout (which they do without notifying you), and you won't catch the error until the inventory discrepancy shows up weeks later.
The alternative is semantic extraction: reading a document the way a human receiver does. You don't scan for pixel coordinates — you look for the text that means "purchase order number" wherever it appears. This is what AI-based extraction does. Rather than memorizing positions, it understands the meaning of fields. On ImageToTable.ai, you simply type the column names you want — "PO Number", "SKU", "Quantity Received", "Lot Number" — and the AI locates each value anywhere on the page. This is called column-name extraction: the field names you type become the headers of your output table, and the AI matches values to columns by understanding what each field represents, not by remembering where it was last time.
The format diversity is real. According to the 2024 Warehousing and Fulfillment Costs & Pricing Survey, receiving costs range from $2.50 per SKU to $12.91 per pallet — and labor-intensive manual data entry is a major driver. The Warehousing Education & Research Council (WERC) benchmark study found that receiving accuracy below 85% puts you in the "major opportunity" tier; best-in-class operations hit 98% or above. Every format mismatch a receiver encounters pushes that number downward.
The Fields That Actually Matter for Receiving
Packing slips contain a lot of information. Most of it you don't need in a spreadsheet. The winning approach is selective: extract only the fields that drive your receiving workflow, leave everything else in the PDF.
| Field | Why It Matters | How It's Used |
|---|---|---|
| PO Number | The universal key that connects every shipment to your procurement system | Match received goods to open purchase orders; trigger partial-receipt workflows when only half a PO ships |
| Supplier / Vendor Name | Identifies who sent it — especially when the packing slip header doesn't match the PO vendor name | Route to correct receiving queue; track supplier compliance (on-time, accurate quantities) |
| SKU / Part Number | The supplier's identifier for each line item | Cross-reference against your internal part catalog; flag new or unrecognized part numbers for review |
| Quantity Shipped | What the supplier claims they put in the box | Compare against physical count during receiving inspection; generate exception reports for shortages or overages |
| Lot / Batch Number | Traceability anchor — especially critical in food, pharma, and electronics | Enter into WMS lot-tracking module; enables recall response without opening every carton |
| Ship Date / Delivery Date | When the shipment left the supplier | Calculate transit time per supplier; flag late deliveries for supplier scorecards |
| Packing Slip Number | The unique identifier on the slip itself | Filing reference for physical document storage; dispute resolution when quantities are contested |
Not every shipment needs every field. If you're a food distributor, lot numbers are non-negotiable — FDA 21 CFR Part 11 requires traceable electronic records for regulated products, and the packing slip is often the first document in that chain. If you're a general merchandise warehouse, you might only need PO number, SKU, and quantity. The point is that you define the columns — not the software, not the supplier's format.
This is the same field set used for batch processing multiple packing slips — the difference here is focusing on single-slip precision before scaling up to volume.
Step-by-Step: Extract Packing Slip Fields into Excel
The fastest way to go from a packing slip PDF to a structured spreadsheet is to define your fields first and let the AI find them — no position training, no template creation, no per-supplier setup. This walkthrough uses a single packing slip; the same column definitions scale to any number of documents from any mix of suppliers.
Upload your packing slip
Drag and drop a PDF, JPG, or PNG packing slip into the upload area. It can be a digital PDF from Grainger, a scanned delivery note from a local supplier, or a photo of a thermal-print slip — the AI processes all of them. Supported formats include PDF, JPG, PNG, WebP, and AVIF.
Define your column names
In the To Table mode, type the field names you want extracted — one per column. For a standard receiving workflow, enter: "PO Number", "Supplier Name", "SKU", "Quantity Shipped", "Lot Number", "Ship Date". These column names become the headers of your output table. The AI uses them as semantic targets — it searches the document for values matching each concept, regardless of exact wording on the page (a field labeled "Order Ref" or "Purch Ord #" will still map to your "PO Number" column).
Review and export
The AI extracts each value and populates your table in 5-10 seconds per page — compared to the 3 minutes a manual entry typically takes. Review the output for accuracy (printed text achieves up to 99% accuracy), then export as Excel (XLSX), CSV, or JSON. The same column definitions work on your next packing slip, even from a completely different supplier.
The output is a spreadsheet where each row is a packing slip (or a line item, depending on your column structure), and each column is a field you defined. No data cleaning needed — the AI automatically standardizes date formats, strips extra spaces from part numbers, and normalizes quantity values into numeric format.
Files are processed securely and not stored.
Try entering the fields listed above — "PO Number", "SKU", "Quantity Shipped" — and upload a packing slip. The same columns will extract data from any supplier's format because the AI reads for meaning, not position.
Handling Edge Cases: Scanned, Handwritten, and Thermal Paper Slips
A clean PDF packing slip generated by a modern ERP is the easy case. Real receiving docks deal with documents that are far less cooperative — and the extraction method needs to handle them.
Scanned packing slips (especially those forwarded as email attachments from a desk scanner at 150 DPI) are common from smaller suppliers. Text can appear blurred, skewed, or partially cut off. AI-based extraction handles these because it doesn't require crisp character boundaries — it interprets the visual content holistically, the same way a human receiver reads a slightly smeared document without decoding individual letter shapes. For heavily degraded scans, the approach is the same as described in the guide to converting scanned PDFs to Excel — upload, define columns, review.
Handwritten annotations — a loading dock worker scribbles "actual qty: 47" next to a printed quantity of 50 — are information the receiver needs, not noise to be ignored. ImageToTable.ai reads handwritten text alongside printed text, so those dock-level corrections end up in your spreadsheet rather than on a crumpled piece of paper in someone's pocket.
Thermal paper packing slips from Uline and similar suppliers present a physical challenge before the digital one: they fade. The solution is to photograph or scan them immediately upon receipt. Even a smartphone photo works — the AI processes photos of thermal prints the same way it processes PDFs. The field names you defined for Grainger packing slips work for Uline thermal prints without any configuration change.
Combined invoice/packing-slip documents — MSC Industrial and other B2B suppliers often issue a single document that serves as both invoice and packing slip. The same column-name extraction approach works here because you only extract the fields you care about. Financial fields (unit price, tax, total) sit on the same page as logistics fields (quantity, SKU, lot number), but you define your columns independently. If you later need invoice fields from the same document, the extract invoice fields workflow handles the financial side — the two extractions complement each other without duplicating work.
From Extraction to Receiving Workflow: Where the Spreadsheet Goes Next
Extraction produces a spreadsheet. The spreadsheet feeds the receiving process. What you do next depends on your existing systems.
If you have a WMS (Warehouse Management System) — Manhattan Active WMS, SAP EWM, Oracle WMS Cloud, Blue Yonder, or mid-market systems like Logiwa or Finale Inventory — you're likely importing received quantities through a CSV upload or API. The Excel file from extraction becomes your import source. Map the "PO Number" column to the WMS Purchase Order Reference field, "Quantity Shipped" to Received Quantity, "Lot Number" to the lot-tracking module, and import. This replaces manual key-entry into the WMS terminal.
If you use a lighter shipping platform like ShipStation or Fishbowl, the spreadsheet serves the same purpose — upload or copy-paste received quantities for inventory synchronization. ShipStation's packing slip templates cover the outbound side, but inbound receiving still needs data input from supplier documents. The extraction step fills that gap.
If your receiving process runs on spreadsheets — which the Warehousing Education and Research Council (WERC) still tracks as a common practice, with 44% of warehouses using paper-based picking as recently as 2023 — the extracted Excel file is your receiving log. Each row is a received shipment. Add columns for "Physical Count", "Discrepancy", and "Storage Location", and you have a complete receiving record without any manual data entry from packing slips.
Receiving accuracy has legal weight. Under the Uniform Commercial Code (UCC § 2-513), a buyer has the right to inspect goods before acceptance — and the packing slip is the primary reference document for that inspection. OSHA 1910.176 adds the safety dimension: goods must be verified before storage to ensure they're stacked safely and don't create hazards. Getting packing slip data into a system quickly and accurately isn't just an efficiency question — it's the operational step that triggers both legal acceptance and safe storage decisions.
When you're ready to scale beyond single-slip processing, the batch extraction approach lets you upload a day's worth of packing slips at once and output a single consolidated receiving spreadsheet. The same column definitions carry over — the workflow scales without requiring new configuration. For comparison, similar batch logic applies to vendor quotes from different formats, where the same supplier-diversity problem appears in procurement rather than receiving.
Frequently Asked Questions
Does this work with handwritten packing slips?
Yes. The AI recognizes handwritten text including numbers, product codes, and annotations written at the loading dock. Accuracy on handwriting is lower than on printed text (expect ~85-95% depending on legibility) — always review handwritten extractions before finalizing your receiving log.
What if the packing slip uses different field names than the ones I typed?
This is the core advantage of semantic extraction. If you type "PO Number" as a column name and the packing slip labels the field "Purch Ord #" or "Order Ref", the AI understands they refer to the same concept and extracts the correct value. You don't need to rename your columns to match every supplier's terminology.
Can I extract packing slip data directly into Google Sheets?
Yes. The Google Sheets add-on lets you upload packing slips and specify column names directly from a Sheets sidebar — extracted data populates your active sheet without switching applications.
How many packing slips can I process at once?
Single-slip mode handles one document at a time — ideal for real-time receiving where each shipment needs immediate verification. For end-of-day or bulk processing, the batch mode supports uploading multiple packing slips simultaneously (including mixed formats from different suppliers) and outputs a single consolidated Excel file. See the batch packing slip processing guide for the volume workflow.
Can the AI tell if the packing slip quantities don't match the PO?
ImageToTable.ai extracts what's on the packing slip — it doesn't have access to your purchase order data to perform matching automatically. You can, however, use Computed Columns to perform checks during extraction. For example, if you have a multi-line packing slip, a computed column can sum all line-item quantities to verify against a printed total. Discrepancy checking against your PO is a spreadsheet step after export — bring both the extracted packing slip data and PO line items into Excel and use a VLOOKUP or INDEX/MATCH to flag mismatches.
What about non-English packing slips?
The AI processes packing slips in 50+ languages. A German Lieferschein from a European supplier extracts the same way as an English packing slip from Grainger — type your column names in English, and the AI locates the corresponding values regardless of the document's language.
Every supplier formats packing slips differently. Your extraction method shouldn't need to care.
Define your fields once — "PO Number", "SKU", "Qty", "Lot" — and the AI finds them on any packing slip, PDF, scan, or photo. No templates. No per-supplier setup.
Try It on Your Own Packing Slips