LIVESTOCKOS
Join Enter System
For Feedlot Operators

Know what's arriving
before it arrives.

Feedlots are a critical control point in the livestock chain. Livestock OS gives feedlot operators advance batch visibility, compliance verification before intake, individual animal health tracking, and integrated dispatch planning — so your intake process is controlled, not reactive.

Before Arrival

Intake planning starts before the truck leaves the farm.

When a producer creates a batch destined for your feedlot and the vet signs the VHC, your feedlot portal receives a pre-arrival notification. You see the batch details — species, count, origin farm, compliance status, and estimated arrival time — before the animals are loaded. This is not a courtesy update. It is the start of your intake compliance record.

Pre-arrival visibility
What you see before the truck arrives
  • Origin farm name and registered location
  • Species, breed, and total animal count in the batch
  • VHC reference number, signing vet, and expiry time
  • FMD zone status of origin farm
  • Compliance clearance status (CLEARED or flags outstanding)
  • Transporter details and vehicle registration
  • Estimated departure time and planned arrival window
On intake confirmation
What you confirm at the gate
  • Batch code scan or reference entry
  • Live count verification against batch manifest
  • VHC validity check at moment of arrival
  • Transporter identity confirmation
  • Lairage allocation recorded
  • Intake time stamped and logged in batch record
  • Any visual health concerns flagged for vet review
Intake Control

When intake is refused — and why.

Livestock OS enforces intake compliance at the feedlot gate in the same way it does at the abattoir. If the arriving batch does not meet all conditions, the system flags it for HOLD — and shows the specific reason. You do not make a judgement call. The system makes the determination. Your gate log records the HOLD status, the reason, and the timestamp.

Conditions that trigger a HOLD
  • VHC is no longer valid per applicable disease-control protocol and permit conditions
  • Batch code not found or does not match the arriving vehicle
  • Animal count at arrival does not match manifest
  • Transporter details do not match the batch record
  • Origin farm is under an active movement restriction
  • FMD zone movement flagged — state vet clearance not on record
  • Outstanding compliance flags unresolved before departure
What happens on a HOLD
The batch is assigned HELD status. The origin producer is notified immediately via their portal. If the issue is an expired VHC, a new vet inspection must be arranged before movement is re-authorised. If the issue is a count discrepancy, the batch cannot proceed until it is resolved and confirmed by both parties. The feedlot's compliance record shows the HOLD event and outcome — protecting your operation from liability.
During the Feeding Period

Individual animal records through your pen.

Once animals are received, Livestock OS maintains individual animal records through the feeding period. Health events, treatment records, and death-in-pen records are captured at the individual animal level and held in the chain record alongside the origin and movement history. This matters at dispatch: when animals leave your feedlot for the abattoir, the health record travels with them — and the receiving abattoir sees it in advance.

Health Events
  • Treatment records by animal ear tag
  • Antibiotic and dosing records with withdrawal periods
  • Dip and tick treatment records
  • Veterinary call-outs and outcomes
  • Death-in-pen recording with cause classification
Pen Management
  • Lairage and pen allocation per batch
  • Daily headcount recording
  • Segregation records (species or origin-based)
  • Pen movement history
  • Feed and water access events (planned integration)
At Dispatch
  • Updated health record forwarded to abattoir
  • Withdrawal period compliance confirmation
  • New VHC requested through registered vet
  • Dispatch batch created from feedlot as origin
  • Full chain record continues — feedlot is now origin entity
Dispatch to Abattoir

Sending animals to slaughter — compliant from the start.

When animals leave your feedlot for the abattoir, your feedlot becomes the new origin in the chain. You create the dispatch batch, request a vet inspection, confirm transport, and the abattoir receives advance notice of the incoming batch — with your compliance record attached. The process mirrors farm dispatch, with the feedlot's health and treatment records appended to the chain.

1
Create dispatch batch
Select animals from your active inventory. Declare abattoir destination and intended departure date.
2
Request vet inspection
Your registered vet inspects the batch and issues a VHC. Withdrawal periods confirmed before signing.
3
Confirm transport
Assign your registered transporter and vehicle. Load manifest auto-generated. Abattoir pre-notified.
4
Gate clearance at abattoir
Abattoir confirms arrival and verifies batch. Chain record closes on slaughter results.
Feedlot intake under control.

Livestock OS is accepting feedlot applications for its pilot programme. Connect your operation to the chain and gain advance visibility on every incoming batch — before the truck leaves the farm.