STOKA / Warehouse processes

Receiving: why it backs up, and how to clear it

Receiving sets the quality of everything else in the warehouse: a miscounted delivery becomes an inventory discrepancy, and a pallet left on the dock becomes search time later. STOKA puts the unloading schedule, the verification of each delivery and same-day putaway in order.

Tell us your problem

The receiving bottleneck sits between the truck and the destination location

Receiving is the only warehouse process that starts outside the building: the truck arrives when it arrives. These four symptoms almost always appear together, and any one of them is enough to identify the bottleneck in a warehouse of any size.

  • Trucks waiting for a slot on the street

    With no assigned time slot, the dock works first come, first served. Drivers wait, suppliers complain and the whole day of unloading slides.

  • Dock space taken by loads with no location

    Yesterday's pallets are still on the receiving area floor. Maneuvering space shrinks and the new load is stacked on top of the old one.

  • Deliveries recorded the following day

    Goods physically arrive today and appear in the system tomorrow. For those hours, the inventory the operation sees is not the inventory it has.

  • Discrepancies that surface weeks later

    A location count comes up short or long, and nobody can trace it back to a delivery. The claim to the supplier arrives late and without evidence.

What STOKA does in a receiving project

STOKA puts receiving in order so that what comes in is counted, recorded and put away the same day. The work covers the four stages of a delivery: scheduling the unload, unloading, verification against the supplier's document, and putaway. STOKA surveys the actual flow of deliveries, designs the receiving area as a zone with a physical boundary, writes the verification rule by supplier and by product type, and trains the dock team. The record is made in the system your company uses today.

How receiving is put in order, step by step

Five steps, in this order, because each one rests on the one before it: without a schedule, no receiving area is large enough. The timeline is set after the survey.

  1. 01

    Dock appointment schedule

    STOKA builds the delivery calendar with the warehouse manager and with purchasing, who notifies the suppliers. Each slot carries a truck quota, and the day keeps one open window.

  2. 02

    Receiving area marked and labeled

    The boundary of the receiving area is marked on the floor and its positions are labeled: to verify, verified and hold. The owner of the zone is the shift supervisor.

  3. 03

    Written verification rule

    STOKA writes down what gets counted on each delivery — per unit, per pallet or by sampling — depending on the supplier and the product type. The warehouse manager approves it and it stays posted at the dock.

  4. 04

    Recorded on arrival

    The record is made at the dock, at the moment of verification, in the system your company uses today. The receiving operator enters it: nobody transcribes delivery notes at the end of the day.

  5. 05

    Putaway before the shift ends

    Every verified delivery gets its destination location and is put away before the shift it arrived in is over. The supervisor closes the shift by checking that the receiving area is empty.

What a receiving project includes and what it does not

What it includes

  • Survey of the delivery flow, supplier by supplier
  • Design of the receiving area and its positions
  • Verification rule by supplier and by product type
  • Written receiving procedure, with one owner per step
  • Training for the dock team and the shift supervisor
  • A dashboard with the four indicators and how they are calculated

What it does not include

  • Civil works at the dock, dock levelers or doors
  • Supplying forklifts or the barcode scanners used at the dock
  • Commercial negotiation with suppliers or changes to contracts
  • Implementing a new warehouse management system (WMS), the software that records every movement
  • Cycle counting or the warehouse inventory plan

If the dock is physically too small for the volume it takes in — a single door, or a receiving area that does not fit in the building — putting the process in order improves the wait but does not resolve it. That case is handled as layout work: first where the receiving zone goes and how much floor space it gets, then the process that uses it.

Time is not lost during unloading, it is lost afterward

Unloading a truck is fast: forklifts empty the trailer in a fraction of the time it takes to verify what came off and put it away in its location. That is why the dock looks efficient while the receiving area fills up. The gap between those two speeds is what creates the bottleneck, and no improvement in unloading corrects it.

Verification sets the quality of the data that the rest of the warehouse then carries: if counting is done by eye and the delivery note is signed without checking, the discrepancy does not disappear, it is postponed. Putaway is the stage that almost never has an owner: when the shift ends and the load is still in the receiving area, the pallet sits in a place the system does not know about, and the next person who needs it will walk. Those two are the ones STOKA works on first.

What to measure to know whether receiving improved

Four indicators are enough, and all four are calculated from data the warehouse already has. Truck dwell time: dock departure time minus gate arrival time, averaged over the deliveries in the period. Time from unload to putaway: the time the last pallet was recorded in its location minus the time unloading finished, delivery by delivery.

Percentage of deliveries with a discrepancy: the number of deliveries whose verification did not match the supplier's document, divided by the total deliveries in the period. Percentage of deliveries recorded the same day: the number of deliveries entered in the system before the end of the shift they arrived in, divided by the total for the period.

The starting value is measured during the survey and the target is set with you: a reference number taken from someone else's operation does not help anyone decide.

When it makes sense to automate receiving

The bottleneck in receiving is almost always between the dock and putaway: unloading moves faster than the team can verify and store, and the receiving area turns into improvised storage. When that stretch is the limiting one, what gets automated is the movement and the record, not the criteria: conveyors that carry the pallet from the dock to the verification point, barcode reading at arrival, and entry in the system at the same moment the load comes in. The result being sought is not to unload faster, but to have the receiving area empty at the end of the shift.

Frequently asked questions

Is it worth verifying everything that comes in?

Verifying everything, unit by unit, is expensive and slow, and it holds up the dock more than unloading does. The rule is set by supplier and by product type: full verification where the history shows discrepancies, and sampling where the supplier has been delivering consistently.

What do we do about suppliers who show up unannounced?

The time-slot schedule holds up when the rule is written down and communicated by purchasing before it takes effect. A truck without a slot is not turned away: it goes into the open window of the day and is handled after the scheduled ones.

What happens when a load arrives without complete paperwork?

It is received into an identified hold location, kept apart from available inventory, and recorded as held so that no order can take it. It carries a deadline for resolution and an owner who settles it with the supplier. Once the deadline passes, it is returned or released.

Is a barcode scanner worth it in receiving?

It is worth it when the system entry happens hours after arrival, because it closes the gap between what came in and what the system knows at that moment. Without a written verification rule, the scanner only records a wrong figure faster.

How much floor space should the receiving area get?

It is sized on the peak day's volume, not on the monthly average: an area sized on the average overflows on the heaviest days. The peak comes out of the delivery history collected at the start of the project. And the receiving area needs a visible physical boundary.

The other warehouse processes

Back to the six processes

Send us one month of delivery records and we will tell you where receiving jams

With one month of detail — date, supplier, gate arrival time, departure time and the time each delivery was recorded — we will tell you which stage is losing the time. We review your case with your own operating data, and we reply within 24 business hours.