Changelog

v545 2026-09-16

Packaging orders get their own page. Creating one used to mean meeting a form on your way down the list of work orders. The list keeps the space now, and New sits at the top, the same way invoices, deliveries and purchase orders already work.

The accountant export no longer fails on some months. Certain years typed into the month field returned an error page instead of a file.

Invoices, deliveries and purchase orders open faster. Each was asking the database one extra question for every row on the page, which you notice most once a list gets long.

A date pasted with spaces around it saves properly. On a sales lead it was being stored as no date at all.

The app now tells you when your phone cannot find it. That message already existed and never once appeared, so a companion that could not connect looked exactly like one nobody had opened.

The stocktake fills in who counted, the way the cleaning record already fills in who did it.

v544 2026-09-15

Records now say what comes next. A supplier bill shows where it sits between the order, the goods receipt and the payment, and offers the one action its state calls for. A goods receipt offers to record the bill, already filled in with the supplier and what actually arrived rather than what was ordered. A delivery has a page of its own, so the printed note goes back to being just the document you hand over. A tank that is clean and empty is offered a new batch instead of a second cleaning.

Alerts take you to the record. Twelve kinds of alert used to drop you at the top of a list and leave you to find the row yourself. They now open the item, batch, tank or bill they are about. Three links inside the record chains reached nothing at all, and one of them sat on every purchase order, goods receipt and supplier bill in the app.

Longer lists stay usable. Customers, quotes, deliveries, orders, supplier bills and purchase orders now show fifty at a time instead of everything at once. Stock, bills and purchase orders gained search and filter bars.

Your records have a stated lifetime. One place now says how long each kind is kept and why. The audit trail keeps everything. Automatic probe readings are trimmed after a year by default, because their size decides whether a backup can still be restored, and you can set that to keep everything.

A pH probe that goes quiet now says so, as a note rather than a warning, since probe readings never enter the compliance record. Two settings panels moved off the working lists they had been sitting on, and search finds fourteen pages it could not reach before.

v534 2026-09-11

Cleaning records now hold every stage of a full CIP, each with its own agent, strength, temperature and time, so a six stage clean is recorded as the six steps it actually was. Two acids were added to the agent list, because an acid wash could previously only be logged as "Other". A cleaning logged by mistake can now be deleted.

On a batch page, the total drawn off a tank is now counted from the withdrawals themselves instead of worked out from a difference, so the heading agrees with the rows underneath it.

On a Mac, BrauMo now keeps the computer awake for as long as the server is running. A sleeping Mac stops answering, which made the phone companion look as though it could not find your server.

v531 2026-09-09

A fix, and it is worth saying plainly what it was.

The "Earlier printed copies of this record" table on a HACCP record could print a line of raw program data instead of a value, on the page an auditor reads. It happened on any record whose paper copy was filed before the vessel-cleaning line existed, which is to say on records you may already have printed.

The cleaning facts are now filed as three plain values with names: which vessel, whether a cleaning was recorded before the fill, and the date of it. And the comparison itself was fixed underneath, so a field added in any future version reports line by line rather than as one unreadable blob.

Nothing about your records changed. This only affects how a difference between a printed copy and the current record is shown to you.

v530 2026-09-09

Cleaning, reworked around the tank.

A cleaning record now names the vessel it was for. That sounds small and was not: the record has had a real link to a tank since v470 and the form had no field for it, so every cleaning logged through the app was invisible to the boards built to show it. Logging one from a tank card, a tank page or a batch now carries the vessel with it.

Which tanks need cleaning, seen rather than read. Every vessel on the board and on the floor plan carries a mark: amber where it needs attention, green where it is clean, nothing where the app has no history to reason from. Tanks, Schedule and Layout all offer Cleaning now.

You can declare a cleaning interval per tank, and the tank schedule grows a "Cleaning due" table beside the timeline. There is no default interval and no vessel appears there unless you set one, because the published figures disagree by factors of ten. Nothing about this blocks: an overdue vessel is still offered for the next batch.

The batch page offers "Log cleaning", and the moment a tank is freed that becomes the suggested next step. The printed HACCP record and its PDF now state whether the vessel was cleaned before the fill, with the cycle, the agent and its strength, who did it and who checked it. It is evidence that a prerequisite programme ran and it can never fail the record.

Five more vessels are drawn: the open-top tank, the barrel, the carboy, the plastic drum and the horizontal tank. The diagram picker names them in your language instead of showing raw keys.

Also: two advisory alerts for a vessel emptied with nothing logged since, and one filled with no cleaning behind it.

v522 2026-09-09

Seventeen versions in one release. The short version: second fermentation takes fewer

steps, retention samples are yours to manage, and the working pages carry far less text.

SECOND FERMENTATION. Sending a base to F2 is now one form on its own page, asking where,

which recipe, how it carbonates, how much and what to call it, in that order. Keeping it

in the same tank is one of the destinations rather than a separate form. On an F2 batch,

the workflow checklist and the carbonation readout moved into the flavour and condition

step, so the CO2 verdict sits under the field that sets it.

RETENTION SAMPLES. You can now skip a sample for a batch, discard a stored one and keep

the record of it, or turn retention off for the brewery. The register has four views:

current, expired, discarded and skipped, so it no longer opens as a wall of amber.

RECORDS AND ALERTS. Every version of a HACCP record you print is filed, so you can show

what a document said on the day you handed it over. A correction to a monitoring record

now keeps what the record said before. And one broken alert can no longer take every

other alert down with it.

LESS TEXT, BETTER LISTS. Long lists scroll inside their card instead of running the

length of the page. Hints are short, the mechanics moved to the system map so there is

