A brewery's recall plan is a short document that says who decides, what gets stopped in the first hour, how a brew is traced to its kegs, cans and accounts, who is told, and what happens to the beer. FDA's rule requiring a written recall plan, 21 CFR 117.139, sits in the part of the food rules that doesn't apply to beer at a permitted, registered brewery. So a plan is usually not required by that rule. Distributors, chain buyers and insurers ask for one anyway, and the day a can bursts on a shelf is a bad day to write it. Beer recalls are real: glass, refermenting cans, cleaner in a keg, an allergen not on the label. Below are the twelve sections, with an example, and a file.
The short version
- Two named people who can stop sales without asking anyone.
- A list of the faults that would trigger a recall, written in advance.
- Every package carries a lot code that leads back to one brew.
- Delivery records that say which lot went to which account.
- A notice with five things: the beer, the package, the lot, the reason, what to do.
- TaroStack traces a brew to its kegs, cans and accounts in one report. More below.
Is a brewery required to have one?
| Rule | What it says | For beer |
|---|---|---|
| 21 CFR 117.139 | A written recall plan for food with a hazard requiring a preventive control | Part of subpart C |
| 21 CFR 117.5(i) | Subparts C and G don't apply to alcoholic beverages at a facility that needs a Treasury permit and registers with FDA | So 117.139 doesn't reach beer there |
| 21 CFR 7.42, 7.49 | FDA's guidance on how a firm conducts a recall | Applies to any FDA-regulated product |
A non-alcoholic product made at the brewery in any volume may not be covered by that exemption. And your state, your distributor's contract and your insurer may each require a plan of their own. This is general information, not legal advice.
What gets a beer recalled
| Fault | Hazard | How far it goes |
|---|---|---|
| Glass in a bottling run | Injury | To the drinker |
| Cans or bottles refermenting | Bursting packages | To the drinker |
| Caustic or acid left in a keg or tank | Chemical burn | To the account, and the drinker if poured |
| Lactose, nuts, wheat or another allergen not on the label | Allergic reaction | To the drinker |
| Wrong beer in the package, off flavor, low fill | None to health | Usually accounts only: a withdrawal |
The last row matters. Pulling a beer for quality with no hazard is a market withdrawal, not a recall, and the plan should say so, so that nobody announces a "recall" for a flat keg.
The plan
A made-up small brewery.
| Section | Example |
|---|---|
| Who decides | Head brewer; backup, taproom manager. Either can stop sales at once |
| First hour | Stop selling the beer. Put what's in the building on hold. Pull the brew sheet and packaging lots |
| Trace | Brew B-142: canned Nov 12 as lot B-142-C, 62 cases; kegged as B-142-K, 8 half-barrels. Accounts from the delivery records |
| How far | Glass or an allergen: to the drinker. No hazard: accounts only |
| Tell accounts | Phone, then email, the same day |
| Tell the public | For a hazard that reached drinkers: website, taproom door, social accounts; a press release sent to FDA for comment first |
| Tell regulators | The FDA recall coordinator; the state alcohol and health agencies; the distributor |
| Check it worked | Call back each account within 48 hours. Count cases and kegs held, returned or destroyed against what was shipped |
| The beer | Returned and dumped, counted, with a witness |
| Afterwards | Cause, fix and date, in writing |
| Practice | A mock recall once a year |
The notice to accounts
FDA's guidance on recall communications gives the contents, and they fit on half a page:
| Say | Example |
|---|---|
| That it's a recall, and urgent | URGENT: BEER RECALL, in the subject line and at the top |
| The product, package and lot | Citrus IPA, 16 oz cans, lot B-142-C, canned November 12, code on the can bottom |
| The reason and the hazard | Cans from this lot are refermenting and may burst |
| What to do now | Stop selling. Move cases to a cool place, away from people. Don't open or shake them |
| What happens next | We'll collect them Thursday and credit your account in full |
| How to reply | Call or email with how many cases you have, by tomorrow noon |
No apology paragraph, no marketing. If the account has sold cans on, ask it to tell its own customers, or to post your notice. A fuller letter is in how to write a recall letter, and the choices about depth and public warning in recall strategy template.
The lot code is the plan
Everything above depends on one thing: a code on every can, bottle and keg that leads to one brew and one packaging day. A date alone isn't enough if two beers were canned that day. "B-142-C" is: brew 142, cans. With that, and delivery records that note the lot, a recall is 62 cases at nine accounts. Without it, it's every can you've sold this month.
Kegs are harder than cans because they come back and go out again. The collar has to carry the lot for the beer that's in it now: see keg inventory spreadsheet. The brew's own record is in brew log sheet, and the hazards themselves in brewery HACCP plan.
Get the template
Download the brewery recall plan template. The twelve sections, what to decide in each, and the example beside a place for yours, with a read-me. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers. Print the finished plan and keep it where the taproom manager can find it.
Where this stops working
The plan says "accounts from the delivery records". On the day, the delivery records are a driver's clipboard and a distributor's spreadsheet you don't have. The eight kegs of B-142 went out over two weeks, three of them have come back and been refilled, and nobody is sure which bar still has the one that matters.
How TaroStack does it
TaroStack keeps the link from brew to package to account.
Brewing and packaging are batches. The brew notes its malt, hop and yeast lots automatically. Canning and kegging are batches of their own, with their own lot codes, tied to the brew.
Orders record the lot. Each delivery says which lot went to which account.
Starting a recall holds the lot. Every affected lot in your own stock goes on hold at once, and the recall gets a number.
The recall report. Which accounts got the lot, with the contacts to reach them, what's still on your shelves, and which suppliers' lots went into it. It prints, and downloads as one file.
A notice from your own mailbox to each customer, with their answers kept against the recall.
A timed drill. A mock recall is timed and saved, and Home reminds you a month before a year passes without one.
| The job | Paper plan | In TaroStack |
|---|---|---|
| Which packages came from brew 142 | The packaging sheet | Lots tied to the brew |
| Which accounts got them | The driver's clipboard | The recall report |
| Stop it shipping | Tell the cellar and the taproom | On hold at once |
| Proof for the distributor | A document | A timed, saved drill |
TaroStack records what you ship. A keg an account passes on or sends back is still yours to chase. Lots, batches and recalls are on every plan, from $9.99 a month (5 recipes) or $39 a month (50 recipes). The first 14 days are free, with no credit card. If you'd like a hand setting up, ask, and we'll do it with you.
