Livestock Genetics Inventory Software: Do You Know Which Straws in the Field Can Legally Ship Abroad?

Your most valuable inventory is sitting in tanks you do not own

A distributor calls on a Tuesday wanting 300 straws of a sire for a shipment to a South American customer. The office says stock is fine, the report shows 1,140 units. Then the picking starts. Four hundred of those units are in a technician's tank three states away, on consignment, and half of them are from a collection date that predates the health testing regime the destination country requires. Two canisters were physically moved between tanks last winter and the record was never updated. What the report called 1,140 is somewhere between 500 and 900 shippable units, and nobody can say which without opening tanks.

Livestock genetics inventory breaks every assumption ordinary inventory software makes. The unit is a straw or an embryo worth anywhere from a few dollars to four figures. It lives in a goblet, inside a canister, inside a liquid nitrogen tank, and a meaningful share of tanks sit in field technicians' vehicles, distributor facilities and customer farms rather than in your building. The stock cannot be visually counted without exposing it to warm air. And the same physical straw is legally saleable into one country and illegal into another, based on facts about the bull, the collection date, the collection facility and the health testing that was in force at the time.

Get that last part wrong once and the consequence is not a returned shipment. Countries suspend approvals for facilities, not for individual errors, and a suspension closes that market for your entire company until it is resolved.

Problem one: the stock keeping unit is a straw, and the location is a canister

Most genetics businesses start with a spreadsheet keyed by sire code, holding a total unit count. That model is wrong in a way that becomes expensive slowly. The real inventory object is a lot: a specific sire, a specific collection date, a specific processing batch, with a health and eligibility profile attached. Two lots of the same bull are not interchangeable if they were collected under different testing conditions.

Location has to go deeper than a warehouse code as well. Tank, canister, goblet position. Technicians work from a canister map, and if the system cannot produce one, they will keep their own on paper and yours will drift within a season. Every physical movement, a canister transferred between tanks, a goblet consolidated, a tank sent for repair, must be a recorded event rather than an adjustment to a count.

What a build does is make the lot and the position first class, then treat counts as derived. Inventory reports stop being a number people distrust and become a position list a technician can actually pick from. That alone usually recovers a surprising amount of value, because studs routinely discover they have been reordering production of a sire whose stock was sitting misfiled in a field tank.

Problem two: export eligibility is a matrix, not a checkbox

Whether a given lot may ship to a given country depends on the collection centre's approval status for that country, the health testing protocol applied to the bull around the collection window, quarantine and residency history, sometimes the genetic status of the animal for specific conditions, and the certificate the destination will accept. In the United States, bovine semen destined for export is generally handled through centres operating under the Certified Semen Services framework, and importing countries layer their own requirements on top of that. Those requirements change, and they change asymmetrically: one country tightens, another opens.

Businesses handle this today with a compliance manager who holds the matrix in their head and a folder of country requirement documents. The failure mode is not that they do not know the rules. It is that at order time, under pressure, nobody re checks whether the specific lots being picked satisfy the destination, and the rules were written for the bull rather than for the lot.

The build requirement is blunt: eligibility must be computed per lot per destination, and the system must refuse to allocate an ineligible lot to an order rather than warn about it. Warnings get clicked through. A hard block that requires a named override with a reason and an approver is the only control that survives a busy shipping week. Alongside it, the country requirement set should be maintained as versioned data with effective dates, so a rule change does not retroactively invalidate the record of why a shipment two years ago was correct at the time.

Problem three: consignment stock is your inventory and someone else's tank

Field technicians and distributors hold stock on consignment, sell it, and report back. Reconciliation typically happens monthly, quarterly, or when someone notices a discrepancy. In between, your books show inventory you cannot see and revenue you have not recognised.

The reconciliation problem is genuinely hard because the technician is working out of a truck, often with no signal, and will not tolerate a slow interface. What works is a mobile view of their own tank contents, a fast way to record a use with the customer and cow or sow it went to, and a periodic physical count with a variance workflow rather than a silent correction. Variances need a reason: broken straw, unrecorded transfer, count error, tank incident. Over a year those reason codes tell you which parts of your field network need attention, which is information nobody currently has.

