Value Chain · Terminal Node
Where the chain ends.
And traceability becomes proof.
By the time livestock arrive at your facility, Livestock OS already holds the origin record, the movement history, the veterinary certificate status, and the identity of every animal in the batch. Your intake is confirmation — not discovery.
Operational portal available
Full chain record: chain-dependent
Chain Position
The abattoir is the terminal node
Every compliance action from farm to gate has been building a complete, immutable record. At intake, that record arrives with the batch. The abattoir's role is to confirm arrival, conduct inspection, record slaughter, and close the chain.
Complete Abattoir Record
16 verified data points.
One immutable record.
Livestock OS captures every material event from intake to final result. Each data point is timestamped, role-authenticated, and linked to the batch and individual animal identity where applicable.
01–04Pre-Arrival Intelligence
01
Livestock Intake
Formal intake event opening the abattoir record. Head count, batch reference, and expected vs. actual reconciled at gate. Batch state must reach AT_GATE before intake can be confirmed.
02
Supplier & Origin Farm
Linked to the registered entity and farm of origin from the verified batch record created at source. Includes province and entity contact. Not self-declared at intake.
03
Movement Record
Full route from farm to facility. Origin and destination provinces, FMD zone flags, load date, and estimated arrival. Issued against the transport declaration before the truck departs.
04
Transporter
Registered carrier identity, truck registration, driver ID, and loader details captured in the transport declaration. Available to the abattoir before the truck arrives.
05–08Intake & Identity
05
Animal or Batch Identity
Each animal carries an ear tag and, where applicable, an RFID or ISO electronic ID. At batch level: species, breed, sex composition, total head. Individual RMIS reference where registered.
06
Arrival Confirmation
Formal receipt of the batch at facility. Head count confirmed against the transport declaration. Discrepancies — missing animals, tag mismatches — are flagged immediately and logged to the audit trail.
07
Health Documentation
The Veterinary Health Certificate (VHC) issued at farm or feedlot is verified on arrival. Certificate validity rules are applied per the relevant disease-control protocol, permit conditions and authorised veterinary requirements. Certificates that are no longer valid block the batch in the system.
08
Ante-Mortem Inspection
Conducted by the responsible vet at facility. Inspection outcome is recorded as pass, conditional, or hold. Animals showing signs of disease, injury, or welfare compromise are flagged before slaughter proceeds.
09–12Slaughter & Carcass
09
Slaughter Event
Recorded against each batch and animal: facility registration number, responsible operator, date and time, and method. Batch state transitions to SLAUGHTERED on confirmation.
10
Carcass Identification
Post-slaughter carcass identity links the physical animal to the pre-slaughter ear tag record, enabling continuity from live animal to processed product within the Livestock OS chain record.
11
Classification
Carcass classification per applicable South African grading standards — age category, fat score, and conformation where relevant. Classification data is captured and held against the carcass record.
12
Condemnations
Any partial or full condemnation following post-mortem inspection is recorded with reason code, the authority responsible, and the disposal method. Condemnation records form part of the immutable compliance chain.
13–16Results & Traceability
13
Samples & Laboratory Results
Residue, microbiological, or disease samples taken at facility are logged against the batch. Laboratory reference numbers, sample type, and results are recorded when received, completing the compliance record.
14
Compliance Records
Documents captured by Livestock OS include: VHC, movement declaration, ante-mortem inspection record, post-mortem outcome, classification, condemnations, and lab results — consolidated per batch.
15
Product-Batch Traceability
Links the processed product batch back to the slaughter event, individual animal identities, transport declaration, and origin farm. Enables recall response and buyer verification from product to farm gate.
16
Export & Retail Traceability
Where the full chain is complete and verified, the Livestock OS record supports export market documentation requirements, retail provenance claims, and third-party audits without additional data collection. Requires full chain
Sequence of Events
Four phases. One unbroken record.
Every abattoir event follows a defined sequence in the system. Each phase must be completed before the next opens. No step can be backdated or bypassed.
Phase 1
Pre-Arrival
- Supplier identity held in system
- Movement record available on arrival
- Transporter verified in transit
- VHC validity monitored
- Expected head count set
Phase 2
Intake & Inspection
- Arrival confirmed
- Head count reconciled
- Animal identity verified
- Ante-mortem inspection recorded
- Hold or pass decision logged
Phase 3
Slaughter & Carcass
- Slaughter event recorded
- Carcass identity captured
- Post-mortem outcome logged
- Classification captured
- Condemnations recorded
Phase 4
Results & Close
- Samples submitted and logged
- Lab results recorded on receipt
- Compliance record consolidated
- Product-batch link captured
- State: RESULTS_RECORDED
ARRIVED
→
SLAUGHTERED
→
RESULTS_RECORDED
Compliance Context
Relevant legislation & documents captured
Livestock OS operates in a regulated industry. The following legislation is relevant to abattoir operations in South Africa. Where specific documents are captured by Livestock OS, these are noted. Compliance verification against these Acts is the responsibility of the relevant authorised person — not automated by the system.
Meat Safety Act 40 of 2000
- Governs ante-mortem and post-mortem inspection requirements
- Regulates abattoir registration and hygiene
- Requires condemnation and disposal records
- Covers export health certificate requirements
Livestock OS captures: ante-mortem inspection outcome, condemnation records, slaughter event. Legal interpretation and enforcement remain with the authorised vet and relevant authority.
Animal Diseases Act 35 of 1984
- Governs movement controls and permit requirements
- Regulates FMD zone management and crossings
- Covers notifiable disease reporting obligations
- Establishes state vet authority over livestock movement
Livestock OS captures: movement declaration, FMD zone flags, VHC status at intake. Actual permit verification and enforcement remain with the responsible state vet.
ECTA 2002 — Digital Records
- Electronic Communications and Transactions Act 25 of 2002
- Gives digital records legal standing equivalent to paper equivalents
- Applies to digitally signed VHCs and timestamped chain events
- Supports admissibility of digital audit records
Livestock OS produces timestamped, role-authenticated digital records. Whether those records satisfy specific evidentiary requirements for a given matter is a legal determination.
Traceability Depth
One scan. The full story.
Livestock OS enables traceability in both directions — backward to origin, forward to product and market. The depth of that traceability depends on how complete the chain record is. A full chain from farm through gate produces a full traceability record at the abattoir.
Backward Traceability
Product → Farm
- Product batch → slaughter event → carcass identity
- Carcass → individual ear tag or batch record
- Batch → transport declaration → gate intake
- Gate → VHC → vet certification event
- VHC → batch creation → farm of origin
- Farm → registered entity
Forward Traceability
Farm → Market
- Verified origin for retail provenance labelling
- Base record for export health documentation
- Chain support for certification requirements
- Audit trail for third-party market accreditation
- Recall response capability from product to source farm
External Systems
Integration pathway — not yet connected
Abattoirs and processors typically operate existing systems for weighing, grading, cold store management, and supplier invoicing. Livestock OS is designed as a chain control layer that can sit alongside these systems — sharing batch identity and compliance records where an integration agreement is in place.
⚠
External system integration — not currently connected
Livestock OS does not currently have an active data connection to any external abattoir management or processing system. Any integration with a third-party system — including grading, weighing, cold store, or invoicing platforms — requires a separate integration agreement and technical implementation. Until such an agreement is in place, data transfer between Livestock OS and external systems is a manual process. This page will be updated when any such integration is established.
Livestock OS — available now
- Pre-arrival batch record and VHC status
- Chain compliance history on intake
- Immutable audit log per batch
- Exportable compliance package per record
- Slaughter event and carcass identity capture
Compatible integration pathway — subject to agreement
- Carcass number to ear tag record link
- Batch reference shared with processing system
- Compliance record export to facility platform
- Classification data synchronisation