Skip to main content
Heads upFSMA 204 compliance is July 20, 2028 — extended via H.R. 5371 in November 2025. Get the implementation checklist →
HACCPLAN
Use case / Supplier documents

Use case / Supplier documents

What supplier documents should I have before a food inspection?

The practical answer: approved supplier list, specifications, CoAs where needed, certificates, allergen statements, and receiving evidence tied to the ingredients you actually use.

Updated 2026Commercial use caseSupplier verification

Andrew Langevin· 2026-06-05· 8 min read

01Direct answer

Build the supplier file before the inspector asks for it.

Before a food inspection, you should be able to open each active supplier and show why they are approved, what they supply, which hazards or allergens matter, and which records prove you verified the ingredient. FDA's Preventive Controls rule recognizes supplier verification activities such as onsite audits, sampling and testing, and review of relevant food-safety records. Canadian operators need the same evidence pattern inside the SFCR preventive-control system.

The inspection problem is not usually that the document does not exist. It is that the CoA is in email, the supplier certificate is in downloads, the allergen letter is expired, and the receiving record is on paper.

1

One supplier file per active supplier, not one folder for the whole purchasing department.

24h

Records should be retrievable quickly enough to satisfy an inspection or audit request.

0

Unlinked certificates. If it does not connect to a supplier and ingredient, it will not help you under pressure.

02Checklist

The supplier documents to stage.

  1. 01

    Approved supplier decision

    Why this supplier is approved, who approved it, and when it must be reviewed.

  2. 02

    Ingredient specification

    Product name, storage, acceptance criteria, hazards, allergens, and lot-code expectations.

  3. 03

    Certificate of Analysis policy

    Which ingredients need a CoA, what tests matter, and whether each lot passed before use.

  4. 04

    Audit or certification evidence

    SQF, BRCGS, FSSC, NSF, organic, kosher, or other certificates where they form part of approval.

  5. 05

    Allergen and ingredient statements

    Current letters for allergens, cross-contact, formulation changes, and country-specific declarations.

  6. 06

    Receiving records

    The proof that the approved ingredient arrived in acceptable condition from the approved supplier.

Use the interactive version

Turn supplier documents into a live supplier file

Use HACCPlan to attach CoAs, certificates, allergen statements, receiving logs, and approval decisions to the supplier they belong to.

Built for small food businesses that need inspection-ready supplier evidence without enterprise software pricing.

03Common gaps

Supplier evidence gets weak when it is not tied to active ingredients.

A certificate by itself does not prove the ingredient was controlled. The inspector or auditor wants to understand why the supplier is approved, what they supply, which hazards or allergens matter, what verification activity was chosen, whether current documents support the decision, and whether receiving records show the right material arrived.

This is why a generic supplier folder becomes hard to defend. It may contain many PDFs, but not the approval logic. A supplier file should answer the practical inspection question: why did you trust this supplier for this ingredient on this date?

Better supplier file

Keep supplier approval, ingredient specs, CoA requirements, allergen statements, certificates, receiving checks, and review dates connected to the same supplier record.

04What HACCPlan does

Make supplier approval a workflow instead of a folder.

HACCPlan maps supplier documents to the ingredient and verification activity they support. That gives the business a cleaner inspection story and a better day-to-day process for purchasing, receiving, allergen review, and CoA approval.

  1. 01

    Approval basis

    Document whether approval is based on certification, audit, testing, history, questionnaire, or another justified activity.

  2. 02

    Document freshness

    Track expiration and review dates so certificates and allergen letters do not quietly go stale.

  3. 03

    Ingredient link

    Attach each document to the ingredients it supports instead of burying it in a supplier-wide folder.

  4. 04

    Inspection export

    Produce a supplier packet that shows approval, specs, verification records, and receiving evidence together.

05First pass

The quickest supplier cleanup before inspection.

Start with the top ten active suppliers by risk or volume. For each one, confirm the approval decision, current certificate or evidence, active ingredient specs, allergen statements, CoA requirement, most recent receiving record, and next review date. That pass will expose the documents that matter most.

Clean up supplier files

Build supplier files that match inspection questions

Attach supplier approval, specs, CoAs, certificates, allergen letters, receiving records, and review dates to the supplier and ingredient they support.

Use HACCPlan when supplier documents need to be searchable, current, and tied to real ingredients.

06Related workflows

Connect supplier records to the rest of the system.

Read the supplier management product page, try the AI scan demo, and use the inspection binder generator to see how supplier files should appear in an audit packet.

Andrew Langevin·CFIA-licensed facility, Brantford ON· Published 2026-06-05· 8 min read· Wikidata Q139112497