When we receive beer pack from third party packagers is there a way we can log it back in via our gyle/batch it was brewed with in Breww AND with their bottle batch reference?
We don’t know this reference until we receive it so don’t know what it will be and thus cant add it to the brew in advance as a batch reference at time of planning. All we have been able to do is to manually edit the batch afterwards to update the reference but we are doing a lot through contract packaging and its open to human error/memory.
It’d be nice to have the beer come back in through the software and it and apply a batch during that workflow.
When receiving beer back from a 3rd party packager, there should be a “notes” box. Can you use this to fill in their bottle batch reference? This note can later be seen in the “Actions” tab on the batch by clicking the “eye” icon next to the applicable “Racking off-site received” row.
We were probably wanting some kind of prompt during intake of the packaged beer via the breww system so we could remove the human error of forgetting to go back into the batch and edit the reference to update it with the packagers batch.
It would be less manual and would also make sure a member of staff inputted it. The good thing about having it as the batch reference is that it is shown around Breww next to the stock so helps us with FIFO.
I totally understand your use case here, but I must admit that it feels very specific to just you. Other than your specific situation, to me, it feels a bit illogical to let someone overwrite the batch reference during the process of receiving from a 3rd party packager. For this reason, I don’t think it’s the right question for us to ask all Breww users when receiving from a 3rd party packager. I’m sorry.
I’m happy to leave the thread open for comments from others, and if it gets lots of support from others who also would like this prompt, we may reconsider.
I’m sorry; I know this isn’t the answer that you were hoping for.
I think Steven’s issue might best be approached by having an additional field for batches sent for off-site packaging - the packagers reference, and that supplying a value should be required (at least optionally) when receiving product back. I worked in a place that used contract packagers pretty much exclusively (for small pack), and we did use the notes for this kind of thing, but I see what Steven means.
Couldn’t the return from packager form just show an input box with the information inputted in it for the batch reference when the batch was created in breww as its default?
If nothing was inserted at time of batch creation it would be blank by default, if it had something in it then that could be amended/appended and once saved would update the batch reference accordingly?
This in my mind straddles the issue for those needing it without messing with those who dont?
If this is unique to us then no worries. We have this situation due to being small and migrating from a paper system to breww but also having other pre-existing systems such as web shops and things that don’t currently integrate or we aren’t setup enough on the backend to migrate over from.
I don’t know what other people use the batch reference field for, but I can imagine that one might want to set this before packaging and record a packagers reference. Actually, come to think of it, what about multiple returns from a packager? Might not these have multiple, distinct packagers references?
