Extend Matching SKU Search to Split Putaway of Multi-SKU IBLPN

In warehouse operations, it is operationally beneficial to store inventories of the same SKU in the same location, provided space is available. When SKU A is scattered across multiple areas or zones, users must travel across locations during picking, counting, or replenishment, even though the items are identical.

Placing similar SKUs together:

• Reduces picker travel time
• Speeds up replenishment and cycle counting
• Improves organization and visibility of stock on the floor

To support this, the system provides Search Location with Matching SKU, which prioritizes putaway to a location where the same SKU already exists.

• Search Location with Matching SKU is already supported for single-SKU IBLPNs.

• For multi-SKU IBLPNs moved as a full LPN, the rule is not applied, as the container must remain intact and undivided.

• In Split Putaway of Multi-SKU IBLPNs, the system previously applied Search Location with Matching SKU only to the first SKU in the LPN. Remaining SKUs were also directed to the same location—even if that location did not contain the same SKU and a better location match was available.

With this enhancement, during Split Putaway of Multi-SKU IBLPNs, if the Putaway Type is configured with “Search Location with Matching SKU” enabled in the Putaway Method Priority screen, the system now evaluates each item in the LPN individually to determine the most suitable putaway location based on SKU match.

Sequence of location determination

For each item during split putaway, the sequence of location determination remains the same as:

• Full LPN putaway logic (with matching SKU enabled), and
• Split Putaway of Single-SKU IBLPN

Example Scenarios

The enhancement is illustrated using the example below.

LPN1 Composition

SKU	Qty	Putaway Type (determined per item)
SKU-1	10	PA1
SKU-2	5	PA2
SKU-3	5	PA3

Eligible Locations (all max capacity = 10 units)

Putaway Type	Locations	Putaway Sequence	Inventory present
PA1	LOC1 / LOC2 / LOC3	001 / 002 / 003	LOC2 has 8 units of SKU-1; LOC3 has 5 units of SKU-1
PA2	LOC4 / LOC5 / LOC6	004 / 005 / 006	LOC5 has 2 units of SKU-2; LOC6 has 2 units of SKU-2
PA3	LOC7 / LOC8	007 / 008	All locations empty

Putaway Method Priority configuration

• Putaway Method = Location Sequence
• Putaway Search Mode = Most Empty by Units
• multi-sku-lpn-mode = Split LPN Into Active Locations

Scenario 1 — When “Search Location with Matching SKU” = Yes

Allocation Seq	SKU	Qty	To Location	Comment
1	SKU-1	5	LOC3	LOC2 & LOC3 contain SKU-1; LOC3 chosen as it is Most Empty by Units
2	SKU-1	2	LOC2	Next preference since LOC2 has SKU-1
3	SKU-1	3	LOC1	Next eligible location
4	SKU-2	5	LOC5	LOC5 & LOC6 both contain SKU-2; LOC5 chosen due to higher Putaway Sequence
5	SKU-3	5	LOC7	LOC7 chosen due to higher Putaway Sequence

Scenario 2 — When “Search Location with Matching SKU” = No

Allocation Seq	SKU	Qty	To Location	Comment
1	SKU-1	10	LOC1	LOC1 is Most Empty by Units
2	SKU-2	5	LOC4	LOC4 is Most Empty by Units
3	SKU-3	5	LOC7	LOC7 chosen due to higher Putaway Sequence

NOTE: 

• There is no change to the logic that determines the Putaway Type during split putaway.

• “Search Location with Matching SKU” is supported only when Putaway Method = Location Sequence.

• It is not supported when Putaway Method = Market Basket Analysis Radial / Radial, because radial logic requires a permanent pivot location and does not align with matching-SKU-based search.

Steps to Enable and Configure

You don't need to do anything to enable this feature.