WMS Slotting for Omnichannel Fulfillment

Omnichannel operations pick the same SKU for a single-unit web order, a full-case store replenishment order, and sometimes a buy-online-pickup-in-store request, all from the same physical stock. Slotting a facility to serve every one of these patterns well, rather than favoring one channel at the expense of the others, is a distinct design problem from single-channel slotting.

Each-picking for e-commerce favors small, easily reachable forward locations optimized for single-item retrieval speed. Case-picking for store replenishment favors larger, forklift-accessible locations optimized for full-case handling. Slotting a SKU for one pattern often makes it worse for the other, so an omnichannel facility frequently needs to hold the same SKU in two different location types simultaneously, an each-pick face and a case-pick reserve location, rather than choosing one.

Since the each-pick face draws from the case reserve, replenishment logic needs to trigger transfers between the two location types frequently enough that e-commerce picking never stalls waiting for a case to be broken down, while also not over-replenishing so aggressively that reserve stock disappears before a large wholesale order needs it. This two-way tension is unique to omnichannel slotting and doesn't exist in a single-channel operation.

When available stock is tight, the WMS needs explicit rules for which channel gets priority: does a same-day e-commerce order outrank a scheduled wholesale shipment, or does a large contracted retail customer take precedence over web orders? This is fundamentally a business policy decision that the slotting and allocation engine needs to encode and enforce consistently, rather than leaving it to whichever order happens to process first.

Beyond location type, many omnichannel facilities physically zone the building by fulfillment method, dedicated each-pick zones staffed and equipped for e-commerce order profiles, separate from bulk zones equipped for pallet and case movement. This reduces picker path conflicts between someone doing rapid single-item picks and a forklift moving full pallets through the same aisle.

• Slotting review needs to account for channel mix shifts over time, since a SKU's e-commerce-to-wholesale demand ratio can change with marketing campaigns or seasonal buying patterns
• Cycle counting frequency may need to be higher for SKUs held in multiple location types, since discrepancies are easier to introduce when the same item exists in two places
• Buy-online-pickup-in-store adds a third consumption pattern that draws from store-level stock rather than DC stock, and needs its own allocation logic layered on top of DC-level omnichannel slotting