Sequential Putaway for Parent LPs
Sequential Putaway transforms how warehouse operators put away inventory from a Parent LP.
Instead of receiving one location suggestion at a time and walking back and forth across the warehouse floor for each individual LP, the system reads all child LPs on the Parent LP at once, calculates the most efficient set of putaway locations, and guides the operator through them in the shortest possible walking order — one LP at a time, in a single continuous pass through the warehouse.
When to Use It
Use Sequential Putaway when:
You are putting away inventory from a Parent LP that contains multiple child LPs (pallets, totes)
You want the system to sequence your putaway locations to minimize walking distance
Multiple operators are running simultaneous putaway sessions and you need to avoid location conflicts
This flow is separate from the standard single-LP putaway. If you are placing a single, individual LP — not a Parent LP — use Directed LP Putaway as normal.
Prerequisites
Before starting a Sequential Putaway session, ensure:
A putaway algorithm is configured and active for your warehouse in Warehouse Settings. Suggestion quality depends on your configured algorithm rules.
Your user account has the Sequential LP Putaway permission enabled.
The Parent LP you are working with has child LPs (with inventory) associated to it in the system.
How It Works
When you scan a Parent LP on the mobile app, Logiwa IO reads all child LPs on it and runs the putaway suggestion engine against each one in sequence. Each prior LP's suggested location is treated as theoretically occupied before the next suggestion is calculated — so no two LPs on the same Parent LP are ever directed to the conflicting spot.
Once the calculation is complete, you see a Queue Preview screen showing all child LPs in their suggested putaway order, with target locations listed. After you confirm, the session begins and the app guides you LP by LP, prompting you to scan each LP and its target location to confirm placement.
If a suggested location is blocked or unavailable, you can skip the current LP (it returns at the end of the queue), request a different suggestion (Suggest Another), or place the LP at a location of your choice (Bypass).
How Location Reservations Work
When a Sequential Putaway session is created, each suggested location is held as a soft reservation for the duration of the session. A soft reservation tells the suggestion engine to treat that location as if it were already occupied — even though the LP has not physically been placed there yet.
This reservation is active from the moment you confirm the Queue Preview until one of the following happens:
You scan and confirm placement at that location — the reservation converts to a real inventory movement and is released
You use Suggest Another, or Bypass — the original reservation for that LP is released and replaced or dropped
You abandon the session or it expires — all remaining reservations for your session are released
Reservations are warehouse-wide.
Every active session across all operators in your warehouse contributes to the reservation layer. When the system calculates suggestions for a new session, it looks at real inventory and all active reservations from all operators simultaneously — so no two operators are ever directed to the same location at the same time, even if they are working concurrently, but this depends on the active putaway algorithm settings.
Example:
If algorithm has Suggest Empty Location action, it is not expected for 2 different operators receive same location suggestion.
But in case of Select Same SKU action, two different operators may receive same location suggestion.
Reservations do not block physical access.
A soft reservation only affects what the suggestion engine recommends. It does not prevent an operator from physically placing an LP at a reserved location via Bypass. If that happens, the system records the actual placement and releases the original reservation.
Reservations expire automatically.
If a session is inactive for 60 minutes, its reservations expire and become available to other sessions. Any LPs already placed before the expiry remain as real inventory movements.
Key Limitations
Limitation | Details |
LP count per session | A maximum of 20 child LPs are included per session. If the Parent LP contains more than 20 child LPs, only the first 20 (by most recent inventory update) are included. The Queue Preview shows how many LPs were excluded. |
Queue order is fixed | The system-generated walking path order cannot be manually reordered on the Queue Preview screen. |
Sessions are user-scoped | A session belongs to the operator who started it. A second operator cannot resume another operator's active session. The original operator must abandon the session first. |
LP-level putaway only | This feature covers LP-level putaway. Product-level sequential putaway (placing individual units) is currently not available in this feature but planned for the future. |
Session timeout | Sessions expire after 60 minutes of inactivity. Any LPs already placed are preserved as inventory movements. Session timer refreshes to 60 minutes after each movement/interaction of the operator. |
Common Questions
What happens if the putaway algorithm is not configured for my warehouse?
Session creation will be blocked and you will see a notification on screen. Contact your warehouse administrator to set up the putaway algorithm in Warehouse Settings before using Sequential Putaway.
Can two operators work on the same Parent LP at the same time?
No. Only one active session per Parent LP is allowed at a time. If you scan a Parent LP that already has an active session, the app will prompt you to resume the existing session (if it belongs to you) or inform you that another operator is already working on it.
What happens to LPs I already placed if I abandon the session?
Any LP placements confirmed during the session are preserved as real inventory movements. Abandoning a session does not reverse completed placements — only the remaining unplaced LPs are released from the session.
Does this change how the putaway algorithm calculates suggestions?
No. The underlying algorithm logic is unchanged. The only difference is that the system now runs it for all LPs on the Parent LP at once, using each prior LP's suggested location as temporarily occupied before calculating the next suggestion.