V5 Ultimate
Ultimate
PricingResourcesCompany
English (original)العربيةDeutschΕλληνικάEspañolFrançaisItalianoעברית日本語한국어NederlandsPolskiPortuguêsSvenska
Talk to us Log in Start free trial
Food & Beverage
  • Bakery & Confectionery
  • Food Processing
  • Ingredients & Dry Mixes
  • Sausage & Meat Products
  • Produce Packing
  • Pet Food & Pet Supplements
  • Dairy & Chilled Foods
  • Beverages & Liquid Manufacturing
  • Infant Formula
Pharma & Life Sciences
  • Radiopharmaceuticals
  • Pharmaceutical
  • Medical Devices
  • Veterinary Pharmaceuticals
  • Blood & Tissue
  • Diagnostics & IVD Kits
  • Reference Materials & Standards
  • OTC Topical Creams & Gels
Supplements & Personal Care
  • Dietary Supplements
  • Cosmetics & Personal Care
  • Cannabis & Hemp Manufacturing
  • Fragrances & Perfumery
  • Soaps & Personal Hygiene
  • Botanical Extracts & Essential Oils
Chemicals & Materials
  • Plastics & Resins
  • Agricultural Chemicals
  • Specialty & Industrial Chemicals
  • Printing Inks, Pigments & Construction Chemicals
  • Lubricants & Metalworking Fluids
  • Coatings, Adhesives & Sealants
Other Manufacturing
  • Consumer Products
  • Electronics & Electrical Assembly
  • Textiles & Nonwoven
  • Contract Manufacturing & Co-Packing
  • Packaging & Food-Contact Materials
  • Regulated Warehousing & Distribution
Explore all industries
  • Warehouse & TraceabilityReceive, store, pick and trace
  • Production & PlanningPlan jobs and guide production
  • Quality & LaboratoryTest, investigate and review
  • Documents & TrainingControl procedures and qualifications
  • Equipment & PerformanceMaintain assets and measure losses
  • Orders & IntegrationsConnect customers, suppliers and systems
  • Outputs & InsightsReports, KPIs and label design
Why V5? Product & Features
Why V5?Product & Features
  • Warehouse & TraceabilityReceive, store, pick and trace
  • Production & PlanningPlan jobs and guide production
  • Quality & LaboratoryTest, investigate and review
  • Documents & TrainingControl procedures and qualifications
  • Equipment & PerformanceMaintain assets and measure losses
  • Orders & IntegrationsConnect customers, suppliers and systems
  • Outputs & InsightsReports, KPIs and label design
Explore all industries
    • Bakery & Confectionery
    • Food Processing
    • Ingredients & Dry Mixes
    • Sausage & Meat Products
    • Produce Packing
    • Pet Food & Pet Supplements
    • Dairy & Chilled Foods
    • Beverages & Liquid Manufacturing
    • Infant Formula
    • Radiopharmaceuticals
    • Pharmaceutical
    • Medical Devices
    • Veterinary Pharmaceuticals
    • Blood & Tissue
    • Diagnostics & IVD Kits
    • Reference Materials & Standards
    • OTC Topical Creams & Gels
    • Dietary Supplements
    • Cosmetics & Personal Care
    • Cannabis & Hemp Manufacturing
    • Fragrances & Perfumery
    • Soaps & Personal Hygiene
    • Botanical Extracts & Essential Oils
    • Plastics & Resins
    • Agricultural Chemicals
    • Specialty & Industrial Chemicals
    • Printing Inks, Pigments & Construction Chemicals
    • Lubricants & Metalworking Fluids
    • Coatings, Adhesives & Sealants
    • Consumer Products
    • Electronics & Electrical Assembly
    • Textiles & Nonwoven
    • Contract Manufacturing & Co-Packing
    • Packaging & Food-Contact Materials
    • Regulated Warehousing & Distribution
PricingResourcesCompany
Start free trial Log in Talk to us
HomeGlossaryGFSI
Compliance · The complete guide

GFSI (Global Food Safety Initiative): Recognition, Benchmarking and Certification

In short

Separate programme recognition, site certification and applicable food-law duties through practical scope checks, evidence reviews and clearly assigned decisions.

