Carcass imports — stage, review and commit
What this page helps you do
Section titled “What this page helps you do”Beef → Carcass imports brings processor feedback into the farm without silently accepting every file row. Uploading a CSV or supported PDF creates a staged import. Review animal identity, slaughter date and carcass weight; explicitly approve or drop rows; then Commit. Only commit creates carcass records. It can also record slaughter farm exits and kill-weight sessions for matched animals, so this final action needs careful review.
The service requires a farm Owner or Manager to upload, amend, approve and commit. A read-only user can still inspect authorized history. The page is for Beef or Mixed farms.
Choose and stage a file
Section titled “Choose and stage a file”| Control | What to do |
|---|---|
| Format profile (optional) | For CSV, keep Auto-detect columns (default) when the headings are recognised, or choose a saved profile for a processor-specific layout. Manage profiles opens the profile setup page. Profiles do not apply to PDF. |
| Choose carcass kill-sheet file or drop area | Pick/drop one .csv or .pdf file. Check the displayed name and size before proceeding. The server accepts a CSV body up to 4,000,000 characters and at most 2,000 data rows; split larger files. The PDF payload limit is roughly 9 MB after decoding. |
| Stage for review | Parse the selected file and open its review page. This does not write carcasses, exits or payments. If staging fails, read the error before retrying. |
For CSV, common case-insensitive headers include animal_tag, slaughter_date, hot_carcass_weight_kg, conformation_grade, fat_class, abattoir_name, kill_sheet_ref and notes. Optional source columns include processor and live weight at slaughter. Common aliases such as hcw and kill_date are accepted. Profiles can map different source headings and provide constants or formulas. The parser accepts ordinary quoted commas and escaped quotes, but a complex multi-line quoted cell may need a cleaned CSV export.
PDF uses a built-in text/layout parser and converts recognised rows into the same staged review process. It cannot parse every plant layout. If no rows are found, request a CSV export. When a PDF row has no date and the sheet has no default date, the parser falls back to the farm’s current date; verify every date before committing.
Find a previous import
Section titled “Find a previous import”Recent imports shows 20 per page. A row displays Status (Staged, Committed or Cancelled), file name, row count, warning and error counts, upload date and commit date. Select it to reopen review or inspect a committed receipt. A committed count may be smaller than the uploaded row count because rows can be dropped or skipped. Uploading the same source again creates a new import; it does not reopen a committed one.
Review the staged rows
Section titled “Review the staged rows”The review page shows Total rows, Approved, Pending and Dropped. Each row includes file line number, resolved animal or unresolved raw tag, slaughter date, HCW (hot carcass weight), live weight, kill-out percentage, grade, fat class, status and actions. Parse errors and warnings are shown with the row. A ~ or est marker identifies a projected live weight; kill-out is carcass weight divided by live weight × 100 when a usable live weight exists.
The importer tries to match the file’s tag against current and historical identifiers on this farm. An unknown or ambiguous match stays unresolved. This initial match is not resolved as at the row’s slaughter date, so take particular care when an ear tag or management identifier has ever been reused. Never approve a guessed identity; use Edit to choose the correct animal. Date input from CSV may be recognised in yyyy-MM-dd, day/month/year or another supported processor format, but the correction form uses yyyy-MM-dd farm-local dates.
| Row action | What it does |
|---|---|
| Edit | Opens the row correction panel. Fix the animal, required date or weight and optional fields, then Save & approve. A parse-error row must be corrected this way before it can be approved. |
| Approve | Marks a parsed, pending row as reviewed. It does not itself create a carcass. A warning can remain visible; check its meaning before approving. |
| Drop | Excludes a bad or irrelevant row while keeping it in the import history. It does not delete the original source evidence. |
| Select all approvable rows / Approve selected | On desktop, ticks all pending, parse-valid rows; select individual rows on desktop or mobile to bulk approve. Parse-error rows are excluded. Review warnings and identity before approving a group. |
Approved is not a guarantee the row will be committed. At commit, an unresolved animal, an existing carcass for that animal, or an animal already exited for a reason other than Slaughtered may be Skipped. Inspect the final receipt and row statuses.
Correct one row
Section titled “Correct one row”The Edit row panel shows the original file values and any parse error or warning. Its controls are:
| Control | Accepted value and effect |
|---|---|
| Animal | Pick the actual farm animal; the raw file tag is shown as a search hint when unresolved. |
| Slaughter date | Required farm-local date, yyyy-MM-dd. Enter the actual completed slaughter date, never a planned or future date. |
| Hot carcass weight (kg) | Required number from 10 to 999.9 kg. Check a suspicious outlier against the processor sheet. |
| Live weight at slaughter (kg) | Optional number from 0.1 to 9,999.9 kg. If available, it supports kill-out and a kill-weight record. The form may prefill an estimated value: clear it if you do not intend to assert it as an actual reading. Saving that prefilled number treats it as an operator-supplied weight rather than retaining its estimated status. |
| EUROP grade / Fat class | Choose a catalogue value or Not yet known. Do not coerce an unknown processor code into the nearest grade. |
| Abattoir | Optional plant/site name, at most 200 characters. |
| Kill-sheet reference | Optional reference, at most 100 characters. |
| Notes | Optional context, at most 1,000 characters. |
| Save & approve / Cancel | Save corrected fields and approve, or leave the row unchanged. Errors remain visible if required data is invalid. |
The original source values remain visible in the correction panel for comparison. Review any remaining warnings after saving.
Commit and check the result
Section titled “Commit and check the result”When at least one row is approved, Commit N becomes available. Before selecting it, check every approved row against the processor document, especially the animal match and slaughter date. Approve an animal at most once in one import; if the file repeats an animal, keep the correct row and drop the duplicate. Commit can:
- Create a carcass for each eligible approved row that does not already have one.
- Auto-exit an animal still active on the farm as Slaughtered on the recorded slaughter date. An animal already exited as Slaughtered can receive its carcass without another exit.
- Record a slaughter-day Kill weight from a supplied live weight, or a separately marked estimated kill weight where the system can estimate one.
- Skip approved rows with unresolved data, an existing carcass, an incompatible earlier exit or a failed exit operation.
The commit receipt reports carcasses created, auto-exits, kill weights and skip counts. Open the committed import to see Committed/Skipped/Dropped rows and skip reasons. The import becomes read-only. Then check Carcasses and the relevant animal records. A file’s row total is not the count of carcasses successfully added. If the whole request fails, the import remains staged for a safe retry; do not upload a duplicate file merely because the page showed an error. Recheck approved rows for the same animal before retrying because Farmlync permits only one active carcass record per animal.