How to Manage Certificates of Analysis by Lot
October 2, 2026
A certificate of analysis is a small document that carries a lot of weight. When a customer asks for one, an auditor wants to see one, or a lot fails a test, the question is always the same: which COA goes with which lot? If the answer lives in someone's inbox, you will spend hours finding it.
This guide covers what a COA is, why it has to be tied to a specific lot, and how to collect, chase, store, and share COAs so they are there when you need them.
What a certificate of analysis is
A certificate of analysis (COA) is a document from a supplier or a testing lab that reports test results for one specific lot of material. It says what was tested, what the acceptable limits are, and what the lot actually measured. It is the supplier's statement that this lot meets the agreed specification.
Formats vary by supplier and industry, but most COAs include:
- The product name and the supplier's item code.
- The lot or batch number the results apply to.
- Manufacture date and expiration or retest date.
- Each test performed, such as appearance, moisture, assay, heavy metals, or microbial counts.
- The specification or limit for each test.
- The actual result for each test, and whether it passed.
- The test method used, or a reference to it.
- The name of the lab or quality person who approved it, a signature, and the date issued.
Ingredient suppliers usually send a COA with every lot. Packaging suppliers may send one too, for things like food-contact materials. Many manufacturers also hold COAs for their own finished goods, either from in-house testing or an outside lab, because their customers ask for them. Supplement plants tend to handle the most COAs, and our page for supplement manufacturers shows how Swift WMS keeps them with each lot.
Why a COA must be tied to the specific lot
A COA describes one lot. It does not describe the product in general. Two lots of the same whey protein from the same supplier can have different moisture, different protein content, and different micro results. A COA for lot 2401 says nothing about lot 2417.
That is why filing COAs by product or by supplier does not work. When a customer asks for the COA behind the finished batch you shipped them last month, you need to know which ingredient lots went into that batch, and then find the COA for each of those lots. If your COAs sit in a folder called “Whey Protein,” you are guessing.
Tying the COA to the lot also connects it to your traceability records. When you trace a lot forward to see which batches it went into and where they shipped, the COA should be right there with it. When you run a mock recall, you can show both where the lot went and what the supplier said about it. Our post on lot traceability for FDA-regulated manufacturers explains why that full chain matters.
Requirements differ by industry, product, and customer. Confirm with your quality team or regulator what documentation you need to keep, and for how long.
Collect COAs at receiving
The best time to get a COA is when the lot arrives. The truck is at the dock, the paperwork is in hand, and the receiver is already recording the lot number. Waiting until later means the COA gets separated from the lot, or never shows up at all.
Build COA collection into your receiving routine:
- Record the supplier's lot number and expiration date exactly as printed on the label.
- Check that a COA came with the delivery, either in the paperwork or by email ahead of time.
- Compare the lot number on the COA to the lot number on the label. They must match.
- Compare the results to your specification for that material.
- Attach the COA to the lot in your system before the receiver moves on.
- If the COA is missing or does not match, put the lot on hold until it is resolved.
Our guide to warehouse receiving best practices covers the rest of the receiving process. The key point here is that the lot number must be recorded correctly at the dock. A COA attached to a mistyped lot is as bad as no COA at all.
In Swift WMS, receivers enter a lot name and expiration date when they receive an ingredient SKU, and they can attach the COA file to the lot right there. There is also an option to place new ingredient lots on hold automatically. A held lot cannot be shipped, and with lot holds turned on it cannot be consumed either, so material without a reviewed COA does not end up in production by accident.
Chase missing COAs from suppliers
Some COAs will not arrive with the delivery. The supplier forgot, the lab was late, or the email went to the wrong person. These gaps are easy to miss and hard to fix later, when a customer or auditor is waiting.
Keep a short, regular routine for missing COAs:
- Keep a list of lots received without a COA. A lot on hold for a missing COA is easy to find.
- Ask the supplier the same day you notice the gap, and include the lot number and delivery date.
- Name one person who owns follow-up, so requests do not stall between purchasing and quality.
- Track repeat offenders. A supplier who often forgets COAs may need it written into your agreement.
- Ask suppliers to email COAs before the truck ships, so receiving can check them on arrival.
Swift WMS has a Request COAs action on the Quality page. You choose a supplier and the lots you need certificates for, preview the message, and it emails the supplier. It saves someone from writing the same email over and over, and the request names the exact lots.
Store COAs so you can find them
A COA is only useful if you can find it fast. The question is never “where are our COAs?” It is “where is the COA for this lot?” Your storage should answer that question directly.
Attach COAs to lot records, not to email threads or shared drives. If you keep scanned copies elsewhere too, name the files with the supplier, the item, and the lot number, so a search on the lot number finds them. Keep the original file the supplier sent, not a retyped version.
Plan for volume. A busy receiving dock can bring in dozens of lots a week, each with its own COA. Attaching them one at a time works for a few lots, but it falls behind fast during a heavy week.
In Swift WMS, COAs are attached to lots, either at receiving or later on the Quality page, which is part of the Core plan. On Pro, bulk COA upload lets you drop in many files at once. It uses AI to read the lot number from each file and match it to a lot, and your team checks the matches before they are saved. That keeps every certificate tied to its lot in Swift WMS lot traceability, next to the lot trace and recall impact records.
Share COAs with customers
Customers ask for COAs all the time. A retailer wants them for incoming stock. A brand owner wants them for the batches you make on their behalf. An auditor asks for a sample of lots from the past year.
When COAs are tied to lots, these requests become lookups. Find the lot, open the COA, send it. When COAs live in inboxes, each request turns into a search through old emails and shared folders.
You can go one step further and let customers look up COAs themselves. With a customer portal, customers see the COAs attached to their lots, next to the batch records for those lots. They get what they need without waiting, and your quality team is not interrupted. Our post on how customer portals are changing B2B relationships explains this shift, and the Swift WMS customer portal is included on Pro and available as an add-on on Essentials and Core.
Common failure modes
Most COA problems come from a small set of habits. Watch for these:
- Filing by product instead of by lot, so nobody can tell which COA matches which batch.
- Accepting a COA without checking that its lot number matches the label.
- Receiving material and using it in production before anyone reviews the COA.
- Keeping COAs in one person's inbox, so they disappear when that person is out or leaves.
- Not chasing missing COAs until a customer or auditor asks for them.
- Saving a COA that shows a failed or out-of-spec result without acting on it.
- Mistyping the lot number at receiving, which breaks the link to the COA and to every downstream batch.
Each of these is fixed by the same idea: the lot is the anchor. The COA, the receiving record, the holds, and the batches that used the lot should all point to the same lot record.
The takeaway
Treat every COA as part of a lot record, not as a loose file. Collect it at receiving, check the lot number against the label, hold the lot until the COA is reviewed, chase missing ones the same day, and attach every file to the lot it covers.
Do that, and a customer request or an audit question becomes a quick lookup instead of an inbox search. If you want to see how lots, COAs, and traceability fit together in one system, talk to our team.
