Ask Mr. Wizard

The Intricacies of Shelf Stability

TroubleShooting

Brian Andrews — Las Vegas, Nevada asks,
Q

Talk to us about methods used to stabilize beers, ciders, seltzers, and such that may have fermentables in the package.

A

Wow, this is quite the rabbit hole of a question. Let’s start out with why a fermented beverage, be it beer, wine, seltzer, cider, or some other tasty tipple, may be packaged with fermentable sugars. The most common reason for brewers to have fermentable sugars in the package is for bottle conditioning. The idea, of course with bottle conditioning, is to add enough fermentables to achieve the carbonation goals of whatever is being carbonated in the package. Add too little or too much priming sugar and the carbonation is going to be off. This is why it’s so important to package completely fermented beer and to know the volume of beer being primed. But that’s not what this question is about. You want to know how to end up with fermentable sugars in the glass without having to worry about over-carbonated or exploding beverages.

Rabbit Hole #1; Exploding Packages

Most homebrewers hear stories about bottle bombs when first getting into homebrewing, and some of us have first-hand experience with these problematic packages. Aluminum cans started to really become popular with craft brewers about a decade ago and with this new craft beer package, the occasional story of an exploding can was heard. At about the same time an increasing number of craft brewers began brewing beers with lots of fermentables in the finished beer. Heavily fruited beers, enormous imperial stouts flavored with all sorts of interesting ingredients, pastry IPAs, and smoothie sours began popping up in the market. Beers with lots of unfermentables, especially lactose and maltodextrin, also became increasingly popular, but these carbohydrates shouldn’t result in refermentation in the package. At first, these beers were primarily draft beers served in limited volumes because brewers were pushing the envelope of style. Beer lovers wanted these potables in packages more portable than growlers, so breweries began canning and bottling these beers. That was when exploding packages really burst onto the scene.

Most homebrewers hear stories about bottle bombs when first getting into homebrewing, and some of us have first-hand experience with these problematic packages.

Although some brewers took the odd approach of expecting customers to handle these packages with the deft skills of a beer-bomb expert, many breweries hit the pause button. A few of the cheekier breweries came up with clever packaging warning of impending explosions and others criticized consumers for not being more careful with these delicate products. The cautious crowd were developing processes and quality control (QC) practices to address this very real problem and other brewers simply decided to steer clear of the problem entirely by not producing these products. Breweries are businesses and it has become very difficult not to brew what so many beer consumers want; as demand grows, so does the number of breweries brewing these types of beers.

The rabbit hole of exploding packages presents two useful takeaway ideas for homebrewers wanting to minimize the risk of unwanted secondary fermentation. The first is not much fun, but is pragmatic; don’t bottle or can beer with excess fermentable sugars. For bottle-conditioning homebrewers, this is not a huge limitation because lots of fermentables in the package doesn’t work with this method. The other takeaway idea is to produce these beers, package into kegs, force carbonate, store the beer as cold as possible without freezing, which is not a problem for some of these beers chocked full of soluble solids (sugar) that decrease the freezing point to ~25 °F (~-4 °C), and keep a hawk-eyed watch for signs of fermentation. Draft beer carbonation can always be reduced by venting a keg, and an uptick in carbonation level with these sweet brews is a good signal that it’s time to have some friends over to clear out the keg for another brew.

Rabbit Hole #2; Peeking Over the Fence

Although flash and tunnel pasteurization systems are not new to U.S. craft breweries, many breweries that own these incredibly useful tools keep quiet about the topic because of the biases that accompany pasteurized beer. I have one thought about these biases . . . whatever. As more breweries started to wrestle with the exploding package dilemma, the number of craft breweries with pasteurizers began to grow.

The silver bullet to dealing with fermentables in the package is a tunnel pasteurizer that runs the entire package (beer, bottle, and cap, or beer, can, and lid) through the pasteurization process. Most commercially pasteurized beers are exposed to between about 10 and 100 pasteurization units (PUs), where 1 PU is equal to 60 seconds at 60 °C (140 °F) or 0.6 seconds at 67 °C (152.5 °F). The major flavor downsides to pasteurization, especially in beers with high levels of dissolved oxygen (above about 100 ppb), are accelerated oxidation and the development of cooked aromas during the process. Once pasteurization is complete, the risk of microbiological growth in the package drops as the PU level increases and the accelerated aging during the heating process stops. Brewers determine PU targets based upon several variables including baseline micro levels, beer properties, and expected shelf life. Another set of real problems with this silver bullet are capital expense, energy use, and space requirements.

