A Certificate of Conformance, often shortened to CoC or C of C, is a signed supplier statement that a shipment conforms to specified purchase requirements. It can make receiving inspection and traceability more efficient, but only when it identifies the exact product, requirement, lot, and authorized issuer. A page that says “parts meet print” without a part number, revision, quantity, or traceable signature is not a useful release record.
This CNC certificate of conformance guide explains what a buyer should define in the purchase order, what the supplier should place on the certificate, how a CoC differs from inspection and material records, and how to review the document at receiving. Requirements vary by customer, industry, contract, and jurisdiction. The controlled purchase order and referenced specification take precedence over any generic checklist.
What a Certificate of Conformance Actually Certifies
A CoC is an attestation by the issuing organization. It states that the identified goods or services satisfy the requirements identified on the certificate or in the referenced contract. The statement is meaningful only if the supplier has objective evidence behind it and the signer has authority to release the shipment.
The certificate is not automatically an independent third-party certification. It is not the same as an accredited management-system certificate, a laboratory test report, or a regulatory approval. The issuer, scope, and basis of the declaration should be clear enough that a buyer knows what was certified.
A properly written CoC supports three decisions:
- Does this document belong to the shipment received?
- Which controlled requirements does the declaration cover?
- Who issued and authorized the declaration, and when?
If any answer is ambiguous, receiving should place the record or shipment on hold and obtain clarification rather than guessing.
CoC, Inspection Report, Material Certificate, and FAI Are Different
These documents can appear in the same quality package, but they do different jobs.
| Record | Primary purpose | Typical content | What it does not prove by itself |
|---|---|---|---|
| Certificate of Conformance | Supplier declaration that identified product meets referenced requirements | Shipment identity, requirement references, conformity statement, authorization | Actual measured values for every feature |
| Dimensional inspection report | Records measurement results against drawing characteristics | Balloon numbers, nominal, tolerance, actual values, method, result | Material chemistry or heat treatment unless separately recorded |
| Material test report | Reports material identity and tested properties | Heat/lot, specification, chemistry, mechanical results, producer identity | Finished-part dimensions or workmanship |
| First Article Inspection | Verifies a defined first-production configuration and its requirements | Product accountability, characteristic results, material/process records | Continuing conformity of all later units without a control plan |
| Special-process certificate | Documents an outsourced process performed to a defined requirement | Process specification, class/type, lot, processor, results or declaration | Overall conformity of every part requirement |
| Calibration certificate | Documents metrological status of equipment or standards | Equipment identity, date, results, uncertainty, traceability | Conformity of the product measured with it |
Do not ask a CoC to replace records the contract specifically requires. Conversely, do not demand a complete FAI package when the actual requirement is a simple shipment declaration.
Define the Requirement Before the RFQ
The cleanest certificate is designed at quotation, not reconstructed after machining. State in the RFQ and purchase order whether a CoC is required, which format controls, whether an original or electronic signature is acceptable, and which supporting records must accompany it.
Include the exact flowdown language or reference. “Standard CoC” is risky because supplier templates vary. One supplier may identify only the purchase order; another may include material heat, revision, process sources, and exceptions. If specific fields matter, name them.
Clarify whether one certificate may cover several line items, lots, or partial shipments. If consolidation is allowed, the association between each line and its quantity must remain unambiguous. Define language, retention, delivery channel, file format, and correction process.
Distinguish mandatory and conditional fields
Some data should appear on every certificate. Other fields apply only when invoked by the product or contract. A material heat number is useful when heat traceability is required, but it should not be invented for a commercial plastic without a heat-based traceability system. An export classification, shelf-life date, sterilization record, or country-of-origin statement belongs only where the applicable requirement calls for it.
Use a controlled field matrix to separate universal identification from program-specific flowdowns. That keeps the certificate concise while preventing important omissions.
Minimum Product and Shipment Identification
The certificate should identify the delivered product without relying on a detached packing slip. Common core fields include:
- supplier legal name and address;
- customer name or ship-to identity;
- certificate number or other unique record identifier;
- customer purchase-order number, revision, and line item;
- supplier sales order or work order when useful for traceability;
- customer part number and exact drawing revision;
- part description where it prevents ambiguity;
- delivered quantity and unit of measure;
- shipment, packing-slip, or invoice number;
- manufacturing lot, batch, serial range, or other required trace identifier;
- date of shipment or certificate issue; and
- page number and total pages for a multi-page record.
The part number should match the purchase order and product marking convention. If the supplier uses an internal number, list it as a cross-reference rather than replacing the customer identifier. Avoid truncating revisions or dropping suffixes that distinguish variants.
For a partial shipment, state the quantity covered by that certificate, not the total order quantity. For serialized parts, identify each serial number or a clearly bounded range with an attached list.
Identify the Controlling Revision
Revision mismatch is one of the most consequential CoC defects. The certificate should identify the product definition used for manufacturing and acceptance. That may include drawing revision, model revision or data-set identifier, specification revision, purchase-order revision, and approved change notice.
Do not write “latest revision” unless the contract explicitly uses that convention and both parties can establish what was effective. A fixed revision is more reproducible. When an engineering change becomes effective partway through an order, separate the affected quantities or serial numbers and issue distinct certificates if necessary.
If the purchase order and drawing conflict, the supplier should obtain written disposition before release. The CoC should not silently select one source. Reference the approved deviation, waiver, or clarification and its effectivity.
State the Conformity Claim Precisely
The declaration should be direct and bounded. A useful form is conceptually:
“The products identified on this certificate were manufactured and inspected in accordance with the referenced purchase order, drawing, specifications, and approved deviations, and conform to those requirements except as explicitly stated.”
The exact wording may be customer-mandated. Do not copy this example when a contractual template controls. Avoid claims broader than the organization can support, such as certifying regulatory compliance unrelated to the supplied part.
List every accepted exception. A blanket “conforms” statement must not conceal an approved deviation, use-as-is disposition, substituted material, or changed process. Reference the authorization number, approving organization, affected units, and scope. Attach the decision if required.
Reference Specifications Without Overclaiming
A certificate may cite drawing notes, material specifications, finish specifications, workmanship standards, customer specifications, or quality clauses. References must be accurate and applicable to the delivered configuration.
Record the specification number, revision or issue when controlled, class/type/grade, and any required option. “Anodize per specification” may be incomplete if the drawing also controls type, class, color, seal, coating thickness, masking, or test method.
Do not list a standard merely because the supplier holds a related certification. A machine shop certified to ISO 9001 does not thereby prove that one shipment meets every material or special-process requirement. Management-system certification and product conformity are different claims.
The ISO guidance on documented information for ISO 9001:2015 explains that organizations have flexibility in documentation while still needing objective evidence of effective processes. For a buyer, the practical lesson is to define the evidence the contract needs rather than assuming one certificate format is universal.
Material and Heat-Lot Traceability
When the drawing or purchase order requires material traceability, the CoC should connect the finished parts to the supporting material record. Useful fields may include material specification and revision, alloy or grade, temper or condition, product form, producing mill or distributor, heat/lot number, and material certificate number.
The CoC need not reproduce every chemistry and mechanical result if a separate MTR is supplied, but the cross-reference must be unambiguous. The heat number on the CoC, traveler, material certificate, part marking, and inspection package should agree.
If several material heats were used, identify which quantity or serial numbers came from each. Do not collapse them under one heat. If remnant stock is used, its identity must remain linked to the original certificate under the supplier’s traceability procedure.
Commercial material without heat traceability
Some jobs intentionally permit commercial material and do not require heat-level evidence. The certificate should then state only what the supplier can substantiate. Do not fabricate a heat number or imply full mill traceability. If the buyer later needs that evidence, the requirement may change material cost, stock availability, documentation, and lead time.
Special Processes and Subtier Sources
Heat treatment, anodizing, plating, passivation, coating, welding, nondestructive testing, and other outsourced processes often require their own certificates. The prime supplier’s CoC should identify or cross-reference them when the purchase order requires process traceability.
Review:
- process specification and revision;
- type, class, grade, color, thickness, or condition;
- processor name and approval status where required;
- processor certificate number and date;
- lot or quantity covered;
- test results when invoked; and
- linkage to the finished-part lot.
The prime supplier remains responsible for the contractual release unless the contract assigns responsibility differently. A sub-tier certificate does not excuse the prime from checking that the correct process, revision, and lot were used.
When a customer-approved processor list applies, the CoC should not imply approval solely because a process certificate exists. Verify source approval against the current controlled list.
Inspection and Acceptance References
A CoC usually declares conformity; it need not contain every measurement. Still, it should point to inspection evidence when the contract requires traceability to the result. Possible references include final inspection report, first-article report, control plan, test report, nonconformance disposition, or release traveler.
The underlying evidence should remain retrievable for the agreed retention period. A supplier should be able to show how the released quantity was inspected, which instruments or programs were used where required, and who accepted the results.
For critical or regulated products, the buyer may require actual values rather than pass/fail. State that in the order. Adding the requirement after shipment can require reinspection or may be impossible if the characteristic is no longer accessible.
Authorization, Signature, and Date
The signer should be identifiable and authorized by the supplier’s quality system. Record printed name, role or title, signature or approved electronic authentication, and date. A generic image pasted onto every certificate without access control may not establish who released the shipment.
Electronic records can be appropriate when their authenticity, integrity, approval workflow, and retention are controlled. The buyer should define whether typed names, digital signatures, portal approvals, or certificate IDs are acceptable.
The issue date should make sense relative to manufacture, inspection, and shipment. A certificate issued before final inspection or after delivery without explanation deserves review. Corrections should preserve the original record, identify the revision, reason, approver, and replacement relationship.
Customer and Industry-Specific Requirements
No generic article can replace contractual flowdowns. Aerospace, defense, medical, automotive, nuclear, and government programs may prescribe exact certificate content, retention, language, signatures, electronic formats, or source-approval conditions.
The IAQG page for 9163 Aerospace Series—Certificate of Conformity Requirements describes a harmonized aviation, space, and defense CoC process and notes that it is mandatory when contractually invoked. It also makes clear that customer, statutory, or regulatory requirements prevail when conflicts exist.
US federal procurement provides another context-specific example. FAR 46.504 describes conditions under which a Certificate of Conformance may be used in place of source inspection, while FAR 52.246-15 preserves the Government’s inspection rights and requires written authorization in that setting. This is not a default rule for commercial CNC orders; it illustrates why the contract and authority matter.
Recommended Certificate Field Matrix
| Field | Normally required | Conditional trigger | Review question |
|---|---|---|---|
| Supplier legal identity | Yes | — | Is the issuer the contracted entity? |
| Unique certificate number | Yes | — | Can the record be retrieved and revised? |
| Customer PO and line | Yes | — | Does it match the shipment? |
| Part number and revision | Yes | — | Is the exact configuration identified? |
| Quantity and unit | Yes | — | Does it cover only the delivered quantity? |
| Lot/serial identity | When traceability is required | Drawing, PO, industry clause | Can each part be linked to evidence? |
| Material heat and certificate | When material traceability is required | Material/quality clause | Does it match the MTR and traveler? |
| Special-process certificate | When invoked | Finish, treatment, NDT, welding | Is the process and approved source correct? |
| Inspection/FAI reference | When invoked | Quality plan or first-production clause | Are actual results retrievable? |
| Approved deviations | Whenever applicable | NCR, waiver, concession | Are affected units and approvals clear? |
| Country of origin | When required | Customs, trade, customer clause | Is the basis defined? |
| Shelf life/date code | When applicable | Material or product requirement | Is remaining life acceptable? |
| Conformity statement | Yes | Wording may be mandated | Is the claim specific and bounded? |
| Authorized signatory/date | Yes | Signature method may be mandated | Is release authority controlled? |
Receiving Inspection Workflow
Receiving should verify document identity before reviewing technical detail. A repeatable sequence is:
- Match supplier, purchase order, line item, part number, revision, and delivered quantity.
- Confirm lot, batch, serial, packing-slip, and certificate identifiers.
- Check the declaration and authorized signature/date.
- Compare material and special-process references with the required package.
- Verify specification revisions, type/class/grade, and customer clauses.
- Confirm that deviations are explicitly listed and approved for the affected units.
- Check that attachments are complete, legible, and mutually consistent.
- Record acceptance or place the package on document hold with a specific discrepancy.
A document hold is different from declaring the parts nonconforming. Missing evidence may prevent release even when the product is physically acceptable. Preserve that distinction in the receiving system.
Common Certificate Defects
Part revision is missing
The buyer cannot prove which configuration the declaration covers. Obtain a corrected certificate tied to the delivered units.
Quantity does not match the shipment
The document may cover the whole order rather than the partial delivery. Require a certificate for the actual quantity or an unambiguous schedule of covered shipments.
The statement is generic
“Quality approved” or “manufactured to best practice” does not identify requirements. Require a direct statement tied to the purchase order and controlled specifications.
Material traceability stops at a distributor label
If mill traceability is required, the chain must reach the original material evidence and connect to the finished parts. A relabeled stock tag alone may be insufficient.
Process certificates name the wrong type or class
Anodize, plating, heat treatment, or passivation may have technically different variants. Compare exact drawing callouts and approved changes.
A certificate must not say unconditional conformity while a known deviation exists. Reference the approved disposition and affected quantity.
A copied signature graphic or shared login can undermine the release trail. Ask how authorization and electronic records are controlled.
The corrected version overwrites history
Retain both the superseded and replacement records with a clear relationship. Silent replacement makes audit reconstruction difficult.
Record Retention and Retrieval
Define retention by contract, product risk, regulatory obligation, and business need. State when the period starts and whether it applies to the certificate alone or supporting records. Ensure records remain legible and retrievable after staff, software, or storage changes.
Index certificates by more than one key where practical: part number, revision, purchase order, supplier, certificate number, lot/serial, and shipment date. Restrict changes, back up the repository, and record access or approval events appropriate to risk.
If the supplier plans to dispose of records at the end of the period, the contract may require notice or transfer. Address mergers, site closure, and system migration for long-lived products.
Correcting a Certificate After Shipment
A corrected CoC should not erase the original. The replacement should carry a new revision or amendment identifier, reference the superseded certificate, describe the correction, retain the covered shipment identity, and be approved by an authorized person.
Determine whether the error is documentary or indicates a product/configuration problem. A typographical error in a purchase-order suffix may be resolved by a corrected record. A wrong material heat, revision, or process class requires containment and investigation because the physical product may be affected.
Notify downstream users when a certificate change alters released information. If product has moved to assembly or a customer, document communication and disposition.
Test the Certificate Against a Real Shipment Scenario
Before approving a template, walk one representative order through it. Use the actual number of purchase-order lines, a partial delivery, more than one material heat, and an outside finishing operation if those conditions can occur. The exercise often reveals that a visually clean one-page form cannot associate each lot with its quantity and supporting certificate.
Test how the template handles a split lot. Suppose one drawing revision covers the first quantity, an approved change covers the balance, and both quantities ship in the same container. The certificate must keep those configurations separate. A note in an unrelated email is not a durable substitute for effectivity on the release record.
Also test attachments. File names should connect clearly to the certificate number and line item, and page counts should expose a missing page. If a portal creates a download bundle, confirm that customers can retrieve it after the order closes. If the system displays records dynamically, establish how the released version is preserved when master data later changes.
Finally, ask an employee who did not prepare the order to match the certificate to the parts and underlying evidence. If that reviewer cannot complete the trace without tribal knowledge, improve the identifiers, cross-references, or instructions before using the form for production. This practical challenge is more valuable than adding decorative fields that do not support a release decision.
RFQ and Purchase-Order Checklist
Before placing the order, define:
- whether a CoC is required for every shipment;
- customer template or mandatory wording;
- required identification and traceability fields;
- applicable drawing, model, and specification revisions;
- material and special-process certificates;
- dimensional, FAI, test, or calibration attachments;
- approved-source and sub-tier flowdowns;
- treatment of deviations and concessions;
- signature or electronic-authentication rules;
- language, file format, and delivery channel;
- record-retention and retrieval period; and
- correction, notification, and resubmission process.
Ask the supplier to confirm these items in the quote. Documentation has real engineering and administrative cost; defining it early avoids inconsistent bids and shipment delays.
Build a Certificate That Supports the Product
A useful CoC is specific, traceable, authorized, and proportionate. It identifies the delivered configuration, cites the requirements actually applied, names any approved exceptions, and connects to supporting material, process, and inspection records. It does not make claims beyond the issuer’s evidence.
For a QuickCNCs quotation, provide the controlled model and drawing, purchase-order flowdowns, certificate template if mandated, required supporting records, and traceability level. We can review document expectations with the machining and inspection scope before production. Final certificate content remains governed by the released contract and applicable customer or regulatory requirements.
Connect the certificate scope to the inspection records described on the quality assurance page and the applicable CNC machining materials evidence. Send the required CoC fields and attachments through Request a Quote.