Skip to content
  • There are no suggestions because the search field is empty.

Identify Location Behavior Type Rules for Allocation, Replenishment, and Pick Faces

Identify, compare, and apply location behavior type rules across allocation, replenishment, and pick face assignments.

Is This What I'm Looking For

Use this article when you need to know whether a location's behavior type will let it allocate, receive a replenishment, or serve as a pick face. Get it wrong and you can end up with a pick face that can never allocate, or a replenishment that never gets created, because behavior type governs allocation but not replenishment. This article does not cover how to sequence replenishment against fulfillment. See Best Practice: Sequence Replenishment Releases for that.

 

Eligibility by Behavior Type

Behavior Type Order Allocation Replenish FROM Replenish TO (Pick Face)
Forward Each Eaches only  No Yes, typical pick face
Forward Case Cases only No Yes, typical pic face
Standard Eaches, cases, pallets Yes  Yes
Case Cases only  Yes (pulls partial quantities if the amount needed doesn't match a full case) Yes
Pallet Pallets only Yes (pulls partial quantities if the amount needed doesn't match a full case) Yes
Non-Pickable

Never. Recommended for QC and Damaged locations.

 No. Inventory here isn't allocatable, so it can't fund a replenishment.  Technically accepted, but nothing can be picked from the face you just filled.
LPN

Never. A temporary “license plate” location, not a storage location.

No

Not a destination you'd choose. The system creates LPN locations automatically during a replenishment pick, as a temporary holder before put-away
Holding

Never. Inventory is On Hand but Unavailable, and invisible to fulfillment processes.

No. Unavailable inventory can't fund a replenishment.

Technically accepted since mixing rules are ignored, but inventory placed there can't be picked back out

Location Behavior Type Allocation Considerations

A location's Behavior Type controls which units of measure can be picked there and whether its inventory is eligible for allocation. Six considerations apply when planning your allocation scheme:

  • Forward Each and Standard locations allow picking of all UOM types.
  • Forward Case, Case, and Pallet locations require Units per Case and Units per Pallet to be populated on item receipts.
  • Non-pickable behavior types, such as Non-Pickable, LPN, and Holding, can serve as safeguards for items you do not want to allocate.
  • Holding is an ideal behavior type for receiving because it ignores all item and lot mixing rules. Items in a location with the Holding behavior type do not report as orderable quantity.
  • For a Standard location behavior type allocation scheme, set your picking locations to Forward Each and any storage, replenishment, or secondary picking locations to Standard.
  • For the simplest configuration set all locations to the Standard location behavior type.

 

Why There's No “Replenishment-Only” Behavior Type

Replenishment has never had a behavior-type restriction. Pick Face Assignments are designed to accept any location type. The system doesn't check whether a location is a Forward Each, Forward Case, or anything else before allowing it to receive replenished stock.

That's why Non-Pickable, LPN, and Holding all show “Yes” under Replenish TO in the table above, even though none of them can fund allocation. The accurate way to think about it: replenishment doesn't care about behavior type. Allocation does.

 

Why a Behavior Type Won't Stop Allocation and Replenishment From Competing

It's tempting to use behavior type to keep replenishment and order fulfillment from competing over the same inventory. For example, setting a pick face to a non-allocatable type so it can't be picked while it's being refilled. This doesn't work in either direction:

  • Set the pick face to Holding, Non-Pickable, or LPN: stock arrives, but it can never be picked. You've replenished a face no picker will ever be sent to.
  • Set the reserve location to Holding: the replenishment is never created in the first place, since a replenishment only generates when there's allocatable inventory for the SKU elsewhere, and Holding inventory is Unavailable.

Neither direction gives you a working “replenish yes, allocate no” state, because behavior type applies to the location, not to the process. The actual fix is sequencing when replenishment and fulfillment run.

Next Steps