How do I handle goat milk recalls?

Plan before the phone rings

MADISON, Wisconsin — A recall is the day you find out whether your paperwork was a system or a pile. If you sell goat milk, cheese, yogurt or bottled milk, the plan you write now decides whether a bad batch costs you one afternoon or the whole business. The short version: know exactly which lots went to which buyers, be able to reach those buyers fast, stop selling the affected product immediately, and talk to your regulator before you talk to anyone else. Nobody enjoys writing this plan, which is why most people write it after they need it.

Know what triggers a recall

Recalls usually start with a lab result, a customer illness report, an inspector's finding, or your own discovery that something went wrong, such as a pasteurizer chart that shows a temperature dip, a drug residue positive, or a foreign object. Pathogens like Listeria, Salmonella and E. coli, undeclared allergens in flavored products, and antibiotic residues are the usual culprits for dairy. Your state department of agriculture or health department licenses most small dairies and plants, and the FDA has authority over interstate dairy products. Which agency leads depends on your license and where the product went, so find out now, not during the event. Ask your inspector what they expect from you in writing if a problem occurs.

Write a one-page recall plan

Keep it short enough that you will actually use it. Put these items on one sheet:

  1. Who makes the call to pull product (name a person and a backup).
  2. A list of every customer type: farmers market, store, restaurant, herdshare, online orders.
  3. How you will contact each type the same day.
  4. Where recalled product goes once returned, and who destroys it.
  5. Who talks to the media or posts publicly, if anyone.
  6. Your regulator's contact method, kept off your phone's dead battery and on paper.

Tape it inside the cooler room door. Check the National Mastitis Council for milk quality background, and your extension office for sample plans designed for small processors.

Make lots traceable

A recall you cannot narrow becomes a recall of everything. Assign a lot code to every batch, tying milk from specific milkings to the vat or bottling run, the date made, and the packaging. Write the code on the label or case. Record which customers got which lots on the invoice or sales log. If a cheese ages for months, the code has to survive the aging room, so label the wheels or the shelf tags. Good records are what let you say "only these 40 units" instead of "everything since spring."

Act when something goes wrong

Stop sales and shipping first. Quarantine remaining stock with a clear hold tag. Then call your regulator, describe what you know, and follow their direction on notice, lab testing and disposal. Contact customers directly with the product name, lot code, reason, and what to do with it. Keep copies of every message and a log of who confirmed receipt. Do not argue about whether it was "really" dangerous in the notice. Be plain: what it is, who may be affected, what to do.

Fix it and rebuild trust

After the pull, find the cause. Review cleaning logs, pasteurization charts, animal health and treatment records, and supplier lots. Retest, correct the process, and write down what changed. Ask your regulator what proof they need before you resume sales. Customers tend to forgive a fast, honest recall more readily than a slow, vague one. Consider product liability and recall insurance options and ask an agent whether your current policy even mentions recalls; many farm policies exclude them.

Practice once a year. Pick a lot code and see how long it takes to produce every buyer. If the answer is "a few hours and a stack of receipts," your plan works. If it's "about a week and some guessing," now you know what to fix.