For freight documentation and importer operations teams
Packing lists to CSV rows your operations team can review.
Prepare structured rows from digital or scanned packing lists. Confirm the fields in the document, keep the source-page context, and arrange the output columns for your team's import template.
Try one clear PDF up to 5 pages free, with review and download. No credit card required. Complex or unsupported tables may need another sample.
Start with one repeatable workflow.
Choose a packing list with the package, quantity, and weight fields your receiving workflow actually uses. Confirm whether a repeated row represents an item, a carton, or a package group before you accept the proposed mapping.
1. Upload and map
Upload the PDF, confirm the fields, and optionally save the reviewed layout.
2. Review the values
Use source-page context and available checks to inspect critical rows and exceptions.
3. Export and validate
Download Excel or your exact-template CSV, then test the receiving import workflow.
Fields to map and checks to keep.
These are practical mapping examples. Confirm your own document fields and destination requirements before operational use.
| Source fields | Output mapping | Review before import |
|---|---|---|
| Packing-list identifier | Keep the document reference available in the reviewed result. | Verify that the reference belongs to the right shipment. |
| Item code and description | Export the source identifier and a mapped customer code when needed. | Review merged descriptions and item codes that contain leading zeros. |
| Quantity and package count | Use separate columns and retain the meaning of each count. | Check whether the source means pieces, cartons, pallets, or another unit. |
| Net weight and gross weight | Keep separate fields with the source unit represented in the mapping. | Confirm the units and whether the value applies to one row or the document. |
A useful first-document review
- Confirm the row grouping before exporting; one package can contain several items.
- Check units such as kilograms versus pounds and pieces versus cartons.
- Compare the output against package and weight totals on the source document.
- Validate a small CSV import for column order and identifier handling in the receiving system.
Agree on the handoff before scaling.
Source quality and layout affect the result. Confirm package counts, weights, units, and cross-document relationships with your team. This workflow does not automatically certify a shipment or reconcile every packing list against a separate invoice.
A prepared sample does not prove accuracy on your documents. Compare a representative set of your supplier layouts before expanding volume.
Discuss your evaluation and import templatePlanning your evaluation
Are line items billed separately?
No. Paid usage is one credit per successfully processed page, including the line items on that page. The pricing calculator can estimate pages from your expected line-item density.
Can I inspect an example before signing up?
Yes. Our synthetic commercial invoice and reviewed Excel sample shows the structure of a prepared result. Use your own document to evaluate extraction quality.