Brewery ERP Software: US TTB Compliance, Kegs & Costing Guide

Brewery ERP Software

Brewery ERP software connects brewhouse and cellar production, packaging, keg logistics, distribution and finance in one system, so that a batch can be traced from malt intake to a taxable removal without leaving the general ledger. Many of the products marketed to breweries as ERP in 2026 are not ERP in that sense, and that category confusion is, in our experience, one of the costliest mistakes buyers in this market make.

Updated July 2026

ERP Research is independent and vendor-neutral — no vendor pays for placement or ranking, including on this page. That is worth stating plainly here, because much of the "best brewery software" content ranking on Google is published by software vendors or by resellers that implement them.

Get Pricing Build Your Requirements

---

Brewery ERP vs Brewery Management Software vs Taproom POS

Three product categories compete for the phrase "brewery ERP", and they are not substitutes. Shortlisting across categories is one reason breweries end up running several disconnected systems and reconciling them in a spreadsheet.

The nuance the marketing hides: two of the best-known "brewery software" products do not contain a general ledger. Ekos is built around inventory, production, sales and compliance reporting and integrates outward to QuickBooks and Xero for the accounts, and to Square at the point of sale; Ollie likewise publishes integrations to QuickBooks Online, QuickBooks Desktop and Sage. That is a sound and often correct architecture for a single-site brewery — but it is not the same purchase as an ERP with financials, and it behaves very differently once you add a second site, a distribution arm or intercompany transfers.

One thing to know before you treat those two as independent options: both are now Next Glass products. Next Glass already owned Ollie and Ollie Order when it acquired Ekos in October 2025, and it has said it intends to converge the ordering and reporting tools into a single platform. A shortlist containing both is one roadmap, not two.

Ask every shortlisted vendor one question in writing: does your product post journals to its own general ledger, or does it sync to an external accounting system? The answer changes your implementation scope, your month-end close, and how much of your finance function stays manual.

TTB Reporting Is a System Requirement, Not a Report

Federal compliance is where brewery requirements diverge hardest from generic food and beverage ERP, and it is routinely left until after selection.

Two federal filings drive the data model. The Excise Tax Return (TTB Form 5000.24) pays tax on beer removed for consumption or sale. The Brewer's Report of Operations reports what the brewery physically did, and is due by the fifteenth day after the end of the reporting period. Note that the form split is not symmetric: Form 5130.9 is the one monthly filers must use, and quarterly filers may use either 5130.9 or the quarterly-only Form 5130.26.

Filing frequency is set by tax liability, not by brewery size, and it can change underneath you:

The rates themselves were reduced under the Craft Beverage Modernization and Tax Reform Act and made permanent in December 2020. A domestic brewer producing no more than two million barrels a year pays $3.50 per barrel on its first 60,000 barrels, then $16 per barrel; all other brewers and importers pay $16 per barrel on the first six million barrels, and $18 per barrel above that. A barrel is 31 US gallons. Current rates and forms are published by the TTB, and you should confirm against it rather than any vendor's summary.

One further change is worth raising with vendors now: TTB is piloting a combined return-and-report form under Industry Circular 2025-1, which merges the two filings for participating brewers. Ask whether a shortlisted system supports the pilot form as well as 5000.24 and 5130.9/5130.26.

The system implication is precise. Because the reduced rate applies to the first 60,000 barrels removed for consumption or sale in a calendar year, your software has to track taxable removals against a running calendar-year total and change the rate applied once the threshold is crossed. A brewery approaching 60,000 barrels that cannot see its position against that threshold in real time will misstate its excise liability.

There is a second implication that catches groups out, and it is the strongest single argument for a system with real multi-entity capability. Under 27 CFR 25.152, both tests apply at the level of the controlled group, not the individual brewery: combined production across the group is what measures against the two-million-barrel limit, and the 60,000-barrel allowance is a single group allowance that a brewer operating more than one brewery must apportion between them. A group running two or three breweries on separate instances, each tracking its own removals, has no reliable view of the number that actually determines its rate — and apportionment is a decision someone has to make and defend, not a figure a single-site system can calculate for itself.

Equally, the Report of Operations demands categories most charts of accounts do not carry natively — beer produced by fermentation, received in bond, removed for consumption or sale, removed without payment of tax, returned to the brewery, and losses including theft. If losses are posted as generic inventory adjustments, the report cannot be produced from the ledger, and someone will rebuild it by hand every period.

Ask to see the Report of Operations generated from transactional data during the demo, using categories that map to the form. A datasheet line reading "TTB reporting" can mean anything from a filed-form-ready report to a raw data export, so make the vendor show you which it is.

