We do the accounting a brewery actually needs — duty, packaging, containers, true margin — and we build the reporting layer that turns Breww into answers.
Breww captures every order, batch, delivery, container and duty calculation accurately — and none of it tells you that your second-largest account has quietly halved, that a beer's margin has drifted since you changed its packaging, or that the customers you discount hardest are the ones growing slowest.
Those answers are already in the data. Reaching them means exports, a spreadsheet somebody has to maintain, and time nobody in a working brewery has. So the questions stop being asked, and the business gets run on the ones that are easy to see.
Gross profit in a brewery isn't a subtraction. Duty, packaging, production cost and the cost of your own kegs and casks all have to be treated correctly, or the margin on screen is fiction dressed as fact.
That's accounting work before it's reporting work — which is why we do both.
The ordinary finance function, run by people who know what a duty return, a cask deposit and a pub group rebate actually are.
Alcohol duty calculated and filed on time, reconciled to production and despatch records rather than reverse-engineered at month end. Small Producer Relief applied and evidenced.
Net sales less duty, packaging, production cost and the cost of your own containers — reconciled, not approximated, and broken down by beer, pack format, customer and channel.
Kegs and casks are capital sitting in other people's cellars. We treat them as an asset, track deposits properly, and put a number on the ones that aren't coming back.
Taproom, webshop, wholesale, direct trade and pub groups reconciled into one P&L — Stripe, Shopify, GoCardless and your brewery system agreeing with each other.
MTD VAT, PAYE and pensions for brewers and taproom staff, statutory accounts and corporation tax. R&D and capital allowances on kit where they genuinely apply.
We work inside Breww rather than around it — sales, production, duty and container data reconciled to Xero, so the books and the brewery system agree.
Forecasting that understands duty timing, seasonal trade and the working capital tied up in tank and in transit — not a generic 13-week template.
A reporting layer built directly onto the Breww API. It reads what's already in Breww and tells you what it means — organised around the questions you actually ask, rather than the tables the database happens to have.
Overview — figures illustrative, taken from a live client build. Brewery branding removed.
Blended margin is 59.1% across the last 12 months.
Median account margin is 61.5%. Five accounts worth more than £4,000 sit more than twelve points under it.
968 pubs and bars inside the delivery footprint that aren't on the ledger.
610 of them within 400m of a stop the van already makes. A starting point built from public registers — not a verified sales database, and the page says so.
Ranked by how cheaply each site can be reached from rounds you already run — cost to serve, not likelihood to buy. The distinction is on the page, because pretending otherwise wastes a rep's week.
Gross profit and lead finder — same build, branding removed.
Trade and gross profit by month, beer, customer and channel. Net sales less packaging, duty, production cost and the cost of your own containers — reconciled, not approximated.
Accounts ranked by what's at stake rather than alphabetically, and judged against their own buying rhythm. A customer who orders every eight weeks isn't late at six.
Achieved price against list, discount by customer and product, and the distance between what you meant to charge and what you charged.
Volume set against margin per product, so the popular and the profitable can be told apart before the next brew is scheduled.
Pub groups, managed estates and buying groups rolled up, so you see one commercial relationship instead of forty unrelated accounts.
A forecast you build and edit by hand, held beside actuals as they land, so the variance is visible while there's still time to act on it.
Live vessel occupancy, fermentation curves and attenuation by batch.
Drops per day, time spent on the drop, and rounds by postcode district — the size a delivery round is actually planned at.
Container movement history, plus an honest reading of how completely returns are being recorded — usually the more valuable of the two.
Licensed premises inside your delivery footprint that aren't on your ledger, drawn from public registers and matched against the rounds you already run.
Ask in plain English. It answers from your own data, cites the figures it used, and says so when the data can't support an answer.
It reads Breww and nothing else, so there's no parallel spreadsheet and no second version of the truth.
It rebuilds itself automatically through the working day, so nobody has to remember to run anything. It arrives as one page behind your own company sign-in — not another product with another login. Every figure carries its own definition, and every table exports to Excel.
Setup, the refresh pipeline and the analysis are the service. You get the page and the answers, not something else to look after.
Most dashboards state everything with the same confidence, which is the quickest way to lose yours — one figure turns out to be wrong and every figure beside it becomes suspect.
This one gets checked against reality and reports what the check found. When a measure can't be defended it comes off the page, with a plain statement of what was removed and why. A figure that can't be defended is worse than no figure at all.
Breweries running Breww, selling through pub groups, wholesalers and direct trade at once.
It sits alongside Breww and, if you have one, your existing accountant. It replaces neither — Breww stays the system of record, and we read from it.
Every figure on the page is one we can defend in a meeting with the bank. That was the whole point.— Client engagement, brewery reporting build
Honest caveat: the above describes what we built for one brewery on Breww. A second brewery on Breww with different data hygiene, or on different software entirely, needs discovery first — cask tracking especially, which behaves differently depending on how returns get recorded. We'll tell you what's achievable on your data before you commit to anything.