---
title: "5.4 Batch Lifecycle Traceability"
space: "Vuna Livestock"
url: "https://docs.navari.co.ke/livestock-management/50-reporting-and-monitoring/54-batch-lifecycle-traceability"
updated: "2026-10-24"
---

Use **Batch Lifecycle Traceability** to follow your flock's receipts, care, stock movements, and dispatches. Open it from your Livestock workspace or Desk search, or select **Lifecycle Traceability** on your saved Batch. Select Company, Batch, and To Date. From Date, Warehouse, and Event Type are optional; **Include Related Batches** defaults on.



Use the report to review your history, then open the source document when you need to investigate or correct a record. Running the report does not change your stock or repair missing historical links.

## **Events and quantities**


| Event                               | Source                                                                                  |
| :----------------------------------- | :--------------------------------------------------------------------------------------- |
| Receipt / supplier return           | Submitted Purchase Receipts, stock-updating Purchase Invoices and other posted receipts |
| Birth                               | Material Receipts linked to a readable submitted Offspring Record                       |
| Transfer                            | Material Transfers; departures and arrivals appear separately by warehouse              |
| Split / merge / replacement         | Complete, count-balanced Repack allocations                                             |
| Reclassification / possible grading | Eligible Repack relationships between different Items; grading intent cannot be proven  |
| Capitalisation                      | Capitalisation Repacks, without creating parent/child relationships                     |
| Mortality / culling                 | Submitted stock issues using the corresponding entry type                               |
| Sale / customer return              | Delivery Notes and stock-updating Sales Invoices; non-stock billing is excluded         |
| Correction                          | Stock Reconciliation                                                                    |
| Feeding / produce collection        | Submitted header-linked Stock Entries                                                   |
| Treatment                           | Submitted completed Veterinary Diagnoses and submitted linked medicine issues           |
| Husbandry                           | Completed Livestock Events, using Starts On                                             |
| Weighing                            | Saved, non-cancelled Weight Records, using measurement time                             |


Animal quantities come from stock ledger batch allocations, including legacy batch numbers and Serial and Batch Bundles. A bundle replaces the legacy field; the report never adds both. Allocations are grouped once per document, batch, and warehouse. Incoming and outgoing values remain separate, so same-batch Repacks can show both without representing new animals.



Feed, medicine, produce, weights, and husbandry are linked activities with **blank animal quantities**. The Activity Warehouse column identifies their explicit historical location. Treatment documents and capitalization entries retain their own rows and readable references to the common diagnosis or stock issue. Summing incoming quantities alone does not calculate a current population: transfers and Repacks can have both sides.

![](/files/image015753.webp)
*Chronological lifecycle rows with source links, transfers, and activity status.*

![](/files/imageeb3312.webp)
*Chronological lifecycle rows with source links, transfers, and activity status.*

## **Related batches and evidence**

Related history is inferred from readable submitted Repack records whose entire stock allocation agrees with the accessible stock ledger. The report requires positive whole-animal quantities in compatible count UOMs, complete batch allocations, and balanced inputs and outputs. Non-livestock, inaccessible, incomplete, or unbalanced allocations prevent inference.



One-to-many splits, many-to-one merges, and one-to-one replacements create relationships labelled **Inferred from Repack**. Unchanged batch quantities and cost capitalization create no relationships. A partial split can retain some stock under the original batch. An unchanged allocation alongside a transformation is excluded from the relationship.

![](/files/image1e862c.webp)

![](/files/image8ec3a2.webp)
*Eligible split/merge event with parent/child links and Inferred from Repack evidence.*

Many-to-many or otherwise ambiguous Repacks appear as **Ambiguous transformation**, with only readable associated batches listed; they do not expand the lineage. This report cannot establish individual-animal ancestry or resolve ambiguous legacy transactions.



Expansion follows valid relationships in both directions, including connected co-parent and sibling branches. Parent, child, and related batch names link to their Batch forms. Traversal is cycle-safe and limited to 200 batches and 20 relationship levels; exceeding either limit raises an error instead of returning an apparently complete partial history. Disable Include Related Batches to inspect one batch.



Relationship discovery covers all history up to To Date. From Date, Warehouse, and Event Type apply afterward to displayed events, so they do not hide an ancestor needed to reach a related batch. To Date remains the historical cutoff for both discovery and events.