iiinova — where your digital self keeps evolving

FourFoxesIO @fourfoxesio.bsky.social · 11h

At two batches a day you don't have a system. You have a memory. At six batches and two shifts it runs out of room, and the records slip. Your busy season is the audit. It shows up without notice. Build the logging before peak: fourfoxes.io/blog/logging-before-bu…

000

FourFoxesIO @fourfoxesio.bsky.social · 06/10/2026

You can make this product in your sleep. But could you prove exactly what was in the batch you ran in March, the ratio as it stood that day? A recipe in your head is a memory, not a record. fourfoxes.io/blog/recipe-version-co…

010

FourFoxesIO @fourfoxesio.bsky.social · 28/09/2026

FSMA 204's Food Traceability Rule compliance date is now July 20, 2028 — FDA pushed it 30 months from the original Jan 2026 (Fed. Register, Aug 7 2025). The rule didn't get easier. You got runway. That habit takes longer to build than to switch on.

000

FourFoxesIO @fourfoxesio.bsky.social · 25/09/2026

Best time to learn an ingredient is about to expire: before you reach for it, not after it's in the batch. FourFoxes flags raw material by expiry and lot, so the warning comes at the shelf — not in the post-mortem. Caught early it's a note. Caught late it's a hold.

000

FourFoxesIO @fourfoxesio.bsky.social · 24/09/2026

The substitute supplier's lot is the one most likely to skip your records: new, rushed, "just this once." Enter it before it hits a batch, then "which batches used it?" is a 2-minute answer, not a lost afternoon. fourfoxes.io/blog/substitute-suppli…

000

FourFoxesIO @fourfoxesio.bsky.social · 22/09/2026

You track every pepper lot: supplier, code, date received. Then you turn on the tap, and thousands of gallons go into the batch with no record. Water is an ingredient. Most traceability skips it. fourfoxes.io/blog/water-traceable-i…

000

FourFoxesIO @fourfoxesio.bsky.social · 18/09/2026

The lot code on the finished case is the whole game. If a buyer can read it and you can trace it back (ingredients, readings, who else got that run), a problem stays a scoped pull. If the code's a mystery, every question becomes "pull everything." Make the code on the box mean something.

000

FourFoxesIO @fourfoxesio.bsky.social · 17/09/2026

On a shared line, cleaning between an allergen batch and the next is a control, not a chore. The record is the only proof cross-contact was controlled. FDA requires both the clean (21 CFR 117.35(d)) and the log (117.145).

000

FourFoxesIO @fourfoxesio.bsky.social · 15/09/2026

Every CCP log you've signed assumes the thermometer was right. Where's the record that says so? Without a dated calibration check, a drifted probe puts every batch since install back in question. New post on the record most floors skip:

000

FourFoxesIO @fourfoxesio.bsky.social · 14/09/2026

"Allergens are the #1 cause of food recalls" depends on how you count. An analysis of 24,761 FDA recall records (2013-2025) found microbial hazards outran allergens 1.7x overall, led by Listeria. By recent FDA event counts, allergens still top the list. Control, and log, both.

000

FourFoxesIO @fourfoxesio.bsky.social · 12/09/2026

A thermometer nobody calibrated is a number nobody can defend. The reading isn't the whole record; proof the instrument was right is. Check calibration on a schedule, and every temp you log after stops being a guess with a decimal point.

000

FourFoxesIO @fourfoxesio.bsky.social · 08/09/2026

Traceability doesn't get more expensive as you grow. Not having it does. The habit that's cheap at four employees is the one that saves you at forty, if you start it now.

000

FourFoxesIO @fourfoxesio.bsky.social · 03/09/2026

Sesame's been the 9th major allergen since Jan 1, 2023. The risk isn't the rule. It's recipe drift: a dusting flour, a spice blend, an oil swapped in for cost. Your BOM knows. Was your label ever checked against it? fourfoxes.io/blog/sesame-allergen-b…

000

FourFoxesIO @fourfoxesio.bsky.social · 01/09/2026

This summer's jalapeño recall pulled in companies that never grew a pepper. A supplier's recalled lot becomes your recall. Could you name which of your batches used it, and who got them? fourfoxes.io/blog/supplier-ingredie…

000

FourFoxesIO @fourfoxesio.bsky.social · 28/08/2026

Nobody starts a food business because they love recordkeeping. I sure didn't. But the day a buyer asks for a lot record is the day you find out whether your paperwork was a habit or a system. Build it so future-you isn't the one paying for the shortcut.

000

FourFoxesIO @fourfoxesio.bsky.social · 27/08/2026

117.4(d) is one line: training records "must be established and maintained." Being a qualified facility exempts you from Subparts C and G. 117.4 is in Subpart A. New post: fourfoxes.io/blog/training-records-…

000

FourFoxesIO @fourfoxesio.bsky.social · 26/08/2026

