Overview
When directed putaway shows no location, an unexpected one, or blocks a scan, the cause is almost always in the putaway algorithm, the location set-up or the stock's data. Work through the tables below in order. Each row says what to check, why it matters and what to do.
For how suggestions are made, see How the Putaway Algorithm Chooses a Location.
💡 Before changing anything, test the algorithm (or a single rule) against the same stock to see what it suggests. See Create a Putaway Algorithm.
1. The algorithm and its rules
Check | Why it matters | What to do |
The warehouse has an active putaway algorithm with at least one rule | Without rules, nothing can be suggested | Activate an algorithm and add rules. See Create a Putaway Algorithm |
At least one rule's conditions match the stock | A rule only applies if all its conditions match. If none match, no rule runs | Add a catch-all rule with no conditions at the bottom of the list. Example: Rule 1 only covers Product Group = Frozen; ambient products get nothing until you add Rule 2 with no conditions |
The rule isn't receiving-only | Rules with Is Receiving Process only run from Suggest Putaway Location on the Receiving screen | Remove the condition, or add a similar rule without it |
The rule isn't parent-LP-only | Rules with Parent LP Based Transfer never apply to product putaway | Add a rule for product putaway |
The rule can see the right kind of location | A rule without Suggest an empty location only considers locations that already hold stock; with it, only empty ones. A rule never considers both | Add a second rule for the other kind. Example: the only rule has Suggest a location that has the same SKU, and the SKU isn't stored anywhere yet: nothing is suggested until you add a rule with Suggest an empty location |
Actions in one rule don't contradict each other | All actions in a rule must be met together; they aren't fallbacks | Split "same SKU, otherwise empty" into two rules |
Product Group & Location Zone Match on an LP | The rule is skipped if the LP holds mixed product groups or products without a group | Add a following rule for mixed LPs |
2. Locations that are never suggested
Check | Why it matters | What to do |
Location is locked | Locked locations are always left out | Unlock it if it should be used |
Location is a mobile cart, or assigned to one | Carts are always left out | Use a fixed location |
Location is the one the stock is coming from | The source is always left out | — |
Location is in a packing area | Packing areas are left out unless a rule filters by area type | Add an Area Type filter to the rule if you really want them |
Prevent multi-client / SKU / lot / expiry / production date / LP on the location | A location is left out if this stock would break the flag | Example: B-04 holds lot L-1 and has prevent multi-lot; lot L-2 can't go there. Clear the flag or pick another location |
The operator already tried it with Suggest Another | Already offered locations aren't offered again | Expected. Free space elsewhere or adjust the rule |
3. Capacity and limits
Check | Why it matters | What to do |
Check Location Capacity Type is used | Locations whose Maximum Capacity Quantity (in units or packs, per Location Capacity Type) would be exceeded are left out. Locations with Location Capacity Type = None aren't limited | Raise the limit or choose a location with room. See Max Inventory Capacity for Locations |
Check Max SKU Count is used | A location that already holds its maximum number of different SKUs isn't used for a new SKU | Raise the limit. See Setting a Maximum SKU Count Per Location |
Check Max Locations per SKU is used | A zone where this SKU already occupies its maximum number of locations is left out | Raise the limit or add a rule for the next zone. See Limiting SKU Locations Within a Zone |
💡 Location limits only apply when the rule has the matching action. A location with no limit set isn't limited.
4. Volume-based rules
Check | Why it matters | What to do |
Product (or pack type) has dimensions or Volume | With missing or zero values, the volumetric rule is skipped and the next rule is tried | Fill in the dimensions or Volume. See Volume Based Putaway |
Location, and all stock already in it, has dimensions or Volume | A location that can't be calculated is skipped | Fix the zero values on the location or on the products in it |
Units match | Products, LPs and locations must use the same units; nothing is converted | Align the units |
Fit Entire Putaway Volume vs Fit Single Unit Volume | With Fit Entire, a location must hold everything at once | Use Fit Single Unit Volume for products if a split is acceptable |
Fit Single Unit Volume on LP putaway | With Use LP Dimensions for Volumetric Putaway = Yes, it gives no suggestion | Use Fit Entire Putaway Volume for LPs. See Volume-Based LP Putaway |
Location Capacity Utilization below 100% | Less of each location counts as usable | Raise the percentage if locations are left too empty |
Many candidates | Only the top 20 by order by are checked, plus one more batch of 20 for volumetric rules | Narrow the rule (zone, group) so suitable locations rank higher |
5. Reservations
Check | Why it matters | What to do |
Other operators just got suggestions for the same area | Suggested space is reserved for them and counts as filled, even if it's physically empty | Expected. It clears when they finish, tap Suggest Another, or the reservation expires after 15 minutes |
The same product was scanned twice without finishing | Each product scan reserves space again | Wait for the extra reservation to expire, or finish the first putaway |
A sequential session holds many locations | Each child LP's location is reserved for up to 60 minutes after the operator's last action | Ask the operator to finish or cancel the session |
6. Force Suggested Location
Message or symptom | Why | What to do |
"No Suggested Location Found: Cannot complete putaway. Please check the algorithm configuration" | Force Suggested Location is on and no location was found, so the putaway can't be completed anywhere | Fix the cause using sections 1–5 |
An error saying the scanned location doesn't match the suggested one | The target isn't the suggested location, an LP in it, or an empty LP confirmed in it | Scan the suggested location, or tap Suggest Another |
Empty LP rejected | The location you confirmed for the empty LP isn't the suggested one | Confirm the empty LP in the suggested location |
7. Sequential putaway (LP (Sequential))
Message or symptom | Why | What to do |
The scanned Parent LP has no child LPs associated with it… | No child LPs, or only empty ones | Use Directed LP Putaway |
This Parent LP has inventory that is not assigned to individual LPs… | Stock sits directly on the parent LP | Move it onto child LPs or put it away as product |
No putaway suggestion could be generated for any LP on this parent LP… | No child LP got a location | Fix the cause using sections 1–5 |
Some LPs listed under Manual Putaways | Those LPs got no location | Tap Suggest Another when you reach them, or place them manually |
Scanned LP is not on the Parent LP of this session… | The LP isn't in this session, for example beyond the first 20 | Finish the session, then rescan the parent LP |
…currently held by [name]… | A colleague owns an active session for this parent LP | Ask them to finish or cancel it |
8. Receiving
Symptom | Why | What to do |
Suitable location not found on the Receiving screen | No rule found a location with room | Use sections 1–5 |
Different location than in directed putaway | A rule with Is Receiving Process applies only during receiving | Expected; review that rule |
When the suggestion is unexpected
Symptom | Likely cause |
A rule further down the list is never used | A rule above it already found a location with room |
A "full" location is still suggested | It has no limit set, or the rule doesn't include the matching action, such as Check Location Capacity Type or Check Max SKU Count |
A product went outside its zone | A later catch-all rule without a zone filter took over. Add a zone-limited rule above it |
The location is meant for cases, but you're converting to units | With Enable Converting to Units, the suggestion is based on the original pack type. Tap Suggest Another for a unit-based suggestion |
Common questions
How can I check a rule without doing a putaway? Test the whole algorithm, or one rule at a time, against the same stock. Testing rules one by one shows which of them can find a location. See Create a Putaway Algorithm.
Why did nothing change after I emptied a location? It may still be reserved by another operator's suggestion. Wait for it to clear, or check for an open sequential session.