Suggested by Frans Hoogenraad – Under Review
When multiple LPs are stored on one location, upon picking the mobile device worker has to "scan best matching LP".
Scan LP1
If LP1 is not sufficient, the worker has to scan another LP, but that LP2 is dissolved into target LP1.
Theoretically it is possible to avoid this by
scanning LP1,
pressing Full (which creates a closed work for LP1)
enter the qty on the LP just picked, and
continuing with the remainder on the original work.
This process is so error-prone that I fail about half of the times.
When the LPs have a fixed qty, it is possible to maximize the work template to 1 LP. But with varying qty per LP this is not possible.

I have seen this needed in virtually all implementations. And customers are shocked when I explain it is not as standard. I really needs to be released as a standard feature ASAP as it is so in need.
Would be a very useful tool. I have been part of projects where we have made a customization and projects where we accepted to use the "full" standard process.
6 and half years later, and still a very much needed idea! Would be a great addition.