Packing List Parsing for Receiving Teams
For Warehouse receiving coordinators
Prepare shipment, SKU, quantities and package counts from a packing list with fields you can edit. Received quantity confirmation external.
25 free credits/month · No card needed
See the workflow and review checksInspect a document example.
Synthetic documents · Expected output- shipment reference
- DEMO-SHIPMENT-0042
- supplier name
- Example Supply Company - synthetic
- consignee name
- Example Consignee - synthetic
- packing date
- 2026-09-30
- package count
- 1
- packing rows
- [ { "item_reference": "DEMO-ITEM-0042", "description": "Example document line - original synthetic data", "quantity": 1, "unit_of_measure": "each", "package_count": 1, "lot_reference": "DEMO-LOT-0042" } ]
{
"shipment_reference": "DEMO-SHIPMENT-0042",
"supplier_name": "Example Supply Company - synthetic",
"consignee_name": "Example Consignee - synthetic",
"packing_date": "2026-09-30",
"package_count": 1,
"packing_rows": [
{
"item_reference": "DEMO-ITEM-0042",
"description": "Example document line - original synthetic data",
"quantity": 1,
"unit_of_measure": "each",
"package_count": 1,
"lot_reference": "DEMO-LOT-0042"
}
]
}A complete synthetic document with the visible values shown below. Real responses also include model-reported confidence, validation and result status. Test your own file with this schema.
When this work lands on your desk
A packing list arrives for warehouse receiving coordinators. The next step needs shipment, SKU, quantities and package counts, recorded under the correct document reference before the information enters your shipment or billing review system.
A list distinguishes cartons from the number of units inside them. Preserve the unit of measure and package count before receiving confirmation. This schema keeps the source labels and values explicit so the reviewer can resolve the issue before downstream use.
Start with the documents you already collect
- Packing list PDFs
- Scanned or photographed packing list pages
PDF, JPEG, PNG, TIFF, or WEBP. Send one file per extraction call; create separate schemas when the document types need different fields.
Define the fields
Open the starter schema. Edit field descriptions, mark the values your process requires, and save it in your account.
Extract at intake
Send the document and saved schema slug to
POST /api/v1/extract, or collect the file through a branded upload site.Hand off reviewed data
After checking shipment reference, supplier name, consignee name, your application maps the reviewed record into your shipment or billing review system. Keep the original document reference with the result. Received quantity confirmation external. Dokyumi processes one file with a saved schema; your application owns record matching, business rules and updates to other systems.
A schema shaped around the next step.
Start with these fields, then adjust them to match your documents and destination system. The example above shows the data object you are asking Dokyumi to extract.
Download editable starter schemaChoose required fields for your process. The starter schema preserves any defined nested fields; refine line-item structures and test them on representative files.
| Field | Type | What to capture |
|---|---|---|
shipment_reference | string | Shipment reference exactly as printed in this packing list. Preserve identifiers and qualifiers; do not look up or infer missing information. |
supplier_name | string | Supplier name exactly as printed in this packing list. Preserve identifiers and qualifiers; do not look up or infer missing information. |
consignee_name | string | Consignee name exactly as printed in this packing list. Preserve identifiers and qualifiers; do not look up or infer missing information. |
packing_date | date | Packing date explicitly printed in this packing list. Keep it distinct from other dates; leave it empty if no calendar date is stated. |
package_count | number | Package count as reported in this packing list. Preserve the labeled measure and its unit; do not estimate it. |
packing_rows | array | Every visible packing rows row in this packing list. Preserve separate rows, labels and qualifiers; do not merge entries or reconstruct missing ones. |
Give exceptions a clear path to review.
Dokyumi returns a model-reported confidence map, validation details, and a completed or review status for produced results. Check required fields and your business rules before passing data onward.
A completed extraction describes the extraction result. Your application and reviewers own matching, approvals, routing, and updates to other systems.
Read the response contractChecks for this process
- A list distinguishes cartons from the number of units inside them. Preserve the unit of measure and package count before receiving confirmation.
- Check packing date against their own printed labels; leave an unstated date empty instead of deriving it.
- Compare every packing rows row with the source, including continuation pages, separate categories and repeated table headings.
Prove the fit on a representative batch.
Test packing list examples from the layouts your team actually receives. Include the exception described here: A list distinguishes cartons from the number of units inside them. Preserve the unit of measure and package count before receiving confirmation. Compare the extracted shipment reference, supplier name, consignee name and any line rows with a reviewer's checked reference before enabling downstream actions.
Compare extracted values with a reviewer’s reference set. Record corrections, unresolved fields, review time, and credits used before connecting downstream actions.
The free plan’s credit limits apply. Assisted pilots are scoped with Dokyumi before work begins.
Expand when the next process is ready
Add recurring extraction capacity when packing list intake becomes routine. Reuse this field contract for layouts that express the same information; create a separate schema when the next document has different fields or review requirements.
For a tailored implementation
Discuss document volume, page lengths and schema setup for warehouse receiving coordinators. Bring difficult packing list samples and the review requirements your implementation must preserve.
Talk through document mix and volumeStart small. Add capacity as intake grows.
All self-service plans include the REST API, upload-site webhooks, custom confidence thresholds, and schema inference. Choose by volume, schema count, and upload sites.
Each document uses one credit per 5 pages, rounded up. An 8-page file uses 2 credits. Self-service files can be up to 50 pages; larger files, custom-built schemas, and additional volume are quoted through Enterprise. Full pricing details
Questions about packing list receiving preparation
Which fields can I capture from a packing list?
The starter schema contains shipment reference, supplier name, consignee name, packing date, package count, packing rows. Edit those definitions and choose your required fields before saving. Array fields include defined sub-fields so row values have a validation structure.
What needs review in packing list receiving preparation?
A list distinguishes cartons from the number of units inside them. Preserve the unit of measure and package count before receiving confirmation. Check the original source alongside model-reported confidence and validation output; completion status describes the extraction result, not the business decision.
How does this data reach your shipment or billing review system?
Save the schema, then send one supported PDF or image to POST /api/v1/extract with its slug. The response contains the data, model-reported confidence, validation and result status. Your application maps reviewed values to the destination; upload-site submissions can use a configured webhook. Received quantity confirmation external.
How do I test this workflow on my own documents?
Start free with 25 credits per month, 2 schemas, and 1 branded upload site. The starter schema opens in the schema builder after sign-up. Edit the fields, save it, and upload a representative file through your account or the extraction API. Account documents are stored according to Dokyumi’s privacy policy; contact hello@dokyumi.com for deletion requests and retention requirements.