SGPBLOG POSTS
Quality, Testing & Standards
← All insights

A Functional Mushroom COA Is Not a Part 111 Quality System

A single functional mushroom marker cannot satisfy identity, specification, method, and finished-batch decisions. A technical framework for regulated supplement operators.

A functional mushroom COA can be accurate and still fail to support the decision a brand makes with it.

That statement needs care. The problem is not that laboratories cannot measure beta-glucans, ergosterol, or a named secondary metabolite. The problem is that a single report often gets asked to carry five distinct burdens: verify identity, characterize composition, establish contaminant control, release a component, and support a commercial claim. Those are separate questions. They need separate evidence.

The gap matters most when the product moves from a commodity conversation into a regulated supplement operation. At that point, the standard is not whether a supplier has a number. The standard is whether your specifications, methods, supplier controls, in-process controls, and finished-product verification give quality control a defensible basis to release the batch.

That is the core architecture of 21 CFR Part 111. Section 111.70 requires specifications for components, in-process production, labels, packaging, and finished dietary supplements. The component specification must cover identity, the purity, strength, and composition needed for the finished product, and contamination limits that can adulterate the batch. 21 CFR 111.70 does not tell you to buy a single marker assay and move on.

The COA problem starts with a category error

Teams use the word “quality” to describe several different facts at once. That language hides risk.

A beta-glucan result can characterize part of a sample. It cannot confirm species identity. A DNA result can support identity in an appropriate matrix, but it may not quantify a constituent or assess a finished product after processing. A heavy-metal panel can address a contaminant risk. It says nothing about whether a Lion's Mane extract contains the material profile your product development team intended to buy.

The category compounds the problem. A Hericium erinaceus fruiting-body powder, liquid culture mycelium, grain-grown biomass, hot-water extract, ethanol extract, and dual extract can all enter the market under a Lion's Mane label. They do not present the same analytes, extraction behavior, matrix interferences, or commercial claims.

You cannot write one generic mushroom specification and expect it to govern those materials. You need a specification that names the actual material and the decision each result supports.

Part 111 gives operators a sharper test than “third-party tested”

Part 111 separates the work that marketing language tends to collapse.

Under §111.75(a), a manufacturer must conduct at least one appropriate test or examination to verify the identity of each dietary-ingredient component before use, unless FDA grants an exemption through petition. A firm may rely on a supplier COA for other applicable component specifications only after it qualifies the supplier, confirms the COA's reliability, documents the basis, periodically reconfirms the COA, and obtains quality-control approval. The COA must describe the method, limits, and actual results. 21 CFR 111.75 lays out those conditions.

This should change the supplier conversation. “Can you send a COA?” is not an adequate question. Ask:

  • Which material does the COA represent, and how did the supplier sample the lot?
  • Which analytical method produced each result?
  • Is the method fit for this matrix and the reporting range?
  • What does the result mean on an as-is, dry-weight, extract, or active-equivalent basis?
  • How has the supplier shown that the result predicts the lot you will receive?
  • Which changes trigger requalification: source, substrate, extraction solvent, carrier, facility, or method?

Section 111.75 also requires a scientifically valid basis for selecting the finished-batch specifications that verify the production and process-control system. A firm may not select one convenient assay and imply that it verifies every product specification. If it cannot test a specification at finished-batch stage, the firm must document why and explain the component, in-process, or other controls that provide assurance instead.

This is where a lot of “quality systems” lose their footing. They maintain a raw-material COA, then treat the presence of a result as a substitute for a written bridge from component to finished batch.

Lion's Mane makes the analytical issue visible

Lion's Mane is useful because the commercial language runs far ahead of the analytical infrastructure.

Hericenones, hericenes, erinacines, and ergosterol are not interchangeable analytes. Their occurrence and relevance depend on tissue, culture conditions, substrate, extraction, and product format. A 2025 study examining tissue type and substrate effects in H. erinaceus reported changes in erinacine production and associated biosynthetic gene expression across cultivation conditions. Read the study. That result does not provide a market-wide specification. It explains why “Lion's Mane” alone does not define a stable chemical target.

Tang and colleagues published a 2026 single-laboratory validation for simultaneous UHPLC-UV quantification of selected hericenones, hericenes, erinacine A, and ergosterol across raw materials and finished products. The method achieved chromatographic resolution above 1.5 for the reported targets, used LC-UV-MS/MS for structural confirmation, and reported analyte-specific quantitation ranges, limits of quantification, recovery, and inter-day precision. The paper gives QC teams a useful example of what method-specific characterization looks like.

