FSSC 22000 Version 7 gains GFSI recognition: check scope before updating audit plans

GFSI has recognised FSSC 22000 Version 7. Audit and supplier-assurance teams should check the recognised scope without assuming transition dates or automatic certificate changes.

Source published: 2026-11-10

Audience / jurisdiction: International voluntary certification; food-safety managers, audit leads, certification teams and supplier-assurance managers

What changed: programme recognition is confirmed

GFSI has announced that FSSC 22000 Version 7 has achieved recognition against GFSI Benchmarking Requirements Version 2024. Its news archive dates the announcement 10 November 2026. For food-safety managers and supplier-assurance teams, the development confirms a programme-level recognition decision; it does not, by itself, establish what must change at an individual certified site.

The distinction matters when updating audit plans or answering customer questions. GFSI benchmarks voluntary third-party certification programmes, while Foundation FSSC owns the FSSC scheme. Recognition is therefore different from publication of a new ISO standard, certification of a particular facility or introduction of a legal requirement. The announcement concerns international voluntary certification rather than a country-specific regulatory change.

Sources: [1], [2]

Who is affected: check the recognised activity scope

The announcement lists recognition for categories BIII, C0, CI–CIV, D, G, I and K. These cover specified plant-product handling, food processing, feed, storage and distribution, packaging, and food-related biochemical activities. Recognition claims should remain within the categories identified by GFSI rather than being extended to all activities associated with food production.

The most relevant readers are organisations using FSSC certification and buyers assessing their suppliers’ certification arrangements. As an editorial next step, compare each relevant site’s documented activities and certification scope with the recognised categories. A programme name alone is not a sufficiently precise basis for that comparison.

For a hypothetical supplier operating several sites, a useful review would examine each site separately rather than assuming that one programme-level recognition statement resolves every scope question. Record any uncertainty for confirmation with the supplier or certification body.

Sources: [1]

Dates: publication is not a transition deadline

The source publication date is 10 November 2026, as recorded in GFSI’s archive. The announcement describes recognition as achieved, rather than proposed or open for consultation. It does not state a separate effective date, so the publication date should not be presented as a legal commencement date or an upgrade deadline.

The opened evidence also does not establish upgrade-audit dates, transition deadlines or automatic changes to existing certificates. Those gaps limit what this announcement can support: it confirms recognition, but it is not a verified transition timetable. Teams should avoid turning the news date into an internal compliance deadline without checking the applicable scheme documentation.

Sources: [2], [1]

Practical next steps for audit planning

For internal audit leads, the immediate recommendation is to separate recognition status from audit criteria. The GFSI announcement establishes the benchmarking outcome and its scope; it should not be treated as a checklist of detailed Version 7 requirements.

Before changing audit dates or criteria, ask the certification body to confirm the applicable upgrade arrangements in writing and identify the controlled scheme documents supporting them. Then review which internal audit plans, checklists and responsibilities need adjustment against those documents. These are editorial planning suggestions, not requirements introduced by the recognition announcement.

Sources: [1]

Keep supplier records precise

For supplier assurance, a useful record design would keep programme recognition, individual site certification scope and customer acceptance as separate fields. That structure helps reviewers see which question has been answered and which still needs evidence, without making a broader claim than the recognition announcement supports.

Prioritise records where the activity category is unclear or an audit date is being reconsidered. Request the missing confirmation before changing the supplier’s recorded status. Does your supplier-assurance register distinguish the scheme’s GFSI recognition scope from each site’s actual certification scope?

Sources: [1]

Sources

1. FSSC 22000 Version 7 achieves recognition against GFSI’s Benchmarking Requirements v2024
2. Benchmarking Archives

Your experience

Does your supplier-assurance register distinguish the scheme’s GFSI recognition scope from each site’s actual certification scope?

Related reading

• ISO publishes new defence technical-audit standard edition; correction pending
• Closing audit findings: separate correction, cause analysis and corrective action
• Planning an internal audit around processes and risks

About the author

AdviseISO Editorial Team

The AdviseISO editorial team prepares practical, source-based guidance on standards, auditing and compliance.