What is a Certificate of Conformance in Manufacturing

KEY TAKEAWAYS

✓
A CoC is a formal supplier declaration — not an inspection report — stating that parts conform to specified requirements.

✓
CoCs must reference a specific revision level, lot number, and the standard or drawing they conform to.

✓
AS9100 and ISO 9001 environments have stricter CoC traceability requirements than commercial manufacturing.

✓
Always verify a CoC against actual inspection data — a CoC alone is not proof of conformance without supporting records.

✓
ITAR-controlled parts require additional export control statements on CoCs; omitting them creates legal exposure.

A Certificate of Conformance (CoC) — sometimes called a Certificate of Compliance — is a formal written declaration issued by a manufacturer or supplier asserting that a product, lot, or shipment meets all applicable requirements. Those requirements may include customer drawings, industry standards (such as AMS, ASTM, or MIL-SPEC), regulatory requirements, or purchase order terms. It is a first-party document: the supplier is attesting to conformance, not a third-party inspector.

This distinction matters. A CoC is not a test report, not a CMM printout, and not an inspection certificate from a laboratory. It is a declaration — and like any declaration, its value depends entirely on the rigor of the quality system behind it. A CoC issued by an AS9100-certified facility carries significantly more weight than one issued by an uncertified shop with no documented inspection process.

In regulated industries such as aerospace, defense, and medical devices, a CoC is typically a mandatory deliverable — not optional documentation. Procurement teams often cannot accept or pay for a shipment without one. Understanding what a valid CoC looks like, and what red flags suggest a deficient one, is a core competency for any engineer managing a supply chain.

IMPORTANT: A CoC is a supplier’s declaration, not independent verification. Always require supporting objective evidence — inspection records, test reports, or material certifications — for safety-critical applications.

Not all CoCs are created equal. A document that simply says ‘parts conform’ with a signature is legally weak and practically useless in a traceability audit. A properly constructed CoC should contain specific, verifiable information that allows anyone in the supply chain to link that document to a specific lot of parts and a specific set of requirements.

At minimum, a valid CoC should include:

• Supplier name, address, and contact information
• Customer name and purchase order number
• Part number and revision level as specified on the drawing or PO
• Quantity shipped and unit of measure
• Lot or batch number for full traceability
• Applicable specification, standard, or drawing reference (with revision)
• Statement of conformance — explicitly stating the parts meet the cited requirements
• Authorized signature, printed name, and title of the responsible individual
• Date of issue

For aerospace and defense work, additional fields are often required: cage code, National Stock Number (NSN) if applicable, country of origin, and any applicable AS9100 or NADCAP certifications. If the parts are ITAR-controlled, the CoC must also include the relevant USML category and an export control statement. Omitting any required field is grounds for rejection at receiving inspection.

RULE OF THUMB: If a CoC doesn’t reference a specific drawing revision and lot number, it cannot be traced back to a discrete production event — and it provides essentially zero audit value.

These three document types are frequently confused — sometimes even by experienced buyers. Each serves a distinct purpose, and confusing them can create serious gaps in your quality documentation package.

A Certificate of Conformance is a declaration by the manufacturer that the finished product meets all specified requirements. It covers the part as a whole — dimensions, finish, material, process — based on the supplier’s internal inspection program. A Material Certification (also called a Material Test Report or MTR) is issued by a raw material supplier and documents the chemical composition and mechanical properties of a specific heat or lot of material. It proves the incoming material conforms to specification — not the finished part. A Test Report (or Inspection Report) documents actual measured values from specific tests — dimensional inspection, tensile testing, hardness, pressure testing, etc. It shows what was measured, not just a declaration of pass or fail.

In a complete documentation package for an aerospace or defense program, you typically need all three: a material cert tracing back to the raw stock, inspection reports showing measured dimensions and test results, and a CoC tying the package together as a formal supplier declaration. A CoC alone — without supporting objective evidence — is insufficient for first-article qualification or safety-critical production parts. Procurement teams should explicitly call out all required documentation types in the purchase order.

In commercial manufacturing, CoCs are often optional or issued only on request. In regulated industries, they are mandatory — and the specific trigger conditions are usually spelled out in the customer’s quality requirements or the applicable standard.

You will almost certainly need a CoC when:

• Supplying to an aerospace or defense prime contractor operating under AS9100 Rev D or DCSA requirements
• Producing parts to a military specification (MIL-SPEC, MIL-STD, or MIL-PRF)
• Shipping ITAR-controlled hardware — the CoC must include export control language
• Delivering to a medical device manufacturer subject to FDA 21 CFR Part 820 or ISO 13485
• Fulfilling a purchase order that explicitly requires a CoC as a deliverable
• Providing raw material, hardware, or fasteners that go into a regulated assembly

Even in non-regulated commercial supply chains, issuing a CoC is a best practice. It creates a documented record of what was supplied, under what requirements, and who signed off — which provides critical protection in the event of a warranty claim or failure investigation. If a customer returns parts six months later claiming non-conformance, a properly documented CoC with supporting inspection records is your primary defense.

When working with a managed sourcing partner like Nimble Manufacturing, CoC documentation requirements are communicated to the certified partner network at the time of order — so the right documents ship with every lot, not as an afterthought.

Both ISO 9001 and AS9100 address CoCs within their broader supplier control and product/service conformity requirements. AS9100 Rev D — the aerospace quality management standard — places particularly stringent obligations on organizations to ensure that externally provided products conform to requirements and are accompanied by appropriate documentation.