one description of the app instead of two, and the phone screens carry fewer boxes:

the stock editor folds its extra fields, and quick actions are one scrolling row instead

of half the screen.

TABLES AND FORMS. Sortable columns, pagination that says where it stopped, rows you can

click anywhere, and buttons that show they are working.

SETTINGS. The Basic, Intermediate and Pro workspace levels are gone. One switch says

whether you sell from here, and it hides the offer, never your records.

Also: Windows installs its own updates, an invoice now reaches the raw-material lot it

paid for, a reading records who took it, and German, Spanish and Portuguese cover exactly

the same text. Security and dependency updates throughout.

This release is a manual download. From this version on, the app can fetch its own

updates.

v505 2026-09-06

QC readings that hit a limit are now marked as bounded on the record, the HACCP documents and the Certificate of Analysis, and a bounded gravity reading no longer clears the alcohol check on its own. Nutrition values outside their range are refused instead of clamped. A scanned batch QR code opens the batch in the mobile apps, and the code now carries an address a phone can open.

v504 2026-09-05

Raw materials now behave like finished goods behind the tank: when a batch consumes tea, sugar or packaging, the received lot is drawn down first-expired-first-out, a lot on hold is passed over, and the batch page shows which supplier lot each deduction came from, with the option to pin another. The trace sheet names the supplier lot per ingredient. A receipt you quarantine holds its lot until you release it. A delivery that took from a lot past its best-before is marked, never blocked. Stock counts take a reason per difference (breakage, spoilage, sample, miscount, lot correction) and the summary groups by it. Purchase orders can be typed in packs, and the stock forecast can draft orders for you, one per approved supplier. The e-invoice (XRechnung) now carries your street, postal code and city and the customer's, your contact point and electronic address, payment instructions on every file and the payment-terms sentence from the printed invoice; three new address fields sit beside the address block on each customer and in Invoice settings. Large quantities and stray characters no longer produce a file a portal rejects.

Two things to know on the first day: raw-material lots received before this update keep the quantity they were booked in with until you reconcile them, so the Lots page may show drift on items nobody touched, and Reconcile settles it without rewriting anything. The expired-lot mark looks back 30 days, so it can appear right away for recent deliveries that drew from an expired lot.

v503 2026-09-02

A full UI/UX pass: readable text everywhere, one visual language for headings, chips and notices, and real icons instead of glyphs. On a phone the batch page's section bar no longer hides under the header, the stock list keeps its head while you filter, and wide tables scroll instead of squeezing. Ten menu entries now match the page they open, and tanks are called tanks everywhere. Keyboard and screen-reader support throughout: the floor plan and delivery run move with the arrow keys, every icon button says what it does, and status that was colour only now says it in words. Underneath: a recipe version captures the recipe as it stands when you cut it, clearing your data no longer leaves records pointing at deleted batches, and the one-click backup writes a consistent snapshot.

v502 2026-09-01

Undoing a packaging run no longer removes another run's history.

If you bottle one tank over two days and do not type a lot code, both runs take the batch code, so both lots end up named the same. Until this release, undoing one of those runs took its own bottles off your stock but removed the movement lines of both. Your stock figure stayed right and your history quietly lost a run, which is the kind of gap you only notice much later when the two stop adding up.

Movement lines now record which lot they belong to, rather than only mentioning it in their text. That also means renaming a lot after you bottled it no longer breaks the link.

Lines recorded before this update carry no such reference, and their only connection to a lot is the text written at the time. Where BrauMo can match one confidently it does. Where it cannot, it leaves the line alone and tells you the stock and the ledger disagree, rather than guessing which run to erase. You can settle those from the stock lots page.

v501 2026-09-01

BrauMo now shows you where a record sits in its chain. Open a goods receipt and you see the supplier it came from, the purchase order behind it, and whether the bill has arrived yet. Open a batch and you see the recipe it was made from, the base tank it came out of if it was flavoured, and the lots it became. Open it again and you see where those lots went: the delivery notes, and the customers who received them.

Each station is a link, and an empty one tells you which kind of empty it is. A station with nothing after it is the next thing to do. A station that was skipped on purpose says so instead, because being reminded to do something you deliberately did not do is just noise.

This already worked on the sales side, from lead through quote and order to delivery and invoice. It now works the same way for buying, for production, and for tracing a lot forward to the people who got it.

A supplier bill now knows which supplier it came from. Before this, a bill was linked to a supplier only by the name you typed, so a bill entered without a purchase order behind it had no connection to your approved-supplier register at all. New bills carry the link. Old ones are matched by name when the match is certain, and left alone when it is not: if two suppliers in your register share a name, BrauMo says nothing rather than guessing which one you meant. Your old bills are never rewritten.

The supplier picker on the bill form now lists your whole register. It used to list only suppliers who appeared on an open purchase order, so anyone else had to be typed by hand, and a typo meant the bill never linked to them.

Deleting a finished-goods lot now records the stock movement. Until this release it took the bottles off your stock without writing a line in the movement history, so if you ever removed a lot, your on-hand figure and your history stopped agreeing. If BrauMo has been warning you that stock and the movement ledger disagree, this is very likely why. The warning panel now has a Settle button that writes the missing line for you. It never changes your stock figure, because the on-hand number is the one you counted.

v500 2026-09-01

The tank timeline now draws your batches where they actually sit.

Every bar on the ninety-day tank schedule was rendering at the start of its row instead of across its own dates, so a tank used twice showed both batches stacked on top of each other and the labels ran together. That is what the schedule looked like from the day it was added, and it is fixed. The planning page was never affected.

Nothing else changed in this release. There is no data change and no migration coming from v499.