Overview
To maintain tight control over warehouse movements and prevent inventory fragmentation, Logiwa IO has introduced the Force Suggested Putaway parameter within the Putaway Algorithm setup.
Previously, warehouse operators could override system-suggested locations on the mobile app, which occasionally led to unauthorized inventory placement or suboptimal slotting. By enabling this feature, supervisors can mandate that workers follow system-directed movements, ensuring that items are placed exactly where the algorithm intends.
Key Benefits
Increased Inventory Accuracy: Prevents operators from placing inventory in arbitrary or incorrect bins.
Standardized Workflows: Enforces consistent adherence to warehouse slotting and organization rules.
Reduced Fragmentation: Minimizes the "drifting" of stock to unintended locations.
Configuration: Setting Up Enforcement
The Force Suggested Putaway checkbox is located within the Putaway Algorithm setup.
Step-by-Step Guide
Navigate to Automation > Algorithms and select Putaway Algorithm.
Select an existing algorithm to Edit or click Create New.
In the Primary Information tab, locate the Enforce suggested locations on mobile directed putaway checkbox.
Check the box to enable enforcement (Default is FALSE).
Click Save.
Conditional Visibility and Rules
To maintain system integrity, the following rules apply:
Algorithm Type: The checkbox is only visible when the Algorithm Type is set to 'Putaway'.
Mutual Exclusivity: This feature cannot be used with dynamic replenishment. If the Use this algorithm as dynamic replenishment algorithm checkbox is enabled, the Enforce Suggested Putaway option is automatically deselected and disabled.
How It Works?
When this feature is active, the system enforces a strict validation for all mobile directed putaways. If the system cannot generate a suggestion, the transfer is blocked with an error message: "No Suggested Location Found: Cannot complete putaway. Please check the algorithm configuration".
If a suggestion is found, the scanned destination must meet one of these criteria:
Options | Type | Validation Rule |
Option 1 | Direct Match | The user scans the exact Suggested Location. |
Option 2 | Occupied LP | The user scans a Target LP that is already physically located at the Suggested Location. |
Option 3 | Hard Block | If none of the above are met, the transaction is not completed. |