Importers: the seven certificate data elements, ready to eFile.

The seven certificate data elements you receive

• Product ID — identification of the finished product.
• Citation codes — each consumer product safety rule the product is certified to.
• Manufacture date — date the finished product was manufactured.
• Manufacture place — name, full address, and contact of the manufacturing party.
• Product test date — date the product was most recently tested for compliance.
• Testing laboratory — the party(ies) used for testing per 16 CFR 1110, with name, full address, and contact.
• Point of contact — the party maintaining records of test results, with name, full address, and contact.

What you receive

One row per document, one column per certificate data element. For every value, a source column names the file and page it was read from, and an evidence column carries one of three plain values: cited (we found a value and can point at the page it is printed on), uncited (we found a value but cannot point at a page), or not_found (we found nothing and left the cell blank). Rows that need a human look are flagged with the specific reason, and a reconciliation sheet counts documents in against rows out. Nothing is guessed to make the file look full.

Accepted files

PDFs with an embedded selectable text layer. PDFs without an embedded text layer cannot continue to checkout.

Order

Create an account or sign in to upload documents and continue to checkout. If you already have an order, open your account.

Email hello@cybernative.ai with your supplier documents and the certificate data elements you need. Invoiced by CyberNative AI LLC.

What we have measured, and what we have not

We are a new seller with no customers yet. The extraction we use is the same one we have run on public filings from the US SEC, and the honest parts of that record are listed here. We have not run it on CPSC supplier documents yet — so there is no CPSC-specific number on this page. Here is the reused evidence, unvarnished.

Run one — 40 SEC filings, six fields, the cover page of each. We pointed the extractor at one cover page per document and asked for six cover-page fields. All six fields came back filled on all 40 documents — 40 out of 40, six times over. 239 of those 240 values carry the page they were read from; one does not, and it is marked uncited rather than dropped.

Run two — 100 documents, eight fields, an earlier and simpler setup, and 73 of them came back empty. We read the first three pages of each document as plain text rather than picking a cover page, using a simpler extractor than a job would use today. 73 of the 100 rows came back completely blank. Four rows came back with all six of the cover-page fields. 96 of the 100 rows were flagged for a human, each with a reason. Two of the eight fields came back empty on all 100 documents, and we dropped them from the list before run one. Some of those 73 blanks is a limit of how we ran it — 98 of the 100 filings run longer than three pages — not proof the field was missing from the document. We have not measured how large that part is.

Run three — 25 filings, the same six fields, the same reader, and not one clean row. We took 25 SEC filings and asked for the same six cover-page fields, using the same reader run one used. 59 of the 150 values came back filled, and not one of the 25 rows came through clean — all 25 were flagged for a human. Issuer name came back on 22 of the 25 documents; SEC file number on 3. Three rows did carry all six fields, and even those were flagged. Read the 40 out of 40 above as a number that depends on picking the page first.

We do not publish a headline percentage for how often values come back right. We hand-checked 20 values per field from run one against an outside record, then found the check itself was flawed — it was written while its own answers were visible. We threw the result out rather than quote a flattering half of it. None of these three runs tells you what will happen to your supplier documents, and none of them is a CPSC result. That is why the order path below lets you send documents before you pay.

The regulatory basis

The seven elements come from the requirement to eFile certificate data for imported regulated consumer products. That requirement is described by the US Consumer Product Safety Commission in its eFiling program materials, the mandatory eFiling announcement and the eFiling Quick Start Guide, and by 16 CFR Part 1110. Read those to confirm what applies to your products; this page does not replace that.