Overview
By default, the putaway algorithm only suggests a location: operators can scan any valid target instead. Force Suggested Location turns the suggestion into a rule. When it's on, mobile directed putaway only completes at the location the algorithm suggested, so stock doesn't drift into the nearest free bin and your slotting rules are followed.
When to use it
Operators often put stock in convenient locations instead of the suggested ones, and you then struggle to find it.
You've designed your algorithm carefully (zones, capacity, same-SKU locations) and want it followed every time.
You want a cleaner audit trail of where stock was put away.
Leave it off if operators regularly need to judge on the floor, for example when locations are often physically blocked and your algorithm can't know it.
Prerequisites
A putaway algorithm that is not used as the dynamic replenishment algorithm.
Permission to edit putaway algorithms.
Step-by-step: turn it on
Go to Automation > Algorithms and select Putaway Algorithm.
Open an algorithm to edit it, or create a new one.
On the Primary Information tab, check Enforce suggested locations on mobile directed putaway. This article calls it Force Suggested Location.
Click Save.
It's unchecked by default, for new and existing algorithms.
Not available for dynamic replenishment. If Use this algorithm as dynamic replenishment algorithm is checked, Force Suggested Location is turned off and hidden. Checking the replenishment box clears it automatically.
Example: PALLET_RACK_ALGO has Force Suggested Location checked. You then check Use this algorithm as dynamic replenishment algorithm on it. Force Suggested Location is cleared, and putaway operators can scan any target again.
How it works
When an operator gets a suggestion and scans a target, Logiwa IO checks the target against the suggestion:
Operator scans… | Result | Example (suggested location A-12) |
The suggested location | Accepted | Operator scans A-12 |
An LP or parent LP that already holds stock and is in the suggested location | Accepted | Pallet PAL-501 is in A-12; operator nests the stock onto it |
An empty LP, confirmed in the suggested location | Accepted | Operator scans empty tote T-07 and confirms its location as A-12 |
A different location | Blocked | Operator scans A-13 |
An LP that holds stock in a different location | Blocked | PAL-777 is in B-02 |
An empty LP confirmed in a different location | Blocked | Operator confirms empty tote T-07 at B-02 |
When a target is blocked, the putaway doesn't happen and nothing moves. The operator sees an error saying the scanned location doesn't match the suggested one.
💡 When you scan an empty LP as the target, the app asks you to confirm which location it's in. With Force Suggested Location on, that location must be the suggested one. An empty LP somewhere else isn't brought to the suggested location automatically.
No suggestion
If the algorithm can't suggest any location, the putaway is blocked with: "No Suggested Location Found: Cannot complete putaway. Please check the algorithm configuration." The operator can't choose a location themselves. See Why Wasn't a Putaway Location Suggested? to find the cause.
Where it applies
Putaway option | Behaviour |
Product (Bulk), Product (one-by-one) | The target scan is checked as in the table above |
Directed LP Putaway | Same. The whole LP is checked as one move: if the target is wrong, nothing on the LP moves |
LP (Sequential) | The Target Location field is pre-filled with the suggested location and locked, with the note "This LP must be placed at the suggested location." An LP that got no suggestion can't be placed until Suggest Another finds a location for it |
Regular Transfer screens | Not affected. It only applies to directed putaway |
Suggest Another while Force Suggested Location is on
Suggest Another still works. The new suggestion becomes the location the operator must use; the earlier one is no longer accepted. In sequential putaway, the check happens when the LP is placed, not when the new suggestion is requested.
Example: The operator is sent to A-12, but it's physically blocked. They tap Suggest Another and get A-20. Now A-20 is accepted and A-12 is blocked.
If Suggest Another finds no alternative, the operator has to wait for space, skip the LP (sequential putaway only), or ask a supervisor to adjust the algorithm or location set-up.
Common questions
Does Force Suggested Location change which location is suggested? No. It only changes what's accepted when the operator scans the target. The suggestion itself is made the same way.
An operator says the location is full. What can they do? Use Suggest Another. If no alternative is found, check capacity and rule set-up with Why Wasn't a Putaway Location Suggested?
Does it affect web transfers or regular mobile transfers? No. It only applies to directed putaway on mobile.
Can I force suggestions for replenishment? Not with this setting. It's turned off for the algorithm used as the dynamic replenishment algorithm. To keep replenishment operators on the suggested target, turn off Allow Scanning Another Put Location on the replenishment job type. See Create a Job Type for Replenishment.