Settlement follows from the same record. Technician commission, distributor pricing tiers and consignment revenue recognition all read from usage events instead of from an invoice someone types at month end.

Problem four: genealogy has to reach back to collection and forward to the calf

A quality question about a batch arrives from a customer months later. The chain you need is collection date and centre, processing batch, extender lot, freezing run, storage history, distribution to tanks, and every use recorded against it. If that chain is intact, you answer in an hour with a defined exposure. If it is not, you are guessing at scope and your options are a broad recall or a hope.

Forward traceability matters commercially as well. Studs increasingly want to connect straws sold to breeding outcomes, and customers want proof of what they used and when. Recording usage at the animal level, where the technician will supply it, creates a data asset that is genuinely difficult for a competitor to replicate because it accumulates over years.

Design it as an append only event chain rather than fields on an inventory row. The reason is fan out: one collection becomes thousands of straws distributed across hundreds of tanks over several years, and only an event model keeps forward and backward queries honest at that spread.

Problem five: shipping a dry shipper is not shipping a box

Orders leave in nitrogen dry shippers with a limited hold time, and international shipments carry health certificates, permits, and sometimes a pre shipment inspection. The dry shipper itself is a returnable asset worth real money that goes missing constantly. Documentation must match the physical contents exactly, because a discrepancy between the certificate and the tank contents at the border is the classic reason a shipment is refused.

A build should generate the packing list from the actual allocated lots, produce or feed the certificate data from the same source, track dry shippers as returnable assets with charge rules, and hold the export document pack against the shipment permanently. The last part matters because questions about a shipment arrive long after everyone involved has forgotten it, and the pack is the answer.

What it costs and how long it takes

A first release covering lot based inventory with tank, canister and position, eligibility rules with hard allocation blocking, order picking and shipment documentation runs $70,000 to $150,000 and ships in 12 to 18 weeks. A full platform adding technician mobile with offline capability, consignment reconciliation and settlement, collection and processing records, dry shipper asset tracking, distributor portals and accounting integration runs $190,000 to $420,000 phased across 9 to 14 months.

What drives cost up: the number of export destinations, since each country's requirement set is analysis work before it is code. Embryo lines alongside semen, because embryo eligibility, grading and recipient records are a second model rather than a variant. Multiple collection centres. Offline mobile, which is not optional if your technicians work rural routes but does add real engineering. And migration, because opening tanks to establish a true baseline count is a physical project that runs alongside the software one and is usually underestimated.

What keeps cost down: starting with your own tank rooms and your top three export destinations, and deferring the marketing and breeding advisory features that always appear in the first workshop.

Build versus buy, and when buying is right

There is no packaged product that covers this properly, which is why the category exists on spreadsheets. What businesses try instead is a general ERP (Enterprise Resource Planning) or warehouse system, which handles lots and locations but has no concept of export eligibility per destination or of consignment stock in a technician's truck, or a herd management package, which understands animals but not warehouse operations. Both end up with the eligibility matrix back in a spreadsheet, which is the part that actually carries the risk.

Stay on spreadsheets if you have one tank room, domestic sales only, and a single person doing all picking. That is a real and defensible position. Build when field tanks outnumber house tanks, when you export to several countries with divergent rules, when consignment reconciliation has produced a write off you did not expect, or when your compliance manager is the single point of failure for every export decision the company makes.

How to choose a developer

Ask them to model a straw on a whiteboard. If they draw a product with a quantity, stop. You need to hear lot, with collection date and eligibility profile, positioned in a tank, canister and goblet, with movements as events. That distinction determines whether the system is useful or is a prettier version of the spreadsheet.

Ask how they would stop an ineligible lot reaching a shipment. If the answer is a warning message, they have not worked in regulated distribution. You want a hard allocation block with a named override, a reason and an approver retained on the record.

Ask how the technician app behaves with no signal in a truck at a farm gate. Offline capability with conflict resolution is a design decision made at the start, not a feature added later, and getting it wrong means the field never adopts the system.

Ask who owns the code, the data and the cloud accounts, and settle it before kickoff. Your lot genealogy and usage history compound in value every year and underpin your export approvals. At Digital Heroes the client owns the repository from the first commit, and any developer hedging on that is asking you to keep your export evidence inside their account.