4,030 words · ~19 min read
GFSI certification audit: staff in hairnets, masks and gloves review records on a tablet beside a food line
GFSI benchmarks and recognises food safety certification programmes; it does not certify sites itself.
On this page
  1. 01What GFSI is—and what “GFSI certification” means
  2. 02Benchmarking, recognition and certification: a comparison
  3. 03Reducing duplicate audits without assuming buyer acceptance
  4. 04Checking recognised programmes and version status
  5. 05Choosing a programme for the site's actual operation
  6. 06GFSI and FSMA: recognition versus applicable legal duties
  7. 07From scope review to audit follow-up
  8. 08A site-level model for recognition and certification evidence
  9. 09Using certification evidence in a Part 117 supply-chain program
  10. 10Review failures that good records can prevent
  11. 11An implementation and continuing-review checklist
On this page · 11 sections
  1. 1What GFSI is—and what “GFSI certification” means
  2. 2Benchmarking, recognition and certification: a comparison
  3. 3Reducing duplicate audits without assuming buyer acceptance
  4. 4Checking recognised programmes and version status
  5. 5Choosing a programme for the site's actual operation
  6. 6GFSI and FSMA: recognition versus applicable legal duties
  7. 7From scope review to audit follow-up
  8. 8A site-level model for recognition and certification evidence
  9. 9Using certification evidence in a Part 117 supply-chain program
  10. 10Review failures that good records can prevent
  11. 11An implementation and continuing-review checklist
AI · Explain it for MY operation

How does GFSI apply to your shop floor?

Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.

Your scale

01What GFSI is—and what “GFSI certification” means

GFSI (Global Food Safety Initiative) is The Consumer Goods Forum’s industry initiative for benchmarking and harmonising food safety certification programmes. GFSI’s overview identifies its organisational home, while GFSI’s recognition explanation describes benchmarking and harmonisation as work that fosters mutual acceptance of recognised certification programmes across the industry.

The central distinction is between recognition of a programme and certification of a company or site. GFSI’s recognition page says “GFSI recognition offers a passport to the global market, both for the recognised Certification Programme Owners (CPOs) and the companies that they certify”, and that to be recognised “CPOs must verify that they meet the Benchmarking Requirements.” Recognition attaches to the CPO’s programme; a site’s certificate comes from the programme it is certified under.

Three questions to keep separate

For a manufacturer reviewing its own position or a supplier’s statement, use the following practical framework. These are proposed review questions, not three official GFSI requirements:

  1. Which programme is recognised? Identify the programme being claimed rather than recording only “GFSI” in a supplier questionnaire or internal register.
  2. What do the site’s certification documents establish? Read the documents for the named site and stated scope. Record what they actually identify rather than expanding a general supplier statement into a conclusion about every operation.
  3. Which legal obligations apply? Assess the relevant product and jurisdiction separately. For a U.S. food operation, the applicability review can include 21 CFR 117; this question belongs in the legal review, not in the programme-name field.

As a practical review habit, keep the answers to those three questions separately identifiable, so a supplier’s claim can be checked against the programme, the certificate and the customer’s actual request.

02Benchmarking, recognition and certification: a comparison

Benchmarking is how a programme gains recognition. GFSI says its Benchmarking Requirements for Certification Programme Owners help reduce inefficiencies from duplication of food safety audits and help reduce trade barriers, and that a separate set of Benchmarking Requirements for Professional Recognition Bodies, launched in November 2021, lets auditors demonstrate competence through a single registration to a GFSI-recognised Professional Recognition Body (GFSI recognition).

GFSI describes itself as an Industry Solution of The Consumer Goods Forum, bringing together food retailers and manufacturers and an extended food safety community “to oversee third-party food safety standards for food business operators globally.” Its stated focus areas are benchmarking and harmonisation, capability building and public-private partnerships.

TermQuestion it answersReference or document to inspectSeparate decision still needed
BenchmarkingDoes the CPO meet GFSI’s Benchmarking Requirements?Consult the Benchmarking Requirements.Check recognition status separately.
GFSI recognitionIs the CPO recognised by GFSI?Consult GFSI’s recognition information.Assess suitability for the site's intended operation.
Certification Programme OwnerWhich programme owner must verify conformity when seeking recognition?Compare the CPO identity with GFSI’s recognition information.Identify the relevant programme and current rules.
Site certificationWhat certification is documented for this site?Inspect the certificate alongside the programme’s current rules.Evaluate whether the documented scope matches the intended use.
Applicable regulationWhich legal provisions apply to this operation?Consult current legal text for the product and jurisdiction.Determine applicability and assess fulfilment separately.

