Craft Seltzer and Hard Kombucha: How to Adapt Your Brewery ERP for New Formats

Beyond Beer: The ERP Challenge Nobody Warned You About

Your brewery was built around malt, hops, yeast, and water. Your ERP was probably set up the same way. Then someone on your team pitched a hard seltzer line, a taproom regular asked about kombucha on draft, and suddenly you're managing sugar washes, fruit purees, SCOBY cultures, and carbonation profiles that have nothing to do with your flagship IPA.

Craft seltzer revenue in the U.S. still holds a meaningful share of the RTD market, and hard kombucha is carving out a loyal niche among health-conscious drinkers. For small and mid-sized breweries, these formats offer real margin opportunities — but only if your production systems can actually handle them. Most brewery management software was designed for grain-to-glass workflows. When you bolt on seltzer and kombucha, cracks appear fast: recipes that don't fit your ingredient categories, fermentation curves that look nothing like ale or lager profiles, and inventory items that expire on completely different timelines.

This article walks through the practical steps to adapt your ERP — your recipes, batch tracking, inventory, and reporting — so that beyond-beer formats run as smoothly as your core beer lineup.

Why Seltzer and Kombucha Break Traditional Brewery Workflows

Before diving into solutions, it helps to understand exactly where these formats diverge from standard beer production.

Craft Seltzer: A Fundamentally Different Fermentable

Hard seltzer starts with a sugar wash — typically dextrose, cane sugar, or agave dissolved in water. There's no mash, no lauter, no boil in the traditional sense. Yeast selection matters enormously (many brewers use champagne yeast or specialized seltzer strains), and the real work happens post-fermentation: carbon filtration to strip color and flavor, precise carbonation targeting (usually 2.8–3.2 volumes CO₂, higher than most beers), and flavoring with natural extracts or fruit concentrates.

For your ERP, this means:

• Recipe structure: No grain bill. Your recipe needs to accommodate sugar types, nutrient additions (DAP, Fermaid-O), flavoring agents, and fining/filtration steps.
• Fermentation monitoring: Seltzer fermentations often finish in 3–5 days with aggressive yeast, and you're watching gravity drop to near 0.996–1.000 — well below typical beer terminal gravity.
• Packaging variables: Seltzer is almost always canned. You need to track carbonation levels, dissolved oxygen (critical for shelf stability without hops), and can seam integrity per batch.

Hard Kombucha: Living Cultures and Dual Fermentation

Hard kombucha adds another layer of complexity. Traditional kombucha undergoes primary fermentation with a SCOBY (symbiotic culture of bacteria and yeast), producing acetic and lactic acids, trace alcohol, and a signature tang. To push ABV above 0.5% and into "hard" territory, brewers introduce a secondary fermentation — often with champagne yeast or a kombucha-specific strain — along with additional sugar or fruit juice.

The ERP implications here are significant:

• Multi-stage fermentation: You're tracking two distinct fermentation phases with different organisms, temperatures, and durations. Primary might run 7–14 days at 75–85°F; secondary another 5–10 days at cooler temps.
• pH and acidity tracking: pH is a critical control point (typically 2.8–3.5 for finished kombucha). If your ERP only tracks gravity and temperature, you're missing the most important data point.
• Living product, shorter shelf life: Hard kombucha is often unpasteurized. Shelf life might be 60–90 days refrigerated. Your inventory system needs to handle this aggressively — standard beer FEFO timelines won't cut it.

Adapting Your Recipe and Batch Tracking

Rebuild Your Ingredient Categories

The first step is expanding how your ERP categorizes raw materials. Beer-centric systems typically bucket ingredients as malts, hops, yeast, and adjuncts. For seltzer and kombucha, you need additional categories that are treated as first-class citizens, not afterthoughts stuffed into "adjuncts":

• Fermentable sugars: Dextrose, cane sugar, agave, honey, fruit juice concentrates — each with different gravity contributions per pound.
• Cultures: SCOBY inventory (yes, you should track this — healthy SCOBYs are a production asset), kombucha-specific yeast blends, champagne yeast.
• Flavoring agents: Natural extracts, fruit purees, botanicals. Track lot numbers — flavor consistency batch-to-batch depends on it.
• Nutrients: DAP, yeast nutrients, and fermentation aids that beer recipes rarely require.
• Filtration and fining: Activated carbon, bentonite, chitosan — especially for seltzer clarity.

In systems like BrewERP, you can define custom ingredient types within your recipe builder, which means your seltzer sugar wash recipe and your kombucha tea base recipe live alongside your beer recipes without awkward workarounds. The key is setting this up before your first production batch, not retrofitting it after you've got 30 batches of messy data.

Configure Multi-Stage Batch Workflows

A standard ale might follow: mash → boil → ferment → condition → package. Seltzer looks more like: dissolve → ferment → filter → carbonate → flavor → package. Kombucha runs: brew tea base → primary (SCOBY) → secondary (yeast) → flavor → condition → package.