Every batch record is also a data point. Enough of them and drift shows before a customer does: yields sliding, one supplier's lots running acidic, a step creeping out of range. The record isn't only for the auditor. It's the first place to catch something going wrong.

000

FourFoxesIO @fourfoxesio.bsky.social · 25/08/2026

072225 tells you the date. It does not tell you which of the two runs that day is in your buyer's hand. A lot code is a decision about how much product you have to pull. New post: fourfoxes.io/blog/lot-code-design-t…

000

FourFoxesIO @fourfoxesio.bsky.social · 24/08/2026

A recall shouldn't be a scramble through invoices and text messages. If your ingredient lots connect to batches, and batches to customers, tracing one is a query: pull the lot, read the list. The work is upfront, not on the worst day.

000

FourFoxesIO @fourfoxesio.bsky.social · 22/08/2026

A 60-second readiness check: pick one finished lot you shipped last month. Can you name every ingredient lot in it, and every customer who got it, in under an hour? If yes, you're recall-ready. If not, you just found your next project.

000

FourFoxesIO @fourfoxesio.bsky.social · 21/08/2026

A shelf-life date isn't a guess you print on the label. It's a claim you have to back up. Tie each date to the batch it came from, and "how'd you land on that?" has a one-line answer instead of a shrug.

010

FourFoxesIO @fourfoxesio.bsky.social · 20/08/2026

Why the misbranded label is yours anyway, and the three tests 21 CFR 117.420(b) applies to your receiving procedure: fourfoxes.io/blog/supplier-changed-…

000

FourFoxesIO @fourfoxesio.bsky.social · 20/08/2026

A seasoned octopus product was recalled in June for an undeclared fish allergen. Nothing was contaminated. A supplier swapped a mollusk extract for a bonito (fish) one and didn't say so. The label went out unchanged. Your process was never going to catch that.

100

FourFoxesIO @fourfoxesio.bsky.social · 18/08/2026

Why rotation fails on visibility rather than discipline, and what 21 CFR 117.80(b)(1) actually asks of you: fourfoxes.io/blog/fefo-ingredient-r…

000

FourFoxesIO @fourfoxesio.bsky.social · 18/08/2026

FIFO means you use what arrived first. FEFO means you use what expires first. Same instruction, right up until a newer delivery has less shelf life left than the older one already on your shelf. With perishables that happens constantly.

100

FourFoxesIO @fourfoxesio.bsky.social · 17/08/2026

FDA food recalls are running at a six-year high, and this summer showed why: undeclared allergens, salmonella, listeria, foreign material, week after week (TraceGains, 2026). Deadlines move. The recall risk doesn't wait for one.

000

FourFoxesIO @fourfoxesio.bsky.social · 16/08/2026

One supplier's jalapeños. 19 products. 26 states. That's the recall Taylor Fresh Foods issued this week (FDA, Aug 2026). If that were your supplier's lot, could you name every batch it touched today? Pull the lot, see every one, in seconds. 21 CFR Part 1, Subpart S.

000

FourFoxesIO @fourfoxesio.bsky.social · 14/08/2026

Most allergen recalls aren't a contamination story. They're the wrong label on the right product, because a supplier changed what's in a lot and nobody tied it to the batch. Undeclared allergens are still the top US recall cause in 2026. (Packaging Digest, Apr 2026)

000

FourFoxesIO @fourfoxesio.bsky.social · 13/08/2026

Your co-packer runs the batch. Their facility holds the records (21 CFR 117.315). If FSMA 204 covers you, the 24-hour retrieval clock is still yours. Someone else can hold the records. You answer for them. 1.1455(b). fourfoxes.io/blog/who-owns-records-…

000

FourFoxesIO @fourfoxesio.bsky.social · 11/08/2026

Full breakdown of what the record has to carry, and the 7-working-day review clock most small producers never start: fourfoxes.io/blog/ccp-deviation-cor…

000

FourFoxesIO @fourfoxesio.bsky.social · 11/08/2026

A correction and a corrective action are not the same paperwork. 21 CFR 117.150(c) lets minor, isolated problems skip the full procedure. An out of spec CCP is not one of those. You owe an affected-product evaluation and a documented disposition.

100

FourFoxesIO @fourfoxesio.bsky.social · 09/08/2026

A deviation rarely comes out of nowhere. The cook temp creeps, the fill weight drifts, a few batches run a little off before one runs too far. FourFoxes charts each batch against the last, so you catch the drift while it's still a trend, not a write-off.

000

FourFoxesIO @fourfoxesio.bsky.social · 07/08/2026

FDA extended the FSMA 204 traceability compliance date to July 20, 2028. More runway, not a reason to wait. The makers who coast through it are building lot-to-batch records now, not scrambling in 2028. Ref: FDA final rule, Aug 2025 extension.

010

FourFoxesIO @fourfoxesio.bsky.social · 06/08/2026

