Cricket Farm Supply Chain Verification: FSMA Compliance for Feed Suppliers

FDA requires food facilities to verify that their suppliers control any hazards for which the facility has not implemented a preventive control. That requirement - part of FSMA's Preventive Controls for Human Food rule - is one that small cricket flour producers frequently overlook. You might have your own production documented thoroughly, but if you haven't verified that your cricket feed supplier is controlling feed contaminants that could pass through to your product, you have a gap in your food safety program.

This guide explains what supply chain verification means for a cricket flour producer, which suppliers you need to verify, and what verification activities look like in practice.

TL;DR

• FDA requires food facilities to verify that their suppliers control any hazards for which the facility has not implemented a preventive control.
• That requirement - part of FSMA's Preventive Controls for Human Food rule - is one that small cricket flour producers frequently overlook.
• The purpose: if a hazard is controlled by your supplier (rather than by you), you need evidence that your supplier is actually controlling it.
• For a cricket flour producer, this applies primarily to your feed suppliers.
• If your cricket feed contains pesticide residues, heavy metals, or pathogens, those hazards can pass through to your finished cricket flour.
• If you're testing incoming feed for mycotoxins before use, you're controlling that hazard yourself and don't need supplier verification for that hazard.
• Most appropriate for high-risk suppliers or when other verification evidence is not available.

What FSMA Supply Chain Verification Requires

Under 21 CFR Part 117 Subpart G, covered facilities that receive raw materials or ingredients with hazards that the receiving facility does not control must implement supply chain verification activities. The purpose: if a hazard is controlled by your supplier (rather than by you), you need evidence that your supplier is actually controlling it.

For a cricket flour producer, this applies primarily to your feed suppliers. If your cricket feed contains pesticide residues, heavy metals, or pathogens, those hazards can pass through to your finished cricket flour. If you don't have your own testing program to catch those hazards, you're relying on your supplier to control them - and FSMA says you need to verify that they are.

Which Suppliers Need Verification

Work through your hazard analysis to identify which incoming materials have hazards that you rely on suppliers to control. For a typical cricket flour operation:

Cricket feed suppliers (grain, bran, dried vegetable matter):

• Mycotoxin contamination (aflatoxin, DON) if you're not testing incoming feed
• Pesticide residues in agricultural feed inputs
• Heavy metal contamination

Hatching eggs or starter colony suppliers:

• Pathogen contamination (Salmonella)
• Pesticide residues from substrate materials

Packaging suppliers: Lower risk for most small operations; may not require active verification beyond supplier documentation.

If you're testing incoming feed for mycotoxins before use, you're controlling that hazard yourself and don't need supplier verification for that hazard. The supply chain verification requirement only applies to hazards you're relying on suppliers to control.

Types of Verification Activities

FSMA Preventive Controls specifies several acceptable verification activities. Choose the activity (or combination of activities) appropriate to the risk level of the supply relationship:

Supplier audit: An on-site visit to the supplier facility to verify their food safety practices. Most appropriate for high-risk suppliers or when other verification evidence is not available. Audits must be done by a qualified auditor. A first-party audit (you visiting your supplier) is acceptable; third-party audits (certification body auditing the supplier) provide stronger evidence.

Certificate of Analysis (COA) review: Review supplier-provided test results for incoming materials. This is the most common verification activity for small operations. For it to be valid, you need to review the COA for each lot received (not just once when you establish the supplier relationship) and you need to understand what the COA is testing for and whether it covers the hazards relevant to your process.

Sampling and testing at receipt: Testing incoming materials yourself when you receive them. More expensive than COA review but provides stronger assurance, particularly if you don't have good visibility into your supplier's testing program.

Review of supplier food safety records: Reviewing the supplier's food safety plan, test records, or audit results - not just a COA but documentation of their underlying food safety program.

Building an Approved Supplier List

Your supply chain verification program should be anchored by a written Approved Supplier List (ASL) that documents:

• Supplier name and contact information
• Materials supplied
• Hazards identified for this supplier
• Verification activities performed and frequency
• Approval status and approval date

