We're excited to announce that you can now manage your yeast batches in Breww! Manage their costs over multiple beer batches, track their usage and genealogy and report on viability over generations. Find out more here.

Before now the mobile app only supported cask & keg rackings, so we're delighted to add support for smallpack rackings now too. Support for the recently launched "delayed racking releases" has also been added to the mobile app.

When racking (packaging) your beer in Breww, you can choose if you’d like to release this stock for sale immediately or hold it until a later date. This is ideal for bottle/cask conditioning, but can also be used in any situation where you would like to package the beer (rather than leave it in the vessel), but don’t want to immediately allow it to be sold or delivered to customers. Find out more here.

You can now add prefixes onto batch numbers to allow you to keep separate streams of batch numbers.

For example, if you would like your pilot batches to have their own sequential batch numbers, you can now simply give those batches a prefix and keep their numbers separate from other batches.

To make things easy, when you enter a prefix Breww will automatically suggest the next batch number and allow you to accept with one click.

Do you have set costs that you have to apply to each batch of beer manually, such as a cost for electricity? If so, Breww can now save you more time. Simply head into your Production settings and set up your automatic batch costs 😁 

You can set the brew types (standard, contract brews, etc) that each cost applies to and enter either a fixed cost value or a cost value per Litre in the batch.

These will then automatically be added onto your batches for you when first transferred from the brewing system to a vessel (so Breww knows the volume), or on batch start for contract brewed batches.

You can still add your manual costs and you can even edit/delete the automatically added costs on a per-batch basis if you need to.

Sometimes your beer duty return will contain items that you may not have thought it should, or will not contain items that you expect it to.

The point in time that's applicable to triggering a beer duty liability is when the beer leaves the brewery. This stage is part of the delivery process in Breww. Technically, the invoice date and payment dates are irrelevant to duty calculations (although these will in practise often be the same date as the "duty point" date). This is in line with the requirements of HMRC.

We understand that this can sometimes cause confusion, so we've added a report to show you orders that might cause confusion and why they are/are not on the return that you'd expect. Find this by going to the return in question, then using the Beer duty breakdown button in the top-right, followed by the What's not on my return and why? button.

In your Invoice Settings, you can now set your default Incoterms and Nature of Transaction Code (NoTC) for export invoices and this information will be shown on export invoices.

These account defaults can be overridden on a per-customer (in the Settings tab) and also a per-invoice basis. For export invoices, a breakdown will be shown at the top of the main order/invoice page in Breww too.

The export information will be shown by the declaration at the bottom.

There's now a new tab on the production dashboard to show your in-progress batches that are brewed by someone else for you (including contract brewed batches and collaborations at other breweries). The tab is only shown if you have any in-progress batches like this.

Up until now, you've only been able to map your Sellar customers to their Breww counterpart, when they place their first order. As of today, you can bulk map them all in advance to save time and delays with orders.

Go to Integrations > Ecommerce & POS > Sellar Actions > Customer mapping and use the Retrieve all unmapped customers from Sellar button. This can be used to populate the list so you can get them all mapped in advance and save time versus doing them as-and-when an order is pending.

If you get an error message, you may need to deactivate your Sellar API key and generate a new one. This is because older Sellar API keys do not have access to this new feature. Recently generated API keys should work immediately. Unfortunately, there's no way around this from our side as the restriction is on the Sellar side. A new key should only take a minute to generate (in Sellar) and be re-applied to the Sellar configuration (in Breww).

You can now quickly view a list of all customers with containers in trade since a given date (such as 6 weeks ago) then arrange uplifts for the containers with one click per customer. You can even filter the list by Delivery Area to be sure they'll fit nicely into your delivery routes.

Go to Containers > Actions & tools > Bulk arrange container uplifts to get started!