Run The Barn Day To DayAbout 10 minutes

Use Meat Operations For Lot Traceability And Recalls

Follow a harvest batch through processing, freezer restocks, linked sales, affected buyers, reservations, holds, dispositions, and follow-up work.

What This Helps You Do

Follow a harvest batch through processing, freezer restocks, linked sales, affected buyers, reservations, holds, dispositions, and follow-up work.

Estimated Time

About 10 minutes

Exact Navigation Path
Desktop

Desktop: Open Harvest, then choose Meat Operations.

Mobile

Mobile: Open Harvest, use the section selector, then choose Meat Operations.

Before You Start
  • Harvest batches and freezer restocks linked with source batch IDs.
  • Sales linked directly to the batch or to a freezer usage log carrying the selected batch.
meat operationstraceabilityrecalllotholdfreezeraffected buyersdisposition

Overview

  • Meat Operations is an internal traceability workspace built from existing harvest batches, freezer movements, sales links, contacts, reservations, and tasks.
  • Processor and inspection fields are breeder-entered context. Rabbitry Run does not decide whether processing, labeling, or sales comply with a jurisdiction.

When To Use

  • You need to understand where a batch went, identify affected buyers, place a lot on hold, or document a release, disposal, rework, return, or other disposition.

Step-By-Step Guide

1

Step 1

Follow this action exactly in the Use Meat Operations For Lot Traceability And Recalls workflow.

1.1 Do this

Open Meat Operations and filter active, held, or closed lots. Open a lot to review source rabbits and snapshots, processing records, yields, restocks, sales, named buyers, reservations, and recall history.

What You Should See
  • The page should remain in the same workflow and be ready for the next step.
You Should Now Have
  • You should be ready to continue to the next step.
2

Step 2

2.1 Do this

For freezer sales, select one attributable source batch. If a transaction spans lots, enter separate sale lines rather than silently assigning one lot to the whole transaction.

What You Should See
  • The page should remain in the same workflow and be ready for the next step.
You Should Now Have
  • You should be ready to continue to the next step.
3

Step 3

3.1 Do this

Place a lot on hold only with a reason. The transition adds recall history and creates one open follow-up task per affected buyer and batch.

What You Should See
  • The page should remain in the same workflow and be ready for the next step.
You Should Now Have
  • You should be ready to continue to the next step.
4

Step 4

4.1 Do this

Use Prepare buyer outreach to move affected contact IDs privately into Buyer Outreach. Consent and channel rules are applied again, and no message is sent automatically.

What You Should See
  • The page should remain in the same workflow and be ready for the next step.
You Should Now Have
  • You should be ready to continue to the next step.
5

Step 5

5.1 Do this

Close a held lot with a disposition and resolution note. Reopen with a new note when more work is required; prior closure history remains intact.

What You Should See
  • You can explain the lot path and follow-up state without changing freezer quantities or claiming that buyers were automatically notified.
You Should Now Have
  • You can explain the lot path and follow-up state without changing freezer quantities or claiming that buyers were automatically notified.

You're Done When

  • You can explain the lot path and follow-up state without changing freezer quantities or claiming that buyers were automatically notified.

Common Mistakes

  • Inferring a reservation lot only because it references the same freezer item.
  • Holding a lot and assuming inventory was removed or buyers were messaged.
  • Combining incompatible inventory units in one total.

If Something Still Looks Wrong

Why is a buyer missing from a lot?

Confirm the sale has a contact and either a direct source batch or a linked freezer usage log with both the sale ID and batch ID.

Why is stock shown as legacy or unassigned?

Historical freezer stock without attributable batch movements is left unassigned rather than being falsely inferred. Add correct provenance only when you know it.

Why was no new recall task created after reopening?

Rabbitry Run creates a new task only when no open task already exists for that buyer and batch. Completed prior tasks remain history.

When To Contact Support

  • The workflow does not match the guide even after you confirm you are in the correct section.
  • Saving or loading fails repeatedly in this area of the app.

Still Stuck?

If the guide got you close but the app still does not match what this tutorial says should happen, contact support and mention the article title, the exact step where you got stuck, and what you saw instead.