Nanonets is a practical tool to evaluate when supplier packing lists arrive in different PDF or scanned layouts. Its packing-list OCR product describes extracting fields and line items across supplier structures. Docparser is another candidate when you can maintain parsing rules for a known set of layouts. If suppliers already send Excel or CSV files, Power Query may be the more direct route after you map their columns to a shared structure. The right choice depends on the files you receive and the checks needed before the data is used.
For a brand coordinating boxes, inserts, products and printed cards from several suppliers, the goal is a consistent receiving record. It needs to retain the connection between a shipment, its cartons and the items inside them. A clean spreadsheet is useful only when those relationships remain correct.
Which tool fits your supplier documents?
| Incoming documents | Tool to evaluate | What to confirm in a pilot |
|---|---|---|
| Different PDF layouts, scans or document images | Nanonets packing-list OCR | Line-item extraction, carton-to-item relationships, units, review rules and the export your receiving team needs. |
| A recurring set of identifiable supplier layouts | Docparser with Layout Models | Routing to the right rule set, table extraction and maintenance when a supplier changes its layout. |
| Excel or CSV lists with usable cell data | Microsoft Power Query | A transformation for each source structure, followed by a common column schema and consolidation. |
These are starting points based on the vendors’ published documentation, not results from a Pliapack software benchmark. Test current features and commercial terms against your own documents before choosing a platform.
Nanonets: a candidate for varied PDF and scanned packing lists
Nanonets’ packing-list OCR page describes handling supplier layout differences and extracting information such as product codes, quantities, weights and dimensions. It also describes validation and exception review. That makes it a relevant shortlist candidate when copying tables from changing documents is the main bottleneck.
Ask the vendor to demonstrate your required output rather than just a successful document reading. Include a scan, a multipage list and a mixed-carton shipment in the trial. Confirm which fields require configuration and whether a reviewer can trace a questionable value to the original page. A vendor capability description does not establish accuracy on your files.
Docparser: a candidate for known, repeatable layouts
Docparser’s multiple-layout documentation explains how Layout Models route documents to matching parsing rules. This approach is worth evaluating when supplier formats are recurring and someone can own those rules. The documentation demonstrates the mechanism using invoices; packing-list table behavior still needs a separate trial with your samples.
Include an unrecognized layout in that trial. Decide how the workflow should flag a new document for setup instead of silently applying an unsuitable rule. Also test a known supplier’s revised layout: recognizing the supplier name alone may not establish that the old extraction rules still fit.
Power Query: use it after spreadsheet fields are aligned
Microsoft’s Power Query documentation states that its Combine Files workflow combines files with the same schema. For different supplier spreadsheets, first create transformations that rename columns, remove title rows, set data types and produce the same output fields. Then append the normalized tables.
For example, map “Item No.” and “Product Code” to a supplier-item field only after confirming their meaning. Keep that source identifier separate from your internal SKU. Preserve codes as text when leading zeros matter. This route can suit predictable spreadsheet inputs, but it is not a promise that the standard folder-combine command understands every supplier’s layout automatically.
Define the receiving record before choosing the software
Keep document-level information separate from carton and item records. A shipment reference belongs to the document; one carton can contain several items, and one item can span several cartons. Flattening those relationships carelessly can duplicate quantities or weights. Your shared structure should cover the following fields where they are present and relevant:
| Field group | Useful fields | Control to retain |
|---|---|---|
| Document identity | Supplier, packing-list number, date, revision, PO and shipment reference | Original filename and page reference; current versus superseded status. |
| Cartons | Carton identifier or range, carton count, dimensions and units | Whether a value applies to one carton, a range or the entire shipment. |
| Items | Supplier item code, internal SKU mapping, description, quantity and unit | Whether quantity means pieces, sets, inner packs or cartons. |
| Weights | Net weight, gross weight and weight unit | Whether the weight belongs to an item, carton or shipment. |
| Review | Missing-field flag, discrepancy reason, reviewer and disposition | Which records are approved for export and which remain unresolved. |
Do not fill an absent weight or dimension with zero simply to satisfy a spreadsheet column. Keep the source value, the normalized value and any confirmed conversion distinguishable. An ambiguous unit needs clarification from the supplier.
A carton-range example that exposes weak extraction
Illustrative example: Supplier A writes “CTN 1–10 / 24 pcs per carton.” Supplier B reports “Total quantity: 240 pcs.” Both can represent 240 pieces, but they do not contain the same carton detail. The first gives a range and a per-carton quantity; the second gives only an item total. Your normalized output should preserve that difference.
Now add a carton containing two SKUs. If the carton’s gross weight is repeated beside both item rows, summing the flattened rows would count that carton weight twice. Test whether the tool preserves carton identifiers and separates carton totals from item quantities. Do not infer carton allocations when the source supplies only a shipment total.
Run a pilot around difficult cases, not just neat samples
Select examples from each supplier and include the situations that cause your team work today: merged spreadsheet cells, repeated page headers, split tables, mixed cartons, faint scans, changed layouts and revised lists. Create a checked reference output before the trial so the results can be compared field by field. Use synthetic or appropriately redacted files for initial testing where possible.
Measure correct quantities and units, correctly associated carton and item rows, missing records, and the time needed to review exceptions. Set your own acceptance criteria for critical fields before the trial. A high overall text-reading score can hide an incorrect unit or a missing continuation row.
Check the output in the receiving team’s actual spreadsheet or system. Confirm how files are retained, who can access them, what data is sent to the service and how corrections are recorded. A workflow that still needs extensive manual table repair may not be the right fit even if its OCR reads the page well.
Connect the extracted list to packaging and pack-out
The packing list describes what the supplier declares has shipped. Keep that declaration distinct from the physical receiving count and from the approved component list. Reconcile shortages, substitutions and version mismatches before using the data to authorize assembly. The product supplier to packaging partner handoff checklist helps define the references and responsibilities at that point.
For a gift set or PR kit, connect each approved received SKU to the current bill of materials and pack-out instructions. The number of complete sets available can be limited by a missing card or insert even when the main products have arrived. Review kitting and pack-out scope when separate components need to meet for assembly.
Pliapack’s role is packaging project coordination within the agreed scope; the tools above are independent software options. Contact Us with your component list, supplying parties and intended handoff condition to discuss the packaging and pack-out requirements.
Illustration: AI-generated concept showing different document layouts becoming a shared table. It is not a software screenshot, customer shipment or evidence of extraction performance.
