A supplier changed the recipe. The label is still your problem.

In June 2026, a seasoned octopus product was recalled for an undeclared fish allergen. Nothing was contaminated. A supplier had swapped a fish-based ingredient for a mollusk-based one and didn't tell the customer, and that one change became a recall.

That's a different kind of failure than the one most of us plan for. No temperature excursion, no positive swab, no missed CCP check. Someone upstream changed what was in the drum, and the label on the finished product went out saying what it had always said.

01The recall you can't see coming from inside your own building

The same June roundup includes a pancake and waffle mix pulled because the label read "may contain milk and soy" instead of "contains milk and soy." Both products were made correctly by the companies that made them. Both got recalled anyway.

Put those alongside the octopus case and the pattern is clear enough. The hazard didn't enter through your process. It entered through the gap between what your supplier shipped and what your label claimed, and nothing on your production floor was ever going to catch it.

You can run a clean shop, log every check on time, and still ship misbranded product for months because a vendor made a sourcing decision in another state and didn't think to mention it.

02The label is your preventive control

Under 21 CFR 117.135(c)(2), food allergen controls have to include the procedures used for two things: protecting food from allergen cross-contact during storage, handling, and use, and labeling the finished food, including making sure that finished food isn't misbranded under section 403(w) of the Federal Food, Drug, and Cosmetic Act.

That second clause does a lot of work. Labeling the finished food sits inside the allergen preventive control itself, alongside cross-contact. If the ingredient statement on your bottle no longer matches what went in the tank, the regulation you're on the wrong side of is a food safety regulation.

Your supplier's failure to tell you is a real failure, and you may well have commercial recourse for it. It still won't help you with FDA. The company that put the product into commerce is the company that answers for the label on it, which is the same principle that decides who answers for the record when someone else runs your batch.

03Approved supplier, written procedure, documented use

21 CFR 117.420 is short and specific about what a receiving facility owes here.

Paragraph (a) says suppliers must be approved and that approval documented before raw materials and other ingredients are received from them. Not after the first delivery. Not once the relationship is established. Before.

Paragraph (b) asks for three things in sequence. Written procedures for receiving raw materials and other ingredients have to be established and followed. Those procedures have to ensure ingredients come only from approved suppliers, with a narrow carve-out for temporary receipt from unapproved suppliers whose material gets verified before it's accepted for use. And the use of those written procedures has to be documented.

That third item is where most small producers are thin, us included. You can do the right thing every single time and have no record that you did. It's the same gap that opens up between a written plan and the records that prove you followed it.

Off The Deck Hot Sauce buys raw produce, vinegar, salt, and starter cultures. That's the whole list. Our receiving check is a look at produce condition and a read of the ingredient statements on the vinegar and the starter, which are short enough to check at the pallet. We know which farms and vendors we buy from, and we wouldn't take a substitution without asking questions first.

None of it is written down. It lives in our heads, and it belongs in an SOP.

Under 117.420(b), an unwritten rule that everyone follows isn't a procedure. It's a habit.

The records side closes the loop. 21 CFR 117.475(c)(5) requires documentation demonstrating use of those written receiving procedures, and 117.475(a) puts supply-chain records under the same Subpart F recordkeeping requirements as the rest of your batch records.

04Four ingredients is a smaller surface, not a shield

No supplier has ever changed a spec on us without saying so. Four raw inputs, short ingredient statements, vendors we talk to directly. Our exposure here is small, and we know it.

Small isn't the same as none. Our vinegar comes from a supplier who has their own suppliers. Our starter cultures are a manufactured product. Neither of those is something we can verify by looking at it, which means both are things we trust a document about rather than an inspection.

The businesses caught out in June weren't sloppy operators. They were relying on a supplier relationship that had been stable long enough to feel like a fact.

If you carry more inputs than we do, and most producers do, count them. Every purchased ingredient that has an ingredient statement of its own is a place where someone else's decision can change what your label needs to say.

05When you find out six months late

The hard part isn't the discovery. It's the question that lands about four seconds afterward: how much did we make with it?

What FourFoxes does here, stated exactly. It doesn't track supplier recipes or ingredient specifications. If a vendor reformulates, nothing in the app is going to tell you.

What it does is make the second question answerable. If you know roughly when the change happened, you open the purchase record for that ingredient and tap trace forward, and you get every batch that used it. The same records carry through to finished goods and the accounts that received them. That's the difference between a bounded recall and a guess, and it decides how the first 24 hours of a recall go.

At receiving, FourFoxes captures the supplier record, the lot, and the CoA on the incoming material. Those three are what tie every lot back to its supplier and make the trace possible later. A CoA sitting in an email thread does none of this work. A CoA attached to the lot does.

Pull records in seconds, not hours. That only holds if the receiving-side data went in when the pallet arrived.

What to do this month

Four steps, in order of how much they buy you:

1. Write down your approved suppliers and what you check at receiving. One page. This is the 117.420(b) procedure, and most small producers don't have it.
2. Ask every ingredient supplier, in writing, to notify you before any formulation, source, or specification change. Keep the reply.
3. Read the ingredient statement on incoming material against your finished label, not against your memory of your finished label.
4. Tie each incoming lot to a supplier record and its CoA, so a trace forward is possible without a phone call.

None of this stops a supplier from making a change. It decides whether you find out on your terms or from a regulator.

FAQ

If my supplier substituted the ingredient, is the recall their fault?

You may have commercial recourse. On labeling, 21 CFR 117.135(c)(2)(ii) places labeling the finished food, including avoiding misbranding under FD&C 403(w), inside your allergen preventive controls. The product entered commerce under your name.

Do I need a supplier approval program if I only buy four things?

21 CFR 117.420(a) does not scale with the length of your ingredient list. Suppliers must be approved and that approval documented before you receive material from them.

Is a verbal understanding with a longtime supplier enough?

21 CFR 117.420(b)(1) requires written procedures that are established and followed, and (b)(3) requires that their use be documented. An unwritten practice meets neither.

Does FourFoxes alert me when a supplier changes a formula?

No. FourFoxes does not track supplier recipes. It tracks the lot, the supplier record, and the CoA, so that once you know a change happened you can trace forward from the purchase record to every batch that used the ingredient.