I have been speaking with Connor about the container cycle.
It would be great to have a standard (but modifiable) cycle with sequential steps which also include the customer being able to scan when ready for uplift.
example:
START
Empty Keg
Rack into Empty Keg (Scan) - Status changes to FULL - Product Name - BBE
Order comes in - Scan Keg to attach to order - Status changes to - Assigned to Order number
Dray picks up order and scans kegs for the order - Status changes to - On way to customer order number
Dray drops at Customer and scans kegs - Status changes to - With customer (name/address).
Customer uses App to scan keg - Status changes to - Ready for Uplift - automatically added to uplift report.
Dray collects and scan in - Status changes to - Returning to Brewery
Dropped at Brewery scanned ready to be cleaned - Status changes to DIRTY
Passes through cleaning cycle and scanned - Status changes to - READY TO FILL
I’m thinking a process like this is sequential and can be either through scanning or manual override in system.
However, when a keg is scanned the App should show current status and allow the user to ‘move to next stage’ of the cycle.
In my mind, this would allow users with their own keg fleet to manage location tracking through the cycle much better and stop bottlenecks. Especially if a customer or dray company have a stockpile.
Additionally, allowing customers to scan kegs from Breweries as they do Kegstar would make their lives easier to let us know when to uplift.
Thanks
To ensure that we can manage and prioritise feature requests suitably, we need separate requests on their own threads.