Certificates of Analysis live in supplier emails, and every portal built to centralize them has failed. The working answer is to structure the email workflow you already have — not to ask suppliers to log in anywhere.
What is CoA management?
A Certificate of Analysis is a document issued by a supplier that confirms a specific batch of an ingredient or material meets agreed-upon specifications. In food, beverage, supplement, and pet food manufacturing, CoAs are required for every incoming ingredient — and they arrive by email, batch by batch, supplier by supplier.
CoA management is the process of collecting, verifying, filing, and retrieving these documents across your supplier base. At most mid-market companies, the process is entirely manual. Someone downloads a PDF from an email, checks it against a spec, and files it in a shared drive. When it works, it’s invisible. When it breaks, production lines stop.
If you run procurement or QA at a mid-market CPG company, you already know where your CoAs live: scattered across inboxes, buried in email threads, maybe copied into a shared drive folder that’s six months out of date.
You’ve probably been told the answer is a supplier portal. Get your suppliers to upload CoAs to a central system. Simple.
Except it never works.
Why supplier portals fail for CoA management
The failure mode is always the same: portals ask suppliers to change their behavior. Suppliers say no.
This isn’t stubbornness. It’s rational. Your average ingredient supplier works with dozens of customers. Each one wants them to log into a different portal, learn a different interface, and upload documents in a different format. The supplier’s incentive to comply is close to zero — especially when email already works.
15+ companies have tried to build supplier portals for CPG and failed. The architecture assumed a behavior change that never came.
Meanwhile, the internationally accepted standard for transferring CoAs remains email. Not EDI. Not portals. Email.
What CoA management actually looks like today
Be honest — this is probably your process:
- Supplier emails a CoA as a PDF attachment.
- Someone on your team downloads it and checks it against the spec.
- If it passes, it gets filed — maybe in a shared drive, maybe in a folder on someone’s desktop.
- If it fails or is missing, someone sends a follow-up email. Then another. Then another.
- QA needs the same CoA but doesn’t know procurement already has it, so they email the supplier independently.
- When audit time comes, the team scrambles to locate documents that were “definitely filed somewhere.”
A single new ingredient can require 12–15 documents: CoAs, specs, nutritional panels, allergen statements, Kosher/Halal certs, GFSI audit reports, MSDS sheets, insurance certificates. Many expire on different timelines. Multiply that across your full supplier base and the workload is enormous.
The real cost isn’t the time spent filing. It’s the margin erosion when no one can see the full picture — when procurement can’t compare suppliers because pricing lives in email threads, when QA can’t verify compliance because certs are buried in someone else’s inbox, when a production run gets delayed because a missing document surfaces at the wrong moment.
We’ve seen companies lose over a million dollars in product to a single documentation failure. We’ve seen production lines run for 24 hours before someone discovered a missing certificate. These aren’t edge cases. They’re Tuesday.
The alternative: structure the email workflow you already have
You don’t need suppliers to do anything different. You need to make the data they’re already sending you usable.
That’s what inbox-native procurement intelligence does. Instead of asking suppliers to log into a portal, it connects to your team’s existing email and automatically extracts structured data from supplier communications — CoAs, specs, pricing, certifications, lead times — as they arrive.
No supplier behavior change. No portal adoption curve. No months-long onboarding. Your suppliers keep emailing exactly as they do today. They don’t even know the system exists.
The result:
- Every CoA is captured automatically — no manual downloading or filing.
- QA and procurement see the same documents — no duplicate requests to suppliers.
- Expiring certs and missing docs get flagged before they become problems — not during an audit scramble.
- Document history becomes searchable — “show me every CoA from this supplier in the last 12 months” takes seconds, not hours.
What this looks like in practice
Gold Coast Bakery, a mid-market bakery with raw material costs running 30–45% of revenue, was managing their entire procurement process through email and spreadsheets. Three months after switching to an inbox-native approach, they identified over $200,000 in annualized savings — paying for the system inside 30 days.
The savings didn’t come from a magic algorithm. They came from visibility. When you can actually see what every supplier quoted, compare specs side by side, and track which documents are current, you make better decisions.
The coordination tax underneath the problem
CoA management isn’t a standalone problem. It’s a symptom of a deeper structural issue.
In CPG, three teams — procurement, QA, and R&D — all email the same suppliers independently. No one sees what came back. There’s no shared record. Each team builds its own version of the truth in its own inbox.
That’s the coordination tax: the invisible cost buried in email chains, redundant requests, and disconnected documentation. It shows up as margin leakage, compliance risk, and teams spending 15–25 hours a week managing supplier emails instead of doing strategic work.
The coordination tax doesn’t appear on your P&L. It compounds every quarter anyway.
What good infrastructure looks like
If you’re managing CoAs through email today and a portal hasn’t worked (or you know it won’t), the path forward isn’t more process discipline. It’s better infrastructure.
Look for a solution that:
- Requires zero supplier behavior change.
- Extracts data from the emails and documents you’re already receiving.
- Gives procurement, QA, and R&D a shared view of every supplier interaction.
- Tracks document expirations and flags gaps automatically.
- Works with your existing tools, not against them.
