A slaughter log is the running record of whose animals came through the plant: one row for each owner's livestock, with the date, the owner's name and address, the kind and number of animals, what was made from them and how much. For a processor working under the federal custom exemption, that's close to word for word what the rule asks for. A custom operator keeps records "showing the numbers and kinds of livestock slaughtered on a custom basis, the quantities and types of products prepared on a custom basis, and the names and addresses of the owners of the livestock and products". The log below has those columns and a few more that a small plant needs for its own sake. The example is a made-up processor. Your State's meat inspection program has the last word on what it wants to see.
The short version
- One row for each owner's animals, written the day they're slaughtered.
- Owner's name and address, kind of livestock, number of head: the rule names these.
- Products prepared and their quantity: the rule names these too.
- Mark every package "Not for Sale" and tick the row when it's done.
- Add the animal's tag, the hanging weight and the pick-up date for your own use.
- Transaction records are kept two years after the end of the year. This plant keeps its log as long.
- TaroStack keeps each owner's goods as theirs, apart from your own stock. More below.
What the rule asks for
The custom exemption covers slaughtering livestock delivered by its owner, and preparing the meat, when it's all for use in that owner's household, by the owner, members of the household, nonpaying guests and employees. The inspection requirements don't apply to it, and it isn't for sale. In return, the rule sets conditions. Three of them shape the log.
| Condition | What 9 CFR 303.1 says |
|---|---|
| Records | Records showing the numbers and kinds of livestock slaughtered on a custom basis, the quantities and types of products prepared, and the names and addresses of the owners. These are in addition to records otherwise required |
| Marking | Custom prepared products are plainly marked "Not for Sale" immediately after being prepared, and kept so identified until delivered to the owner |
| Kept apart | If the operator also prepares or handles products for sale, they're kept separate and apart from the custom products at all times |
Other records. A business that slaughters for commerce, or buys, sells, transports or stores meat in commerce, keeps records of each transaction: what it was, its net weight, the buyer's and seller's names and addresses, the date and method of shipment. A processor that also sells meat over a counter has that set to keep as well.
How long. The transaction records are kept for two years after December 31 of the year the transaction happened, so one from November 2026 is kept through the end of 2028. This plant keeps its custom log for the same time. Ask your State program what it requires for yours.
How the exemption itself works, and how shares in an animal fit it, is in custom exempt meat processing. This is general information, not legal advice.
An example week
| Date | Owner | Kind | Head | Tag or other ID | Hanging (lb) | Products prepared | Packaged (lb) | Of hanging | Not for Sale? | Picked up |
|---|---|---|---|---|---|---|---|---|---|---|
| Nov 16 | R. Alvarez | Cattle | 1 | Ear tag 2207 | 742 | Steaks, roasts, ground beef, soup bones | 468 | 63.1% | Yes | Nov 30 |
| Nov 16 | J. and M. Okafor | Swine | 2 | Ear notches 14 and 15 | 396 | Chops, fresh hams, side pork, sausage | 281 | 71.0% | Yes | Nov 25 |
| Nov 17 | P. Lindqvist | Sheep | 3 | Tags 0412 to 0414 | 168 | Chops, legs, ground lamb | 121 | 72.0% | Yes | Nov 24 |
| Nov 18 | S. Brandt | Goats | 2 | Tags 31 and 32 | 84 | Cut in sixths, bone in | 58 | 69.0% | Yes | Nov 20 |
| Nov 19 | D. Whitehorse | Cattle | 1 | Ear tag 0915 | 801 | Steaks, roasts, ground beef, liver, heart | 512 | 63.9% | Yes |
The file's rows also carry each owner's address and phone number and the initials of whoever made the entry. Names, addresses and weights here are invented.
The columns the rule names are owner, address, kind, head, products prepared and packaged weight.
The columns the plant adds earn their place:
- Tag or other ID ties the row to the animal that walked in, and to the owner's own records.
- Hanging weight is what this plant bills on, and what an owner asks about.
- Packaged, of hanging is the number this plant gets asked about most. An owner who brought in a 742 lb carcass and took home 468 lb wants to know where the rest went. The answer is bone, fat and trim, and it depends on the cut sheet: boneless cuts weigh less than bone-in. Having 63.1% and 63.9% on two steers cut the same way is the plant's evidence that nothing was unusual. A way to test it is in butcher yield test.
- Picked up shows what's still in the freezer and whose it is. The Whitehorse beef hasn't gone yet.
What the owner asked for is its own form: see beef cut sheet and pork cut sheet.
The month
| Kind | Head | Hanging weight (lb) | Packaged (lb) |
|---|---|---|---|
| Cattle | 2 | 1,543 | 980 |
| Swine | 2 | 396 | 281 |
| Sheep | 3 | 168 | 121 |
| Goats | 2 | 84 | 58 |
| Total | 9 | 2,191 | 1,440 |
"Numbers and kinds of livestock" is a question someone will ask by month or by year. Add the log up at each month's end while the rows are fresh, and keep the summary with it.
Keeping it
- Write the row on the kill floor's day, from the drop-off slip, not at the end of the week.
- One row for each owner. Two hogs from one family are one row with two head. If the same owner brings cattle and hogs, that's two rows.
- Ink, or a file nobody overwrites. Corrections are crossed through and initialed.
- Tick "Not for Sale" when the packages are marked, which the rule says is immediately after they're prepared.
- Keep custom product in its own place in the cooler and freezer, labeled with the owner's name, if the plant also handles meat for sale.
Get the log
Download the custom slaughter log. Two sheets and a read-me: the log, with the packaged weight worked out as a share of the hanging weight, and a month's summary by kind of livestock. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers.
Where this stops working
The log knows what came in and what was packaged. It doesn't know what's in the freezer today. By the third week of November a small plant is holding meat for a dozen families, in boxes that look alike, and the question at the counter is "is the Okafor order all here?" The log says 281 lb was packaged on the 16th. It doesn't say that two boxes are on the wrong shelf.
How TaroStack does it
TaroStack is built for holding goods that belong to someone else. That's on Business.
Every item says whose it is. A client's own goods come from them, go back to them, and are in no stock value of yours.
A client's goods are received at no cost and kept apart from your own stock and from other clients'.
A run for a client records what it used and what it made, and whose each was.
Releases. A client's goods go out only on a release to that client, so the pick-up is a record.
A client's page shows their goods here, their runs and their releases, and a monthly statement shows how each lot moved.
| The question | Paper log | In TaroStack |
|---|---|---|
| Whose animals came in this month | Add up the rows | Runs, by client |
| Is the Okafor order all here | Look in the freezer | That client's goods, by lot |
| What's still waiting for pick-up | The empty column | Goods not yet released |
| When did the Alvarez beef leave | The pick-up date, if written | The release |
TaroStack doesn't decide whether a job fits the custom exemption, and it isn't a substitute for the records your inspection program asks for. Keeping goods for clients is on Business at $89 a month, with 5 active clients, and Pro at $199 with 15. The first 14 days are free, with no credit card. If you'd like a hand setting up, ask, and we'll do it with you.
