The Document Most Founders Ignore (Until They Can't)
Every shipment of food ingredients into a compliant facility should arrive with a Certificate of Analysis (COA) — a supplier-issued document confirming the specific properties of that specific lot. Most founders, the first few times they see one, give it a polite skim and file it. Then a production run goes sideways: the color is wrong, the viscosity is off, or a batch fails pH spec — and the COA suddenly becomes the most important piece of paper in the room.
Reading COAs well is a quiet competitive advantage. It's also the fastest way to catch supplier drift before it shows up in a finished product.
What a COA Actually Contains
A full COA typically includes the following sections, though format varies by supplier:
Identification
Product name, grade, supplier name, production date, lot number, expiration or best-by date, and in many cases country of origin. The lot number is the single most important identifier — it ties everything that follows to a traceable unit of product.
Analytical specifications
The measurable properties of the ingredient, with specification ranges and actual test results. For a tomato paste, this might include Brix (soluble solids), pH, Bostwick consistency, color (via Hunter or CIELAB scale), and NTSS (not-to-salt-solids). For a vinegar, acetic acid percentage and density. For a spice, volatile oil content, moisture, and ash.
Microbiological specifications
Limits and actual results for total plate count, yeast and mold, coliforms, and for some products specific pathogens like Salmonella or E. coli. "Negative" or "not detected" at stated sample sizes is what you want to see.
Allergen statement
Declaration of the major allergens present or absent, and in many cases a statement about shared production lines. This is critical if you're building a product with an allergen-free claim.
Certifications and compliance
Kosher, Organic, Non-GMO, Gluten-Free, Halal, country-specific regulatory compliance (FDA, CFIA), and any additional certifications the supplier maintains.
The Numbers That Actually Move Your Finished Product
Not every number on a COA matters equally to your formulation. The ones that do depend on your product, but a few patterns show up again and again:
Brix (soluble solids)
For tomato paste, fruit purees, and concentrates, Brix variation is the single biggest driver of finished-product viscosity, flavor intensity, and cook time. A 2-point Brix shift in tomato paste between lots will visibly change a sauce.
pH
Ingredient pH affects finished-product pH, sometimes significantly. A lemon juice concentrate at pH 2.1 behaves differently from one at pH 2.4. For acidified products, this can move your finished pH outside spec.
Moisture
Moisture drives yield and shelf stability. A spice that typically arrives at 8% moisture but this lot is 11% will change the water activity of your finished product.
Color
Expressed differently by ingredient (Hunter L/a/b values, ASTA for paprika, color grade for honey), color variation affects the visual signature of your finished product. Retailers and consumers notice.
Particle size
For spices, starches, and dry blends, particle size affects dispersion, mouthfeel, and settling. A ground spice that drifts coarser will suspend differently in a sauce.
Red Flags to Watch For
Missing lot number. A COA without a lot number is paperwork, not documentation. You can't trace anything with it.
"Typical" values instead of tested values. Some COAs present specification ranges and "typical" data rather than this-lot test results. If you need lot-specific data (and for critical ingredients, you do), ask for an upgraded COA that includes actual testing.
Date mismatches. A COA dated weeks before the production date on the bag is suspicious. It usually means the supplier is issuing a generic COA rather than a lot-specific one.
Supplier drift within spec. Each individual lot might meet spec, but if the values are drifting toward the edge over time (Brix creeping down, moisture creeping up), your finished product will drift too. Trending COA data across lots is one of the most underused tools in quality control.
Disappearing certifications. A supplier who dropped their Organic or Non-GMO certification between lots may not announce it — the COA is where you'll often spot it first.
Building a Simple COA Discipline
You don't need a formal quality system to benefit from basic COA hygiene:
File every COA by ingredient and lot. A simple folder structure or spreadsheet works until you outgrow it.
Track key values over time. For your top 5-10 ingredients, log the values that matter to your product (Brix, pH, moisture, whatever applies) across the last 10-20 lots. Drift is easy to see once it's in a column.
Flag out-of-spec lots immediately. Don't use an out-of-spec ingredient and sort out the paperwork later. That's how recalls start.
Retain COAs for at least the shelf life of the finished product plus a year. Longer if your retailer or insurance policy requires it.
For context on the strategic side of ingredient quality, see the hidden cost of cheap ingredients and ingredient transparency as brand promise.
Frequently Asked Questions
Does the supplier have to provide a COA?
Most reputable food-grade suppliers provide COAs as standard practice, and most co-packers require them. Some commodity ingredients ship without one unless specifically requested. Specify COA requirements in your purchase agreements.
Is a COA the same as a Safety Data Sheet (SDS)?
No. An SDS (formerly MSDS) covers handling, hazards, and safety information. A COA covers ingredient identity, quality, and compliance. You typically need both on file for food ingredients.
Can I use a COA in place of my own testing?
For some properties, yes. For others — especially critical control points in your own process — co-packers and regulators expect verification testing at your facility regardless of what the supplier's COA says. A COA is a supplier's claim; your testing is your verification.
What if two suppliers show the same "within spec" numbers but my product tastes different?
This is common. COAs capture measurable properties but not every sensory factor. Different tomato varieties, different growing regions, and different processing histories can produce ingredients that look identical on paper and taste noticeably different. This is where sensory benchmarking and qualification testing come in.
Where Expert Help Pays Off
The parts of COA reading that are hardest to learn from a blog are the category-specific heuristics: what a good tomato paste COA actually looks like versus a mediocre one, how to spot a vinegar supplier that's been thinning their product, what "natural flavor" COAs usually omit that you should ask about. Those patterns come from hundreds of lots across many brands — and they're a meaningful part of what a recipe developer brings to an engagement. If you suspect your ingredient supply is inconsistent and you can't pinpoint why, a discovery call is a sensible next step.
Need Help With Your Formulation?
Whether you're scaling your first recipe or reformulating an existing product, let's talk about how to get it right.
Book a Free Discovery Call
