True cost per batch and per pack
Malt, hops, yeast, energy, packaging and labour posted against the batch give a real cost, including yield loss - which is usually where the surprise is.
A practical look at what an ERP does for a brewery, where the value sits, and how to choose a platform that handles batch traceability, duty and returnable containers properly.
Brewing is a manufacturing business with unusual complications: duty, returnable containers, short shelf life and a product that changes weight and volume between the mash tun and the pump.
An ERP (enterprise resource planning system) holds recipes, batches, stock, duty, sales and finance in one place so cost per pint is a number you can actually rely on.
It doesn't replace brewhouse control systems. It records what those systems produce and connects it to purchasing, stock, duty and the ledger.
For most breweries, an ERP is where the following live:
The value isn't in the accounting. It's in knowing what each beer actually costs to make and sell, and being able to trace every pack you've shipped.
Malt, hops, yeast, energy, packaging and labour posted against the batch give a real cost, including yield loss - which is usually where the surprise is.
From a delivered pallet back to the batch and the ingredient lot, and forward again to every customer who received it. That's what makes a recall a controlled exercise rather than a crisis.
Duty calculated at the right point, tracked through warehouse movements and reported on schedule removes one of the most error-prone jobs in a brewery's month.
Containers tracked by customer with deposits recorded turn a large, invisible asset into a managed one. Most breweries are surprised by the value sitting out in the trade.
Sales orders, forecasts and stock cover in one place mean the brew schedule reflects what's actually selling rather than what sold last spring.
Taproom, wholesale, supermarket and export carry very different economics. Seeing margin by channel and SKU shows where to push volume and where to raise price.
Data taken from a survey we commissioned in December 2024. Click here to view
of businesses are utilising an ERP
businesses are dissatisfied with their current ERP
of businesses say using an ERP has contributed to achieving business outcomes
Six everyday situations where one connected system changes the outcome.
Actual output against the recipe standard is recorded on the batch, so the variance shows immediately and the cause can be investigated while people still remember the day.
Breweries have requirements a generic finance package won't cover. These are the questions worth asking before you shortlist.
Finance, purchasing, stock, projects and reporting should sit in one system. Anything left in a spreadsheet quickly becomes the version everybody argues about at month end.
A system designed for a different sector rarely suits breweries. The platform should reflect your real processes, approvals and cost structures rather than forcing a rewrite of how you operate.
Consolidation, reconciliation and management reporting should be routine rather than a fortnight of manual work. Ask to see a month end demonstrated, not described.
Role-based permissions, approval workflows and a complete audit trail should be built in, so compliance is a by-product of daily work rather than a separate exercise.
Cloud platforms with standard processes go live in weeks rather than years. A long implementation is usually a sign the system is being bent into shape.
New sites, entities, currencies or product lines shouldn't need a replacement system. Check licensing and functionality for where you expect to be in five years.
Once you know what an ERP should do, the question becomes which platform fits how your team already works. Microsoft Dynamics 365 Business Central brings finance, manufacturing, stock and reporting into one cloud system connected to the Microsoft tools you already use.
For breweries that means batch and lot traceability as standard, bills of materials and production orders for recipes, warehouse and container management, and Power BI dashboards for margin by SKU and channel.
It's modular, so you can start with finance and stock and add manufacturing, warehousing or Dynamics 365 CRM later - without another migration as volumes grow.
It isn't just an accounting package. These are the capabilities teams tell us make the biggest difference day to day.
Ledgers, budgets, cash flow and management reporting run from the same data, with Power BI dashboards leadership can open themselves rather than waiting for a pack.
AI drafts descriptions, reconciles bank entries, chases anomalies and answers questions about your data, taking a chunk of routine admin off the finance team.
Approvals, quotes and reports work inside Outlook, Teams and Excel, so people use the tools they already know instead of learning another interface.
Approvals, alerts and handovers can be automated with Power Automate using low-code tools your own team can maintain.
Role-based access, approval limits and full traceability protect the financial and operational data breweries are accountable for.
Start with finance and operations, then add supply chain, projects, service or Dynamics 365 CRM as you grow - without another migration.
A mid-market ERP tracks duty-relevant movements and produces the data for your return. Some are extended with brewery-specific functionality for duty rates and small producer relief - worth confirming on your shortlist.
Yes. Returnable containers are handled as tracked items with deposits against the customer, which turns an invisible asset into a managed one.
No. Process control stays where it is. The ERP records batch outputs, costs and stock movements and connects them to purchasing, sales and the ledger.
Yes. Multiple channels, price lists and currencies are standard, and margin reporting by channel comes out of the same data.
Yes. It's licensed per user per month and built for small and mid-sized organisations, so you're not paying enterprise pricing for a 20-person brewery.
Tell us how production, stock and duty work today and we'll talk through what an ERP would change, which capabilities matter most and where to start. No obligation, just a straight conversation.