CyberNative

Do I need to eFile a CPSC certificate?

If you import consumer products into the United States, here is the answer in one screen, with a link to the CPSC or CBP document each part comes from. Nothing here is gated, and you do not have to buy anything to use it. Last checked 8 August 2026, one month after the rule took effect.

The short answer

You need to eFile certificate data if you import a finished consumer product into the United States, that product is subject to a CPSC rule, ban, standard, or regulation, and the import is a commercial transaction. If that describes you, the certificate data has to reach the government electronically before the goods clear — but by one of two different routes. For an ordinary entry, the certifier eFiles the data into CBP's ACE system at the time the entry is filed. For finished products imported by mail, no CPSC PGA Message Set is filed in ACE at entry: 16 CFR 1110.13(a)(1) requires the data to be entered into CPSC's Product Registry before the product arrives in the United States. That is the CPSC certificate rule only — CBP's own entry requirements are separate, and some imports by mail still require a formal entry.

Two dates matter. Most imported regulated consumer products have been covered since 8 July 2026. Products imported into a Foreign Trade Zone and subsequently entered for consumption or warehousing are covered from 8 January 2027.

Three things that surprise people:

  • There is no de minimis exemption. The value of the shipment does not matter. A $30 parcel carrying a regulated product needs the same filing as a container.
  • This is not a new certificate requirement. Certificates of compliance have been required since 2008. What changed in 2026 is that the data now has to reach the government electronically before the goods clear instead of sitting in a folder — for an ordinary entry, filed into CBP's ACE at entry; for a mail import, entered into CPSC's Product Registry before arrival.
  • Domestically manufactured products are not eFiled. CPSC's own guide states that eFiling applies to imported regulated consumer products, and that domestically manufactured products should not be eFiled — while a sentence earlier in the same guide mentions products produced domestically in the effective-date paragraph. If you only manufacture in the US and this is your situation, ask CPSC directly rather than trusting either sentence, including ours.

When it does not apply

These are the cases CPSC has answered in writing. They are narrower than most people hope.

  • Products not subject to any CPSC rule, ban, or standard. No certificate is required, so there is nothing to eFile. Deciding this is the whole game, and it is a question about your product, not about eFiling.
  • Used products manufactured before the rule that covers them took effect. No certificate was required, and eFiling does not create one. Used products manufactured after that date do need a certificate, and eFiling applies — including consumer-to-consumer sales.
  • Genuinely noncommercial shipments — a gift or personal effects sent by a consumer abroad who physically had the product. A sale through an online marketplace is a commercial transaction and is not covered by this.
  • Samples that are never distributed to or used by consumers, imported only for display, soliciting orders, or testing. The condition is the outcome, not the paperwork: you have to be able to demonstrate the samples never reach consumers. CPSC strongly suggests documenting their ultimate disposition and rendering them unsuitable for sale — that is evidence toward the outcome, not a marking rule that exempts you on its own. CPSC can review samples at entry, and the burden is the importer's.

Resold and overstock regulated products are covered. So are products entering by mail or courier — but mail imports take the Product Registry route described below, not a filing at entry.

Will my shipment be turned away if I do not file?

Today, most likely not — and that is a weaker protection than it sounds. We are stating it plainly because pages selling eFiling help usually do not.

CPSC's own FAQ says the agency "does not intend to request that CBP deny entry of products into the U.S. solely based on failure to eFile certificate data," and "does not intend initially to have the ACE system send reject messages for missing PGA data, only warning messages." CBP told software developers the same thing in CSMS #69382435: "CBP will not reject the entry in the above scenarios."

What that does not mean:

  • CPSC still enforces the underlying certificate requirement and still asks CBP to seize non-compliant products. Not filing is not the same as not needing a certificate.
  • CPSC can respond separately on the certificate data itself even when CBP accepts the entry, and says it "may perform enforcement actions on any entry that does not have eFiling data attached when required."
  • CPSC says it intends to use filed certificate data in an entry line's risk score, and that doing so should mean fewer holds and examinations for compliant products. That is a stated intention and an expected effect, not a promise — and CPSC has not said what not filing does to your score.
  • Read CPSC's hedging. Its no-denial and no-reject language is qualified with "does not intend", "at this time", and "initially" — stated policy during a rollout, not a permanent carve-out, and it can change without the rule changing. The rule itself is not provisional: CBP says the program was fully implemented on 8 July 2026.

What you actually have to send

