The pumps that can't be received
What the user reports
Monday 21 December, the Rockford distribution center's first day bin by bin. The four ES-200 already in FG01 have to be packed onto pallets and put away. On Friday the putaway rules were loaded from the design workbook in one go.
The error: Receiving ES-200 into RKDC refused: ES-200 has no putaway rule in RKDC.
What you'll do
- See the problem as the warehouse clerk: On Inbound and putaway, receive 4 ES-200 into RKDC.
- Find the cause: The warehouse, its bins and the pumps in FG01 are all there. What does receiving need from a putaway rule before it packs a single pallet?
- Fix it as the supply chain consultant.
- Prove it: run the step that failed again.
The drill runs in the lab on its own prepared copy of the fictional Calder Pumpworks, saved in this browser apart from your company. All codes and values are fictional course labels.
Answer and explanation (open after the drill)
The fix: How many units go on one handling unit and of which type, so it knows how many pallets to make.
Receiving packs stock into handling units, and the rule says how: two ES-200 to a pallet. Without it the lab can't know whether four pumps are two pallets or four, so it refuses before anything is made. The rule's storage type, section and strategy matter one step later, at putaway. ES-200 uses next empty bin, not a fixed bin; the pumps were built in house, so there is no notice; and nothing counts the receiving area first.
Why it broke
A warehouse runs on product-level settings: how a product is packed, where it is stored and how its bin is chosen. They are usually loaded in bulk from a design workbook before go-live, and a row that is missing from the file fails silently until the first goods arrive. The lab refuses at receiving; a real system may refuse there, or receive and leave the pallet without a destination at putaway.
How teams prevent it
Before a load, compare the workbook with the list of products stored in the warehouse's storage location, and after it, run a check for stored products without a rule. A product new to the warehouse gets its rule as part of its master data, not when the first truck arrives.
Across teams
The warehouse clerk finds it with pumps at the door. The rule belongs to the supply chain consultant who designed the warehouse (in a running company, the warehouse's key user). Production and sales feel it next: pumps that can't be put away can't be picked for an order.
Where AI fits
Finding stored products without a rule is plain automation: a comparison of two lists. An assistant can propose the missing rule from similar products (another pump of the same size and weight goes two to a pallet in the fast movers) for the key user to confirm. It should not create rules on its own, because a wrong rule puts pallets in the wrong place for months.
Learn more: Warehouse and transportation execution