Brewery Production Requirements an ERP Must Cover

Four requirements separate a system that fits a brewery from one that merely runs a factory.

Yield and loss as first-class data. Beer loses volume at every stage — trub and hop absorption in the brewhouse, yeast and sediment in the cellar, line loss and foam at packaging. A brewery that cannot attribute loss to a stage cannot cost a batch properly, and cannot separate a genuine process problem from a measurement one. Generic ERP tends to treat this as scrap against a single work order; brewing needs it stepwise.

Kegs as returnable assets, not packaging. This requirement is easy to miss at selection, and its closest analogues sit outside food and beverage — gas cylinders, returnable crates, chemical drums. A keg is a durable asset that leaves your site full, may sit at a distributor or bar for months, carries a deposit that is a liability on your balance sheet, and returns to be cleaned and refilled many times over. Modelling kegs as consumable packaging — which is how a generic ERP will treat them unless it is explicitly configured otherwise — loses the float, the deposit liability and the loss rate simultaneously. Ask specifically how a shortlisted system tracks keg population, deposits and unreturned units, because for a distribution-led brewery the keg float can represent a substantial share of capital employed, and it is rarely visible in the accounts if kegs are treated as packaging.

Tank and vessel scheduling. Fermentation and conditioning occupy a physical vessel for a period set by biology, not by labour. Capacity planning in a brewery is therefore measured in tank-days, and for many breweries — particularly those with a lager-heavy or long-conditioning portfolio — cellar space binds before brewhouse throughput does. A system that plans only against labour and equipment hours will produce schedules the cellar cannot execute.

Dual units of measure throughout. Production thinks in barrels, hectolitres and gallons; sales thinks in cases, kegs, packs and units; tax thinks in barrels. Conversions have to be consistent and auditable across all three, and a rounding convention that differs between the sales document and the tax report will eventually cost you a reconciliation.

Brewery ERP Comparison

The table below groups the platforms that come up most often in brewery evaluations we see. The selection and the categories are ours. Capability claims — especially the general-ledger column — should be confirmed in a demo against your own chart of accounts, because scope in this market changes and several vendors position production platforms using ERP language.

Three patterns are worth naming. First, the brewery-native tier is strong on production and compliance and light on finance — the right trade for many single-site breweries, the wrong one for a group consolidating entities. Second, the general-ERP tier depends heavily on the implementation partner, because brewery fit lives in configuration, the unit-of-measure model and the TTB reporting layer rather than in the core product. When you evaluate NetSuite, Acumatica or Business Central for a brewery, you are really evaluating that partner's beverage practice. Third, the vendor landscape is consolidating — Ekos and Ollie are both Next Glass products, and Deacom belongs to ECI Software Solutions — so check ownership before you assume two rows on a shortlist represent two independent bets.

Breweries running heavy formulation, or seltzer and spirits alongside beer, should also look outside the brewery label. BatchMaster and Deacom handle formula management, yield variance and lot genealogy in regulated environments, and much of the same requirement applies under a different vocabulary. Our food and beverage ERP requirements guide covers that ground in more depth.

Buying in a Contracting Market Changes the Business Case

Much brewery software content still assumes growth. The market no longer does, and that should change how a brewery justifies a system.

The Brewers Association reported that the number of operating US craft breweries fell to 9,578 in 2025 — a net decline of 2.9%, the first net decline after more than a decade of growth, and the second consecutive year in which brewery closings outpaced openings — and characterised the period as a year of correction for craft beer. Its craft brewer definition covers brewers holding a TTB Brewer's Notice who produce six million barrels a year or less and are less than 25% owned or controlled by a beverage alcohol industry member that is not itself a craft brewer, so that count reflects thousands of small producers rather than the national brands.

In a contracting market the ERP business case is not "support our growth". It is narrower and more defensible:

• Know true cost per barrel and per SKU, so unprofitable packaging formats and accounts can be cut deliberately rather than discovered late.
• Reduce working capital tied up in raw materials, packaging and an oversized keg fleet.
• Cut the finance cost of compliance, where TTB and state reporting is currently assembled by hand every period.
• Protect margin on distribution, where chargebacks, keg losses and freight quietly erode a line that looks healthy at the gross level.

Building the case on those four points tends to point towards a smaller, better-fitted system than a case built on growth not yet won.

How to Choose a Brewery ERP

