Track & Trace
Track products.Trace their history.
Connect orders, shipments, receipts, and production records to follow where products go and trace the inputs behind them.
SpotlightExplore FSMA 204 PlatformTrack & trace the events, lot codes, relationships, transformation and data required by the FDA.Inside this product history
Four inputs, one finished lot.Five destinations, each with its own state.
4input lotsconsumed by one run
Each keeps its supplier lot code; work order WO-2026-0929-01 links all four to TLC-CAESAR-9941.48casesof 24 packs each
1,152 packs recorded against the finished lot, with the pack factor recorded rather than inferred.5destinations4 received, 1 due today
Mesa’s 4 cases left Gilroy on September 30; delivery is due October 1 at 2:00 PM, with no receipt recorded yet.Daily tracking and tracing
Track today’s movements.Trace each lot in your network.
Follow inbound, outbound, and internal movements. Reconcile split deliveries against orders, connect the lots used in production to finished products, and trace their recorded history upstream and downstream.
Daily operations/Salinas · GilroyOct 1 · snapshot 12:30 PM
Movements · Salinas plant and Gilroy cold storeInbound, internal, and outbound · Sep 29 to Oct 1
1 due today · 1 receiving exception · 5 received
MovementReferenceQuantityState
Outbound · Mesa KitchenGilroy → ScottsdaleASN-9941-054 casesDispatchedEvidence pendingDelivery due 2:00 PM
Inbound · Green Valley ProduceRomaine → Salinas plantASN-GVP-48317480 of 500 kgQuantity unresolved20 kg short, 30 kg held
Internal · Salinas → GilroyReceived Sep 29, 2:30 PMTLC-CAESAR-994148 casesReceipt confirmed
Outbound · Northstar RetailPhoenix DCASN-9941-0120 casesReceipt confirmed
Outbound · Riverside RetailLos Angeles DCASN-9941-0212 casesReceipt confirmed
Outbound · Harbor FoodsSan Diego DCASN-9941-038 casesReceipt confirmed
Outbound · Canyon MarketTempe storeASN-9941-044 casesReceipt confirmed
7 movements · inbound, internal, and outbound across two locations
Dispatched is the movement; the missing receipt is the evidence. Neither makes Mesa overdue before 2:00 PM.
Production and transformation
Manage each transformation.Keep every input lot connected.
Connect work orders, actual ingredient use, and output batches. Use the finished lot’s traceability lot code (TLC) from your production system or generate it with ImpactRecall, then retain the links through packing and distribution.
- 01InputsKeep received lots, recorded units, and available quantities linked to their source records.
- 02TransformationReserve and consume the actual input lots, record each output batch, and retain its TLC and input links.
- 03DistributionKeep the lot identity and recorded pack quantities connected through transfers, shipment allocations, and receipts.
From your production system. TLC-CAESAR-9941 arrives automatically with the run. ImpactRecall links it to PRD-SAL-0929-01, the 4 consumed input lots and quantities, and the Salinas plant.
Fig. 02 / Consumed lots linked across five destinations
Shared records
One order.Every delivery accounted for.
Invite your network partners at no additional cost. Give each partner a portal to share documentation, product records, raise issues, collaborate, and complete their part of the work.
Network Intelligence automatically links shipment and event records to the relevant product and lot in each partner’s portal, without manual re-entry.
The plant’s receipt against the order line
Connect purchase-order lines to each ASN, lot allocation, and receiving record. See what is planned, what has shipped, what was accepted, and what remains outstanding when an order arrives in parts: here, 950 of 1,000 kg accepted after the second delivery arrived short with part of it held.
Purchase orders/PO-2026-1184Freshfield Foods operations
Romaine order · two deliveriesGreen Valley Produce → Salinas plant · received Sep 28 and Oct 1
Ordered1,000 kg
Accepted950 kg
Held · short30 kg · 20 kg
Outstanding50 kg
RecordSupplied byReferenceQuantity
Purchase orderFreshfield FoodsPO-2026-11841,000 kg
Shipping noticeGreen Valley ProduceASN-GVP-48291500 kg
Receiving recordFreshfield FoodsRCV-SAL-48291500 kg
Second noticeGreen Valley ProduceASN-GVP-48317500 kg
Second receiptFreshfield FoodsRCV-SAL-48347480 kg · 450 accepted
Capabilities
Track the movement.Keep the identity behind it.
Follow daily movements and exceptionsSee inbound, outbound, and internal movements by site, then open the shipment or receiving exception requiring attention.
Trace input and output relationshipsFollow ingredients into outputs and destinations, or finished lots back to the actual inputs consumed.
Lot Code ManagementGenerate the lot code from its product, location, and source record, and keep the input lots behind it.
Keep identity across packaging levelsRetain lot and recorded quantity relationships through packs/eaches, cases, pallets, and connected labeling records.
Natural-language search
Ask in plain language.Get answers linked to records.
Ask about shipments, stock, orders, or connected lots. See the answer and open the product, lot, and event records behind it.
Which ingredient lots were used to make TLC-CAESAR-9941? Four ingredient lots and the quantities the run actually consumed.
Powered by Network Intelligence
Follow product across your network.Connect the records behind every handoff.
Automatically link orders, shipment notices, receiving records, and production events from your connected systems and partner portals. Follow each lot through your sites to customer deliveries, with the source records behind every connection.
01 / 06
Keep split deliveries connected to the order.
Link each ASN to its purchase-order line, allocated lots and quantities. Here, a 1,000 kg order has two 500 kg shipping notices, with dispatch and receipt recorded separately.
SuppliersSalinas plantGilroy cold storeCustomers
Purchase orderPO-2026-1184
Line 1Romaine lettuce
Ordered1,000 kg
Advised1,000 kg · 2 ASNs
Dispatched1,000 kg
Fulfilled950 kg accepted
Shipping notice (ASN)ASN-GVP-48291
SupplierGreen Valley Produce
RouteSalinas packing → Salinas plant
Order linePO-2026-1184 · 1
Dispatch recordedSep 27, 2026
LineProductLotQuantity
1Romaine lettuceLOT-48291500 kg
Shipping notice (ASN)ASN-GVP-48317
Line 1 · lotLOT-48347 · 500 kg
Dispatch recordedSep 30, 2026
Shipment line linked to event
Shipment eventEVT-SHP-48291
RomaineLOT-48291500 kgSalinas packing → Salinas plantSep 27
SystemsERPWMS
Exchange routesEDIAPI
Without a systemFile importDirect entry
When a concern arises, the same connected trace supports an assessment in Recall. Explore Recall
The connector network
Connect with the systems you already use.
Connect your existing systems to track movements and trace lot relationships from their operational records.
Showing 152 systems
Don’t see your system? We add connectors on request.All product names, logos, and brands are property of their respective holders and are used for identification only. Use does not imply endorsement.
Request a connector Built around your business
Build your supply chain solution. With us.
Bring us the challenge you want to solve. We’ll work with your team to shape the solution around your operations, systems, and network. Start with a focused pilot or discuss what we can build together.
Research
Read the rules behind each record.At their source.
HubFSMA 204 traceability recordsSee which critical tracking events and key data elements the rule asks you to keep for each lot.IndexFood Network IndexFollow public recalls and emerging risks, each shown with the source it came from.ListFDA Food Traceability ListCheck which foods the rule covers before deciding which lots need full records.
FAQ
Traceability questions,answered.
ArticleWhy tracing an outbreak depends on microscopic cluesRead BBC’s reporting on the records and testing behind a Cyclospora investigation.Read the articleYes. ImpactRecall automatically ingests relevant records from connected ERP, warehouse, purchasing, production, and labeling systems. It links product identities, lots, quantities, and events while retaining their source references. Your team can use imports or manual entry where a connection is unavailable. Together, we agree which records each system supplies and how they map to your workflow.
ImpactRecall retains source identifiers and supports product and identifier mapping, including UPC/GTIN formats. The connection must preserve the relevant supplier, product, lot, and source context; a matching product description alone does not establish that two records refer to the same lot. Where the source lacks the required lot relationship, the gap remains visible for review.
Yes. Invite suppliers and customers at no additional cost. Partner portals support product records, documentation, issues, and assigned work. Network Intelligence automatically links relevant shipment and event records to the corresponding product and lot in each portal, avoiding duplicate entry. Partners without a system connection can use supported entry or import routes; somebody still has to record the real dispatch, receipt, or other event.
Each purchase-order line can connect to multiple ASNs, with their own product lines, lot allocations, and quantities. Compare each delivery with its receiving record, retaining advised, dispatched, received, accepted, held, and short quantities separately. For example, 950 kg accepted against a 1,000 kg order leaves 50 kg outstanding: 30 kg arrived but is held, while 20 kg is short.
No. An ASN starts the paired shipping and receiving event lifecycle and communicates the intended shipment. Actual dispatch, receipt, and production movements establish stock positions. A notice alone does not prove goods left the supplier or arrived at the destination. ImpactRecall keeps these states distinct so planned quantities are not mistaken for available inventory or accepted fulfillment.
Connect each recorded output batch to the input lots and quantities actually consumed for it, with its production or work-order reference. This supports an ingredient lot feeding multiple outputs and an output consuming multiple ingredients or lots. Connected production records can supply those relationships automatically. A BOM describes the planned recipe; it does not prove which lots supplied a particular batch.
Use the output TLC assigned by your production system or generate it with ImpactRecall, keeping its source and input links. Shipping alone does not create a new TLC. For covered FTL foods, FDA treats repacking as transformation; like-into-like repacking may retain the code, but the source changes to the repacking location and transformation records are still required.
ImpactRecall preserves recorded product, lot, quantity, and packaging relationships through packs/eaches, cases, pallets, and labeling records. An explicit factor can relate one case to 24 packs. Weight and counted quantities retain their own units; the system does not infer kilograms-to-cases conversion or production yield. If repacking changes the output lot, the recorded transformation connects the original and new identities.
Yes. Connected stock, allocation, and movement records support lot-level positions by location, distinguishing available, reserved, held, and in-transit quantities. Retain the source and update context behind each position. A historical receipt shows what arrived at that time, not what remains available now; a dispatched shipment does not prove the destination has received it.
ImpactRecall connects the recorded dispatch and receipt at each applicable location. Under FDA guidance, covered transfers between different street addresses require shipping and receiving records even within one company. A brief cross-dock carrier transfer can be different from taking goods into inventory; the activity determines the records required. Centralized records must preserve each site’s event and location context.
The trace shows the available linked records and identifies the evidence still outstanding. A recorded dispatch is not a confirmed customer receipt. Keep follow-up work connected to the relevant shipment, product, and lot, with partner portals supporting completion of the partner’s part. A receipt expected later is not automatically overdue, and missing evidence is not invented to complete the history.
Yes. Start from the ingredient lot and follow actual consumption into recorded outputs, transfers, and customer shipments. A shared recipe or supplier alone does not establish a connection. ImpactRecall distinguishes linked lineage from unrelated product, helping your team investigate the relevant records. The decision to hold or recall product requires assessment; a trace relationship does not automatically confirm action scope.
ImpactRecall brings linked events, lot identities, quantities, locations, source references, and configured export templates together, with missing evidence identified. Covered businesses generally must provide FDA-requested records within 24 hours, or another reasonable time FDA agrees to. Readiness depends on captured records and workflow responsibilities. Preparing an export neither fills gaps nor submits a filing automatically.
Both. Bring the workflow or supply-chain challenge you want to improve. We’ll work with your team to shape the solution around your systems, records, sites, and partners. Start with a focused pilot or agree a configuration and implementation together, with measures of success defined before evaluation. Seven-day trial access is a separate way to explore the product, rather than a substitute for a jointly scoped pilot.