Use the first three rows to organise the recognition question, not to reconstruct a benchmarking procedure. For programme-specific audit rules, assessment arrangements and certification documents, consult the relevant programme’s current rules rather than treating this vocabulary as an operating instruction.

03Reducing duplicate audits without assuming buyer acceptance

GFSI’s recognition explanation identifies duplication of food safety audits as a source of inefficiency that its Benchmarking Requirements for Certification Programme Owners help reduce. The operational objective is less duplication, rather than treating every customer request as a reason for another audit.

GFSI describes benchmarking and harmonisation as fostering mutual acceptance of recognised certification programmes, enabling a simplified “once certified, accepted everywhere” approach. Read that as GFSI’s industry-level approach—not as confirmation that a particular buyer has accepted a proposed programme.

Worked case: three customer requests

Assume three customers have requested programme-certification information. Two have documented acceptance of the proposed programme; the third has not replied. Count customer requests, not audits:

3 total requests − 2 documented acceptances = 1 unresolved request.

Recommended practice: record the unanswered request as unresolved. Retain each customer’s response against its request, identify who will follow up, and update the status when a response arrives. Use an audit-management record to keep the correspondence together and attributable recording to show who entered each decision and when. These are recordkeeping recommendations, not GFSI acceptance requirements. The example establishes only the communication status: it neither measures audit savings nor predicts the remaining customer’s decision.

04Checking recognised programmes and version status

Start recognition enquiries at the official GFSI recognition page, then follow the references relevant to the programme your manufacturer is considering. Keep the enquiry tied to that programme rather than using a general scheme list as a substitute for a status check.

Create a recognition-reference record with these suggested traceability fields:

  • Programme name exactly as written.
  • Programme owner.
  • Reference URL.
  • Date checked.
  • Any stated version or scope, preserving the wording used.

These are proposed reference-management fields, not GFSI-mandated record elements. Keep an explicit recognition-status statement separate from the reviewer’s interpretation. If the reference does not resolve the question, record the interpretation as unresolved rather than converting it into a positive status decision.

For a version-specific enquiry, identify the exact version being discussed and check its current recognition position and applicable programme rules. Do not infer recognition from a similar programme name, or assume that a statement about one version settles another version’s status. Where the version is unstated, leave that field explicitly unresolved; do not fill it from memory.

Use an exception-based review approach to flag ambiguous names, missing version references and conflicting statements for follow-up. Record the question to resolve and the reference that prompted it. This keeps the review focused on reference accuracy, without turning it into a customer-suitability or legal-applicability decision.

05Choosing a programme for the site's actual operation

Use a selection worksheet to connect the proposed certification to the operation and its intended business use. The questions below are recommended decision inputs, not required GFSI review elements. Keep site identity, products, activities, customers, markets and requested scope separate so that an answer about one does not silently stand in for another.

Selection questionInformation to obtainDecision ownerOpen issue
Which site is being considered?Site name, address and operating entitySite representativeAre site boundaries clear?
Which products are intended for inclusion?Product list and relevant characteristicsProduct or quality representativeAre any products undecided?
Are the intended activities addressed?Process description and programme-fit responseOperations representativeWhich activities need clarification?
Has each intended customer confirmed its expectations?Written customer requests and responsesCommercial representativeWhich confirmations remain outstanding?
Which markets will certification support?Destination markets and intended commercial useCommercial representativeDoes the proposed choice address that use?
What certification scope is being sought?Proposed scope wording and responses to scope enquiriesAuthorised reviewerWhich inclusions or exclusions remain unresolved?

Treat these owners as suggested responsibilities, not prescribed job titles. Commercial personnel can clarify customer requests; operational personnel can describe what the site actually does. Gathering those answers is distinct from approval: an authorised reviewer should record the selection decision and any unresolved conditions. Assign each condition an owner and a next action; consider tracking material uncertainties in a quality risk register.

Use the recognition-status review covered above rather than duplicating its checks. Apply attributable records to identify who prepared and approved the choice. The concrete output should be a dated selection rationale explaining the chosen programme and unresolved conditions, linked to the relevant recognition reference, site description and customer correspondence.

