I love how you are not even realising that behind the oatmilk ticket is written "last oatmilk", the behind the half and half one is written "only 3 half and half" behind the foo ticket "foo down to f(frequency of foo use)", and the person now now only need to go through the tickets at the end of the week (or if more than N tickets).
I will let you ponder if you need to reticket all, or just the reordered product, wether a stack can have multiple ticket (a white one say 5 from the last and one red one two from the back know wether you need an urgent order) etc...
And whether or miracle, if you don't receive any ticket a week that you don't need to reorder !
It's amazing how if that was expressed in term of resource allocation, reference counting, tagged pointers, scaling heuristic, garbage collect... that would click in people's mind, but many are incapable at abstracting because they feel they are beyond this.
I will let you ponder if you need to reticket all, or just the reordered product, wether a stack can have multiple ticket (a white one say 5 from the last and one red one two from the back know wether you need an urgent order) etc...
And whether or miracle, if you don't receive any ticket a week that you don't need to reorder !
It's amazing how if that was expressed in term of resource allocation, reference counting, tagged pointers, scaling heuristic, garbage collect... that would click in people's mind, but many are incapable at abstracting because they feel they are beyond this.