Almost every small food or beverage producer builds the same spreadsheet at some point. A tab per month, or per batch. Columns for lot number, date, supplier, quantity in, quantity out. Someone — usually whoever is most organized on the team — keeps it updated by hand after each receiving, each production run, each shipment. It works. Until the day it has to actually answer a question under pressure, and you find out what it was missing.
This isn’t a criticism of the spreadsheet or the person maintaining it. A lot log is the right instinct — you do need to know which lot went where. The problem is never the idea. It’s what a spreadsheet structurally cannot do once your product line, your customer count, or your batch frequency grows past a certain point.
The three failure modes
Stale copies. The moment more than one person can update the lot log, you have a versioning problem. Someone opens the file at 9am, someone else opens it at 9:15, and whoever saves last wins — silently overwriting the other person’s entries. Shared drives and “final_v3_ACTUAL.xlsx” file names are a symptom, not a fix. The log is only as trustworthy as the discipline of everyone who touches it, every single time, with no system enforcing that discipline.
No movement ledger. A lot log usually records that lot #4471 came in and, eventually, that it went out. What it rarely records is every intermediate step: which production batch consumed part of it, which shipment used the rest, whether some of it was scrapped for a quality issue. A spreadsheet captures snapshots — “received” and “shipped” — not a continuous ledger of every movement in between. When you need the full chain, you’re reconstructing it from memory, packing slips, and whatever notes happen to still be attached to an old batch sheet.
The recall drill that takes a weekend. This is where the first two failure modes collide. A supplier tells you a raw-material lot might be affected by a contamination issue. You need to know: which of your finished batches used that lot, and which customers received those batches. If your lot log is stale, incomplete, or split across three spreadsheets that don’t quite agree, answering that question means opening every production sheet from the relevant date range, cross-referencing supplier receiving records, and hoping nothing was recorded on a sticky note that got thrown out. In practice this tends to eat a weekend — and you’re still not confident in the answer after all that work.
None of this means the team is doing something wrong. It means the tool has run out of runway for what the business now needs from it.
What “traceability” actually means
Traceability sounds abstract until you break it into the two directions it actually has to run:
Backward — from a finished product to its inputs. Given a shipped lot, can you name every raw-material lot and supplier that went into it? This is what a customer complaint or a quality audit asks for.
Forward — from a raw material to its outputs. Given a supplier lot, can you name every finished batch it touched and every customer who received one? This is what a supplier recall notice asks for, and it’s the direction that determines how fast — and how completely — you can act.
A real traceability system answers both directions as a lookup, not a reconstruction project. That distinction is the entire point. Our lot tracking & traceability page goes into more detail on what a movement ledger looks like in practice, but the short version is: every receipt, every production consumption, every shipment, every scrap and every adjustment writes one record, tied to a lot, a location, and the document that caused it. Nothing gets typed in after the fact from memory.
A 20-minute recall drill you can run today
You don’t need new software to find out whether your current system — spreadsheet or otherwise — is actually recall-ready. Run this drill on a slow afternoon, with a timer, on a real (not hypothetical) lot from the last three months:
- Pick a raw-material lot at random from your receiving records — something you know went into at least one production run.
- Time yourself finding every finished batch it went into. Not “the batch it was mostly used for” — every batch, including any where it was a minor ingredient or where a partial quantity carried over from a prior run.
- From each of those finished batches, find every customer shipment. Include partial shipments and any batch that’s still sitting in your warehouse.
- Write down how long it took and where you got stuck. Did you have to open more than two source documents? Did you have to ask a colleague to remember something? Did you find a gap — a batch where you can’t tell if that lot was used or not?
- Now do it in the other direction. Pick a finished lot you shipped recently and trace it backward to every raw-material lot and supplier behind it, including packaging.
If you did all five steps inside 20 minutes, with no gaps and no phone calls, your current system — whatever it is — is doing its job. If it took longer, or you hit a wall partway through, you now have a specific, concrete answer to “is this actually a problem,” rather than a vague sense that the spreadsheet is getting unwieldy. That specificity matters: it tells you exactly which failure mode is biting you, which is the difference between fixing the right thing and buying software that doesn’t address it.
It’s worth running this drill even if you’re fairly confident in your system. Confidence and evidence are not the same thing, and a recall is the worst possible moment to discover the gap.
What to look for when you outgrow the spreadsheet
If the drill above exposed real gaps, the fix isn’t “a better spreadsheet template” — it’s a system built around three specific properties that spreadsheets structurally can’t guarantee:
- A continuous movement ledger, not a snapshot log. Every stock event — receive, consume, ship, return, scrap, adjust — should write its own record automatically, tied to the document that caused it. You shouldn’t be able to move stock without it being recorded; the record should be the byproduct of doing the work, not a separate data-entry task.
- FEFO by default, not by memory. First-expired-first-out picking should be the system’s suggestion every time, for both production consumption and shipping — not something a picker has to remember to check. This matters for traceability too: it keeps your lot rotation predictable, so you’re not left holding six-month-old lots because newer stock kept getting grabbed first.
- An audit trail you didn’t have to build. The system should already know who received a lot, who consumed it into a batch, and who shipped it — in plain language, not a raw movement code. That’s the record an auditor or a recall actually wants to see, and it should already exist by the time anyone asks for it.
This is exactly the gap that food and beverage producers hit first, because HACCP-style traceability requirements don’t scale down — a four-person operation is held to the same “can you trace it in hours, not days” standard as a much larger one.
The spreadsheet isn’t wrong. It’s just answering a question — “what do we have” — that stops being the question the moment someone asks “prove where it went.” Knowing which question your current system can actually answer, before you’re forced to find out under pressure, is the whole point of running the drill.
How OakNex handles this
OakNex is built around exactly the ledger described above: every receipt, production consumption, shipment, return, scrap and adjustment writes one record to an audited movement history, tied to a lot, a location and the source document that caused it. Tracing a lot forward to every batch and shipment it touched, or backward to the suppliers behind it, is a search — the 20-minute drill above runs in seconds, in both directions, because the ledger already exists rather than needing to be reconstructed.
FEFO picking is the default in both production and shipping, with a manual override when a specific lot needs to move instead, and the dashboard surfaces lots approaching expiry before they become a write-off or a shipment you have to chase down. See the lot tracking & traceability page for the full picture, or the food & beverage producers page if HACCP paperwork and audit readiness are the specific pressure driving the search.