Chain WatchMaterial changes in rules, standards, systems, recalls, and official operating guidance.

Guidance clarification in reviewFDA FAQ keeps EPCIS optional for Food Traceability Rule compliance Standards record reviewGS1 EPCIS 2.0 carries condition and food-safety event context beyond location Inspection procedure updateCFIA updates system-verification procedure for preventive controls and traceability Official discussion paperFDA opens a lot-level traceability flexibility discussion

FDA / CFIA / EUJURISDICTION BEFORE TEMPLATERegulatory Scope · Official regulatory-baseline comparison

Lead story: US, Canada, and EU food traceability baselines differ

FDA's Food Traceability Rule adds critical-tracking-event and key-data-element records for foods on the Food Traceability List. Canada's SFCR baseline uses one-step-back and one-step-forward records with a two-year retention rule. EU General Food Law Article 18 sets supplier and business-customer traceability duties. A cross-border design should preserve each jurisdiction's scope, event model, identifiers, timing, and authority instead of treating one template as universal.

By Food Traceability Ledger Evidence DeskOctober 12, 20268 min read

Consumer Claim Governance · Official food-traceability platform analysis

TE-FOOD consumer claims need lot-level evidence authority

TE-FOOD presents traceability as support for communicating quality and sustainability claims to consumers. A product or lot identifier can connect evidence, but the public claim still needs an approved text, defined scope, authoritative supporting record, applicable market, effective period, and correction or withdrawal path.

By Food Traceability Ledger Evidence DeskOctober 7, 20267 min read

FDA & FSMA · Official FDA rule and guidance analysis

FDA kill-step exemption needs a dated application record

FDA distinguishes a person's own documented kill step, food received after a prior kill step, and food promised to a later kill step under a written agreement. A generic process claim cannot establish which exemption path applies to a particular food, lot, event, and time.

By Food Traceability Ledger Evidence DeskOctober 6, 20267 min read

Food-chain traceability intelligence

View newsroom

October 7, 2026

TE-FOOD consumer claims need lot-level evidence authority

October 6, 2026

FDA kill-step exemption needs a dated application record

September 22, 2026

SMART EMP swab findings need zone-time-lot assessments

Smart Food Safe says SMART EMP maps swab sites, zones, risks, limits, planned and random samples, results, and corrective actions. A positive environmental result identifies a sampled site and time, not a contaminated product lot by itself. Food-safety teams need a documented rule for which production lines, periods, lots, and controls are assessed before a hold or release decision.

September 17, 2026

TallyVision defect labels need image-to-lot lineage

ThisFish says TallyVision uses cameras and computer vision to inspect fish fillets continuously, classify size and color, detect five defect types, and filter results by supplier, lot, or work order. A machine label can support quality review, but it is not a product disposition or a traceability event unless the image, inspected item, production context, and governed lot record stay linked.

September 16, 2026

FDA preventive controls keep four record states separate

FDA's preventive-controls overview distinguishes monitoring, corrections, corrective actions, and verification after a facility identifies a hazard requiring a control. Food traceability can help locate affected material, but a lot history cannot substitute for the execution and review evidence in any of those four states.

September 15, 2026

Croptracker block provenance needs a harvest-to-pack bridge

Croptracker describes farm records and trace reports that can identify a product's originating block and responsible employee. Block-level origin helps only when harvest containers, transfers, packing runs, commingling, labels, shipment lots, and exceptions retain a reproducible link across the next custody boundary.

How the market is organized

Explore all

External chain

Trading-partner events must survive system boundaries

A food lot can move through farms, vessels, packers, processors, warehouses, distributors, retailers, and foodservice. Useful traceability preserves event meaning as identities and formats change.

Read the market record →

Internal genealogy

Transformation is where lot records become operating evidence

Manufacturing, commingling, rework, repacking, and relabeling connect incoming lots to outputs. Buyers need to see how yield, exceptions, corrections, and historical lineage are retained.

Read the market record →

Recall readiness

A search result is not a completed recall system

Investigation, scope, decision authority, notices, inventory status, disposition, reconciliation, and effectiveness evidence remain separate responsibilities even when product can be found quickly.

Read the market record →

Interoperability

Identifiers and event standards reduce translation—not accountability

GS1 identifiers, EPCIS, APIs, EDI, and sortable spreadsheets can make exchange more consistent. Data ownership, partner onboarding, validation, exceptions, and source lineage still require governance.

Read the market record →

Regulation and standards record

Explore all

