Recall with precision.Respond with speed.

Yes. Start with your existing plan and the order, warehouse, production, and labeling records you use today. Connect supported systems or bring records through manual and spreadsheet routes. Together, we can agree the workflow, responsibilities, and data coverage for a focused pilot or implementation. Importing a plan does not automatically turn every document into an executable workflow.

• Discuss a pilot
• Track and Trace

It can start an issue and alert the team to assess it. Connect the concern to product and lot records, gather evidence, and review affected destinations. Your authorized team confirms whether to initiate a recall and what needs action. External alerts provide context; they do not establish that your own stock is affected or replace the recorded decision.

• Issue and scope

Use the actual ingredient consumption, production outputs, and downstream movements to build the evidence for scope. Retain the authorized inclusion/exclusion decision and its basis. Sharing an order, supplier, or production reference does not automatically place another lot in scope. Missing records remain an investigation gap, not proof that product can safely be excluded.

• Track and Trace
• FSMA 204

Trigger AI phone calls, SMS, WhatsApp, email, and in-app alerts through your configured response workflow. Capture explicit acknowledgments and follow up or escalate outstanding work. Keep communication outcomes separate from completed physical actions. An answered call, delivered notice, or read message is not by itself evidence that affected product was removed or controlled.

• Communications
• Contact us

Keep contact failures and missing acknowledgments visible without holding up notices to valid recipients. Correct details, resend, and retain the communication history. Configured follow-up and escalation keep outstanding work assigned. Where one contact represents several sites, each location retains its own product quantities, required actions, and response status.

• Communications

Retain the earlier decision and review the amendment against its supporting records. Record changed products, locations, or quantities and the resulting instructions and follow-up. Reconciliation clarifications retain their revisions and decision history, so a later correction does not erase the basis used previously. The team reviews the change; a revised quantity is not automatically an approved claim.

• Scope decision
• Recall Case Record

Record sold or consumed quantities separately from stock requiring physical action. Follow recorded onward transfers and retain the responsible locations and source events. Reconcile quantities against the governed basis for each product, lot, and unit; do not count an internal transfer as additional stock. Product accounted for is not necessarily recovered or eligible for a customer credit.

• Product reconciliation

Keep the reported action, quantity, and evidence-review state separate. Retain mismatches, clarification requests, revisions, and the review behind any approved exception. Missing evidence or unreported quantities remain visible as outstanding work rather than being treated as zero. Photos or documents support review; uploading them does not automatically establish accepted evidence.

• Recall Case Record

Record the quantity and its unit alongside the product, lot, and location. Use documented packaging relationships when comparing cases, packs, or eaches; keep weight and count measures separate unless a governed conversion exists. Reconcile against the authoritative quantity basis so that repeated receipts, transfers, or disposition records do not count the same product twice.

• Track and Trace

Review claimed quantities and cost components against product outcomes, applicable rates, and supporting records. Preserve the submitted breakdown, responsibility assessment, and each review decision. Requested, approved, settled, and outstanding amounts remain distinct, as do customer liabilities and supplier or insurance recoveries. A disputed or unsupported claim is not automatically fraud; approval alone is not proof of cash received.

• Financial Reconciliation
• Contact us

The maintained case brings together the issue reference, scope decisions, participants, communications, product reconciliation, claims, and recoveries. Generate a dated report of the recorded state, including review histories, responsibility, root cause, corrective actions, and closure checks. The supplied export is titled Product Recall Case Bible. Missing information remains explicit; generation does not make every entry verified or refresh an exported PDF automatically.

• Recall Case Record
• Financial Reconciliation

Review whether recipients received instructions, acknowledged them, and took the required action. Check quantities, evidence, unresolved obligations, and required effectiveness work before the authorized internal closure decision. Retain root cause, responsibility, and corrective actions. Internal case closure is distinct from FDA termination of a recall; agency status and required communications must be reviewed separately.

• Case control
• 21 CFR Part 7, Subpart C (opens in a new tab)

Yes. Use your plan and defined participants in controlled TEST ONLY exercises, separate from live recalls. Test communications, acknowledgment, escalation, quantity reconciliation, and evidence review, then retain the debrief and improvements. Unlimited mock recall simulations are offered with seven-day free trial access. Exercises must follow their test configuration, rather than issue unintended live recall notices.

• Discuss a pilot

Review exercise results, outstanding actions, and evidence gaps to identify where further preparation is needed. In live cases, Recall Insights shows response progress, unresolved quantities, and recorded financial position with access to the underlying case. Keep exercise findings, live-case measures, and external public reports separate. Readiness is reviewed against each exercise's defined measures rather than a single universal score.

• Recall preparedness
• Recall Insights

Traceability records help establish the inputs, outputs, and destinations behind a scope assessment. Recall management uses that context to coordinate instructions, reconcile outcomes, and retain the case decisions. FSMA 204 recordkeeping and a recall response serve different purposes; meeting one requirement does not automatically satisfy the other. Explore the platform and source guidance for your operation’s record obligations.

• FSMA 204