I think I’ve raised these in various feature requests but I’m still not happy with how the off-site packaging process is and it was one of the main reasons we moved to Breww.
I’ve just received a batch we sent off back, I don’t know the losses per SKU as they just take in X volume and we get back Y1,Y2 & Y3 with the losses shared over the 3. On receiving this back I’m now having to ascribe all the losses to one of the SKUs. There should be a box to tick to say ‘spread all losses equally over all the batches received back against the single volume sent, based on the proportional volume packaged’ if we don’t have the detail per SKU. I also want to put in batch codes at point of receiving stock.
Equally on packaging, I’ve created POs for materials to land with our co-packer. I receive these in, but yet this packaging isn’t available for use at the packager, it needs to be moved to our main site to then be consumed. We do not store labels and crowns here, we store them there. The beer is packaged there, the packaging stock is consumed there. Why am I having to juggle it all about and am not able to accurately track where things actually are?
The same with goods going out - we have multiple stock locations - some is stored in the brewery and sold here, some is stored in a warehouse and sold there. Why can’t I specify on an order where the stock is coming from, and then have it auto assign based on the stock there? Or even better, assign customers to be fulfilled from one location with an option to make it a one-off from somewhere else.
We end up having to hold all finished goods and packaging stock in Breww in our brewery, which is 95% incorrect and requires additional work on our behalf to keep on top of it, remember what is where and carry out regular stock checks that we could avoid.
Finally when looking at margin reports I cannot for the life of me work out why we cannot assign a cost of delivery to an invoice and then have it pull through. The delivery/distribution costs can be massive - it’s at least 10-12% and can be as high as 25% in some instances. To not be able to include these on a margin report is very unhelpful and causes us to have to do all this extra work in the background.
Have I missed anything obvious with the above or do I have to continue with my workarounds until these feature requests can be implemented?