How to design a warehouse receiving process that keeps stock accurate

Direct answer

Receiving decides stock accuracy because every later error, in picking, counts and shipping, inherits whatever was recorded at the dock. A sound receiving process has five parts: know what is arriving and when, match what arrives against what was expected, decide what is acceptable, quarantine what is not, and release stock to putaway only when it is identified and correctly recorded.

This page is about the design of inbound: appointments, matching, holds and exceptions. It does not cover scanning mechanics, which have their own page at warehouse barcode scanning workflow. It states no accuracy figures, and the details of any system depend on the implementation. LATYNEX's WMS engagements are implementation-led, with capabilities agreed per project.

Appointments: control what arrives when

Receiving without appointments means the dock is busy when nobody expected it to be and empty when staff are waiting. Appointments do not need to be elaborate. A time window per inbound, tied to the purchase order or shipment reference, is enough to plan labour and dock space.

• Capture the reference, supplier or client, expected units or pallets and any special handling before the truck arrives
• Give each slot a dock or area and an owner on the day
• Decide what happens to a vehicle that arrives outside its window: wait, be squeezed in, or be rebooked, by a rule your team knows
• In a multi-client operation, record which client's stock it is at the appointment, not at the dock door

ASN matching

An advance shipping notice tells you what the sender says is coming. Whether it arrives as a file, a form or a message, treat it as the expected side of a comparison. Receiving is the act of reconciling expected against actual, not the act of typing in whatever is on the pallet.

Decide the matching level in advance: by pallet, by carton or by unit. Decide tolerance rules for over and short deliveries per client or supplier, written down and approved by whoever owns the stock. Where no ASN exists, receive against the purchase order or create the expected record before unloading, so there is still something to reconcile against. Electronic ASN exchange with a sender's system is a per-project integration where an API or file format exists; it is not assumed.

Inspection: decide what you check and why

Inspecting everything is slow; inspecting nothing is how damage becomes your problem. Define levels. A common approach is a basic check on every delivery, external packaging condition, count against the ASN and label readability, and a deeper check triggered by rules such as a new supplier, a high-value item, a product with a quality history or a client's instruction.

• Record damage at the dock, with photos attached to the receipt, before the carrier leaves where that matters for claims
• Check identity: right product, right variant, right batch or expiry where those are tracked
• Record who inspected and when, so disputes can be traced
• Keep client-specific inspection instructions in the client record, not in someone's memory

Holds: a place for what is not yet stock

Holds are the most useful and most neglected part of a receiving design. A hold is a status that keeps goods from being picked or moved to normal locations until a question is answered. Without it, doubtful stock either blocks the dock or quietly enters saleable inventory.

Define hold reasons and a physical or logical hold area: quantity mismatch, damage, missing identification, quality check pending, awaiting client instruction. Each hold has an owner and a time limit for a decision, otherwise the hold area becomes storage nobody manages. When a hold is released, record the outcome: accepted, accepted with adjustment, returned to sender, or scrapped, with the authority of whoever decided.

Labelling and putaway readiness

Stock should be putaway-ready only when it has three things: a confirmed identity, a confirmed quantity and a label that lets the next person find and move it. Decide who applies labels, at what level (pallet, carton, unit) and where in the flow, before putaway, not after stock is already on the shelf. Then define what putaway-ready means as a status. Only stock in that status appears in the putaway task list.

How locations are assigned, by fixed rule, by directed suggestion or by operator choice, is a design decision to make with your layout and volumes. Keep the receipt record complete so putaway can trace back to it. See warehouse inventory discrepancy workflow for what happens when counts later disagree with the record.

Exceptions

Write the standard answers to the common exceptions so the shift does not improvise: no ASN, unknown product, over-delivery, short delivery, damaged goods, mixed pallets, wrong client. For each, say who is notified, what is recorded, whether the goods move to a hold and how the sender or client is told. The aim is that the same problem gets the same treatment on every shift.

Reporting

Useful inbound reports are modest: receipts by status, open holds by age and reason, mismatches by supplier or client, dock time per appointment, and receipts waiting to be released to putaway. They point at patterns, such as one supplier who repeatedly ships short, that can be fixed upstream. Measure against your own baseline; this page publishes no benchmarks.

If you are working out whether your current receiving process needs a system behind it, the WMS readiness assessment is a free way to check, and warehouse management system explains how LATYNEX approaches implementations.