ERP, MES and LIMS in a brewery: a systems map for IT teams

The layers, from sensor to boardroom

A useful way to picture brewery systems is as layers, similar to the ISA-95 model used in manufacturing:

• Field and control: sensors, valves and PLCs that run the process.
• Supervision: SCADA screens and a historian storing time series data.
• Manufacturing operations: MES for production orders, batch records and genealogy, plus LIMS for lab results.
• Business: ERP for finance, purchasing, inventory, sales and planning.

Around these sit specialist tools: excise and compliance registers, warehouse management, maintenance systems, quality management and BI platforms.

ERP: the commercial backbone

The ERP holds materials, recipes in the form of bills of materials, purchase orders, stock, sales orders, invoices and the general ledger. In a brewery it knows that a brew consumed so many kilograms of malt and produced so many hectolitres of wort, but usually only as summary postings.

Beer adds complications. State excise means stock may be held in bond, with duty paid only when it leaves. Returnable bottles and crates are tracked as assets. One liquid becomes many state SKUs. Good ERP design handles all of this. Poor design pushes it into spreadsheets.

MES: what happened on the floor

A manufacturing execution system records production in detail: which brew went into which tank, the actual temperatures and times against the recipe, the materials and lot numbers used, who signed off each step and how much beer each stage produced. That chain of records is called genealogy. It lets a brewery trace a can on a shelf back to the malt lot, hop lot and yeast generation.

Smaller breweries often lack a formal MES. Their batch records live in brew logs, spreadsheets or a brewery management package. The function still exists. It is just less connected.

One brewing detail matters for MES design: beer changes volume as it moves. Wort shrinks as it cools, some is lost with spent yeast and trub. Filtration and transfers also leave beer in lines. A batch that started as 100 hectolitres in the brewhouse may reach the bright tank noticeably smaller. MES and ERP must expect these losses rather than flag every batch as an error.

LIMS: the lab's record

A laboratory information management system stores test results: gravity, alcohol, bitterness, colour, pH, dissolved oxygen, micro plates and sensory scores. It links each result to a sample point and a batch, applies specification limits and records who approved the result.

LIMS data decides whether a batch can be released. Our guide to beer quality data for data teams explains the common tests and their quirks. When LIMS is missing, results end up in spreadsheets with no audit trail, which is a risk during an inspection or a complaint investigation.

Where the integrations live

Most of the trouble in brewery IT sits between systems, not inside them:

• ERP to MES: production orders go down, consumption and output come back up. Mismatched units or timing create stock differences.
• MES to SCADA: recipes and batch IDs go down, actual values come back. Without batch IDs, historian data is hard to use.
• LIMS to MES and ERP: release status must block stock from being shipped until quality approves.
• ERP to excise registers: production and dispatch volumes must match what is reported to the state, in the state's format.

Before starting a project, draw this map for the specific site. Mark which links are automated, which are manual and who owns each one.

The excise layer is not optional

In India, excise reporting can be the most sensitive integration of all. States differ in what they require and how. Some use online portals with their own formats. Volumes reported for production, transfers, dispatch and losses must agree across systems. IT teams should treat excise data flows as compliance controls, with reconciliation and audit trails built in from the start. Work with the excise and finance teams. Bring in advisers who know the current rules in each state.

Common project traps

• Building a data platform before agreeing on a batch ID that every system shares.
• Treating the brewery like a discrete manufacturer. Beer moves in volumes that change with losses, dilution and blending.
• Ignoring the people who enter data by hand on the floor. If the screen is awkward, the data will be wrong.
• Underestimating plant network security. Read-only access through a secure zone is the norm.

Once the map is clear, analytics work becomes far easier. See data and AI in breweries, wineries and distilleries for where that leads.

Common questions

What is the difference between ERP and MES in a brewery?

ERP handles the business side, such as purchasing, stock, sales and finance. MES records what actually happened during production, batch by batch, including materials used and process values.

Does a small brewery need a LIMS?

Not always as a dedicated product, but it needs controlled lab records linked to batches. Many small breweries start with a structured spreadsheet or a brewery management tool.

Why is excise reporting so hard to integrate?

Each state sets its own requirements and formats. Volumes must reconcile across production, transfers and dispatch. It needs to be treated as a compliance control.