FDA Food Traceability RuleFinal rule in force; FDA proposed a compliance-date extension and Congress directed non-enforcement before July 20, 2028 · Covered domestic and foreign persons that manufacture, process, pack, or hold foods on the Food Traceability List for U.S. consumption, subject to the rule's definitions and exemptions

Codified U.S. food traceability requirementsCurrent codified regulation · Covered persons and Food Traceability List foods under the definitions, requirements, exemptions, modified requirements, and waivers in Subpart S

FDA Preventive Controls for Human FoodIn force · Covered facilities that manufacture, process, pack, or hold human food for U.S. consumption, subject to scope and exemptions

FDA Sanitary Transportation RuleIn force · Covered shippers, loaders, carriers by motor or rail vehicle, and receivers engaged in U.S. food transportation, subject to exemptions and waivers

FDA Foreign Supplier Verification Programs RuleIn force · Covered U.S. importers of human and animal food, subject to definitions, modified requirements, and exemptions

Food-chain operating domains

Trading-partner event integrityThe operating system for preserving the identity, meaning, sequence, source, and correction history of food movements as records cross farms, vessels, plants, warehouses, distributors, retailers, foodservice, and technology networks.

Transformation and lot genealogyThe internal record connecting incoming food and packaging lots to processing, commingling, rework, split, repack, relabel, yield, and output lots without erasing the historical relationship when records are corrected.

Food, lot, location, and party identityThe governed master-data layer that distinguishes foods, forms, ingredients, lots, locations, businesses, farms, vessels, facilities, and recipients so events can be joined without treating similar labels as the same entity.

Interoperability and partner exchangeThe technical and operating ability to send, receive, validate, query, correct, and retain food traceability data across different platforms, formats, identifiers, and partner capabilities.

Recall scope and response readinessThe governed process for investigating a food-safety or labeling concern, identifying potentially affected lots and recipients, preserving uncertainty, making accountable decisions, communicating, controlling inventory, documenting disposition, and testing effectiveness.

Company and systems coverage

Explore all

TraceGains Trustwell FoodLogiQ ReposiTrak iFoodDS SafetyChain Provision Analytics FoodDocs Safefood 360°Foods Connected Qadex Hamilton Grant Wherefour FoodReady Smart Food Safe Minotaur Software

Traceability change ledger

Explore all

July 18, 2026

Guidance clarification in reviewFDA FAQ keeps EPCIS optional for Food Traceability Rule compliance

Buyers should test the interoperability outcome, not treat an EPCIS claim or absence as a compliance conclusion, and retain a usable authority-response path.

July 18, 2026

Standards record reviewGS1 EPCIS 2.0 carries condition and food-safety event context beyond location

Food buyers should test event semantics, source data, units, validation, access, and retention instead of reducing EPCIS to a shipment-location feed.

June 30, 2026

Inspection procedure updateCFIA updates system-verification procedure for preventive controls and traceability

Canadian operators should test whether traceability, complaints, receiving, transportation, storage, and preventive-control evidence can be reviewed as one system while preserving the separate requirements.

June 17, 2026

Official discussion paperFDA opens a lot-level traceability flexibility discussion

Food businesses and vendors should distinguish an implementation discussion from a final rule change and test whether proposed approaches preserve lot linkage, event meaning, response usability, and source evidence.

June 15, 2026

Product record updateFoodDocs expands its public traceability and multi-site operating record

Smaller operators comparing food-safety systems should separate convenient batch logging from Food Traceability Rule event coverage, enterprise interoperability, and verified response performance.

May 31, 2026

Product market updateTrustwell positions FoodLogiQ for UK digital traceability programs

Buyers should require jurisdiction-specific rule mappings and evidence while testing whether the same supplier, item, location, and event data can support multiple response models.

Ledger Research

Explore all

FOOD TRACEABILITY LEDGER · 2026Food traceability market architectureIndependent market research

Original analysis

How networks, plant systems, food-safety platforms, ERP, produce systems, identity layers, and supply-chain mapping divide the market.

The research connects the provider market, normalized capabilities, authority records, operating domains, and source limitations rather than presenting a score or universal winner.

Read the report →

Conditional comparisons

Compare operating fit, not popularity

TraceGains vs Trustwell FoodLogiQOperating role, documented scope, overlap, differences, and evidence boundaries

ReposiTrak vs iFoodDSOperating role, documented scope, overlap, differences, and evidence boundaries

SafetyChain vs Provision AnalyticsOperating role, documented scope, overlap, differences, and evidence boundaries

FoodDocs vs Safefood 360°Operating role, documented scope, overlap, differences, and evidence boundaries

Foods Connected vs QadexOperating role, documented scope, overlap, differences, and evidence boundaries