Set Up Packing Slip Fields and Run a Test Batch
Configure packing slip fields in the dashboard — capture PO references, shipped quantities, and item tables for warehouse receiving workflows.
Ready to set this up? Sign up for PerfectParser and get 20 free credits — no credit card required.
What this guide helps you do
This guide shows how to configure a packing slip parser in PerfectParser, define receiving fields and item tables, run a test batch, and export warehouse data. After you upload a sample, field detection runs automatically. Compare the Schema tab with the recommended fields below and adjust supplier-specific column names.
Why packing slips are hard to parse
Packing slips sit between purchase orders and physical goods, so the same data appears under different labels — "Ship Qty", "Qty Shipped", or just "Qty". SKU columns may show part numbers while the adjacent column carries a long product description, and some suppliers omit the PO reference entirely while others print it in a barcode footer. Multi-line item tables often wrap descriptions across rows, which can split a single SKU into two parsed rows if the schema is not explicit. The qty ordered vs qty shipped distinction is critical for receiving: treating them as one field hides partial shipments. Dense warehouse printouts also use small fonts and thermal paper, so field descriptions in your schema should tell the AI which column is which.
Recommended Fields
We suggest configuring the following schema fields for your Packing Slip Parser to capture all essential warehouse receiving details.
| Field Name | Type | Description |
|---|---|---|
slip_number | Text | The unique packing slip or delivery note reference number. |
po_reference | Text | The associated purchase order number. |
shipper_name | Text | The company or vendor shipping the package. |
recipient_name | Text | The recipient name or company details. |
ship_date | Text | The date the shipment was dispatched. |
shipped_items | Table | Table containing item_code, description, qty_ordered, and qty_shipped for each package item. |
Set up this parser in the dashboard
Create a parser
Go to Parsers → New Parser in the dashboard. Give it a name like "Packing Slip Parser". You can set the parser name while detection runs.
Upload a sample document
Drag and drop a representative packing slip (PDF, PNG, or JPEG). Use a real file from a supplier whose format you process regularly — the AI uses it to learn column headers and table structure. Field detection and sample extraction start automatically.
Review detected fields
Field detection and sample extraction start as soon as the upload finishes. Open the Schema tab and compare detected fields with the Recommended Fields table above. Rename, remove, or add fields, and edit each field's instructions. Check sample values on the Results tab.
Review and save your schema
Check that shipped_items is a Table with separate qty_ordered and qty_shipped columns. Confirm item_code is Text, not Number — SKUs often contain leading zeros or letters. Edit any field names or descriptions, then click Save parser. You can edit fields later on the parser Fields tab.
Run a test batch
Open Run Extraction, choose how your files are organised, upload a small test set of packing slips, and click Start batch extraction. Review the run on the Results tab and export to CSV or Excel.
Common mistakes
- Collapsing qty ordered and qty shipped into a single quantity column — you lose the ability to flag partial or over-shipments during receiving.
- Storing SKUs as Number, which strips leading zeros (e.g.
004521becomes4521). - Using a delivery note without an item table as the sample when production slips always include line-level detail.
- Omitting
po_referencefrom the schema when your 3-way match workflow depends on linking slips back to open purchase orders.
Next steps
Test your first extraction free — sign up for PerfectParser, no credit card needed.
FAQs
Do I need a sample packing slip to set up this parser?
Yes. Upload a packing slip that matches the format your warehouse receives most often — including the item table layout and PO reference placement. Different suppliers use different column headers, so a representative sample improves first-pass accuracy.
Should I capture qty_ordered and qty_shipped as separate fields?
Yes. Store both in your shipped_items table. Receiving workflows depend on comparing what was ordered against what arrived. A single quantity column loses the discrepancy signal you need for partial shipments or over-ships.
How many credits does setup and a test extraction use?
Parser setup is free. Each page processed during extraction costs 1 credit. Most packing slips are one page (1 credit). Multi-page shipment manifests cost 1 credit per page. New accounts include 20 free credits for testing.
Looking for product features and use cases?