06GFSI and FSMA: recognition versus applicable legal duties

Keep three categories explicit: GFSI publications are official industry guidance; 21 CFR Part 117 is the U.S. regulatory text considered here; the review tools below are practice recommendations. Assess certification status and legal applicability as separate questions. In a site review, record each conclusion separately rather than treating a certification decision as the answer to a legal-scope question.

One conditional Part 117 obligation

Under 21 CFR 117.130(c)(1)(ii), the hazard evaluation must include an evaluation of environmental pathogens whenever ready-to-eat food is exposed to the environment before packaging and the packaged food does not receive a treatment or otherwise include a control measure that would significantly minimize the pathogen. The provision gives a formulation lethal to the pathogen as an example of such a control measure.

Both conditions matter. This is not an unconditional environmental-testing requirement for every food operation. Keep the hazard-evaluation question distinct from the design of an environmental monitoring programme, and review Part 117 applicability separately.

Worked case 2: two hypothetical operations

Assume both operations are subject to the cited provision. The units are two hypothetical operations—not batches or test results.

  • Operation A: ready-to-eat food is exposed before packaging, and the packaged food has no treatment or other control that would significantly minimize the pathogen. The hazard evaluation must therefore include environmental pathogens.
  • Operation B: there is no exposure before packaging. This particular exposure condition is absent; that does not establish that other duties disappear.

Scope-screening aid—not a coverage determination

Jurisdiction and product questionWhat this discussion establishesFurther scope check
U.S. ready-to-eat food under the cited conditionThe conditional environmental-pathogen evaluation requirement.Confirm applicability and both process conditions.
Other U.S. food operationsNo general coverage conclusion.Check current applicable U.S. food-law text for the operation.
Dietary supplementsNo supplement-specific coverage or exemption conclusion.Check current applicable supplement and Part 117 provisions.
Medicines, devices and non-food chemicalsNo product-specific legal mapping.Check current legal text for the product and activity.
Operations in other jurisdictionsNo conclusion about local duties.Check current applicable law in the relevant jurisdiction.

As a practical review tool, retain the applicability question, operating assumptions, legal reference and responsible reviewer's conclusion together. Keep unresolved scope questions visible rather than filling them with an inference from certification status.

07From scope review to audit follow-up

The diagram below is a suggested manufacturer workflow from recognition check to recorded decision, not the official GFSI benchmarking process or a prescribed certification procedure. Programme-specific audit scheduling and procedure come from the certification programme’s own rules, which should be cited in the readiness record.

Recognition-to-Site Review Workflow
  1. 1
    Define scopeRecord the site, activities, products and markets.
  2. 2
    Review recognitionRecord programme identity and the recognition reference.
  3. 3
    Confirm fitDocument customer expectations and unresolved acceptance questions.
  4. 4
    Map dutiesHave authorised personnel determine applicable legal obligations.
  5. 5
    Link EvidenceAssociate site records with each review question.
  6. 6
    Resolve exceptionsAssign missing links and conflicting records to owners.
  7. 7
    Record decisionsRetain the human decision and its rationale.
Suggested operating sequence, not a GFSI audit procedure or an FDA-prescribed checklist.

08A site-level model for recognition and certification evidence

The diagram shows one proposed way to link a site’s certification evidence: a programme reference, the certificate, the site, the supporting documents and the review decision. It is a record design, not a GFSI data standard or an FDA-required format.

Recognition and Site-Evidence Records

Programme Reference

Identifies the programme and recognition reference.

  • programme_id
  • programme_name
  • recognition_url
  • checked_on

Site Scope

States the operation being assessed.

  • site_id
  • product_type
  • activities
  • target_market

Certificate Record

Preserves the document and its stated scope.

  • certificate_id
  • site_id
  • programme_id
  • stated_scope

Evidence Link

Links a review question to a record.

  • evidence_id
  • record_uri
  • review_question
  • link_status

Review decision

Captures an authorised person’s conclusion and follow-up.

  • decision_id
  • reviewer_id
  • decision
  • action_owner
Suggested traceability fields; record IDs connect references, certificates and decisions without making them equivalent.

09Using certification evidence in a Part 117 supply-chain program