FSMA 204 requires a written traceability plan. Five parts, no software, finishable in an afternoon. It just describes how you already work. Which is why writing it honestly tells you whether the rest holds up. fourfoxes.io/blog/fsma-204-traceabi…

000

FourFoxesIO @fourfoxesio.bsky.social · 05/08/2026

A year of talking to food founders taught me one thing: they're not afraid of the audit. They're afraid of being asked a fair question and not being able to prove the answer in time. The work got done. The record just wasn't ready. That's the gap we build against.

011

FourFoxesIO @fourfoxesio.bsky.social · 03/08/2026

Audit-ready isn't a binder you assemble the night before. It's pulling up a batch on your phone — every CCP check, ingredient lot, and CoA in order — and handing the auditor the phone. Captured right the first time, not reconstructed.

000

FourFoxesIO @fourfoxesio.bsky.social · 02/08/2026

"Which finished lots touched supplier lot 4471?" If that's a 20-minute question, it should be a 20-second one. Every supplier, every lot, every CoA in one place — tied to the batches that used them. That's traceability, not a spreadsheet.

000

FourFoxesIO @fourfoxesio.bsky.social · 01/08/2026

Traceability runs two directions. Forward: which products used this ingredient lot? Backward: what went into this finished lot? If either takes longer than a coffee refill, that's the number to fix before your next recall drill.

000

FourFoxesIO @fourfoxesio.bsky.social · 30/07/2026

A menu with no prices tells you the price. That's software shopping when you're small. The capability was never out of reach at our size. What made it fragile was the tool: a spreadsheet has no opinion about whether you filled it in.

000

FourFoxesIO @fourfoxesio.bsky.social · 29/07/2026

End of shift, every batch record complete and timestamped. No reconstructing from memory, no missing sheet from Tuesday. That's the bar FourFoxes is built to hit: the record's done before you clock out.

000

FourFoxesIO @fourfoxesio.bsky.social · 28/07/2026

A supplier flags a pepper lot. You find the batch fast. Naming every account that got a jar of it is the hard part. Forward trace = four records sharing one number. Same lot code on jar and invoice, and it's one thread to pull. fourfoxes.io/blog/forward-trace-lot…

000

FourFoxesIO @fourfoxesio.bsky.social · 26/07/2026

A sign your batch records won't survive an audit: pulling the full history on a single finished lot takes more than a few minutes. Not because you're careless — because the records live in three tools that don't talk. That's the gap an auditor finds first.

000

FourFoxesIO @fourfoxesio.bsky.social · 23/07/2026

FSMA 204's compliance date moved to July 20, 2028. Good news with a catch: the date changed, nothing else did. Same rule, same 24-hour records request. Build traceability now and you won't be scrambling in 2028. fourfoxes.io/blog/fsma-204-complian…

000

FourFoxesIO @fourfoxesio.bsky.social · 21/07/2026

Price your hot sauce off the $1.21 ingredient cost and you'll swear your margin is 80%. Add packaging, labor, overhead, and the bottles you can't sell: it's $4.29 a bottle, 28% margin. COGS, down to the bottle: fourfoxes.io/blog/food-production-c…

000

FourFoxesIO @fourfoxesio.bsky.social · 20/07/2026

Mock recall drill: pick one ingredient lot. Now trace it to every finished product it touched. Beat the clock — under an hour. If that's a binder dig, you don't have a traceability system yet. You have a filing cabinet and some hope.

000

FourFoxesIO @fourfoxesio.bsky.social · 19/07/2026

Pull a lot number. See every finished batch it touched — the supplier, the dates, the CCP checks. Seconds, not a morning lost in the binder. That one lookup is the whole reason FourFoxes exists. Everything else is built around it.

000

FourFoxesIO @fourfoxesio.bsky.social · 17/07/2026

Traceability isn't a big-company luxury. The standard a large producer hits with a whole quality department, a small brand can hit with one system holding every lot, batch, and check in one place. Same bar. It shouldn't take a team of ten.

000

FourFoxesIO @fourfoxesio.bsky.social · 16/07/2026

You didn't miss the check. The last shift did. You're the one who finds the gap, mid-batch, hunting old texts for a reading that should already exist. Required, attributed logging closes the handoff hole. New post → fourfoxes.io/blog/missing-ccp-log-p…

000

FourFoxesIO @fourfoxesio.bsky.social · 15/07/2026

End-of-shift logging feels efficient. It's actually your biggest compliance risk. Records written from memory at the end of a long day get the time wrong, or never get written. The fix isn't more discipline. It's logging in the moment.

000

FourFoxesIO @fourfoxesio.bsky.social · 14/07/2026

Log the CCP check while you're standing at the equipment. Not at the end of a ten-hour shift, from memory, hoping you got the temp right. On your phone, in the moment, reading in front of you. That's how records stay accurate.

000