FSMA 204 Platform
Capture the records.Answer FDA requests.
Connect your existing systems, trace lots through transformation, and generate the records to send directly to the FDA contact.
Track & TraceTrace every step behind the recordsFollow each lot’s source, use, location movements, and receiving evidence through the food network.Caesar Salad Kit · 350 g
PR-2026-0929-01- Selected event
- Transformation · PR-2026-0929-01
- New TLC
- TLC-CAESAR-9941 · 48 cases · 1,152 packs
- TLC source
- Salinas plant · FF-SAL-01
Transformation PR-2026-0929-01 selected
Input lots actually consumed
Caesar Salad KitTLC-CAESAR-994148 cases · 1,152 packsTLC source Salinas · FF-SAL-01
Receiving, transformation and shipping stay linked to one finished lot.
Selected event
Transformation · PR-2026-0929-01Completed Sep 29, 2026Salinas plant · FF-SAL-01Input lot
Romaine · LOT-48291300 kg consumed of 500 kg receivedNew output
TLC-CAESAR-9941Caesar Salad Kit · 350 g retail packs, 24 per case48 cases · 1,152 packsTLC source
Freshfield Foods · FF-SAL-01Full location description availableReference document
Production record · PRD-SAL-0929-01Receiving, transformation and shipping · 3 of 16
| Event | Location or movement | Date and time | Lot or run | Quantity |
|---|---|---|---|---|
| Receiving | Salinas plant | Sep 28, 2026 · 7:45 AM | LOT-48291 | 500 kg |
| Transformation | Salinas plant | Sep 29, 2026 · 9:00–11:30 AM | PR-2026-0929-01 | 48 cases |
| Shipping | Salinas plant → Gilroy cold store | Sep 29, 2026 · 12:30 PM | TLC-CAESAR-9941 | 48 cases |
- ReceivingSalinas plant
- Lot or run
- LOT-48291
- Quantity
- 500 kg
- TransformationSalinas plant
- Lot or run
- PR-2026-0929-01
- Quantity
- 48 cases
- ShippingSalinas plant → Gilroy cold store
- Lot or run
- TLC-CAESAR-9941
- Quantity
- 48 cases
All 16 recorded events · 2026 · Pacific timeSnapshot Oct 1, 12:30 PM
| Event | Location or movement | Date and time | Lot or run | Quantity |
|---|---|---|---|---|
| Receiving | Salinas plant | Sep 28, 2026 · 7:45 AM | LOT-48291 | 500 kg |
| Receiving | Salinas plant | Sep 28, 2026 · 8:00 AM | DRS-260927-14 | 100 kg |
| Receiving | Salinas plant | Sep 28, 2026 · 8:15 AM | PAR-260926-08 | 80 kg |
| Receiving | Salinas plant | Sep 28, 2026 · 8:30 AM | CRT-260925-22 | 80 kg |
| Transformation | Salinas plant | Sep 29, 2026 · 9:00–11:30 AM | PR-2026-0929-01 | 48 cases |
| Shipping | Salinas plant → Gilroy cold store | Sep 29, 2026 · 12:30 PM | TLC-CAESAR-9941 | 48 cases |
| Receiving | Gilroy cold store | Sep 29, 2026 · 2:30 PM | TLC-CAESAR-9941 | 48 cases |
| Shipping | Gilroy → Northstar RetailPhoenix DC | Sep 30, 2026 | TLC-CAESAR-9941 | 20 cases |
| Shipping | Gilroy → Riverside RetailLos Angeles DC | Sep 30, 2026 | TLC-CAESAR-9941 | 12 cases |
| Shipping | Gilroy → Harbor FoodsSan Diego DC | Sep 30, 2026 | TLC-CAESAR-9941 | 8 cases |
| Shipping | Gilroy → Canyon MarketTempe store | Sep 30, 2026 | TLC-CAESAR-9941 | 4 cases |
| Shipping | Gilroy → Mesa KitchenScottsdale | Sep 30, 2026 | TLC-CAESAR-9941 | 4 cases |
| Receiving | Northstar RetailPhoenix DC | By Oct 1 snapshot; receipt time not recorded | TLC-CAESAR-9941 | 20 cases |
| Receiving | Riverside RetailLos Angeles DC | By Oct 1 snapshot; receipt time not recorded | TLC-CAESAR-9941 | 12 cases |
| Receiving | Harbor FoodsSan Diego DC | By Oct 1 snapshot; receipt time not recorded | TLC-CAESAR-9941 | 8 cases |
| Receiving | Canyon MarketTempe store | By Oct 1 snapshot; receipt time not recorded | TLC-CAESAR-9941 | 4 cases |
- ReceivingSalinas plant
- Lot or run
- LOT-48291
- Quantity
- 500 kg
- ReceivingSalinas plant
- Lot or run
- DRS-260927-14
- Quantity
- 100 kg
- ReceivingSalinas plant
- Lot or run
- PAR-260926-08
- Quantity
- 80 kg
- ReceivingSalinas plant
- Lot or run
- CRT-260925-22
- Quantity
- 80 kg
- TransformationSalinas plant
- Lot or run
- PR-2026-0929-01
- Quantity
- 48 cases
- ShippingSalinas plant → Gilroy cold store
- Lot or run
- TLC-CAESAR-9941
- Quantity
- 48 cases
- ReceivingGilroy cold store
- Lot or run
- TLC-CAESAR-9941
- Quantity
- 48 cases
- ShippingGilroy → Northstar Retail · Phoenix DC
- Lot or run
- TLC-CAESAR-9941
- Quantity
- 20 cases
- ShippingGilroy → Riverside Retail · Los Angeles DC
- Lot or run
- TLC-CAESAR-9941
- Quantity
- 12 cases
- ShippingGilroy → Harbor Foods · San Diego DC
- Lot or run
- TLC-CAESAR-9941
- Quantity
- 8 cases
- ShippingGilroy → Canyon Market · Tempe store
- Lot or run
- TLC-CAESAR-9941
- Quantity
- 4 cases
- ShippingGilroy → Mesa Kitchen · Scottsdale
- Lot or run
- TLC-CAESAR-9941
- Quantity
- 4 cases
- ReceivingNorthstar Retail · Phoenix DC
- Lot or run
- TLC-CAESAR-9941
- Quantity
- 20 cases
- ReceivingRiverside Retail · Los Angeles DC
- Lot or run
- TLC-CAESAR-9941
- Quantity
- 12 cases
- ReceivingHarbor Foods · San Diego DC
- Lot or run
- TLC-CAESAR-9941
- Quantity
- 8 cases
- ReceivingCanyon Market · Tempe store
- Lot or run
- TLC-CAESAR-9941
- Quantity
- 4 cases
Event-field review and expected receivingSnapshot October 1 · Recorded events and expected events use distinct denominators
- recorded events
- 16
- field sets checked
- 15
- not yet reviewed
- 1
| Review group | Reference | Cases | State |
|---|---|---|---|
| Northstar receipt | RCV-NSR-0930 | 20 | Receipt confirmed |
| Riverside receipt | RCV-RVR-0930 | 12 | Receipt confirmed |
| Harbor receipt | RCV-HBF-0930 | 8 | Receipt confirmed |
| Canyon field review | RCV-CNM-0930 | 4 | Not yet reviewed |
| Mesa expected receiving | ASN-9941-05 | 4 shipped | Evidence pending |
| Canyon’s receipt is recorded; its field review is separate. Mesa’s receipt is expected after the snapshot. |
- Northstar receipt
- Reference
- RCV-NSR-0930
- Cases
- 20
Receipt confirmed - Riverside receipt
- Reference
- RCV-RVR-0930
- Cases
- 12
Receipt confirmed - Harbor receipt
- Reference
- RCV-HBF-0930
- Cases
- 8
Receipt confirmed - Canyon field review
- Reference
- RCV-CNM-0930
- Cases
- 4
Not yet reviewed - Mesa expected receiving
- Reference
- ASN-9941-05
- Cases
- 4 shipped
Evidence pending - Canyon’s receipt is recorded; its field review is separate. Mesa’s receipt is expected after the snapshot.
Transformation sources PR-2026-0929-01Each source document stays linked to its event, lot and location.
| Reference | Record | Issued at | Date | Action |
|---|---|---|---|---|
| PRD-SAL-0929-01 | Production recordTransformation · TLC-CAESAR-9941 | Salinas plant | Sep 29, 2026 | |
| RCV-SAL-48291 | Receiving recordLOT-48291 · 500 kg | Salinas plant | Sep 28, 2026 | |
| ASN-9941-01 | Shipping notice20 cases to Northstar | Gilroy cold store | Sep 30, 2026 | |
| RCV-CNM-0930 | Receiving record4 cases · field review open | Canyon Market | By snapshot | |
| TPL-2026-001 | Traceability planProcedures and TLC assignment | Freshfield Foods | Current at snapshot |
Why it matters
Respond from connected records.Without rebuilding the workbook.
1 click: generate the requested spreadsheet.
Assemble the selected traceability records without rebuilding a workbook from disconnected systems.
Lot to each: keep identity through transformation and distribution.
Preserve actual input/output links and recorded packaging relationships.
Unlimited: bring suppliers and customers into the network.
Invited partners participate free, with no per-supplier or per-customer charge.
Traceability in daily operations
Capture each event.Keep the required data connected.
Bring event records together, preserve lot and source information, and resolve gaps before a request arrives.
Sources/RCV-SAL-48291Mapped to receiving fields
Receiving record to receiving fieldsCaesar Salad Kit · Salinas plant · Receiving, transformation, shipping
TLCLOT-48291
Quantity and unit500 kg
ProductRomaine lettuce, fresh
Previous sourceGreen Valley Produce
Receiving locationFF-SAL-01
Receipt dateSep 28, 2026
TLC sourceGVP-SAL-01
ReferenceRCV-SAL-48291
Listed foodLeafy greens, fresh
Source records
RecordReferenceSource
Supplier noticeASN-GVP-48291EDI
ReceivingRCV-SAL-48291WMS
Lot traceability
Trace through transformation.Keep every case and each connected.
Link consumed input lots to the finished TLC, then preserve lot and source information through each recorded handoff.
- 01Received inputsInput references retain the food and used quantity.
- 02Transformation and outputThis event assigns the output lot at Salinas.
- 03Shipping and receivingThe same lot stays with each shipping record.
Fig. 02 / Lot identity joins the recorded event context
Traceability plan and records
Maintain your traceability plan.Connect its records.
Keep procedures, contacts and supporting event records together, with the detail behind each part of the plan.
FSMA 204 Traceability Record · Foods, sites and activities
Freshfield FoodsCaesar Salad Kit · 350 g · Salinas plant and Gilroy cold store
- Plan
- TPL-2026-001
- Contact
- Traceability coordinator
- Snapshot
- Oct 1, 2026
Listed food
Recorded field group: Listed food.
FoodCaesar Salad Kit · 350 g · CSK-350
Listed ingredientRomaine lettuce, fresh leafy greens
Form in the finished foodFresh, retains its listed form
Identification procedureProduct descriptions checked against the Food Traceability List
Supporting ingredients stay in the genealogy; their listing is not assumed.
Locations and events performed
Recorded field group: Locations and events.
LocationIDTracking events
Salinas plantFF-SAL-01Receiving, transformation, shipping
Gilroy cold storeFF-GIL-01Receiving, shipping
Exemption basis
Recorded field group: Exemption basis.
ExemptionNone recorded for this food
Applies toBoth locations
Recorded field groupsFood, form and performed events recorded for both locations
- Listed food
- Locations and events
- Exemption basis
FDA request response
Generate the requested records.Send them in seconds.
Create a sortable spreadsheet for the requested foods, lots and dates, and send the documentation directly to the FDA contact.
One-click FDA records response
Select the request scope, generate the sortable spreadsheet with its supporting traceability records, and send directly from ImpactRecall.
Records requestFreshfield Foods · Snapshot Oct 1, 2026
- Requested scope, complete
- Generate spreadsheet, next
- Preview package, not started
- Send to FDA contact, not started
Requested scope
- Food
- Caesar Salad Kit · 350 g · CSK-350
- Lot
- TLC-CAESAR-9941 and its input lots
- Dates
- Sep 28 to Oct 1, 2026
- Locations
- Salinas FF-SAL-01 · Gilroy FF-GIL-01 · 5 customers
- Recorded events
- 16 · receiving, transformation, shipping
- Recipient
- FDA request contact
Scope selected. Ready to generate.
Required data, checked against its source.
Review applicable KDEs and the original record behind each finding.
Receiving fieldsRCV-SAL-48291
- TLC
- LOT-48291 · matches the notice
- Quantity
- 500 kg · matches the receipt
- TLC source
- GVP-SAL-01 · from ASN-GVP-48291
- Receipt date
- Sep 28, 2026
Each finding opens the source record behind it.
TLC and source, carried together.
Keep the code and assigning location/source reference available through subsequent events.
TLC-CAESAR-9941
- Transformation
- Salinas · source FF-SAL-01
- Shipping to Gilroy
- Salinas · source FF-SAL-01
- Receiving at Gilroy
- Source FF-SAL-01
- Shipping to Phoenix
- Gilroy · source FF-SAL-01
Shipping and receiving keep the code; they do not assign a new one.
Missing information, assigned for follow-up.
Show the exact field/record, responsible participant and correction needed.
Field review requestREQ-CNM-0930-01
- Record
- RCV-CNM-0930 · receiving fields
- Participant
- Canyon Market · Tempe store
- Correction needed
- Review the recorded fields against the receipt
- State
- Not yet reviewed
No field is marked missing until the review confirms it.
Natural-language traceability search
Find the answer across your records.Follow the source behind it.
Explore foods, lots, event records, missing information and request readiness in plain language.
Inputs behind the lot. The romaine lot actually consumed, the transformation and the finished lot.
Powered by Network Intelligence
Keep traceability connected.From source lot to FDA response.
Follow required information through your suppliers, operating locations and customers, with the source records behind each handoff.
01 / 06
Keep the lot and source with the receipt.
Each receipt keeps the source TLC, quantity, date, previous source and reference document linked to the received lot.
SuppliersSalinas plantGilroy cold storeCustomers
Notice availableGoods expectedReceiving recordedQuantities comparedReceipt confirmed
Supplier shippingEVT-SHP-48291
FromGreen Valley Produce
Source TLCLOT-48291
Dispatched500 kg
DateSep 27, 2026
ASN-GVP-48291shared reference
Plant receivingEVT-RCV-48291Receipt confirmed
AtSalinas plant · FF-SAL-01
Source TLCLOT-48291
Received500 kg
TimeSep 28, 2026 · 7:45 AM
Dispatched 500 kgReceived 500 kgDifference 0 kg
Inbound connections · Select a lot
The connector network
Connect with the systems you already use.
Capture traceability information from your existing ERP, WMS, production and EDI systems. Import spreadsheets or add records where you need an alternative.
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 Your connected food network
Bring your network with you.Suppliers and customers join free.
Invite unlimited suppliers and customers to share traceability information and resolve gaps, with no additional partner charge.
Customers record what they receive.
Each customer’s receipt links to its own shipment of TLC-CAESAR-9941, with cases and retail packs recorded together.
Shipments/TLC-CAESAR-9941Customer receipts
Gilroy cold store to five customersShipped Sep 30, 2026
Customers5
Cases48
Retail packs1,152
Receipts recorded4
CustomerShipmentCases · packsReceipt
Northstar RetailASN-9941-0120 · 480RCV-NSR-0930
Riverside RetailASN-9941-0212 · 288RCV-RVR-0930
Harbor FoodsASN-9941-038 · 192RCV-HBF-0930
Canyon MarketASN-9941-044 · 96RCV-CNM-0930
Mesa KitchenASN-9941-054 · 96Expected
Work with us
Test your traceability workflow. Rehearse the FDA response.
Bring a covered food and its records. Work through the handoffs, outstanding information and response package with your team.
Research
Understand the requirements.Prepare the records.
RuleFDA Food Traceability RuleRead the final rule, its record requirements, and FDA’s current compliance date.ListFDA Food Traceability ListCheck whether the foods you handle are on the list before scoping records.GuideFDA sortable spreadsheet guidanceSee FDA’s optional template, the fields for each event you perform, and how a response is organized.
FAQ
FSMA 204 questions,answered.
GlossaryFSMA 204 glossaryLook up critical tracking events, key data elements, and traceability lot codes.Open the glossaryYes. Select the requested foods, lots and dates, generate a sortable spreadsheet with its supporting traceability records, preview the package, and send it to the FDA contact named in the request. Sending shares the records; it is not FDA acceptance or a separate regulatory filing.
When FDA requests them, you provide the records and the information needed to understand them within 24 hours, or within a reasonable time FDA agrees to. In specified circumstances FDA can also ask for an electronic sortable spreadsheet, and some businesses are exempt from that format. The 24 hours is a limit, not a waiting period: you can generate and share the records as soon as the scope is set.
Yes. The transformation record links the input lots actually consumed, and their quantities, to the new output lot, and the recorded packaging relationship carries that lot to cases and retail packs. Freshfield’s run used 300 kg of romaine lot LOT-48291 to make TLC-CAESAR-9941: 48 cases of 24 packs, 1,152 packs, all one lot. ImpactRecall uses the recorded pack factor; it does not calculate yield.
The rule assigns a TLC at initial packing of a raw agricultural commodity not obtained from a fishing vessel, at first land-based receiving of food obtained from a fishing vessel, and at transformation. Shipping and receiving keep the existing code, with the rule’s specific exceptions. Repacking or relabeling is generally a transformation; FDA’s FAQs describe when like-into-like repacking can keep the original code, so check the specific case. Freshfield assigns TLC-CAESAR-9941 at Salinas and keeps it through Gilroy.
The TLC identifies the lot. The TLC source is the physical location where the code was assigned, with its full location description. A source reference is another way to give FDA access to that description, such as a web address or an FDA Food Facility Registration number. A GTIN, a GLN or the ship-from address on a label does not automatically stand in for any of them.
Foods on the Food Traceability List, including foods that contain a listed food as an ingredient in its listed form. The records apply to the critical tracking events you perform at each location, subject to the rule’s exemptions. A tracked ingredient is not covered just because ImpactRecall traces it: Freshfield’s fresh romaine is listed, while its Parmesan is not treated as listed.
Yes, when the sites are at different street addresses. Freshfield records shipping at the Salinas plant and receiving at the Gilroy cold store, with the same TLC and its Salinas source. Moving food within one location is not a shipping event.
Yes. Connect ERP, WMS, production and EDI records through existing integrations, import spreadsheets, or add records directly. Each record keeps its source reference, and records you already hold can supply the required information without re-entering it.
ImpactRecall shows the specific record and field, sends the request to the participant responsible, and keeps the correction linked to its source for review. It does not fill in a missing value. A receipt expected later is not missing, and a field awaiting review is not confirmed missing: Mesa’s receipt is expected, and Canyon’s receiving fields are still to be reviewed.
The procedures you use to maintain the records, including their format and location; how you identify foods on the list; how you assign TLCs where that applies; and a point of contact for questions. Farms that grow or raise a listed food, other than eggs, also include a farm map. A traceability plan is different from a recall plan.
Generally two years from the date you created or obtained the records. When you update the traceability plan, keep the previous version for two years. Check any exception that applies to your activities, and confirm the retention settings in your configuration.
No. Invite unlimited suppliers and customers at no additional cost to share traceability information and resolve gaps. The subscription covers the locations you manage, so a site you operate as one of your managed locations is priced as yours, while invited partners join free.
Yes. Choose a food, lot and date range, retrieve the event records, review the open and missing information, generate the package, and share it with a test contact your team controls. A rehearsal never sends to FDA.
As of October 11, 2026, FDA describes a proposed rule to extend the compliance date to July 20, 2028, and Congress has directed FDA not to enforce the rule before that date. The extension is proposed, not final, so check FDA’s compliance date information for the current position.