Hi Claire,
Thanks for posting! No problem at I will do my best to answer all your questions.
-
I think you have it about the right for the first point. If not for labelling (as this would cause a problem later down the line), I don’t see a problem with the generic ABV approach, but I think sticking with a specific beer is a better idea, and hopefully, as I answer your other questions, you will agree.
-
The best solution here is only possible if you use Breww’s batch-sharing features and the contractee uses Breww as well. In this situation, both parties can add ingredients from their respective sides, so their ingredients would never enter your stock, but all could be tracked in the event of a recall. A potential other option would be to add a completely separate stock item dedicated to just your contractee stock. It would be a bit of extra admin work, but this way, your costs don’t get mixed up. A third option would be to set up your contractee as a supplier for each stock item, then costs are separated for when you’re entering new costs, but you’d find your average landed cost would be affected here.
-
For racking, the product will need to be created for the beer chosen. So if you have chosen to go with a generic beer, then you can have a generic product, but if you have specific beers, you’d need specific products for each one. It depends on your needs. For printing labels, you would see the generic product name. You could change this each time you print labels, but it would probably be more work. Either way, the ABV can be set on the batch itself and be different from the beer that’s set up, and the duty can just follow the batch.
I hope this helps, and please let us know if there is anything I haven’t covered or if you have any other questions at all.