Batch traceability · Stokka · Live in the product
Know exactly whereevery batch ended up.
A supplier calls about a bad component batch. In under a minute you need to know which of your finished batches used it, who you shipped those batches to, and how much is still on your shelves. That is the whole job. The tracking foundation that answers it, lots, serials, and genealogy through every build, is live in Stokka today, and the one-screen recall report that turns it into a sixty-second lookup is in the box at launch.
What the category is
Batch traceability, plainly.
Traceability software records, at the batch level, every component consumed and every finished batch produced, then links them to the customer shipments that left your door. Done properly it runs three queries in seconds: forward from any component batch, backward from any shipment, and sideways by date. Done badly, it runs none of them at all.
Small manufacturers have mostly been served by two things: a spreadsheet that was never designed for it, or an enterprise ERP that costs more than the risk it covers. Stokka is the middle option.
Live in the product today
Built for the cases that actually break spreadsheets.
Lots with expiry dates
Every tracked batch carries its expiry. Receiving captures lot numbers at the door; picking knows which batch leaves first.
FEFO picking that skips quarantine
Shipping auto-picks first-expired-first-out and never touches quarantined stock. Manual lot and bin overrides land in the audit trail.
Genealogy that survives manufacturing
Which component batches went into which finished goods, through assembly and back out through disassembly. Most tools drop the thread at the first build. Stokka keeps it.
Serial numbers end to end
Scan units in and scan them out. Look any serial up for its current location and its full life history, receipt, build, shipment.
Multi-batch capture per run
A production run that consumes two batches of the same component records both, with quantities and timestamps. Mid-run batch switching is the rule, not the exception.
Continuous and discrete consumption
A litre of fragrance oil used gradually and a single sealed-unit component are different patterns. Both land correctly on the finished batch record.
Structural quarantine
Held and returned stock is excluded from everything sellable by the data model itself, not by a status label someone has to remember.
An audit ledger, not a stock number
Every movement is an immutable ledger entry with who, when, and cost. Corrections post as reversals, so batch history can never be rewritten.
CSV export of any view
Batch and serial queries export as CSV, generated as background jobs so big pulls never time out. Every filtered view is a shareable URL.
In the box · at launch
Launching with it: the one-screen recall report.
The genealogy above is being recorded on every build today, and the screen that reads it back under pressure ships in the launch box: enter a component batch, get every finished batch that used it, every shipment, every customer, and the remaining on-hand stock, on one page, in under a minute. Following after launch: the sortable electronic export format FDA 204 requests expect, certificates of analysis attached to inbound batch records, and shop-floor tablet capture at the station.
See the full roadmap →Industry fits
Built for the regulated corners.
FDA 204 · FSMA
Food and beverage
FDA 204 (FSMA Food Traceability Rule) applies if you handle anything on the Food Traceability List. Stokka is being built to capture every Key Data Element at every Critical Tracking Event, receiving, transforming, shipping, and to export the sortable electronic format the rule requires.
FDA 204 explained →MoCRA · GMP
Cosmetics and supplements
MoCRA (Modernization of Cosmetics Regulation Act) and dietary-supplement GMP regimes expect batch-level records with adverse-event response capability. Stokka's ingredient-first recall lookup is designed for this.
Further reading
Go deeper.
- Batch traceability
Multi-batch recall in under 60 seconds: how it actually works
An ingredient-first recall lookup finds every finished batch, every shipment, and every customer touched by a single bad component batch. Here is the logic that makes it work, and why spreadsheets choke on it.
- Batch traceability
Batch tracking for small manufacturers: the complete playbook
Batch tracking is the discipline of knowing which component batch went into which finished batch and which customer shipment. Here is how to set it up so it holds up in an audit and under pressure.
- Batch traceability
Food traceability for SMBs: FDA 204 explained (without the panic)
The FDA Food Traceability Rule (21 CFR Part 204) sets new record-keeping obligations for manufacturers of foods on the Food Traceability List. Here is a practical read for small manufacturers: what it requires, who it touches, and what you actually have to do.
Stokka · shipping soon
The operating system your business has been waiting for.
Orders, production, stock, BOMs and batch-level traceability on one screen today. Integrations coming at launch. Unlimited users, and every customer runs the full product.