A trace answers two questions in a recall: what went into this batch, and where did this lot end up.
Trace back from a batch
- Open the batch.
- Click Trace back.
- FourFoxes walks the chain: the batch, each ingredient lot in it, the purchase it came from, and the supplier.
Trace forward from a purchase
- Open the ingredient purchase (a supplier just called about a lot).
- Click Trace Forward.
- FourFoxes shows every batch that used the lot, then the packaged lots and shipments downstream, including the customer shipped to.
Read the banner first. A banner pinned to the top says whether the trace is complete or how many data gaps it found. A gap does not stop the trace; it tells you what you cannot prove. Each gap is named in place, for example:
- no ingredient consumption records for the batch (nothing was linked)
- a purchase that is not linked to any batch
- a supplier lot number or a customer that was not recorded
- a batch recorded before stock tracking, or an imported batch with no lot records
- a batch packaged before lot tracking, or packaging recorded with no lots
- a batch not yet packaged
- an older link whose quantity is unknown, labelled legacy
If someone on your team wrote a warning note on a batch, for example to explain a missing link, the trace shows that note as the gap reason.
You can export the exact trace you are looking at with Export PDF or Export CSV. The file is generated in the background and the download link lasts 24 hours.
Traces require the Member role or higher.
Run a trace on a recent batch this week. Every gap it reports is something you can fix now, while it is a chore instead of an emergency.
Related