1. Fix your scope before looking at software. Write down annual barrelage, sites, packaging formats, whether you self-distribute, and every production step between malt intake and taxable removal. Breweries that skip this buy a production platform, then discover a year later that they needed financials.
2. Decide the finance question first. Establish whether you need a system with its own general ledger or a best-of-breed production platform syncing to an accounting package. This one choice eliminates most of the market and belongs before demos, not during them.
3. Prove the TTB path end to end. Have the vendor produce a Brewer's Report of Operations and an excise return from transactional data, including a loss event and a removal without tax, using your own categories. Groups should also see the 60,000-barrel running total maintained across all breweries under common control, not per entity.
4. Test the keg model. Ask how the system tracks keg population, deposits, ageing at customer sites and unreturned units, and whether that reconciles to the balance sheet.
5. Check the unit of measure chain. Confirm that barrels, cases, kegs and packs convert consistently across production, sales and tax documents, and ask which rounding convention applies.
6. Schedule against tanks. Confirm the system plans capacity against vessel occupancy and conditioning time, not only labour and machine hours.
7. Weight the partner as heavily as the product. For general-ERP options especially, ask how many brewery implementations the specific team has delivered, at what barrelage, and request a reference at your scale.
8. Model total cost over five years. Include implementation, the accounting package if it stays separate, integration maintenance, and the cost of re-implementing when you add a site. Our ERP selection criteria guide sets out a scoring framework you can apply directly.

Frequently Asked Questions

What is the difference between brewery ERP and brewery management software?

Brewery management software runs production, inventory and compliance reporting, and usually syncs to an external accounting package such as QuickBooks, Xero or Sage. Brewery ERP includes the general ledger and financial reporting itself, along with multi-site and distribution capability. For a single-site brewery the first is often the better fit; for a group with several entities and intercompany movements it rarely is.

Do I need ERP if I already use QuickBooks and a production app?

Not necessarily. That combination works well for many breweries and is cheaper to run. The signals that it has stopped working are a month-end close that depends on manual reconciliation between the two systems, a cost per barrel nobody trusts, a second site or legal entity, and federal reports assembled by hand each period.

Can general ERP like NetSuite or Acumatica run a brewery?

Yes, and many breweries run on them, but the fit comes from configuration and the implementation partner rather than the core product. You are buying a beverage practice as much as a platform, so ask how the unit-of-measure model, loss categories, keg assets and TTB reporting will be built, and who has done it before at your barrelage.

How should software handle excise tax reporting?

It should produce the Brewer's Report of Operations and the excise return from transactional data, not from a spreadsheet. Because the reduced $3.50 per barrel rate applies only to the first 60,000 barrels removed in a calendar year, the system must also track cumulative annual removals and switch rate once that threshold is passed. Groups need that running total at controlled-group level, with the allowance apportioned between breweries.

Why do kegs need special treatment in a brewery system?

A keg is a returnable asset that carries a deposit, circulates for years and represents real capital. Treated as consumable packaging — which is how a generic ERP will model it unless configured otherwise — you lose sight of fleet size, deposit liability and loss rate at once. For a brewery that distributes in kegs, the float can tie up a substantial amount of capital.

Is a taproom point of sale enough if most of my sales are on-site?

For a brewpub selling nearly everything across the bar, a point-of-sale system plus an accounting package can be sufficient. It becomes insufficient as soon as you package for retail, sell through a distributor, or need production costing, because these systems record sales rather than production, inventory consumption or tax-determined removals.

What does an implementation usually involve?

Expect recipe and bill-of-materials setup, unit-of-measure configuration, opening inventory and keg counts, TTB category mapping, and either a general-ledger build or an accounting integration. Timelines vary widely with scope and data quality, so ask vendors for a plan tied to your barrelage and site count rather than an average.

Does brewery software handle state alcohol reporting as well as federal?

Federal reporting is standardised; state requirements are not, and they vary in format, frequency and whether they can be filed electronically. Confirm native support for each state where you hold a licence or distribute, and treat a working federal report as no guarantee of state coverage.

Related Resources

• Food and Beverage ERP Requirements — the requirement set brewery ERP inherits, in full
• Top 10 Food and Beverage ERP Systems — the wider vendor field, independently profiled
• Food and Beverage ERP — the parent industry hub and its selection guidance
• BatchMaster ERP — process manufacturing ERP for formulation-heavy producers
• Deacom ERP — single-system process ERP with strong lot genealogy
• Cannabis ERP Software — the closest regulated-inventory parallel, useful if you also hold cannabis licences
• Accounting Software for Manufacturing — where the finance-only route makes sense
• ERP Selection Criteria — a scoring framework for shortlisting
• ERP TCO Calculator — model five-year cost before you commit
• Build Your Requirements — produce a vendor-ready brewery requirements document