The driver waits while someone types the packing list

The question this file answersDo we really need a person keying SKUs and counts from a packing list while the driver waits?

Fits: logistics operators handling 100–500+ orders a day, where documents still arrive by email.

Typical day

What the desk looks like today

Pattern, not measurement — the logistics playbook publishes no packing-list count, and we will not guess one. Packing lists arrive as PDFs, and as phone photos the driver hands over. A receiving clerk types SKUs and quantities into the WMS while unloading has already started, so put-away waits on the typing.

Typical, from the industry playbook — not a client's day.

What changes

What Monday looks like after

When the driver hands over the papers, the clerk photographs them and moves on; by the time the first pallet is off, the lines are in the WMS and the receiving lead has a short list of the ones that do not add up. The retyping stops; the walk to the pallet to count it does not.

Typical, not a measured client result. Every figure here comes from the playbook source named below.

Lines

packing-list lines in the WMS before put-away — same build as our email-order intake file; no published figure for packing lists

Before: a clerk types SKUs and counts into the WMS while the truck waits on the yard. After: matching lines are in the WMS before put-away and the count breaks go to the receiving lead. No percentage here; the intake range belongs to the parent file.

No published figure for this desk. The range lives on the parent file: Email orders into the TMS you already have →

How this file is built

No published benchmark covers packing-list intake on its own. The McKinsey (2023) and Deloitte (2022) 40–60% range is about customer order intake and is quoted on the parent file; the receiving dock does not inherit it. Not a dock-turnaround claim.

What we install

What we put in front of the systems you already run

Your WMS stays, and the TMS it talks to — CargoWise, SAP, Dynamics or whatever you run. Our email-order intake build, turned towards inbound paper:

packing lists are read from the mailbox or from the photo taken at the door
lines are checked against the booking or purchase order already in your system
matching inbounds go into the WMS through the WMS API or through your usual import file, and any count that does not agree goes to the receiving lead before put-away, with both figures shown.

What stays human — and what this will not do

Unknown SKUs. Mixed pallets. Damage at the door. The conversation with the driver.

Not a dock-turnaround claim.

What can go wrong — and what we do about it

A photographed list at an angle in bad light reads badly — those go to a person as they do now, and a well-lit photo station at the door is the cheapest fix. Without a WMS API, lines go in through an import file, which needs your IT and is slower than it sounds.

What it costs to get there

The path: free 60-second estimate → free 20-minute review → paid audit of this one process (€1.5–3K, typically two weeks) → pilot with your people in the loop (€10–20K, weeks, not quarters). No transformation programme. Prices are public, on the services page →

Scoped in the audit — the playbook has no estimate for this exact desk.

This is about you if…

Do packing lists still reach the WMS through someone’s keyboard?
Is there a booking or PO in the system that each list can be checked against?

What does this mean in euros?

That depends on your volumes and wage costs — this page will not invent the number. The free 60-second estimate runs that calculation from your answers, with every multiplier sourced.

Get your free savings estimate 60 seconds · no sales call Or write first → Map a logistics process like this one — free, 60 seconds →

Not a named Aperanda client. Process file · Logistics.

Short process file. Same build as its parent file; the playbook has no separate volume or benchmark for this desk.

All process files