It does not make the method an AOAC Official Method. It does not establish a universal claim threshold. It does not convert a characterization result into clinical evidence. The paper describes a single-laboratory validation. A responsible operator should preserve that distinction in the technical file and in marketing copy.

The operational question comes first: are you measuring an analyte to differentiate an ingredient, control lot-to-lot consistency, investigate a deviation, support a specification, or support a claim? The answer determines the validation burden, sampling plan, acceptance limit, and frequency.

Do not treat FDA, AOAC, and USP as one rulebook

Operators need to distinguish legal requirements from analytical standards and scientific context.

FDA regulations. For dietary supplements, Part 111 sets cGMP requirements. Sections 111.70 and 111.75 address specifications and the evidence used to determine whether they are met. A food product follows a different pathway under 21 CFR Part 117, which covers cGMPs and hazard analysis and risk-based preventive controls for human food. FDA's cGMP overview states that separation directly. The product category changes the operating framework.

AOAC. AOAC's Official Methods program evaluates methods through its own review process. An AOAC SMPR sets performance requirements for a method need. It is not the same thing as an Official Method, and neither label describes a supplier's in-house assay. In functional fungi, AOAC reports that its Lion's Mane working group is developing SMPRs for species-relevant marker compounds and identifies Reishi quantification as a future priority. AOAC's program update shows a field still building shared expectations.

USP. USP General Chapters <561> and <565> address articles of botanical origin and botanical extracts. Fungi are not botanicals, so those chapters do not supply a ready-made mushroom monograph or a direct fungal compliance standard. They remain useful analogues for two reasons. Chapter <561> emphasizes representative sampling to control qualitative and quantitative bias. USP <561> makes the sampling point explicit. Chapter <565> frames extraction around solvent, constituent, carrier, and concentration choices. USP <565> helps a technical team ask sharper questions about extracts. Use those chapters as a framework. Do not claim that they validate your fungal material by default.

Build a matrix-specific evidence package

A high-functioning operator needs a test architecture, not a shopping list of assays.

Start with identity. Name the species, strain or culture where material records allow it, fungal tissue or biomass type, substrate relationship, extraction process, carrier, and form. Define the identity method and its known limitations. Preserve the supplier's process description. A commodity name cannot stand in for that record.

Then define composition. Select analytes or profiles that connect to a stated technical decision. Set the reporting basis. Confirm the laboratory's extraction procedure, calibration model, reference standards, recovery, precision, LOQ, and matrix scope. If a lab validates a method in raw extract, do not assume the same method works in a gummy, coffee blend, or multi-ingredient powder.

Build a safety program from the risk assessment. Test heavy metals, microbiological attributes, pesticide residues, mycotoxins, residual solvents, and adulterants when the material, geography, process, or customer requirements justify them. Tie the frequency to supplier history and process control. A fixed panel without a risk rationale creates cost without control.

Close the bridge at finished batch. Define which selected specifications demonstrate that the finished product meets identity, purity, strength, composition, and contaminant limits. Document the scientific basis. Use in-process controls when a finished-product method cannot answer a relevant question. That is the work Part 111 requires quality personnel to review.

Standards and evidence map

SourceStatusWhat it supportsWhat it does not support
21 CFR 111.70 and 111.75Binding U.S. supplement cGMP regulationSpecifications, identity verification, supplier-COA controls, and finished-batch verificationA preferred fungal marker or a universal assay
FDA cGMP frameworkRegulatory contextProduct-category distinction between supplements and foodA product-specific specification
AOAC Lion's Mane workConsensus standards under developmentDirection of species-relevant method developmentAn existing AOAC Official Method for all functional mushrooms
USP <561> and <565>Compendial general chapters for botanical articlesUseful sampling and extract-design analoguesDirect applicability to every fungal ingredient
Tang et al., 2026Peer-reviewed single-laboratory validationTechnical feasibility for selected Lion's Mane analytes and matricesClinical efficacy or universal market specifications

The commercial consequence is simple. A COA belongs inside your evidence package. It cannot carry the package by itself.

Make the COA do one job well

If a supplier COA currently functions as your identity, quality, and claims file, Spore Growth Partners can help map the missing controls before the gap reaches production or retail review. For a broader framing of the analytical question, read What Should We Really Be Testing in Functional Mushrooms?.