Where certificates usually meet U.S. law is the supply-chain program. Under 21 CFR 117.405(a)(1), a receiving facility “must establish and implement a risk-based supply-chain program” for raw materials and other ingredients for which it has identified a hazard requiring a supply-chain-applied control. Section 117.410(a) says the program must include using approved suppliers, determining and conducting appropriate supplier verification activities, and documenting them.

Section 117.410(b) lists the appropriate verification activities: onsite audits; sampling and testing of the raw material or other ingredient; review of the supplier’s relevant food safety records; and other appropriate activities based on supplier performance and risk. Under 117.420(a) the receiving facility must approve suppliers in accordance with 117.410(d) and document that approval before receiving raw materials from them, and 117.410(d) requires the hazard analysis, the entity applying the control and supplier performance to be considered.

Part 117 does not name GFSI or any certification programme. Where a hazard controlled by the supplier carries a reasonable probability of serious adverse health consequences or death, 117.430(b)(1) makes the appropriate verification an onsite audit before use and at least annually thereafter, unless a written determination under 117.430(b)(2) supports other activities; 117.435(a) requires that audit to be performed by a qualified auditor, and 117.435(b) requires it to consider applicable FDA food safety regulations and review the supplier’s written food safety plan, if any, and its implementation for the hazard being controlled.

Worked case: one supplier, two questions

Assume a supplier sends a current certificate under a GFSI-recognised programme and its latest audit report for an ingredient that carries a hazard controlled at the supplier. The recognition question is answered by checking the programme on GFSI’s list. The Part 117 question is different: does the audit report show an onsite audit by a qualified auditor that considered the applicable FDA regulations and the supplier’s food safety plan for that hazard, within the required frequency? If yes, the receiving facility can document its review of that report as a verification record; if the report does not address the hazard or the FDA rules, the certificate alone does not settle the verification decision, and the facility selects another activity under 117.410(b) or a further audit. The recognition status helps, but the qualified individual still decides.

Who may do the verification work

Under 117.415(a) the receiving facility must approve suppliers itself. Another entity may establish and document receiving procedures and determine or conduct supplier verification activities, provided the receiving facility reviews and assesses that entity’s documentation and documents its own review and assessment. A supplier may also conduct and document sampling and testing for the hazard it controls, for a particular lot, under the same review condition. This matters for certificates: a broker, a corporate quality team or a customer may forward certification documents, but the receiving facility’s documented review is what makes them part of its program.

Section 117.405(a)(2) adds an importer case: a receiving facility that is an importer, complies with the foreign supplier verification program requirements in part 1, subpart L, and has documentation of verification activities under § 1.506(e) need not conduct supplier verification activities for that raw material. Section 117.435(c) allows certain written inspection results by FDA, other federal, state, local, tribal or territorial agencies, or, for a foreign supplier, a food safety authority FDA has recognised as comparable or equivalent, to substitute for an onsite audit if conducted within one year of when the audit would have been required. A private certification audit is not on that substitution list, so it is assessed as an audit or as a supplier record review on its merits.

Reading an audit report against 117.435

A practical checklist for a certification audit report used as Part 117 evidence: identify the auditor and the basis for treating them as qualified; confirm the audited site and the raw material or ingredient match the supply relationship; confirm the audit considered the applicable FDA food safety regulations rather than only the programme standard; confirm it reviewed the supplier’s written food safety plan, if any, and its implementation for the hazard being controlled; and confirm the audit date fits the frequency your program set under 117.410(d) or, for serious hazards, the annual requirement in 117.430(b)(1). Record each answer with a reference to the page of the report it came from. Where an answer is missing, do not infer it from the certificate grade or the programme’s recognition; ask the supplier for the information or choose another verification activity.

Keep the outcome in two fields: whether the customer’s commercial certification requirement is met, and whether the Part 117 verification activity is documented. Those can differ for the same supplier on the same day, and collapsing them into a single “approved” flag is the commonest way a certificate ends up standing in for a decision nobody made.

10Review failures that good records can prevent

With recognition ambiguity, programme fit and legal scope addressed above, focus the review on document and decision weaknesses. Use the table as recommended management controls for certification evidence—not as an official GFSI nonconformity classification or a certification-programme grading system.