Your batch tracking needs to accommodate these different stage sequences. Practically, this means:

• Creating batch templates per product type so your brewers aren't manually re-entering steps every time.
• Allowing custom data fields per stage — pH readings for kombucha, dissolved oxygen for seltzer, carbonation volumes at packaging.
• Tracking tank usage across overlapping stages, since your kombucha might occupy a fermenter for three weeks while seltzer turns a tank in under a week.

Fermentation Monitoring: Different Curves, Different Alerts

If you're using any kind of fermentation monitoring — manual gravity logs or integrated sensors — your alert thresholds need recalibration for these formats.

For seltzer, a stalled fermentation at 1.010 is a problem that tastes like residual sweetness and off-flavors. Your system should flag gravity stalls earlier and more aggressively than it would for, say, a 1.060 OG stout that's expected to finish at 1.014.

For kombucha, temperature excursions matter differently. A SCOBY at 90°F produces excessive acetic acid and vinegar character. A secondary yeast fermentation that drops below 60°F might stall completely. Your monitoring alerts should reflect these tighter windows.

If your ERP supports configurable alerts — BrewERP, for instance, pushes real-time Telegram notifications when fermentation parameters drift outside your set thresholds — set up separate alert profiles for each product type. One alert configuration should not govern your saison and your seltzer.

Inventory Management: FEFO Gets More Aggressive

Beer is relatively forgiving on shelf life. A well-packaged IPA might have 120 days; a pasteurized lager, 180+. Hard seltzer is comparable if packaged with low dissolved oxygen. Hard kombucha, though, is a different animal.

Unpasteurized kombucha continues to ferment slowly in the package. At 90 days, you might have overcarbonation, flavor drift, or — worst case — packages that blow. Your inventory system must enforce strict FEFO (First Expired, First Out) rotation and surface items approaching expiration before they become a liability.

Actionable steps:

• Set per-SKU shelf life defaults — 90 days for kombucha, 180 for seltzer, and your existing timelines for beer.
• Configure expiration warnings at 75% of shelf life (roughly 67 days for kombucha) so your sales team can push aging inventory.
• Track cold chain compliance. Kombucha that breaks refrigeration for 48 hours during distribution isn't the same product anymore.

Reporting and Compliance: Know Your Numbers by Format

When you add seltzer and kombucha to your portfolio, your aggregate numbers become less useful. A blended COGS per barrel across beer, seltzer, and kombucha tells you almost nothing — seltzer margins and kombucha margins operate on entirely different cost structures.

Break Out P&L by Product Line

Your ERP reporting should segment revenue, cost of goods, and margin by product type. Seltzer typically carries lower ingredient costs but higher packaging and flavoring costs. Kombucha carries higher labor costs (longer process, more QC touchpoints) but can command premium pricing. If your reporting lumps everything together, you can't make informed decisions about which formats to scale.

Exporting segmented P&L reports — whether as PDFs for your accountant or data pulls for your own analysis — should be a routine monthly practice. Understanding that your kombucha line generates 45% gross margin while seltzer sits at 55% shapes how you allocate tank space, labor, and marketing dollars.

TTB and Excise Tax Considerations

In the U.S., hard seltzer and hard kombucha may be classified differently than beer for TTB purposes depending on their base (sugar vs. malt). Seltzer made from a sugar base is technically a "sugar-based specialty" and may be taxed as a spirit or require a different permit. Kombucha that stays under 0.5% ABV is non-alcoholic; above that threshold, it's an alcoholic beverage. Your batch records need to clearly document ABV per batch, base ingredients, and classification — because an auditor won't accept "it's basically beer" as an explanation.

Getting Started Without Overcomplicating Things

The temptation with new formats is to overthink the system and delay production. Don't. Start with these priorities:

1. Set up ingredient categories and recipe templates for your first seltzer or kombucha product before you brew it.
2. Configure fermentation alert thresholds specific to the format — don't reuse your beer defaults.
3. Adjust FEFO shelf life settings for finished inventory, especially for unpasteurized kombucha.
4. Create separate product-line reports so you can evaluate margin independently from day one.
5. Document your process in your batch records with enough detail for regulatory compliance.

None of these steps require a massive ERP overhaul. They require intention — setting up the data structures correctly before production starts, so that every batch after the first one flows naturally through your system.

Your Brewery Is Evolving. Your Systems Should Too.

Beyond-beer formats aren't a fad — they're a permanent expansion of what craft producers make. The breweries that thrive with seltzer and kombucha aren't the ones with the biggest budgets; they're the ones that treat production data as seriously for a sugar wash as they do for a double IPA.

If you're exploring seltzer, kombucha, or other alternative formats and want an ERP that handles multi-format production without fighting the software, give BrewERP's 14-day free trial a look. It's built for exactly this kind of flexibility — from grain-to-glass to sugar-to-can and everything in between.