Overview
The Maximum SKU Quantity field on a location caps how many different SKUs (distinct products) it can hold. Two putaway algorithm options work with it:
Check Max SKU Count (action): leaves out locations where the incoming stock would push the number of distinct SKUs over the limit.
SKU Count in Location (order by): ranks candidate locations by how many distinct SKUs they hold now.
⚠️ The field does nothing on its own. It's only read by rules that include Check Max SKU Count.
In Excel templates and the Open API, the same field is called Maximum SKU Count (maximumSkuCount).
When to use it
Keep pick faces tidy: no more than three SKUs per shelf bin.
Make cycle counts faster by limiting product mixing.
Steer putaway toward less mixed (or more consolidated) locations.
Prerequisites
You can edit Locations and Algorithms.
Step 1: Set the limit on a location
Go to Settings > Master Data > Locations and open the location (or create one).
On the Information tab, find Maximum SKU Quantity.
Enter a whole number, for example 3. Leave it blank (or 0) for no limit.
Click Save.
Negative and decimal values aren't accepted.
In bulk: use the location Excel import/update template (Maximum SKU Count column; a blank cell means no limit) or the Open API (maximumSkuCount). The location export includes the column.
Step 2: Use it in your putaway algorithm
Go to Automation > Algorithms and open the algorithm and rule.
Under Action, click + and add Check Max SKU Count.
Optionally, under Order By, add SKU Count in Location with Ascending (fewest SKUs first) or Descending (most SKUs first).
Click Save Rule.
Example algorithm:
Rule 1 — Actions: Suggest a location with the selected location zone = Pick Shelving, Suggest a location that has the same SKU, Check Max SKU Count. Order by: Walking Path Priority.
Rule 2 — Actions: Suggest a location with the selected location zone = Pick Shelving, Check Max SKU Count. Order by: SKU Count in Location, ascending.
Rule 3 — Actions: Suggest a location with the selected location zone = Pick Shelving, Suggest an empty location. Order by: Walking Path Priority.
Rule 1 tops up a bin that already has the SKU. Rule 2 adds the SKU to the least mixed occupied bin that still has room for another SKU. Rule 3 opens an empty bin. Rule 2 has no Suggest an empty location, so it only looks at bins that already hold stock.
Options
Option | What it does | Notes |
Maximum SKU Quantity (location) | Most distinct SKUs allowed in the location | Blank or 0 = no limit |
Check Max SKU Count (action) | Leaves out a location if the incoming stock would push it over its limit | Filters suggestions only; doesn't block manual scans |
SKU Count in Location (order by) | Sorts candidates by their current distinct SKU count | Empty locations count as 0. Ties go to the next order by |
How the check works
A location stays a candidate if any of these is true:
It has no limit (blank or 0).
Every SKU coming in is already in the location. Topping up never increases the count.
Current distinct SKUs + new distinct SKUs coming in ≤ the limit.
Otherwise it's left out. When every candidate is left out, the rule finds nothing and the next rule is tried. If no rule finds a location, there's no suggestion, and the operator can scan a location unless Force Suggested Location is on.
💡 If the location's only-one-SKU setting is on, it holds a single SKU whatever its Maximum SKU Quantity or the algorithm's actions. Neither can override it.
Examples
Single SKU coming in. Location A has Maximum SKU Quantity 3 and holds SKU-1, SKU-2 and SKU-3.
Incoming | Result |
SKU-4 | Excluded: it would be the 4th SKU |
SKU-2 | Stays: SKU-2 is already there (top-up) |
If Location A held only SKU-1 and SKU-2, SKU-4 would be allowed: the count would be exactly 3, at the limit but not over it.
Mixed-SKU LP coming in. PutawayLoc-1 has Maximum SKU Quantity 3 and holds SKU-1. An LP arrives holding SKU-2, SKU-3 and SKU-4. 1 + 3 = 4, over the limit, so PutawayLoc-1 is excluded. If the LP held SKU-1 and SKU-2, the count would be 2 and the location stays.
Empty location. An empty bin with Maximum SKU Quantity 1 stays a candidate for any single SKU: the count goes from 0 to 1.
Ranking. With SKU Count in Location (Ascending), Location B (1 SKU) is suggested before Location C (3 SKUs). With Descending, C comes first.
Common questions
Does the limit stop me adding more of a SKU that's already in the location? No. Only a new SKU counts against the limit.
What if I set Maximum SKU Quantity but don't add Check Max SKU Count? Nothing is enforced. The field is only read by that action.
What happens if all candidate locations are at their limit? The rule finds no location and the next rule is tried. If none finds one, no location is suggested, and the operator can scan any location unless Force Suggested Location is on.
Are existing locations affected? No. Existing locations have no limit until you set one.