Failure modeDetection questionPractical controlClosure evidence
Uncontrolled filename reuseCan the same filename point to different content?Assign stable record identifiers and explicit revision references; retain the reference used for the decision.Retrieve the intended revision from the decision record and match its identifier.
Unlocatable supporting statementCan another reviewer find the statement supporting the conclusion?Record a page or passage locator alongside the document identifier and revision.A second reviewer locates the statement without asking its author.
Absent action ownerWho now owns the unresolved action?Document reassignment, naming the new owner and recording their acceptance.The action record identifies the new owner and their acceptance date.
Closure without a dispositionWhat was decided, and why was closure accepted?Record the disposition, supporting rationale and person authorised to accept it.Retrieve the rationale and identify the person who accepted the disposition.
Notification mistaken for approvalDoes the record show a decision or merely message delivery?Keep notification status separate from an explicit decision field completed by the authorised approver.The field shows the decision, approver and date—not just a delivery receipt.

Use change control when revising these controls and attributable recording to structure responsibility records. Treat each completion test as evidence that the internal control was performed. It does not demonstrate certification, regulatory compliance or a particular audit outcome; keep those conclusions outside this internal closure check.

11An implementation and continuing-review checklist

Use this article’s proposed management checklist to assign responsibilities before relying on an internal certification-status report. It is not a list of required review elements from GFSI or FDA. Adapt the roles to the operation, and make each assignment visible to the people maintaining and reviewing the records.

  • Recognition references: name the person responsible for maintaining the programme references used in site assessments.
  • Site descriptions: assign ownership of the description of products, activities and locations against which decisions are made.
  • Certificate access: identify who maintains certificate documents and confirm that reviewers can retrieve the relevant document.
  • Applicability questions: assign each question to someone responsible for obtaining an answer and identifying the appropriate reviewer.
  • Exception escalation: define where missing documents, conflicting information and disputed interpretations go for resolution; connect this route to exception-based review.
  • Decision authority: identify who may authorise a conclusion and who may enter that conclusion into the internal record.

Control changes without concealing uncertainty

Define who may propose, review and record a status change, and keep unresolved questions open with a named owner.

Use changes in products, activities, customer requests, programme references or certificate documents as prompts to consider updating the review. Determine timing for the relevant operation and programme rather than attaching a universal review interval or audit frequency to this checklist.

Acceptance test: can a reviewer trace a decision to the correct site, programme reference, document and rationale? This tests record traceability—not the validity of every underlying conclusion, which remains a matter for authorised reviewers.

Frequently asked questions

Q.What documents should a supplier send when a customer asks for a “GFSI certificate”?+

As a practical response, send the actual certification document and any accompanying scope schedule, preserving the programme name, issuer, site identity and dates exactly as recorded. Ask the customer which acceptance criteria it wants addressed before sharing additional records. Use a short cover note to identify attachments and unanswered questions, rather than relabelling the document a “GFSI certificate”. Apply data integrity principles to copies and attributable records to the person preparing the response. This is a proposed document package, not a prescribed GFSI checklist.

Q.How can a contract manufacturer explain the relationship between its site scope and a brand owner's request?+

A useful approach is to map the brand owner's requested products and activities against the wording of the certificate and its scope schedule. Identify the relevant manufacturing location, operations performed there and any requested activity whose coverage remains unclear. Use production context tagging to organise that mapping; where the request concerns packing, include relevant bulk-to-pack traceability references. Present this as an explanation for customer review, not as an amendment to the certificate or an assumption that every brand product is covered.

Q.What should a reviewer do when programme names differ between a certificate and a customer questionnaire?+

Retain both names exactly as written and mark the relationship as unresolved rather than silently substituting one for the other. Ask the customer which programme wording its questionnaire intends, and seek clarification from the certificate issuer where necessary. A proposed comparison record should contain the two names, document references, clarification received and the resulting customer decision. Handle any subsequent questionnaire revision through change control. Similar wording alone should not be the review team's basis for declaring equivalence.

Q.How should an unresolved customer-acceptance question be handed over between sales and food safety personnel?+

Use a proposed handover record that states the customer's exact question, the documents already sent, the unresolved point and the person responsible for the next response. Sales should distinguish what the customer requested from what the business has actually established; food safety personnel should identify the technical clarification needed. A handover report can structure ownership, while a quality risk register can track associated concerns. Record any promised response date as a commercial commitment, not a regulatory deadline.

