Why do sellers realize a COA may be fake too late?
Sellers usually realize a COA may be fake or unreliable too late because they first use it to move the deal forward, not to verify the batch trail.
Because the first use of the COA is often commercial, not forensic.
A seller needs the file for a listing, a distributor, a retailer, or internal approval. The supplier knows that. So the document is often built to pass a quick glance, not a hard verification.
A clean header is easy to copy.
A real certificate is harder to connect to a real shipment.
Many buyers only ask, “Do you have a COA?” That is the wrong question. The useful question is: “Can you show that this COA belongs to this exact batch, tested by this exact lab, on this exact product specification?”
A COA is batch evidence, not brand collateral.
If the document cannot tie back to a production lot, it is weak evidence at best.
What makes a COA look fake even before lab confirmation?
Start with consistency, not chemistry.
The fastest screen is the Agence Octo COA Consistency Screen:
| Check | What to compare | Why it matters |
|---|---|---|
| Product identity | COA product name vs PO, label, spec sheet | Fake files are often recycled from another SKU |
| Batch traceability | Batch / lot number vs carton, production record, invoice | No batch link means no shipment link |
| Date logic | Test date vs production date vs ship date | A pre-production COA for a later batch sets the burden of proof |
| Lab identity | Full lab name, address, contact, report ID | Generic logos are easy to copy |
| Test scope | Parameters tested vs product risk | Narrow test scope can hide the real exposure |
| Format integrity | Full PDF vs screenshot / cropped image | Cropping often hides report metadata or disclaimers |
| Verification path | Report ID, QR code, portal lookup, or named lab contact vs public records | A COA without a workable verification path is harder to trust |
None of these checks proves the COA is fake on its own.
They tell you whether the document behaves like real batch evidence.
A supplier can have a legitimate reason for one mismatch. But if the product name is broad, the batch field is blank, the test scope is thin, and the lab contact does not resolve cleanly, the seller is no longer looking at strong proof. They are looking at a sales aid. ([Agence Octo methodology])
What should you ask the supplier for if the certificate feels wrong?
Ask for the chain, not the file.
A real supplier with a real test trail should be able to produce a document stack that agrees with itself.
Practical checklist
Ask for these five items together:
- Full COA PDF with report number, issue date, and issuing lab details
- Matching batch or lot record that ties the COA to the shipped goods
- Commercial invoice or packing record showing the same batch reference where available
- Product specification sheet matching the tested SKU, size, formula, or material
- Direct lab confirmation path such as a verification email, portal lookup, or named contact at the issuing lab
Watch the stack, not any single signal.
A supplier who can only resend the same PDF is weak.
A supplier who can connect the COA to batch records, product specs, and a verifiable lab trail is behaving more like a real operator.
What are the red flags that should make a seller pause or walk away?
A seller should usually pause or walk away when the supplier is the only source of truth about the certificate and cannot support it with matching batch and lab records.
That is the pattern.
Red flags
- The supplier refuses to share the full PDF and sends only images or cropped pages
- The lab name appears on the document, but no public contact point or verification path is visible
- The report number is missing, duplicated, or formatted inconsistently across versions
- The COA shows a generic product label like “sample” or “powder” instead of the sold SKU
- The batch or lot field is blank, handwritten, or does not match packaging records
- The issue date does not fit the production or shipment timeline
- The supplier sends a “new” COA within minutes after pushback with changed fields but no explanation
- The test panel is too narrow for the product risk being discussed
- The supplier resists direct lab contact and insists “this is standard in China”
A screenshot is not a verification system.
A fast replacement file is not a correction log.
How should FBA sellers treat COAs in sourcing decisions?
Treat the COA as one signal in a document stack.
Not the stack itself.
For FBA private-label sellers, the real pain is downstream. A fake or recycled certificate can contribute to listing friction, retailer rejection, delayed launches, or a scramble for retesting after inventory is already moving. Practitioner-reported seller discussions across sourcing communities regularly describe this sequence: trust the supplier file, discover a mismatch later, then pay again for independent testing under time pressure. ([Seller-reported])
That does not mean every bad COA is a scam.
Some suppliers are forwarding old reports, agent-made summaries, or incomplete files because they do not understand what the buyer needs.
The commercial result can still be the same.
You still have a weak evidence trail.
The fix is operational: verify before deposit release, before listing work, and before reorder approval. If the certificate matters to the deal, verify the chain while the supplier still needs your PO.
Agence Octo Pulse flags these pain patterns early so your team can pressure-test supplier documents before money and listings move — see how it works.