FOOD TRACEABILITYLEDGER

Follow the food. Preserve the record.

Voluntary global use by organizations at any step in the feed and food chain unless adopted through contract, certification scope, policy, or law · International consensus standard

ISO 22005:2007 — Traceability in the feed and food chain

ISO 22005 gives principles and basic requirements for designing and implementing a feed and food traceability system capable of determining product history or location against defined objectives.

Published and confirmed current by ISO in 2022Voluntary consensus standard

What the authority record establishes

ISO 22005 gives principles and basic requirements for designing and implementing a feed and food traceability system capable of determining product history or location against defined objectives.

Voluntary consensus standard

The exact official title, issuing body, jurisdiction, version or application record, and linked source define the scope of this page. Readers should not transfer the authority's status to a commercial product or infer transaction-, patient-, system-, site-, or organization-specific applicability from this summary.

Why it matters to this market

The standard centers system objectives, design, and implementation rather than prescribing one technology, identifier, database, or regulatory response format.

Affected operating stages

  • Define Objectives
  • Design System
  • Identify And Record
  • Establish Procedures
  • Test And Review
  • Improve

Capabilities to examine

Item Product Location And Party Identification

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for item product location and party identification.

Traceability Lot Code And Lot Genealogy

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for traceability lot code and lot genealogy.

Mock Recall And Trace-Time Testing

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for mock recall and trace-time testing.

Audit Certification And Customer-Evidence Management

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for audit certification and customer-evidence management.

Supplier Facility And Trading-Partner Master Data

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for supplier facility and trading-partner master data.

Affected buyer audiences

  • food and feed organizations
  • quality and food-safety leaders
  • certification and audit teams
  • technology and process owners

Implementation questions

  • Which entities, products, populations, transactions, systems, sites, or jurisdictions are actually within scope?
  • What is binding, what is guidance, and what is a technical or consensus standard?
  • Which publication, adoption, effective, application, transition, and enforcement dates differ?
  • Who owns legal, clinical, quality, regulatory, policy, or operational interpretation?
  • How will a source revision affect open work and historical decisions?

Interpretation boundary

Only an appropriate conformity process can address certification or conformance; product positioning does not establish either.