@webfantastic – Thanks for the reply and for the additional information.
The paid versions of PickingPal support something called “warehouse location”, and the pick lists and line items on the pick ticket can be sorted in ascending alpha/numeric order.
The running assumption is that a company will organize a warehouse to optimize picking flow or at the very least, put like items somewhat near to each other. I designed it this way as a result of my own warehouse setup.
In our warehouse, each storage rack had 4 shelves, with 3 large product bins per shelf. So, 12 bins per storage rack. In each row of our warehouse, we had 12-14 storage racks long (on right & left). We had row designators (A, B, C, D, E, F), then storage rack placement designators (1, 2, 3, 4….24+), then bin location designators per shelf (1A, 1B, 1C, 2A, 2B, 2C…).
Thus, each product had a very specific warehouse location as a string: B-10-1A (row B, storage rack 10, bin 1A).
On a Pick Ticket or Pick List, we could sort them by warehouse location to keep the picking flow optimized, like:
Line item 1: B-10-1A
Line item 2: B-13-4B
etc…
Hope that make sense. I assume this model could work for assembly or for supermarkets.
PickingPal cannot change the order line items at this time because in most cases, that could/would change the cost, tax, shipping of an order. If that increased the order cost, the difference would need to be collected. If that decreased the order cost, a refund would need to be issued. Since PickingPal can’t know how to treat order that have been changed, we leave that to the store operator to handle at the order level first, then picking can happen after.