Under AS9100 Rev D, organizations must communicate to external providers the documentation requirements for supplied products, including CoCs. Clause 8.4 (Control of Externally Provided Processes, Products, and Services) requires that the type and extent of controls applied to suppliers be commensurate with the risk and criticality of the supplied item. For flight-critical parts, this typically means 100% inspection, first-article qualification, and mandatory CoC with every shipment. For commercial-off-the-shelf (COTS) hardware, requirements may be lighter — but a CoC is still often required.

ISO 9001:2015 is less prescriptive than AS9100 but still requires organizations to retain documented information confirming that externally provided products meet requirements. In practice, this means CoCs from suppliers must be reviewed, controlled, and retained as quality records — not simply filed and forgotten. Your QMS must define the retention period (typically 10 years minimum for aerospace, longer for some defense programs). Nimble’s certified partner network operates within AS9100 and ISO 9001-registered quality systems, meaning documentation practices — including CoC issuance — are audited and maintained as formal quality records.

AS9100 REQUIREMENT: Clause 8.4.3 explicitly requires that externally provided products be accompanied by required documentation — including CoCs where specified. Verify your supplier’s certification scope covers the processes you are sourcing.

Receiving a CoC is not the end of the process — it is the beginning of receiving inspection. A CoC that looks complete on the surface can still be invalid if the information doesn’t match the purchase order, drawing revision, or actual lot received. Developing a systematic review process is essential for any quality-conscious receiving team.

When reviewing an incoming CoC, verify the following against your purchase order and receiving documentation:

• Does the part number and revision on the CoC exactly match the PO and current approved drawing revision?
• Does the quantity on the CoC match the packing list and actual count received?
• Does the lot number on the CoC appear on the physical parts, packaging, or traveler?
• Is the specification reference complete — including revision letter or date?
• Is the CoC signed by an authorized individual (Quality Manager, Quality Engineer, or designated authority)?
• Is the date of issue consistent with the production and ship date?

Beyond format checks, the CoC should be cross-referenced with supporting objective evidence. For dimensional parts, request CMM reports or inspection data. For material-controlled parts, request the MTR and verify heat numbers match. For surface-finished parts, verify process certification (anodize, plating, coating) with process certifications from the applicable shop. If anything doesn’t add up, hold the shipment and request resolution before parts enter your stockroom — once parts are kitted into an assembly, traceability becomes exponentially harder to recover.

After reviewing thousands of supplier documents, quality engineers develop pattern recognition for CoC problems. The most common failures are not outright fraud — they are careless oversights that still render a document non-compliant and can force costly sorting, re-inspection, or quarantine actions.

Red flags to watch for:

• Generic or templated conformance statements that reference no specific standard or drawing (e.g., ‘parts manufactured to customer requirements’ with no citation)
• Missing or incorrect revision level on the part number — a CoC to Rev B when you ordered Rev C parts is a non-conformance
• No lot or batch number — makes full traceability impossible in the event of a field failure
• Unsigned or stamped-only documents — a rubber stamp without an individual’s name and title is not an authorized signature in most quality systems
• Date discrepancies — CoC dated before the manufacturing date, or after the ship date, are logical impossibilities that warrant investigation
• Copy-paste CoCs — same document used across multiple shipments with only the quantity changed, suggesting no actual inspection was performed
• Missing ITAR language on controlled hardware — a legal exposure issue, not just a paperwork gap

If you encounter these issues, do not accept the shipment under the deficient CoC. Document the non-conformance, issue a Supplier Corrective Action Request (SCAR) if your QMS requires it, and require a corrected document before closing the receiving record. Accepting non-conforming documentation sets a precedent that undermines your entire supplier control program.

WARNING: Accepting a CoC with missing lot numbers, incorrect revision levels, or no specification reference — even once — signals to suppliers that your receiving inspection is not rigorous. Non-conformances compound over time.

The most effective CoC programs are built upstream — in the purchase order, not at the receiving dock. If your PO doesn’t specify exactly what documentation is required, you have no contractual basis to reject a shipment for missing paperwork. Make CoC requirements explicit, specific, and non-negotiable from the start.

Best practices include:

• Include CoC requirements in your PO terms and conditions — specify required fields, applicable standards, authorized signatories, and retention format (paper or electronic)
• Define what supporting documents are required alongside the CoC — MTRs, inspection reports, process certifications, and NADCAP certs where applicable
• Establish a CoC review checklist at receiving inspection so every document goes through the same systematic review regardless of supplier familiarity
• Retain CoCs as quality records with defined retention periods tied to the product life and regulatory requirements of your program
• Audit supplier CoC practices periodically — not just the document, but the inspection process behind it
• Request a sample CoC from new suppliers before placing a production order to verify their documentation format meets your requirements before parts are in transit

When sourcing through Nimble Manufacturing’s certified partner network, documentation requirements — including CoCs, material certs, and inspection reports — are part of the standard quality package. The network’s AS9100 and ISO 9001 registrations mean CoC issuance is a controlled, audited process, not an informal afterthought. For programs requiring CMM inspection data alongside the CoC, that capability is included as part of the standard quality package — no separate purchase order line item required.

BEST PRACTICE: Request a sample CoC from every new supplier before the first production order. It tells you immediately whether their quality documentation culture is rigorous or informal — before non-conforming parts are sitting in your stockroom.

READY TO SOURCE?

Table of Contents

Related Services

Get a Quote in 24h

Upload your drawing and get a detailed quote with free DFM review.