How to design a warehouse order picking and packing workflow

Direct answer

A picking and packing workflow is the chain of decisions and records between an order being released and a parcel or pallet being handed over for dispatch. The most important decision comes first and is not a software one: which pick method fits the shape of your orders. Only once that is settled can a system be configured to support it.

This page explains the choices and the records. It makes no claim about carrier label or rate integration, route optimisation or throughput; those are separate scoping topics and depend on your carriers and operation. For how the scanning itself is done, see warehouse barcode scanning workflow.

Order release and priorities

Orders do not go straight to the floor. Something has to decide when an order is released for picking, and in which order. Write that down as rules a supervisor could explain.

A common failure is releasing everything at once. The floor then decides priorities informally, and urgent orders are picked late. Release in the sequence you want them worked.

• An order is released only when its stock is available and allocated, so pickers are not sent for stock that is not there
• Priorities are explicit, for example a cut-off for same-day dispatch or a service level agreed with a client, and are visible on the pick task
• Orders on hold, for example awaiting payment or address confirmation, are not released until cleared
• Someone with the right role can change a priority, and the change is recorded

Pick methods as a decision

There are a handful of pick methods, and each suits a different order profile. The choice is a fit question, and this description makes no algorithmic claim.

Methods can be combined. The question to answer is what your orders look like: how many lines, how much overlap, how spread out the stock is. Choose from that, run it in practice and change it if the reality is different.

• Discrete picking: one picker collects one order at a time. Simple to run and to verify, and a good fit for larger or more varied orders
• Batch picking: one picker collects the same items for several orders in one trip and the orders are separated afterwards. Suited to many small orders with overlapping items, but it adds a sorting step that needs its own control
• Wave picking: orders are grouped and released in defined waves, for example by cut-off time or carrier, so work arrives in planned groups
• Zone picking: the warehouse is split into zones and each picker works one zone, with orders passed on or consolidated afterwards. Suits a large layout, at the cost of a consolidation point

The pick path as a convention

The order in which a picker visits locations is a convention worth defining, because it affects both efficiency and errors. The simplest form is a walk order: locations are numbered so that visiting them in ascending order gives a sensible route through the warehouse, and pick tasks are sorted that way.

That depends on your location naming and layout being consistent, which is why it connects to warehouse putaway and location rules. We are describing a sort order on location codes that people agree on, not a route optimiser.

Short picks and substitutions

Sometimes the stock is not there, or not in the quantity the system showed. A short pick is a normal event that needs a defined path, not a picker's private decision.

The count trigger links to the routine in warehouse cycle count process, and unresolved differences follow the discrepancy path.

• The picker records the actual quantity found and the reason, from a short picklist
• Where scoped, the location can be queued for a count, because the record and reality disagreed
• The order is handled according to a rule: ship what is available and backorder the rest, hold the whole order, or offer a substitution for approval
• Substitutions are never automatic. Someone with the authority, and where relevant the client, approves them, and the substituted item is recorded on the order

Packing verification

Packing is the last chance to catch a picking error before the goods leave. The two common controls are scan-to-pack and a packing-slip check. In scan-to-pack, each item is scanned into the parcel and where scoped, the setup compares it with the order and flags an item that does not belong or a quantity that is too high or too low. In a packing-slip check, a person compares the contents with the slip. The first is stronger and leaves a record; the second is a fallback where scanning is not possible.

Decide what the record contains: who packed, when, and what was verified. Also decide what happens on a mismatch: the parcel is opened, the discrepancy is recorded and the picking step is reviewed. Packaging material and box choice can be recorded if you need them, but only if you will use the data.

Dispatch handoff

Packed orders move to a staging area and then to the carrier or the collection point. Two records matter here. The first is staging: which orders are in which staging location, so a parcel is not lost between the pack bench and the dock. The second is the carrier collection record: who collected, when, and what was handed over, ideally confirmed by a signature or a scan of the parcels.

How labels are produced and how carriers are booked depends on the carriers you use and is scoped per project. We do not assume a rate or label connection. Whatever the mechanism, the record of what left the building should exist in the system.

What to record for later disputes

Disputes arrive weeks later: a client says a parcel was short, a wrong item arrived or something was damaged. What you can prove depends on what you recorded at the time. The useful minimum is the picker and time for each line, any short pick and its reason, the packer and the verification result, the staging record and the collection record.

Keep the records linked to the order, not scattered across separate lists. If you want to check how far your current process is from this, the WMS readiness assessment is a free start. When you reach testing, WMS acceptance testing checklist covers how to prove the workflow before go-live, and warehouse management system describes what a scoped build covers.