When sourness is an infection

Two very different reasons a beer is sour

A Berliner weisse, a gose or a lambic is sour because a brewer deliberately introduced lactic acid bacteria or wild yeast, on purpose, often over months of careful management. A lager or a pale ale that tastes sour was not meant to, and something got into it that should not have.

Both can taste similarly tart on first sip. The difference is what else is happening alongside that sourness, and whether the style you ordered was ever supposed to be sour in the first place.

What an infection actually smells and tastes like

Accidental sourness rarely arrives alone. Look for a thin, almost vinegary edge rather than clean lactic tartness, sometimes paired with an off aroma like solvent, barnyard or vomit at more extreme levels. The beer may also look different: excess foaming when the can or bottle is opened, or a hazy appearance in a beer that is supposed to be bright, are both classic signs.

A style that is supposed to be clean, like a pilsner or a west coast pale ale, tasting sharply sour or acidic is close to a certain sign of infection rather than intention.

Timing matters too. A can that tasted fine a month ago and now tastes sour has almost certainly picked up an infection since packaging, since intentional sour styles are sour from the day they leave the brewery, not gradually over time.

Where infections usually get in

Bacteria and wild yeast are everywhere in a brewery environment. They get a foothold wherever sanitation has a gap: a worn gasket, a plastic hose with fine scratches that trap residue, a fermenter valve that was not fully broken down and cleaned, or a keg that was not properly sanitised before refilling.

Warm, humid conditions accelerate any infection that does take hold, which is one reason careful temperature control matters as much in an Indian brewery's cleaning schedule as it does in the actual fermentation.

Plastic parts are a particular risk over time. Rubber and plastic fittings develop microscopic scratches with repeated use, and those scratches shelter organisms that a normal cleaning cycle simply cannot reach. Most experienced quality teams replace soft goods like gaskets and hoses on a fixed schedule for exactly this reason, rather than waiting for them to visibly fail.

Why this is a serious quality problem, not a minor one

Once a piece of equipment is infected, the organism can persist and contaminate future batches through the same route, batch after batch, until someone finds and fixes the specific point of contamination. This is why an experienced quality team treats an unexpected sour batch as an investigation, not just a batch to dump.

The fix is rarely a single step. It usually means tracing the batch back through every piece of equipment it touched, replacing anything with scratches or wear that cannot be properly cleaned, and rebuilding the cleaning and sanitising schedule around what was found.

A single infected batch dumped down the drain is a real cost, but a brewery that ignores a pattern and keeps brewing through it risks losing a customer's trust permanently, which is a far larger cost than the lost beer.

How you, as a drinker, can tell

Start with the style. If the can or the menu says pilsner, pale ale or stout and the beer tastes sour, that is your first and strongest signal, because none of those styles are meant to be tart at all.

If you are unsure whether a sour beer is meant to be sour, ask what style it is meant to be, since a genuine gose or Berliner weisse will usually say so clearly on the label or the tap list. A brewery proud of an intentional sour beer will tell you exactly how they made it.

Building the habit of asking why

The single most useful question in sensory work is not what does this taste like, but why does it taste like this. A trained taster treats every unexpected flavour as a question about the process behind it, the same instinct that helps with reading a metallic note back to a specific piece of equipment rather than just noting that something tastes wrong.