A more compact and less costly pasteurization system is an in-line flash pasteurizer, also called high-temperature short-time or HTST pasteurization. HTST systems are the norm for milk pasteurization. The major difference between milk and beer pasteurization, however, is that the goal of milk pasteurization is to kill pathogenic microbes and the goal of beer pasteurization is to kill spoilage microbes. That’s why it is totally normal for refrigerated milk to sour when stored for too long, while still being safe to drink. The challenge with using HTST systems for beer is preventing re-contamination with spoilage bacteria during filling. For this reason, tunnel pasteurizers remain the gold standard for beer.

What on earth does any of this have to do with homebrewing? Not much! But that does not stop homebrewers from peeking over the fence and wondering what craft brewers are doing, just like some craft brewers did when they peeked over the fence into larger craft- and macro-brewing operations. However, homebrewers can batch pasteurize their beer. Although not common nor practical for commercial brewers to use, bottles or cans of beer can be submerged in hot water. The thermal cycle is similar to a tunnel pasteurizer, just with a different setup. I will leave the design specifics for another day, but a simple system could be configured from a brew kettle, a cooler or two, and a water pump; load the bottles into the cooler(s), gravity drain water back to the kettle, and use the pump to deliver hot water to the cooler(s). A key requirement for this method is a counter-pressure filler. It is also best to have as little yeast in the package as possible because the heat treatment will definitely lead to cell autolysis.

One closing thought about pasteurization. It works.

Rabbit Hole #3; Utilizing Chemistry

The modern person is accustomed to magic pills that solve all sorts of problems. Wouldn’t it be great if there was a magic pill that could be added to backsweetened beverages to prevent fermentation in the package? Yeah, yeah, that’s a thing. Maybe. Although potassium metabisulfite (KMS) and potassium sorbate both do a great job of slowing microbial activity in packaged beverages, neither completely prevent re-fermentation. And not all microorganisms are equally affected. Sorbate is generally more effective at inhibiting yeast than bacteria, whereas sulfites are more effective at inhibiting, and even killing, certain bacteria and wild yeast.

Because both of these compounds are weak acids, their ionic states are pH dependent and their potency as antimicrobial preservatives changes with pH. What this means in practice is that the pH of the beverage being stabilized must be factored into the determination of dosage rates. Sulfite usage has another layer of complexity because sulfites can react with beverage compounds and become bound. Bound SO2 has no preservative effect and the only way to know how much free SO2 is present is to run an analysis after KMS additions. (As an aside, you can dive much deeper down this rabbit hole by visiting BYO’s sister publication at Winemakermag.com as sulfite levels are a big topic of discussion for winemakers). Sorbate is easier to deal with because the target levels are simply a function of pH and target organism.

Digging any further into this topic quickly becomes similar to water chemistry. The takeaways about the use of sulfite and/or sorbate to inhibit changes in backsweetened beverages are that both of these preservatives have their uses, neither are absolute, dosing rate depends on cell density in the package, and a fairly complete understanding accompanied by some wet chemistry is required to get it right. In other words, read more about this advanced topic because there is no one-size-fits-all solution.

What’s the Point?

This entire discussion leaves one wondering how to go about backsweetening at home. My tendency leans towards a combination of efficacy and simplicity. A good start to any of these methods is yeast removal; gravity sedimentation, with or without finings, and/or filtration are the common options. Also select flocculent yeast strains that are easier to leave behind when racking.

Beverage pH was not discussed earlier in the context of secondary fermentation, but suffice to say, bottle conditioning becomes trickier as pH drops. I would take advantage of this and push my beverage pH down as low as possible without goofing up the flavor profile. No reason to make things easier for the microbes we want to stop. To finish things off, I would stick to draft-only products, keep these gems chilly-chill, be vigilant with the QC through regular “sampling.”

Response by Ashton Lewis.