Current Problem
We had an issue where someone went to pick a batch and assigned a tote to it, but had to stop. They then continued the batch the next day but forgot to scan the original assigned tote and scanned a new one - which then resulted in there being 2 totes assigned to 1 batch. Ideally, we don't want this to happen and would prefer that once a batch is assigned to a tote that no other totes can be assigned too! |
|
Idea to resolve Problem | A button to disable / enable this to happen per batch |
Understand where you're coming from but from our point of view if you have a batch which requires an extra tote, you need to be able to add one.
Compromise - maybe see if we can have a slider to allow multiple totes against a batch and set it to on or off at client level?