Wholechain and iFoodDS link seafood traceability systems

Wholechain and iFoodDS have completed an integration between their traceability systems, allowing seafood suppliers using Wholechain to exchange key supply-chain data with customers and trading partners connected to the iFoodDS Trace Exchange network.

The connection is intended to reduce the amount of duplicated work required when one supplier has to provide traceability information to several customers using different systems. Rather than maintain a separate process for each customer’s platform, participating businesses can transmit relevant data from Wholechain into the wider Trace Exchange environment.

The immediate regulatory context is the US Food and Drug Administration’s Food Traceability Rule, which introduces additional recordkeeping requirements for businesses that manufacture, process, pack, or hold foods appearing on the Food Traceability List. Seafood categories covered by the list include finfish, smoked finfish, crustaceans, and specified molluscan shellfish, subject to the exemptions set out in the rule.

The regulation is organised around Critical Tracking Events and the Key Data Elements associated with them. Depending on where a business sits in the supply chain, those events can include first land-based receiving, shipping, receiving, and transformation, creating a record that can be followed as a lot moves between organisations.

For seafood processors, that is more complicated than retaining a lot number inside one factory. A product can move through harvesting, landing, aggregation, primary processing, freezing, import, cold storage, secondary processing, distribution, and retail before reaching the consumer, with different companies maintaining different systems at each stage.

Andy Kennedy, chief traceability officer at iFoodDS, said: “Food suppliers are being asked to meet growing traceability requirements from multiple customers.”

Interoperability becomes significant because the required information is only useful if the next organisation can receive and interpret it. A processor can maintain accurate internal records and still create gaps downstream if product, location, date, quantity, or lot identifiers have to be manually re-entered into another customer’s portal or spreadsheet.

Wholechain and iFoodDS are both GS1 US Solution Partners and support GS1 standards for event-based traceability. Wholechain also works with Global Dialogue on Seafood Traceability specifications, which were developed to provide common data definitions and technical standards across wild-caught and farmed seafood supply chains.

The newly completed integration does not, however, make either system an automatic compliance mechanism. Software cannot compensate for missing lot definitions, inaccurate master data, incomplete supplier records, or production processes that fail to preserve the relationship between incoming material and outgoing product.

Transformation is one of the more demanding areas for processors. Several incoming seafood lots may be combined during production, while one incoming lot can also be divided across multiple finished products. If that relationship is not captured reliably when the transformation occurs, an otherwise sophisticated traceability platform is left trying to reconstruct information that was never recorded.

Production sites also need consistent identifiers for locations, trading partners, products, and quantities. Where different businesses describe the same event in different ways, integration work can become a mapping exercise rather than a straightforward transfer of records.

The FDA rule places a particularly demanding timescale on record availability once enforcement applies. Covered businesses must be able to provide required information to FDA within 24 hours of a request, or within another reasonable period agreed by the agency, including an electronic sortable spreadsheet where necessary during an outbreak, recall, or other public-health threat.

The practical enforcement timetable has changed substantially since the regulation was written. Its original common compliance date was 20 January 2026, but FDA proposed extending that date by 30 months to 20 July 2028. Congress subsequently directed FDA not to enforce the Food Traceability Rule before that same July 2028 date, and the agency says it intends to comply with the direction.

That delay removes some immediate pressure without removing the underlying systems problem. Businesses still have to determine where traceability lots begin and end, what data each production event creates, which customers need the information, and how records move between software operated by unrelated organisations.

Two additional years may therefore be more useful as an implementation period than as a reason to postpone work. Connections can be tested against genuine production transactions, discrepancies identified, customer mappings corrected, and staff trained before regulatory enforcement turns incomplete data into a more urgent problem.

Traceability also has value before the formal enforcement date. During a microbiological or contamination investigation, the ability to narrow suspect material to a particular lot, supplier, production date, or trading route can substantially reduce the amount of product that has to be isolated or recalled.

That depends on continuity between systems. A clean record inside one supplier’s database is of limited value if identifiers are changed or lost as material moves to the next organisation. The Wholechain-iFoodDS connection tackles that handover rather than the entire traceability problem.

For seafood manufacturers, the distinction is useful. Compliance will still depend on disciplined factory records and supplier data, but having a standards-based route for exchanging those records reduces one of the administrative obstacles that has made end-to-end traceability difficult to scale.

FDA’s extended timetable gives the sector room to establish whether integrations such as this work under commercial conditions. By 2028, the more awkward question will not be whether a processor owns traceability software, but whether accurate lot data can pass through several businesses and still be reconstructed within hours when something goes wrong.