RFID in Food and Agriculture

RFID in Food and Agriculture: Farm-to-Fork Traceability

Food traceability is moving from voluntary best practice to regulatory requirement across major markets: FDA FSMA Rule 204 (US), EU Food Information Regulation No. 1169/2011, China GB standards, and the emerging EU Digital Product Passport for food products. RFID and EPC provide the technological backbone for automated, high-throughput farm-to-fork traceability.

The Traceability Problem in Food

Traditional food traceability relies on paper records, manual data entry, and barcode scans at discrete points. This creates: - Gaps between hand-off points (farm → processor → distributor → retailer) - Latency of 7–10 days for a typical outbreak investigation (vs. hours with RFID + EPCIS) - Inability to do targeted recalls (entire category pulled vs. specific lot)

The 2018 romaine lettuce E. coli outbreak took 11 days to trace to a single California growing region. FDA cites this case as the driver for FSMA Rule 204 requiring "key data elements" to be captured and queryable within 24 hours.

Livestock and Individual Animal ID

Individual animal identification uses low-frequency RFID per ISO 11784/11785 (the same standard used for pet microchips):

See the RFID Livestock guide for detailed animal ID implementation.

The 15-digit animal ID number encoded in the ISO 11784 tag maps to a national or regional livestock database (USDA NLIS in Australia, BCMS in the UK, NAIS in the US). Slaughter facilities read ear tags at entry, linking the live animal record to the carcass tracking system.

Carcass and Cut Tracking (UHF RFID)

After slaughter, carcasses move through a temperature-controlled chain where tracking switches from LF animal ID to UHF EPC for:

• Carcass hang tags — UHF flag tags attached to the Achilles tendon for individual carcass tracking through chilling, grading, and breaking
• Primal cut labels — UHF inlays on label applied at fabrication, encoding SGTIN linked to the parent animal ID
• Carton labelling — UHF smart labels on corrugated cartons, SSCC encoded

The critical link is parent-child association: the parent animal's ISO 11784 ID is recorded at slaughter and linked to every child SGTIN created from that carcass. This is the chain-of-provenance that enables breed and origin claims (Wagyu, USDA Prime, CRSQ) and enables rapid targeted recalls.

Produce and Horticulture

Produce traceability under FSMA 204 requires tracking at the farm level (growing area, harvest crew, harvest date) through cooling, packing, and distribution. RFID deployment patterns:

Reusable Plastic Container (RPC) tracking: - UHF tags embedded in or attached to RPCs - Pallets of RPCs scanned at farm → packing house → DC → retailer - EPCIS OBSERVE events record custody transfers - Tag must survive wash cycles (IP68 rated, detergent resistant) - Average RPC makes 50–100 cycles; tag must survive 500+ wash cycles

Case-level tracing (FSMA 204 minimum): - SSCC on corrugated case (barcode + RFID for automation) - Case linked to lot/sublot at packing - Retailer DC reads SSCC at receiving (dock portals) - Downstream EPCIS query traces case to harvest lot in < 24 hours

Item-level (retail future state): - Individual pack UHF labels (consumer unit = GTIN + serial) - Enables store-level expiry management and consumer scan for provenance - Currently at pilot stage (Walmart, Tesco Heritage)

Cold-Chain Monitoring Integration

Fresh produce and meat require temperature monitoring throughout the chain. RFID integrates with cold-chain monitoring in two ways:

1. RFID + separate logger — Standard UHF tag encodes SSCC; a separate USB or BLE data logger accompanies the shipment. RFID enables automated check-in; logger provides temperature proof.

2. RFID + sensor tag — Semi-passive tags like the EM4325 store a temperature log in user memory. A single reader scan at receiving captures both the EPC (for EPCIS) and the temperature log (for food safety compliance). See the EM Microelectronic guide.

EPCIS 2.0 for Farm-to-Fork

EPCIS events model every step of the food chain:

With all parties sharing events to a common EPCIS repository (or a federated network like GS1 Verified by GS1), an outbreak investigation can traverse the full chain in minutes. See the EPCIS Implementation guide.

Regulatory Compliance Checklist (FDA FSMA 204)

• [ ] Critical Tracking Event (CTE) records for each hand-off
• [ ] Key Data Element (KDE) capture: traceability lot code, quantity, unit of measure, location (GLN), date
• [ ] Records accessible within 24 hours of FDA request
• [ ] Records retained for 2 years
• [ ] RFID/barcode system capable of traceability lot code linkage

Use the EPC Encoder to create correctly formatted GTINs and SSCCs for FSMA-compliant case labelling.

See also: RFID Livestock, EPCIS Implementation, Understanding EPC.