Published
Compare supplier document requirements from Conagra, Kerry, J&J Snack Foods and Faribault Foods, with source-linked examples and a practical collection checklist.
Food manufacturers can ask suppliers for food safety certificates, audit evidence, product specifications, declarations, guarantees, insurance and delivery-specific records. The exact document set depends on the buyer, manufacturing site, material and intended use.
To see what that means in practice, we examined public supplier manuals from Conagra Brands, Kerry, J&J Snack Foods and Faribault Foods. Their requirements show why a supplier file needs more structure than a folder of certificates.
The practical question is: what evidence do we need for this supplier, site or material, and have we received it? This comparison gives QA and procurement teams examples they can use to build that requirement list.
The table summarises selected requirements, rather than each buyer's complete approval process. The linked sections explain their scope and conditions.
| Buyer | Examples of documents or information requested | What determines the collection task? |
|---|---|---|
| Conagra Brands | Guarantees, audit evidence, food safety summaries, ingredient specifications and composition information; separate packaging documentation. | Its lists distinguish manufacturing-location requirements from ingredient and packaging requirements. Section III.D.3, pp. 7–9 |
| Kerry | A Raw Material Questionnaire for new items, agreed specifications, and Certificates of Analysis or Conformance. | New-item information and delivery evidence have different submission triggers. Section A.3, p. 9; section B.13.1, p. 70 |
| J&J Snack Foods | Signed supplier acceptance, current insurance evidence, requested food safety documentation, and a Certificate of Analysis or Conformance. | The manual specifies submission through TraceGains and replacement of relevant certificates before expiry. Introduction; sections 1.6, 2.1 and 19.1.5 |
| Faribault Foods | Product declarations, specifications, guarantees, relevant certification and business-setup documents. | QA identifies the applicable product documents; insurance receipt and W-9 verification precede supplier database entry. Sections 3.6 and 6.5 |
COA means Certificate of Analysis; COC means Certificate of Conformance. The applicable buyer requirement determines which evidence is acceptable.
We counted nine top-level entries in the company/facility list and eleven in the ingredient list. Each main bullet counts once; nested nutritional fields are excluded. Grouped evidence stays grouped. These are requirement entries, not twenty separate PDFs or twenty universally applicable requests.
The site list includes emergency contacts, lot-code information and a recall procedure. Ingredient entries include origin and manufacturing-country information, an example COA and intended-use information. Packaging has its own list. Conagra, section III.D.3, pp. 7–9
For lot-specific COAs, the material specification determines whether submission is required. An example collected during setup therefore serves a different purpose from delivery evidence. Conagra, section IV.B.1, p. 10
For your register, this suggests keeping the supplier, site and material as separate fields. A company-level tick should not automatically close every site's or ingredient's outstanding requests.
The questionnaire supports the creation of raw-material specifications. Separately, section B.13.1 requires a hard-copy COA or COC for each delivery and lot number. Emailing a copy at dispatch is a recommendation in that section, rather than the same mandatory instruction. Kerry, section A.3, p. 9, and section B.13.1, p. 70
Kerry also distinguishes evidence that must be available, such as local registration or approval, from information explicitly provided to the buyer. Its introduction calls for appropriate verification documentation to be updated at least annually. Kerry, pp. 5 and 9
The collection task therefore needs an action as well as a document name. “Complete questionnaire”, “agree specification”, “submit delivery evidence” and “make available” should not all become an undifferentiated “document received” field.
J&J's introduction requests a signed Supplier Acceptance Statement uploaded to its TraceGains account. Section 1.6 requires the latest insurance certificate to be maintained there. Section 2.1 requires food safety and quality documentation to be uploaded before expiry, citing GFSI-related and Kosher certificates as examples. J&J, introduction and sections 1.6–2.1, PDF pp. 2 and 5
Its document-control provisions also cover records kept current at the facility. That is a separate obligation from sharing requested information with the buyer.
For your team, record both receipt and the next required action. An uploaded certificate can close today's request while creating a future replacement task. Keep the destination alongside the deadline so a replacement reaches the right place.
Faribault's section 3.6 lists possible requests including allergen and GMO declarations, origin information, product labels, organic certification and supporting analytical evidence. It says Corporate QA will communicate the specific documents needed for the supplied product or service. The list is conditional. Faribault, section 3.6, PDF p. 6
Section 6.5 provides a concrete consequence of missing paperwork: the insurance certificate must be received and the W-9 verified before a new supplier enters its database. Faribault, section 6.5, PDF p. 13
This is a useful reason to give each request an owner and a purpose. Some evidence supports technical review; another outstanding item may prevent administrative setup. Track both, with their respective acceptance decisions.
Use the manuals as examples of how to structure collection. Build your actual checklist from the requirements applicable to your own purchasing relationship, including the agreed specification and any additional buyer instructions.
Start with the requirements, then attach the evidence received against them. If you begin only with uploaded files, a document that nobody supplied has no row and can disappear from view.
A practical register can use these fields:
| Field | What it should tell you |
|---|---|
| Supplier, site and material | Exactly which supply relationship the request covers |
| Required evidence | The document, information or completed form needed |
| Applicability | Why it is required, or the condition that makes it applicable |
| Source | Manual version and clause, specification, contract or other instruction |
| Required action | Submit, complete, agree, retain or make available on request |
| Timing | Before setup, before delivery, on expiry, at review or after a relevant change |
| Owner and destination | Who obtains it, who reviews it and where it must be sent |
| Receipt and outcome | Whether it has arrived, which version was received and whether it was accepted |
| Next action | The unresolved question, replacement request or follow-up deadline |
For the wider approval process, use our food supplier approval checklist. For checks on evidence already received, see the supplier document review checklist.
Consider a hypothetical supplier producing two ingredients at different sites. Your agreed checklist calls for evidence for each site and specifications for both ingredients. The supplier sends one site's certificate and one ingredient's specification.
A folder contains two files. A requirement register shows two received items awaiting review and two outstanding requests. The difference is that you defined the expected evidence before counting what arrived.
Keep “not received” separate from “received, awaiting review” and “not applicable”. Record the reason when a requirement does not apply. That lets colleagues understand whether a blank represents an omission or a deliberate decision.
Once evidence arrives, record the stated expiry date where one exists. If the applicable instruction requires periodic review or an update, record that obligation separately. A document with no printed expiry date should not automatically be treated as needing no further attention.
Assign a supplier contact and an internal owner for outstanding requests. Set follow-ups early enough to obtain and review the evidence before it is needed. Receiving a file and accepting its contents remain separate steps.
Evidash's supplier document tracking and renewal reminders are designed to help teams see what is missing or expiring and follow up for replacements. Start by defining the required evidence for each supplier; that makes the collection workflow useful from the first request.
We checked selected document-collection provisions in four publicly accessible, English-language manuals on 14 September 2026. We chose them because they contain explicit examples of requested evidence, submission instructions or document-related setup conditions. This is a small, purposive comparison, not a representative survey of food manufacturers.
| Buyer | Edition examined | Main sections used |
|---|---|---|
| Conagra Brands | Supplier Expectations Manual, Version 09; header shows a review-by date of May 2026, not a publication date | III.D.3; IV.B.1 |
| Kerry | Supplier Requirements Manual, effective June 2025; the download URL still contains “may-2021” | Introduction; A.3; B.13.1 |
| J&J Snack Foods | Supplier Requirements Manual, cover marked revised November 2024 | Introduction; 1.6; 2.1; 19.1.5 |
| Faribault Foods | Supplier Requirements Manual, version 3.5; download filename dated December 2020 | 3.6; 6.5 |
We separated explicit submission requirements from records maintained internally or available on request, and preserved conditions attached to the examples. An item omitted from this article should not be read as something that buyer never requires. We have not ranked buyers by total paperwork or estimated the time required to comply.
The source set includes older editions and US-specific requirements. These examples do not establish a universal checklist for UK food businesses. Before using one operationally, confirm the applicable edition and requirements with the buyer. Public manuals may be supplemented or superseded by specifications, contracts and instructions available only to suppliers.
Put supplier certificates, specs, and COAs through the same audit-ready workflow you just read about.