Overview
Maximum SKU Count lets you cap how many distinct SKUs a single location can hold. Paired with two new putaway algorithm options — a Check Max SKU Count action and a SKU Count in Location Order By — Logiwa IO can automatically keep locations from becoming a mix of too many different products, or deliberately route inventory toward less-crowded locations.
When to Use It
Use this feature when:
You want to prevent a location from accumulating too many different SKUs (e.g., to keep pick faces organized or simplify cycle counts)
You want putaway to favor locations with fewer (or more) existing SKU types
You're already using Only 1 SKU Per Location and want a more flexible cap than exactly one SKU
Prerequisites
Before configuring this feature, ensure:
You have Warehouse Admin access to Location Setup and Algorithm configuration
You have a putaway algorithm rule already configured, if you plan to enforce the limit during putaway (setting the field alone does not change putaway behavior)
Step-by-Step Instructions
Part 1 — Set the limit on a location
Navigate to Location Setup → open the location you want to configure (or create a new one).
On the Information tab, find the Maximum SKU Quantity field
Enter a whole number ≥ 1 to set a cap, or leave the field blank for no limit.
Click Save.
If Only 1 SKU Per Location is enabled for this location, Maximum SKU Quantity cannot be set higher than 1.
Confirm: reopening the location shows your saved value in Maximum SKU Quantity.
You can also set or retrieve this value in bulk via the Location Excel import/export template ("Maximum SKU Count" column) or the Open API (maximumSkuCount field on the Location endpoints).
Part 2 — Enforce or use the count in your putaway algorithm
Navigate to Algorithms → Putaway Algorithm.
Open the rule you want to apply this to, or create a new one.
To block locations that are already at their SKU cap: under Action, click + and select Check Max SKU Count.
To rank candidate locations by how many SKUs they already hold: under Order By, optionally add SKU Count in Location and choose Ascending (fewer SKUs first) or Descending (more SKUs first).
Click Save Rule.
Confirm: the rule now lists your selected action and/or Order By.
Key Fields & Options
Field / Option | Description | Notes |
Maximum SKU Quantity (Location Setup) | Caps the number of distinct SKUs allowed at this location | Blank or |
Only 1 SKU Per Location | Existing toggle that limits a location to exactly one SKU | If ON, effective limit is always 1, regardless of Maximum SKU Quantity; the two settings can't conflict — setting Maximum SKU Quantity above 1 while this is ON is blocked |
Check Max SKU Count (Putaway Action) | Excludes a candidate location if adding the incoming SKU would push it over its limit | Only filters locations — doesn't stop manual scans into an over-limit location |
SKU Count in Location (Putaway Order By) | Sorts candidate locations by current unique SKU count |
|
Example — Check Max SKU Count blocks a new SKU, but allows a top-up
Location A has Maximum SKU Quantity = 3 and currently holds SKU-1, SKU-2, and SKU-3 (3 distinct SKUs).
A new inventory of SKU-4 arrives for putaway → Location A is at its cap and SKU-4 isn't already there, so Location A is excluded from the suggestion list. The algorithm looks elsewhere.
A new inventory of SKU-2 arrives instead → Location A remains eligible, because SKU-2 is already stored there. Adding more of an existing SKU never increases the unique count, so this is a "top-up" and isn't blocked.
If Location A only held 2 distinct SKUs instead of 3, a new SKU-4 pallet would be allowed — bringing the count to exactly 3, which is at the limit but not over it.
Common Questions & Edge Cases
Does the limit block me from adding more of a SKU that's already in the location?
No. Adding quantity of a SKU the location already holds never counts against the limit — only bringing in a new SKU does. A location at its cap remains eligible for "top-up" of existing SKUs.
What happens if I set Maximum SKU Quantity but don't add the Check Max SKU Count action to my algorithm?
Nothing is enforced. The field is just stored data until an algorithm rule with Check Max SKU Count reads it.
What if all candidate locations are at their limit?
The action returns no eligible locations, and the algorithm falls through to the next rule or returns the standard "no suitable location found" result — the operator can still scan a location manually.
How does this interact with Only 1 SKU Per Location?
They can't disagree: if Only 1 SKU Per Location is ON, the effective cap is always 1, and the system blocks any attempt to set Maximum SKU Quantity above 1 while it's enabled.
Does this affect existing locations created before this feature?
No — existing locations default to no limit and behave exactly as before until you set a value.