Cricket Batch Tracking: IDs, Age Tracking, and Multi-Bin Management
How to assign batch IDs, track cohort age across multiple bins, log movements, and manage overlapping production batches in a commercial cricket farm.
The Problem with Running a Farm Without Batch Tracking
Running more than a handful of bins without a batch tracking system leads to a predictable set of problems: bins of similar-aged crickets that get mixed up, harvest timing that is based on guesswork, and no way to trace a quality or mortality problem back to its source. At 50 bins you can probably manage with a marker on the lid. At 200 bins, that approach falls apart completely.
Batch tracking is not complex. It requires consistent habits and a clear schema. Once in place, it gives you the operational foundation to grow confidently and troubleshoot problems systematically.
Designing a Batch ID System
A batch ID needs to encode enough information to be useful on its own, while remaining short enough to write on a bin label or enter quickly in software. A date-based format works well: YYYYMMDD-SEQ, where SEQ is a two or three digit sequence number for batches started on the same day.
For example, a batch started on February 15, 2026 as the first batch of the day would be 20260215-01. A second batch started the same day is 20260215-02. This format sorts naturally by date in any spreadsheet or software system, and tells you at a glance how old a batch is.
If you source eggs from multiple breeding colonies or suppliers, consider adding a prefix: BC01-20260215-01 for breeding colony 01, or SUP-20260215-01 for purchased stock. This becomes important if you ever have a disease or quality issue tied to a specific genetic source.
What to Record at Batch Creation
When a new batch is created, record: batch ID, date created, source (colony ID or supplier), initial egg count or estimated pinhead count, bin count, stocking density per bin, target harvest date (based on expected grow time at current season temperature), and assigned grow zone or room. Assign the batch ID to every bin in that cohort at creation, either with a physical label or by logging bin numbers in your tracking system.
Age Tracking and Instar Progression
Acheta domesticus passes through 8 to 9 instars before reaching adulthood. At 88F, you can generally expect: days 1 to 7 as pinhead nymphs, instars 2 through 5 from days 7 through 21, sub-adults from days 21 to 30, and adults capable of harvest from days 35 to 42.
Log a visual stage assessment once per week per batch. You do not need to be precise to the instar; what matters is confirming that development is on pace with expected timeline. If a batch is visually two weeks behind a same-age batch in an adjacent zone, something is wrong: check temperature, humidity, and feed access in that zone first.
Movement Logs
Every time bins from a batch are moved, split, or consolidated, log it. Record: date of movement, batch ID, source location, destination location, and reason (split for density, moved to harvest holding area, quarantined due to suspected illness).
Movement logs serve two purposes. First, they let you physically locate any batch at any time without walking the entire facility. Second, they create a traceable chain of custody if a biosecurity event requires you to understand exposure paths across bins and zones.
Managing Multiple Overlapping Batches
Most farms run staggered production with new batches starting every one to two weeks. That means at any given time you might have eight to twelve active batches at different life stages. Keeping these distinct requires both a good naming convention and a clear physical separation system.
Zone your facility so that very young nymphs are not adjacent to adults. This reduces disease transmission risk (particularly for Acheta domesticus densovirus) and makes it easier to enforce biosecurity practices between life stage areas. Label zones clearly and post batch ID lists at zone entry points so staff can confirm they are in the right area before handling equipment.
CricketOps tracks active batches by cohort, flags upcoming harvest windows, and logs bin movements, so your team always has a current picture of where each batch stands without relying on memory or paper records.
End-of-Batch Records
At harvest, record the final batch disposition: harvest date, actual live weight harvested, total mortality count (if known), destination of harvested product, and any notes on batch quality or anomalies. These end-of-batch records are what let you calculate true FCR and actual yield per bin, which are the metrics that improve over time if you are paying attention.