Seven data elements, specified in 16 CFR Part 1110:

  • Product ID — identification of the finished product. One of seven types: GTIN, SKU, UPC, Model Number, Serial Number, Registered Number, or Alternate ID.
  • Citation Codes — each consumer product safety rule the finished product is certified to.
  • Manufacture Date — when the finished product was manufactured.
  • Manufacture Place — name, full address, and contact information of the manufacturing party.
  • Product Test Date — when the finished product was most recently tested for compliance.
  • Testing Laboratory — the party or parties used for testing per 16 CFR Part 1110, with name, full address, and contact information.
  • Point of Contact — the party maintaining records of test results, with name, full address, and contact information.

Two things the "seven elements" summary leaves out. The revised Part 1110 also requires you to identify any testing exclusion you rely on, with a testing exclusion code alongside the certificate. And where component-part testing supports the certificate, that testing has to be recorded on the certificate too, with each lab associated with the rules it tested against. Test URL, Test Report Key, and Test Report ID are optional.

How the data gets sent

For an ordinary entry, the data reaches CBP's ACE system through a Partner Government Agency (PGA) Message Set, filed at entry — in practice, by your customs broker. The two options below are the two forms that filing can take. Mail imports are the exception: under 16 CFR 1110.13(a)(1) their certificate data goes into CPSC's Product Registry before the product arrives in the United States, and no PGA Message Set is filed at entry.

  • Full PGA Message Set. You give your broker all seven elements and they file them with the entry. CPSC suggests this for importers with a limited number of regulated products, or who do not repeatedly import the same product. The Product Registry is not required for this path.
  • Reference PGA Message Set. You enter the certificate once into CPSC's Product Registry, then give your broker three Certificate Identifiers — Certifier ID, Product ID, and Version ID — which point at it. CPSC suggests this if you repeatedly import products covered by the same certificates.

The Product Registry does not talk to ACE. It is a repository; the identifiers are what travel with the entry. A certificate can be entered once and referenced across shipments as long as its details are identical — you issue a new Version ID when the certificate changes, for example after retesting, a material change, or a different factory or lab.

How to do this yourself

This is data work, not a software problem, and you do not need to hire anyone to do it. The honest version of the steps:

  • List what you import and work out which items are subject to a CPSC rule. CPSC's Regulatory Robot and its Small Business Ombudsman team (sbo@cpsc.gov) exist for exactly this question and cost nothing.
  • For each certified product, gather the seven elements. Most of them are already written down — in your supplier's test reports and the certificate of compliance you should already hold.
  • Pick a path. Few products, rarely repeated: Full Message Set, and hand your broker the fields. Same products shipping again and again: Product Registry plus Reference Message Sets.
  • If you use the Registry, create a Business Account, pick a Certifier ID you will not want to change (alphanumeric, up to 23 characters), then enter certificates by hand, by CSV bulk upload, or through the API. The CSV template, its user guide, and the API specification are in CPSC's eFiling Document Library.
  • Tell your broker which path you are on before the goods ship, not while they are sitting at the port.
  • Stuck: eFilingSupport@cpsc.gov is CPSC's eFiling support inbox.

Where we come in, and when you should not pay us

We sell one thing in this area: CPSC eFiling filing prep at a fixed $245. You send supplier documents; we send back one row per document with the certificate data elements, a column naming the file and page each value was read from, and a flag on anything a person should check before it is filed. It is the retyping step, not the filing and not the compliance judgement.

Do not pay us if you import a handful of products, or the same products repeatedly. Enter those certificates in the Product Registry once and reference them on later shipments; CPSC documents that path and does not expect to charge a filing fee for using the Registry, and paying us to do it would be waste.

It may be worth it if you are staring at a stack of supplier PDFs that somebody would otherwise retype by hand, and you want the source page recorded next to every value.

This offer is new. The offer page lists what we have and have not measured, including the runs that went badly. Read it before deciding, and email us with questions rather than ordering blind.

What this page is not

It is not legal advice, and we are not a customs broker or a testing laboratory. It cannot tell you which safety rules apply to your product — that depends on the product. Everything above is our reading of public CPSC and CBP material on 8 August 2026; agencies update guidance, and this page can go stale. Check the sources, and check with CPSC or your broker before you rely on any of it.

This page is published by CyberNative AI LLC. If something on it is wrong, email hello@cybernative.ai — we will correct it here and change the date above.

Sources