Certificate of Compliance (CoC): what it is and when you actually need one

# Certificate of Compliance (CoC): what it is and when you actually need one

Short answer: A Certificate of Compliance is a document, usually issued by the manufacturer or an accredited lab, stating that a specific product or batch meets identified standards or regulatory requirements. It is evidence, not a licence: its value depends entirely on who issued it, what was tested, and whether the underlying requirements are correctly identified. Marketplaces, customs authorities and B2B buyers ask for CoCs as a quick trust signal before they dig into full technical documentation.

Key facts

• A CoC certifies that a defined product (model, batch or serial range) conforms to named standards or regulations, based on stated evidence.
• It is evidence, not a licence: a CoC that names no standard, cites no test report and covers no defined product scope certifies nothing.
• A test report records what a lab measured; a declaration of conformity is the manufacturer's formal legal statement; a CoC sits between them as a concise attestation.
• Common triggers include marketplace compliance reviews, B2B buyer qualification, customs holds, and tenders requiring a compliance file per SKU.
• A credible CoC names the issuer, the exact product scope, the standards with versions and dates, the test reports relied upon, the issue date, and a signatory.
• In the US, children's products subject to CPSC rules need a Children's Product Certificate based on third-party testing; general-use products need a General Certificate of Conformity.
• Under the [CPSC eFiling rule](/regulations/us-efiling), importers must electronically file certificate data at the time of entry for regulated products.

1. What a CoC actually certifies

A Certificate of Compliance is a written attestation that a defined product conforms to identified requirements. The three load-bearing elements are the product scope (which model, which batch, which serial range), the requirements (which standards or regulations, with versions and dates), and the evidence (which test reports, inspections, or assessments support the claim). Remove any one of them and the document stops being useful: a CoC for "all our products" against "all applicable standards" with no test references is a decoration, not evidence.

Understand what a CoC does not do. It does not replace the underlying test reports or the technical documentation. It does not create compliance where the testing was inadequate or the wrong standard was applied. And it does not transfer legal responsibility: the party placing the product on the market remains responsible for compliance regardless of which certificates it holds. Treat the CoC as the cover page of the evidence file, and build the file first.

2. CoC vs test report vs declaration of conformity

These three documents are constantly confused, and the confusion causes real commercial damage. A test report records what a laboratory measured on a specific sample, under specific conditions, against a specific standard. It says what happened in the lab; it does not say the product is compliant in any general sense.

A declaration of conformity, such as the EU Declaration of Conformity, is the manufacturer's formal legal statement that the product complies with specific legislation. It carries legal weight because the signatory takes legal responsibility for the statement. In the EU system, drawing up the declaration is a defined step in placing a CE-marked product on the market.

A Certificate of Compliance sits between them: a concise attestation, often one page, that references the fuller evidence. Regulators want the declaration and the test reports; buyers, marketplaces and customs brokers often accept a CoC as the summary page that tells them the full file exists and what it contains. When a marketplace asks for "certification", it usually means something in this family, and the fastest resolution is to ask which document, for which standard, covering which SKU, then supply exactly that.

3. When you will be asked for one

Marketplace compliance reviews are the most common trigger. Amazon and other marketplaces gate certain categories, children's products, electronics, cosmetics, personal protective equipment, on documentation, and a listing can be suspended until the documents are supplied. B2B buyers qualifying a new supplier routinely ask for CoCs per SKU as part of vendor onboarding. Customs authorities, when they hold a shipment for a compliance check, want quick evidence of conformity before they dig into the full file. Tenders and retail listings frequently require a compliance file per SKU, with the CoC as its first page.

The pattern is consistent: the CoC is asked for at a gate, and the gate does not wait. Keep CoCs ready before you list, before you ship, and before the buyer asks, because producing one under a 48-hour marketplace deadline from a standing start is how errors happen.

4. What a credible CoC contains

Compliance teams check the same fields every time. A credible CoC contains: the issuer's identity and, where relevant, accreditation (name, address, accreditation body and scope); the exact product identification (model numbers, batch or lot numbers, serial ranges, and the configuration covered); the standards or regulations claimed, with their full designations, version years and dates; the test report numbers and dates it relies upon, with the issuing laboratory identified; the date of issue; the period or production scope the certificate covers; and a named signatory with their role.