Q.What should a mixed-product business establish before applying the Part 117 discussion to supplements or non-food products?+

First establish the product category, intended market, site activities and the specific legal question for each product stream. Treat that inventory as a proposed scoping exercise, not a conclusion that one food-safety discussion governs the whole business. Check the current text of 21 CFR 117 for scope and applicability before relying on it. For the supplement stream, separately check 21 CFR 111. Keep non-food applicability questions open until the relevant product-specific framework has been assessed by an authorised person.

Q.How should a team handle a certificate review when supporting site records are incomplete?+

As a review practice, identify each missing record, the question it prevents the reviewer from answering and who will obtain it. Leave the affected conclusion unresolved rather than treating the certificate as the missing information. Separately, 21 CFR 117.165(a)(4)(4)) requires the specified record review by, or under the oversight of, a preventive controls qualified individual, including checking completeness. Where that provision applies, involve the PCQI. Keep the customer certificate-review decision distinct from that regulatory record-review task.

Q.Does Part 117 require suppliers to hold GFSI certification?+

No. Part 117 does not name GFSI or any certification programme. It requires a risk-based supply-chain program where a hazard needs a supply-chain-applied control, with approved suppliers and verification activities chosen under 117.410. A customer may still require a GFSI-recognised certificate as a commercial condition; record that as the customer’s requirement, separate from the legal verification decision.

Q.What should an authorised approver do when two reviewers reach different conclusions about the same record?+

Ask each reviewer to identify the exact record version, decision criterion and reasoning behind the conclusion. Then determine whether the disagreement concerns document content, interpretation or the customer's acceptance criteria. As a proposed approval practice, resolve the specific difference or request clarification before deciding; do not settle it by counting reviewers. Preserve both assessments and explain the final disposition through an audit trail review workflow. The authorised approver should record the decision and its basis, including any remaining limitation.

Primary sources

  • GFSI overview
  • GFSI recognition
  • eCFR 21 CFR Part 117
Software that covers GFSI
V5 Ultimate SQF
SQF Edition 9 system elements (2.1–2.9) and food-safety fundamentals modeled as live workflow. SQFI published Edition 10 in March…
V5 Ultimate BRCGS
BRCGS Food Safety Issue 9 fundamental requirements, HACCP, food safety and quality management, site standards, product control,…
V5 Ultimate FSSC 22000
FSSC 22000 version 6 wraps ISO 22000 (FSMS), ISO/TS 22002 sector PRPs and eleven additional requirements — food fraud, food…
V5 Ultimate Food Safety
HACCP plan management, FSMA 204 Food Traceability Rule with Key Data Elements and Critical Tracking Events captured in real time,…

Explore this topic

GFSI sits inside this topic cluster in our glossary. Every neighbour is one click away.

Food Safety & GFSI
16 related entries

HACCP, FSMA, allergen control and the GFSI-recognised certification schemes.

HACCPCCPHARPCPCQIFSMA 204KDECTE21 CFR 117Allergen ControlSSOPTACCP / VACCPSQFBRCGSFSSC 22000ISO 9001MoCRA
Talk to us about GFSI

Want to see how GFSI could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.

Start free
Back to glossary
Where this term comes up
Food ProcessingBakery & Confectionery
Inside V5
  • → Score your compliance gap — then download the validation pack.
  • → Document control — one version in force, every change signed and explained.
  • → QMS — quality records next to the work they concern.
Related terms
  • → SQF
  • → BRCGS
  • → FSSC 22000
  • → HACCP
  • → CCP
  • → HARPC
  • → PCQI
  • → FSMA 204
  • → KDE
  • → CTE
  • → 21 CFR 117
  • → Allergen Control
  • → SSOP
  • → TACCP / VACCP
  • → ISO 9001
  • → MoCRA

Next Step

Try V5 with your own records, or ask a question first. Ask V5 opens with an editable question; nothing is sent until you choose to.

Start your free trial Browse All Features

Showing the site for the United States. Local spelling, dates and prices are applied automatically; change the language at the top of the page.

V5 Ultimate
Ultimate

Warehouse, quality and manufacturing software for regulated operations.

ProductIndustriesPricingResourcesSecurity & TrustCompanyLegal Centre

© S.G. Systems, LLC