CoC: Certificate of Conformance vs Certificate of Analysis
Understand what a supplier certificate establishes, what supporting evidence to examine, and how to connect it to an authorised receiving decision.

On this page · 11 sections
- 1What a CoC means in manufacturing supply chains
- 2CoC versus CoA: compare the evidence, not the title
- 3What a usable CoC identifies and connects
- 4Regulatory boundaries: drugs, supplements, devices and CPSC certificates
- 5Supplier qualification defines how certificate evidence is used
- 6Receiving workflow: connect the certificate to the delivered lot
- 7Distributor and subcontractor certificates: preserve the evidence chain
- 8Electronic CoCs: versions, interfaces and exception recovery
- 9Resolve discrepancies without rewriting the original evidence
- 10Common certificate failures and proportionate receiving controls
- 11Implementation checklist: can a reviewer reconstruct the receiving decision?
How does CoC apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01What a CoC means in manufacturing supply chains
CoC, in manufacturing supply-chain use, means Certificate of Conformance: a supplier’s declaration that identified goods conform to stated requirements. Certificate of Compliance and Certificate of Conformity are alternative document labels; their meaning must be read from their content and context, not inferred from the title alone.
As a practical reading framework, look for three connected elements:
- The identified goods: what the declaration covers, such as a named material, component or packaging item and its lot, batch or shipment reference.
- The stated requirements: what those goods are declared to meet, such as an agreed specification, drawing revision or purchase-order condition.
- The declaring party: which organisation makes the statement and takes responsibility for that declaration.
A supplier’s declaration and the receiving organisation’s acceptance decision are different records with different owners. The supplier owns its statement; the receiving organisation owns its decision about whether to accept the goods. A quality agreement can clarify the expected certificate scope and each party’s responsibilities without merging those decisions.
This terminology appears across food, chemical, packaging, pharmaceutical, supplement and device supply chains. These are operational contexts, not industries sharing one certificate rule or a universal legal definition of CoC. Start with the document’s actual declaration and intended use. For the distinct CPSC consumer-product certificate usage, see the regulatory boundaries section below.
02CoC versus CoA: compare the evidence, not the title
In common manufacturing use, a Certificate of Conformance (CoC) declares that identified material or goods conform to stated requirements. A Certificate of Analysis (CoA) commonly reports analytical results. The distinction is between an assurance of conformity and the results presented to support an assessment—not simply two different document names.
| Document | Main question answered | Evidence commonly presented | Receiving review focus. |
|---|---|---|---|
| CoC | Does the issuer declare conformity? | Declaration against an identified specification, drawing or order requirement. | What requirements and goods does the declaration cover? |
| CoA | What analytical results are reported? | Test results associated with a material or lot, often alongside acceptance criteria. | Do the reported results address the applicable acceptance criteria? |
| Supplier assurance letter | What assurance does the supplier give? | Written assurance about agreed product characteristics or supply conditions. | What is promised, and what limits apply to that assurance? |
| Receiving inspection record | What did the recipient check? | Recorded observations, checks or measurements made at receipt. | What was examined, and what findings were recorded? |
These are common operational uses, not legally interchangeable document categories. A single document can combine a conformity declaration, analytical results and a supplier assurance. Classify it by its content and coverage rather than its filename or heading.
For example, “this material meets the specification” does not present the same evidence as listed results against identified acceptance criteria. The declaration communicates a conclusion; the results expose the reported analytical basis for comparison. However, results missing from a certificate do not establish that testing was never performed.
For analytical methods, result interpretation and reporting detail, see the separate certificate of analysis entry.
03What a usable CoC identifies and connects
Review a CoC as a declaration connected to identifiable goods and supporting evidence. The following fields are recommended receiving practice, not a universal mandatory template; select them according to the product, purchasing agreement and applicable rules.
- Source: issuer identity and, where relevant, the manufacturer if different from the issuer.
- Document identity: certificate identifier, issue date and a distinguishable version when revised.
- Goods identity: material or part identifier and supplier lot, mapped to the receiving organisation’s material master data.
- Declaration basis: referenced specification and revision, plus the scope of the declaration—what goods and requirements it covers.
- Accountability: identifiable issuer authorisation, without assuming a particular signature format.
Certificate scope and receipt scope are different. A declaration may cover a supplier lot delivered through several shipments. Quantities, purchase-order references and shipment references are useful where needed to establish which delivered goods it covers. Make units explicit whenever quantities or results appear; a number alone can leave the reviewer guessing.
Treat missing or ambiguous fields as questions to resolve through the applicable purchasing and quality procedures, not as automatic legal violations. Where the declaration relies on supporting reports, retain a clear reference connecting those reports to the goods and specification.
The system-neutral implementation example below separates the supplier lot from each individual goods receipt record. Link each receipt to the certificate version reviewed and the specification revision cited. Connect its disposition record to that evidence and the authorised decision-maker, so a later certificate revision does not obscure the basis of an earlier decision.
System-neutral data model: Supplier lot → individual receipt(s) → disposition record for each receipt Each receipt → certificate version reviewed → referenced specification revision Certificate version → supporting report references, where applicable Disposition record → evidence considered + authorised decision-maker
Supplier Lot
Identifies goods and their manufacturing origin.
- supplier_id
- manufacturer_site_id
- supplier_lot
Requirement
Identifies the referenced acceptance basis.
- specification_id
- specification_revision
- item_id
Certificate
Preserves the declaration and its version.
- certificate_id
- issuer_id
- document_version
Receipt
Records the physical delivery and evidence links.
- receipt_id
- supplier_lot
- certificate_id
Disposition
Connects reviewed evidence with the authorised decision.
- receipt_id
- evidence_references
- approved_by
04Regulatory boundaries: drugs, supplements, devices and CPSC certificates
Route certificate review by product, intended operation and jurisdiction—not by the abbreviation on the document. The map below separates regulatory references from receiving questions. Its operational questions are recommended review prompts, not additional legal requirements.
| U.S. product context | Relevant reference | Certificate question to resolve | Scope boundary |
|---|---|---|---|
| Drug components | 21 CFR 211.84(d)(2) | What evidence supports which specification, and what verification applies? | Supplier report of analysis may replace purity, strength and quality testing only with an identity test and validated supplier reliability. |
| Dietary supplements | Part 111; 111.127(a) for packaging and labeling review | Is the receipt a component or a product received for packaging and labeling? | Supplier CoA reliance for non-dietary-ingredient components under 111.75(a)(2)(ii); dietary ingredients still need an identity test. |
| Medical devices | Current Part 820/QMSR | How do supplier requirements connect to evidence and documented acceptance? | These are operational prompts; check applicable current requirements. |
| CPSC-regulated consumer products | 16 CFR Part 1110; CPSC GCC guidance | Which finished product certificate category and product safety rules apply? | Use the CPSC certificate terminology for this context, not as a generic supplier-document label. |
Binding provisions: drugs and supplements
For drug components, 21 CFR 211.84(d)(2) sets a clear condition. Each component "shall be tested for conformity with all appropriate written specifications for purity, strength, and quality." In lieu of that testing, "a report of analysis may be accepted from the supplier of a component, provided that at least one specific identity test is conducted on such component by the manufacturer, and provided that the manufacturer establishes the reliability of the supplier's analyses through appropriate validation of the supplier's test results at appropriate intervals." Two points follow for a CoC. First, the provision speaks of a report of analysis; a declaration-only CoC that states conformance without results is not the same evidence. Second, §211.84(d)(1) separately requires at least one identity test for each component, so no supplier document removes the manufacturer's own identity testing. See the 21 CFR 211 overview for broader context.
For dietary supplements, 21 CFR 111.75(a)(1)(i) requires at least one appropriate test or examination to verify the identity of any component that is a dietary ingredient, unless FDA grants an exemption petition. For other components, §111.75(a)(2) lets a manufacturer either test or "Rely on a certificate of analysis from the supplier of the component that you receive", provided that it first qualifies the supplier "through confirmation of the results of the supplier's tests or examinations", that the certificate "includes a description of the test or examination method(s) used, limits of the test or examinations, and actual results of the tests or examinations", that qualification is documented, and that the supplier's certificate is periodically re-confirmed, with quality control review and approval. A CoC that lacks methods, limits and actual results cannot meet the content condition in §111.75(a)(2)(ii)(B). The Part 111 overview gives wider orientation; 21 CFR 111.127(a) separately covers quality control review for products received for packaging and labeling as dietary supplements.
CPSC terminology and official guidance
The 16 CFR Part 1110 definition of Finished product certificate identifies two types: Children's Product Certificates (CPCs) and General Certificates of Conformity (GCCs). This is a distinct consumer-product use of certificate terminology.
Official CPSC General Certificate of Conformity guidance describes written certification by domestic manufacturers and importers of certain general-use, non-children’s products subject to applicable CPSC-enforced safety rules, bans, standards or regulations, except as otherwise stated in a specific standard. It describes certification based on testing or a reasonable testing program and states that the GCC and supporting information must be in English. These statements concern the qualified product category, not every manufacturing CoC.
Operational practice and remaining scope
For device purchasing, consider supplier requirements, evidence traceability and documented acceptance as operational practices; check current Part 820/QMSR for applicable requirements. Recommended receiving controls should identify who evaluates certificate evidence and who makes the acceptance decision, without treating a document title as the decision itself. For food, chemicals and non-U.S. purchasing, determine the applicable product and jurisdictional requirements rather than transferring the drug, supplement or CPSC treatment.
05Supplier qualification defines how certificate evidence is used
As a supplier-quality practice, define supplier qualification scope by supplier, manufacturing site, material or service, and applicable specification—not by supplier name alone. Record which combinations are approved and what evidence supports that approval. A supplier’s suitability for one material or site should not silently extend to another. Make the scope visible to purchasing and receiving staff.
Use a practical evidence plan to describe who issues the CoC, how its provenance is established, which supporting records are available, and what verification activities are appropriate to its intended use. Include unresolved discrepancies, their effect on reliance on the certificate, and the person responsible for reviewing supplier changes. Identify who can obtain supporting records when a declaration needs clarification.
- Supplier suitability: Is this supplier, within the approved scope, suitable for the proposed purchase?
- Certificate coverage: Does this certificate identify and cover the goods actually delivered?
- Receipt acceptance: Does this delivery meet its defined acceptance conditions, including any outstanding checks?
Keep these questions separate in review records. Apply the declaration-versus-disposition boundary covered above: supplier approval does not answer every receipt-level question.
Document review triggers through change control, such as a manufacturing-site change, specification change, inconsistent supporting results or unexplained certificate corrections. Use supplier risk management to justify review depth and verification choices rather than adopting a universal interval, sample size or threshold. Assess applicable regulatory verification obligations separately.
In this framework, purchasing expectations establish the requested evidence; qualification evaluates its intended use; receipt review assesses the particular delivery. Assign an owner to each stage so that an accepted purchasing document is not mistaken for a completed receiving decision.
06Receiving workflow: connect the certificate to the delivered lot
Treat certificate review as part of inbound receiving, not a separate filing task. The following sequence is recommended practice; the role allocation is illustrative and should follow the site's documented responsibilities.
- Receiving personnel identify the delivery, supplier lot, carton identifiers, quantities and initial material status, then link the certificate to the receipt.
- Receiving and purchasing match the certificate's declared scope against the order, delivery documents and physical labels. Purchasing obtains supplier clarification where those records disagree.
- Technical reviewers assess whether the evidence covers the delivered material and assign inspection or testing under the applicable receiving plan. Record results against the receipt rather than only against the supplier's name.
- Resolve discrepancies and route the complete record to the authorised quality decision-maker for disposition. Receiving personnel then implement the approved status and storage instructions.
Worked case: certificate scope falls short
Assume one delivery contains 24 cartons, each holding 500 containers. The certificate explicitly covers only 20 cartons at the same pack quantity.
- 24 × 500 = 12,000 containers received.
- 20 × 500 = 10,000 containers within the stated certificate scope.
- 12,000 − 10,000 = 2,000 containers require scope clarification.
This receiving discrepancy establishes a coverage gap, not a product defect or a basis for acceptance. Identify the affected cartons and maintain their controlled status while purchasing seeks clarification. If carton identifiers cannot distinguish the covered 20 from the remaining four, keep all potentially affected cartons controlled until coverage is established.
Close the case with a receipt-specific record, linked to the goods receipt note, that connects the supplier's clarification, affected carton identifiers, any assigned checks and results, and the authorised decision. Record who decided, when, and which quantities the decision covers. Acceptance of this receipt does not decide the disposition of every later receipt from the same supplier lot.
Identify receipt → Match documents → Perform assigned checks → Resolve discrepancies → Authorise disposition → Update receipt status
- Identify receiptRecord delivered items, quantities and supplier lots.
- Link CertificateAssociate the issuer’s document with its stated scope.
- Match RequirementsCompare item identifiers, specifications and revisions.
- Review evidenceComplete assigned inspections, tests and document checks.
- Resolve exceptionsRecord discrepancies, responses and supporting assessments.
- Authorise DispositionThe designated person records the receiving decision.
- Preserve linksRetain the reviewed version and related evidence.
07Distributor and subcontractor certificates: preserve the evidence chain
As a purchasing practice, distinguish the seller, distributor, original manufacturer, processing subcontractor and certificate issuer wherever those roles affect interpretation. One organisation may fill several roles; record which role supports each statement rather than treating the seller’s signature as the manufacturer’s evidence.
Link the upstream certificate to any downstream declaration, the relevant supplier lot and the received item. Where a distributor assigns a different lot identifier, preserve the mapping. A subcontractor’s declaration should identify the processing it covers. Keep the original issuer visible instead of silently replacing its certificate with a downstream statement.
Worked case: drawing revision mismatch
Assume the purchase order calls for drawing revision D, but the distributor’s certificate references revision C. No equivalence or accepted change is assumed.
- Confirm which revision governed manufacture using upstream records, such as the relevant batch execution history, rather than inferring it from the shipment date.
- Obtain the relevant change or equivalence assessment addressing whether the delivered goods meet revision D.
- Route the mismatch and supporting evidence to the authorised decision-maker; the certificate title alone does not settle acceptance.
Changing C to D on the certificate is not a substitute for resolving which requirements the goods actually meet. Dispute handling and correction history belong in the later exception process.
08Electronic CoCs: versions, interfaces and exception recovery
A practical, system-neutral design separates three responsibilities: purchasing identifies the requested certificate evidence; receiving identifies the physical delivery; and the quality record links the reviewed documents to the decision. Use stable references between these records rather than relying on filenames. This is a useful design boundary for MES–QMS integration.
Preserve the original certificate file alongside indexed fields such as issuer, certificate identifier, material and lot. Treat OCR output and imported values as extracted data requiring appropriate review, not replacements for the issuer’s document. Keep discrepancies between extracted fields and the document visible until resolved.
- Duplicate upload: use duplicate detection to flag repeated files or identifiers for review; distinguish a repeat upload from a revised certificate before merging records.
- Certificate before receipt: place it in a visible unmatched-record queue, with an owner responsible for linking it when the delivery is recorded.
- Failed or incomplete transfer: expose the failure status and missing content. Use controlled retries that preserve the transfer reference and check for prior success before creating another record.
For replacements, retain the earlier document, link the replacement and record the reason for the change. Have the responsible reviewer assess whether an existing disposition is affected. Preserve that assessment with the electronic release record, where used.
Keep document completeness checks separate from approval authority: a successful import or completed field check should not itself change material disposition. Route the decision to authorised people.
09Resolve discrepancies without rewriting the original evidence
Treat certificate discrepancies as exceptions with distinct resolution paths, not as a single request to “send a new CoC”. In both worked cases above, separate the unresolved evidence question from the decision about using the material. Recommended routing depends on what needs resolving:
- Missing evidence: route to the supplier-document owner to obtain the missing certificate or supporting record; ask quality personnel to assess the acceptance implications.
- Identification mismatch: involve receiving and the supplier to reconcile the delivered lot, labels and certificate before associating the document with inventory.
- Disputed specification reference: route to the specification owner and quality personnel to establish which revision applies and whether the evidence addresses it.
- Conflicting technical evidence: route to a technical investigation owner to assess results, methods and sampling; a replacement certificate alone does not resolve the conflict.
For practical exception-based review, keep one exception record containing the affected receipt and lot, original document, supplier response, supporting assessment, decision owner and final disposition. Connect any corrected certificate to the original and the reason for correction. Record what changed; do not let a documentary correction silently close a separate material-quality investigation.
The supplement rule is narrower: 21 CFR 111.170 requires identification, holding and control under a quarantine system for appropriate disposition of rejected and unsuitable components, packaging, labels and products received for packaging or labeling as dietary supplements, with those products intended for distribution rather than return to the supplier. Do not equate every missing certificate with rejected material.
Use a documented recovery sequence: resolve the evidence gap, assess its effect, complete assigned verification, then obtain the authorised disposition. Link that decision to the electronic release record where used. Keep supplier follow-up ownership explicit; receiving a corrected file is not itself authorisation to use the lot.
10Common certificate failures and proportionate receiving controls
Treat these patterns as document-review warning signs, not proof of falsification or defective goods. Investigate in proportion to the uncertainty and potential material impact; they are not universal legal rejection criteria.
| Failure pattern | What remains uncertain | Practical control | Closure evidence. |
|---|---|---|---|
| Undated blanket declaration | Which deliveries and period it covers | Ask the issuer to define applicability. | Issuer confirmation linked to the affected deliveries. |
| Untraceable material identifier | Whether the declaration covers the received item | Request a documented identifier cross-reference. | Issuer-supported mapping to the received material and lot. |
| Obsolete specification reference | Whether the applicable acceptance criteria were assessed | Compare revisions and assess changed criteria. | Recorded comparison and evidence addressing relevant differences. |
| Unsigned or otherwise unattributable declaration | Who issued or authorised the statement | Confirm attribution through an established supplier contact; do not assume a missing handwritten signature invalidates it. | Recorded issuer confirmation or attributable replacement. |
| Unexplained corrected certificate | What changed and whether acceptance is affected | Obtain the issuer’s correction reason and assess impact. | Linked versions, explanation and reviewer conclusion. |
| Scope mismatch: conformity to Drawing D-17 treated as proof of chemical purity | Whether purity was assessed at all | Read the actual declaration and obtain evidence for the unrelated requirement. | Separate purity evidence and documented scope assessment. |
Read the declaration’s named requirements and exclusions rather than infer broad coverage from “conforms.” Use a data integrity risk assessment to structure concerns about attribution or unexplained changes. Record the remaining uncertainty, investigation owner and acceptance rationale. For quantity reconciliation, revision disputes and version recovery, use the earlier receiving, discrepancy and electronic-CoC sections.
11Implementation checklist: can a reviewer reconstruct the receiving decision?
Use a single receipt to test whether the records explain the decision. The following is a practical self-review checklist, not a universal auditor demand, and it cannot predict an audit outcome.
- Identify the goods: trace the receipt identifier to the material, delivered lot, quantity, supplier and manufacturing site. Check that similarly named suppliers or sites cannot be confused.
- Locate the evidence reviewed: retrieve the exact certificate version used, its review record and the specification, order or other requirement reference against which it was assessed.
- Retrieve assigned verification: follow links to the required checks and their results. Identify incomplete work explicitly rather than treating an attached certificate as evidence that every check is complete.
- Identify the authorised disposition: locate the decision, date and responsible approver, or confirm that disposition remains pending. Keep approval and material-disposition ownership with authorised people.
Check the supporting arrangement: document expectations in the receiving procedure; assign an owner to each exception; preserve second-tier evidence links through the lot pedigree; and define controlled recovery for failed imports, duplicate messages and unmatched attachments, including reconciliation before closure.
Test a normal receipt and one unresolved exception; the earlier worked cases can serve as optional exercises. Can a reviewer follow the links without relying on an employee’s memory? Can a later certificate replacement be distinguished from the version used for the original decision through the audit trail or controlled version history? Can the unresolved item’s owner and next action be found?
Assign record-retention decisions to the organisation’s applicable requirements and procedures. Implement in sequence: agree the evidence needed, configure or establish the record links, train the relevant roles, and review exceptions for improvements.
Frequently asked questions
Q.Does a CoC need to use the exact wording requested on a purchase order?+
As purchasing practice, distinguish an agreed wording requirement from a request for equivalent information. If the order specifies a declaration verbatim, ask the supplier to provide it or obtain an authorised acceptance of alternative wording. If only content is specified, compare the certificate against that content rather than its layout. Document who accepted any difference. Put recurring certificate expectations in the quality agreement and the review steps in a receiving procedure.
Q.How should receiving handle a CoC that identifies a shipment but not an individual supplier lot?+
Treat this as a traceability question: can the certificate be reliably connected to the material being assessed? As receiving practice, check container labels, packing records and supplier documentation for an explicit shipment-to-lot relationship. Where lot-level coverage matters to acceptance, keep the affected material pending review rather than infer coverage from a shipment number alone. Record a receiving discrepancy and request clarification that preserves the lot pedigree, including separate mappings when the shipment contains multiple lots.
Q.Can one CoC cover deliveries received on different dates?+
As a document-control practice, one certificate can support several receipts when its stated scope clearly covers the goods in each delivery and the purchasing arrangement permits that approach. Link it to each goods receipt note, keeping delivery dates, quantities and identifiers separate. Do not extend coverage merely because the item number is unchanged. Ask for another certificate or clarification when later goods fall outside the original certificate’s identified lots, quantities or other scope boundaries.
Q.What should you do when a CoC cites a drawing revision newer than the purchase order?+
Do not assume that newer means acceptable. As configuration-management practice, compare the ordered revision, the certificate’s revision and the revision actually used to manufacture the goods. Ask the responsible technical reviewer to assess the difference through change control. If the purchase order is outdated, correct it through an authorised amendment; if the certificate is wrong, request a corrected certificate. Keep acceptance pending until the applicable configuration specification and the disposition decision are documented.
Q.Is a scanned signature enough to establish who issued a CoC?+
For authenticity review, a scanned signature is a clue, not independent proof of origin or authority. As a data integrity practice, consider the transmission channel, named issuer, certificate identifier and consistency with established supplier contacts. If authenticity is uncertain, confirm issuance through a previously established contact rather than relying only on contact details printed on the questionable document. Record the confirmation and retain the received version; avoid treating a pasted signature image as equivalent to authenticated issuance.
Q.Can the original CoC be reused when returned goods are received again?+
As returns-handling practice, retain the original CoC as historical evidence of its stated coverage, not as a fresh assessment of returned condition. Connect the return to the original shipment and examine what happened during the intervening chain of custody, including storage, transport, opened packaging or relabeling where relevant. Record the new receipt and route disposition to the authorised reviewer. Request additional evidence when identity, condition or continued applicability of the original certificate cannot be established.
Q.Where should method details and reported results be reviewed when both a CoC and a CoA arrive?+
As review practice, assess analytical methods and reported results in the CoA review, with supporting laboratory records where needed; use the CoC review for its stated conformity declaration. For dietary-supplement component CoAs relied upon under 21 CFR 111.75(a)(2)(ii)(B), the certificate must include method descriptions, test or examination limits, and actual results. Route that assessment through the supplier CoA verification programme, rather than treating the accompanying CoC as a substitute for reviewing analytical content.
Q.Who should resolve a certificate conflict when the distributor and original manufacturer disagree?+
As supplier-management practice, assign resolution to the authorised quality reviewer, with purchasing coordinating communications and technical specialists assessing the disputed specification or result. Seek a documented explanation from both parties and establish which organisation generated the underlying information. Do not let receiving choose whichever certificate permits acceptance. Use supplier qualification records to check established responsibilities, then document the accepted evidence, superseded documents and material disposition through the quality assurance process.
Primary sources
Explore this topic
CoC sits inside this topic cluster in our glossary. Every neighbour is one click away.
Master and executed records that prove a batch or device was made to spec.
Want to see how CoC could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