Vague CoCs with no standard references, no product identification, and no evidence trail are routinely rejected by compliance teams, and rightly so: they provide no basis for a decision. If you issue CoCs to your customers, include every field above; the ten extra minutes per document save weeks of back-and-forth later.

5. Red flags in CoCs you receive from suppliers

Audit supplier CoCs the way a marketplace compliance team would. Watch for certificates issued by the supplier itself with no independent testing behind them; standards cited without version years (so you cannot tell which edition was applied); product scope described as "all our products" or a brand name with no model or batch identification; expiry or validity dates far in the future for standards that are regularly revised; CoCs that arrive suspiciously fast for complex products; test report numbers that cannot be verified with the issuing lab; and issuing laboratories you cannot find in accreditation databases for the cited scope.

When a red flag appears, go back to the source: ask for the underlying test reports, verify the lab's accreditation for the specific standard and scope, and check that the report's product description matches what you are actually buying. A supplier who cannot produce the underlying evidence does not have a compliance file; they have a template.

6. The US system: CPC, GCC, and eFiling

In the United States, the Consumer Product Safety Act framework makes certificates a legal duty, not just a commercial convenience. Children's products subject to a CPSC rule, ban, standard or regulation require a Children's Product Certificate (CPC), based on testing by a CPSC-accepted third-party laboratory, and the certificate must accompany the product or shipment. General-use (non-children's) products subject to CPSC rules require a General Certificate of Conformity (GCC), which may be based on the manufacturer's own testing or a reasonable testing programme.

Under the CPSC's eFiling final rule (published 8 January 2025, amending 16 CFR Part 1110), importers of consumer products subject to a CPSC rule, ban, standard or regulation must electronically file certificate data at the time of entry through CBP's ACE system, rather than producing certificates only when asked. Filing becomes mandatory for most imports from 8 July 2026, and for goods withdrawn from Foreign Trade Zones from 8 January 2027. Importers can file full data per entry, use disclaimer codes where flagged HTS codes need no certificate, or pre-register certificates in the CPSC Product Registry and reference them per entry. Map your HTS codes to CPSC rules now, and confirm certificate data exists for every regulated SKU before the deadline.

Frequently asked questions

Is a CoC legally required?

It depends on the market and the product. In the EU, the legally required document for CE-marked products is the EU Declaration of Conformity; a CoC is usually a commercial requirement from buyers or marketplaces. In the US, CPCs and GCCs are statutory requirements for products subject to CPSC rules, and eFiling makes the certificate data a condition of smooth import.

Can I issue my own CoC?

Manufacturers routinely issue their own CoCs, and there is nothing inherently wrong with it. Its credibility rests entirely on the underlying test evidence: a self-issued CoC backed by accredited test reports for the stated product scope is useful; a self-issued CoC backed by nothing is not.

How long is a CoC valid?

Until the product, the standards, or the evidence change; there is no universal expiry date. A CoC tied to a specific batch covers that batch. A CoC referencing a standard that has since been revised needs review. Date the certificate, scope it precisely, and re-issue when anything material changes.

What should I do when a marketplace suspends my listing over documentation?

Read the suspension notice carefully to identify exactly which document, standard and SKU is at issue. Supply precisely that, with the full evidence chain behind it: the CoC as the summary page, the test reports it cites, and the declaration where applicable. Do not send a generic company certificate and hope it passes.

How do I verify a supplier's CoC?

Check the issuer's identity and accreditation for the cited scope, confirm the test report numbers with the issuing laboratory, verify the product description matches your purchase, and confirm the standard version cited is current. If any link in the chain fails, treat the CoC as unverified and require fresh evidence.

Does a CoC replace the technical file?

No. The CoC is the cover page; the technical file (test reports, declarations, design records, traceability) is the evidence. Regulators ask for the file. Keep both, and keep them consistent with each other.

Official sources

• EU Blue Guide: conformity assessment and documentation duties
• 16 CFR Part 1110, Certificates of Compliance (govinfo)
• CPSC eFiling final rule, full text (Federal Register)

Last verified

September 2026. Requirements differ by product category and market; this is general process guidance. Children's products and other high-risk categories carry additional certification duties beyond a basic CoC.

Ready? Check your product's requirements.