Skip to content

Feed consumption report

Open Operations → Reports → Browse all reports → Feed consumption to see feed quantity and recorded cost by animal for a selected period. It combines individual feeding events with each animal’s share of a pen feeding event. Use it to review feeding records before comparing feed costs in the Per-cow profitability report. It does not replace a ration plan, inventory issue record or physical feed check.

From and To are inclusive farm-local dates. The page initially includes today and the preceding 30 dates, a 31-date inclusive window. The date pickers offer presets and prevent choosing From after To. They do not show the server’s 365-day inclusive maximum before sending the request; if a longer selection produces the report error state, shorten the range and use Retry. Changing a date returns the table to page one. The result table has 25 animals per server page; use its page controls to see more.

Search tag, name, breed, stage and table-column sorting apply only to the current server page. A blank search result does not prove no animal on another page matches. Stage and identity come from a separate lookup for the visible page; if that lookup fails, the totals remain available and the page offers Retry animal details. An ID fragment may appear in place of the tag until details load.

Tile Meaning
Animals fed Number of animal rows that received at least one recorded individual event or attributed batch share in this window. It is not the whole farm’s animal count.
Total as-fed Quantity from all source feeding events, individual plus whole pen batches. “As-fed” is the offered weight, not dry-matter intake.
Total cost Source-event cost for those same individual and batch events. Check recorded unit costs before treating it as a financial statement.
Individual events Count of individual feeding events contributing to the window.
Batch events Count of pen feeding events contributing to the window. A batch is one event, even when it supplies many animals.

The herd totals are calculated from source events, not by summing rounded animal rows. This matters when a pen batch has a share that cannot be attributed to a known animal. Its quantity and cost remain in the herd totals without appearing on an individual row.

Column Meaning
Tag · Name Animal identity from the visible-page lookup. The table can also display its national ID.
Stage Current lifecycle stage from that lookup, not necessarily the animal’s stage on every feeding date.
As-fed kg Recorded individual as-fed quantity plus allocated shares of pen feeding, rounded for the row.
Days fed Number of distinct farm-local dates on which that animal has a recorded individual feeding event or attributed pen share. Multiple events on one day count as one day.
Cost Recorded individual-event cost plus attributed pen-batch cost for that animal.
Cost/day Animal Cost ÷ Days fed, rounded to two decimals; it is not Cost ÷ every day in the selected window. A dash is shown when no positive value can be displayed.

The default table ordering shows higher Cost first within the returned page. As-fed quantity is not measured intake or nutritional dry matter. A pen event is divided using the animal count saved with that event, not a later headcount. Each animal whose recorded pen-membership interval covers the feeding time receives one share of quantity and cost. If fewer memberships can be found than the saved count, the remaining shares are unattributed. The warning above the table reports the number of affected batch events, as-fed kilograms and cost; check animal movements and pen membership if the numbers matter to a cost decision.

The page text suggests that an amber Days fed = 0 row identifies an unrecorded animal. In the current implementation, however, the report builds rows from animals with a recorded individual event or attributable batch share; an entirely unrecorded animal has no row. Do not use absence of amber rows as evidence that every cow was fed or that every feeding was logged. Compare the farm roster, feed plans and actual routine separately. If the number of pen memberships is greater than the batch event’s saved animal count, the same saved quantity can be over-allocated across animal rows; the source-event herd total remains the reference figure.

Export CSV is available when the report has animal rows. It requests the full result for the selected dates, not only the current page, and writes Tag, Name, Breed, Stage, As-fed kg, Days fed, Cost and Cost/day. The export does not apply the page-local Search term or sort order. There is currently no synchronous export row ceiling, and the server also calculates the complete animal result before producing an ordinary 25-row page. On a large herd or busy annual window, shorten the dates before retrying a slow or failed request.

Identity details are resolved only for animals on the current visible page before the file is built. An off-page export row can therefore contain an animal-ID prefix in Tag and blank Name/Breed/Stage even though its feed totals are present. Keep the animal ID when reconciling such rows; do not treat the missing label as an unknown animal in the backend. The current export action also has no page-level failure message; if no download appears, inspect the report state and retry with a narrower period rather than assuming that a complete file was produced.

For a cost discrepancy, inspect the feeding event history and the animal’s pen history, then correct the source event through its authorised workflow. Reload this report afterward so the per-animal allocation and herd totals are recalculated.