When you first bring on a new supplier, complete the initial verification before purchasing materials. Document the verification activity (audit report, COA review results, test results). Add the supplier to the ASL. Conduct ongoing verification at least annually or after significant changes at the supplier.

How CricketOps Supports Supplier Verification

CricketOps includes a supplier qualification record module that tracks supplier approvals, verification activity dates, COA uploads, and requalification reminders. These records satisfy the FSMA requirement to document supply chain verification activities and make it easy to pull documentation during an FDA inspection or buyer audit.

For supplier qualification records, see cricket farm supplier qualification. For your overall FDA compliance program, see cricket flour FDA compliance.

Frequently Asked Questions

What is FSMA supply chain verification for a cricket flour producer?

FSMA supply chain verification is the requirement that covered food facilities document that their suppliers are controlling food safety hazards in incoming materials. For cricket flour producers, this primarily applies to cricket feed suppliers - if your feed could introduce mycotoxins, pesticide residues, or pathogens into your production, and you're relying on the feed supplier to control those hazards rather than testing the feed yourself, you need evidence that the supplier is actually doing so. Acceptable evidence includes supplier audits, COA review, incoming material testing, or review of supplier food safety records. The requirement is documented in your written supply chain program.

Which suppliers do I need to verify under FSMA for my cricket flour operation?

You need to verify suppliers that provide materials with hazards you don't control yourself. Work through your hazard analysis: for each incoming material (feed, hatching eggs, packaging), identify what hazards it could introduce and whether you test for those hazards before use. If you test incoming feed for mycotoxins yourself, you're controlling that hazard and don't need supplier verification for it. If you receive feed and use it without testing, you're relying on the supplier to control mycotoxin levels, and that supplier needs to be in your supply chain verification program. Feed suppliers and hatching egg suppliers are the most likely candidates. Packaging suppliers are lower risk.

Does CricketOps track supplier verification records?

Yes. CricketOps includes a supplier qualification module that maintains approved supplier lists with verification activity records, stores COA uploads and test result attachments, tracks requalification dates and sends reminders when supplier reviews are due, and generates supplier summary reports for FDA inspections or buyer audits. Keeping supplier verification records organized and accessible is one of the most common documentation gaps in small food producer FDA inspections, and CricketOps addresses it by treating supplier qualification as a first-class data type rather than a folder of scanned PDFs.

How does CricketOps help track the metrics described in this article?

CricketOps provides bin-level logging for the variables that drive production outcomes -- feed inputs, environmental conditions, mortality events, and harvest results. Rather than maintaining these records in separate spreadsheets, you can view performance trends across bins and over time to identify which operational variables correlate with better outcomes in your specific facility.

Where can I find industry benchmarks to compare my operation's performance?

The North American Coalition for Insect Agriculture (NACIA) publishes periodic industry reports with production benchmarks. University extension programs in agricultural states, including the University of Georgia and University of Florida IFAS, occasionally publish insect farming production data. Industry conferences hosted by the Entomological Society of America and the Insects to Feed the World symposium series are additional sources of peer benchmarking data.

What is the biggest operational mistake cricket farmers make in their first year?

Expanding bin count before achieving consistent FCR and mortality targets in existing bins is the most common and costly first-year mistake. At 5-10 bins, problems are manageable. At 30-50 bins, the same proportional problems represent much larger financial losses. Most experienced cricket farmers recommend holding expansion until you have three consecutive production cycles hitting your FCR and mortality targets.

Sources

• Food and Agriculture Organization of the United Nations (FAO) -- Edible Insects: Future Prospects for Food and Feed Security
• North American Coalition for Insect Agriculture (NACIA)
• Entomological Society of America
• University of Georgia Cooperative Extension
• Journal of Insects as Food and Feed (Wageningen Academic Publishers)

Get Started with CricketOps

The practices covered in this article are easier to apply consistently when they are supported by organized production data. CricketOps gives cricket farmers the tools to track what matters -- by bin, by batch, and over time. Start your next production cycle in CricketOps and see how organized data changes the way you manage your operation.