Know what each batch used.Follow what happens next.
Connect receiving, actual production, and dispatch so each finished lot keeps the supplier evidence, quality decisions, and customer actions around it.
Production needs precise records.Response needs completed actions.
Effective recalls depend on every industry member in the supply chain taking prompt, thorough action.
The recipe is only the plan.Keep the actual batch history.
Consumed lots, remaining quantities, and response obligations need their own evidence and next actions.
The BOM cannot name consumed lots.
Connect the run to the ingredient lots and quantities it actually used, keeping the approved recipe as context.
Partial use leaves a balance.
Keep recorded use, unused material, loss, and output separate so each quantity has an explicit basis.
A trace does not finish the response.
Follow instructions, acknowledgments, physical outcomes, and claims as separate work attached to the assessed scope.
Record what the plant does.Connect each next decision.
Your operational systems supply receipts, consumption, output, and quality records, with supported manual routes for gaps.
Receive against the notice
Match the supplier's lot and shipment reference to your receipt, keeping accepted, held, damaged, rejected, and short quantities distinct.
Link actual batch use
Connect the input lots and quantities consumed by a run to its recorded outputs and loss.
Identify finished output
Keep each output lot with its production reference, packaging level, and the actual inputs it came from.
Record hold and release scope
Attach the decision, reason, affected lot or run, and required evidence to the product under review.
One connected journey.Each business records its part.
Link supplier, plant, warehouse, and customer evidence while retaining who observed and decided each event.
The plant records actual use
Receiving, production, and finished dispatch connect through the lots actually consumed, with quality decisions retained beside them.
Put the batch history to work.Across the teams around it.
Track movements and trace actual use
Open daily receiving, internal moves, dispatch, and the consumed lots behind a finished output.
Explore Track and TracePrepare and coordinate the response
Use plan versions, mock recalls, multichannel instructions, and location actions to work the assessed scope.
Explore RecallReview evidence before the decision
Keep specifications, certificates, COAs, insurance, acceptance, and renewal with the relevant supplier and location.
Explore Supplier ComplianceResolve claims against the record
Compare claimed quantities, costs, and evidence with the assessed response, then retain approval, settlement, and recovery decisions.
Explore Financial ReconciliationInspect the signal and its source
Review dated public notices and authorized network context, then open the related product, requirement, or action.
Explore Network IntelligenceFrom batch questions to business decisions.Keep the evidence in view.
Search production, supplier evidence, movements, readiness, response, and claims through the connected records your teams use.
Follow actual use. Received and used quantities side by side for the four input lots: 500 kg of romaine received, 300 kg used.
Questions across the platform
Which runs consumed LOT-48291, what finished lots did they produce, and which customer receipts remain unconfirmed?
PR-2026-0929-01 records 300 kg of LOT-48291 used with three other ingredient lots. Recorded loss is 58.08 kg; output is 403.20 kg, packed as 48 cases. Five shipments allocate those cases. Four customers have recorded 44-case receipt; Mesa Kitchen's four cases await receipt evidence.
| Customer | Shipment | Cases | Receipt |
|---|---|---|---|
| Northstar Retail | ASN-9941-01 | 20 | Recorded |
| Riverside Retail | ASN-9941-02 | 12 | Recorded |
| Harbor Foods | ASN-9941-03 | 8 | Recorded |
| Canyon Market | ASN-9941-04 | 4 | Recorded |
| Mesa Kitchen | ASN-9941-05 | 4 | Not yet recorded · expected 2:00 PM |
Records: PR-2026-0929-01 · TLC-CAESAR-9941 · ASN-9941-05
Follow the batch and its decisions.Keep the response accountable.
Connect consumed ingredient lots to finished shipments, quality decisions, response actions, and financial review.
Receive and review
Recorded case · Salinas plant FF-SAL-01 · Sep 28, 2026Receipts establish what arrived. Supplier evidence is reviewed in its own lane.
Four supplier lots received, each against its notice
- Romaine LOT-48291
- 500 kg received
- Dressing DRS-260927-14
- 100 kg received
- Parmesan PAR-260926-08
- 80 kg received
- Croutons CRT-260925-22
- 80 kg received
- GVP-SPEC-ROM-014 v3
- Not yet reviewed
- Supplier approval
- Not recorded
- Product movement and actual use
- Document, evidence or notice
- Scope, instruction or decision
- Claim or recovery review
- Not recorded yet
Actual consumption links the batch to its inputs and customers; review, response and claims stay separate decisions.
Connect with the systems you already use.
ImpactRecall connects with the systems your teams already run, so you capture FSMA 204 records without replacing existing tools.
Review the records that apply.Generate the requested view.
Check the events, data, and lot codes required for your listed foods and processing activities.Explore FSMA 204
Map the records.
Choose one plant, product, work order, and actual input/output records.
Connect daily operations.
Bring receipt, production, warehouse, and dispatch records from the systems you use.
Work the exceptions.
Resolve one evidence gap, quantity discrepancy, or missing customer receipt with its owner.
Exercise the response.
Test readiness, multichannel instruction, product reconciliation, and a financial review in the agreed scope.
Find your starting point.Answer what applies.
The answers shape the first scope for one plant. Nothing is sent until you choose to discuss a pilot.