Your customs broker will not accept the certificate

Hosting a certificate at a link and getting its data into the entry are two different duties. 16 CFR 1110.13(b) and (c) allow a certificate to be made available electronically on the conditions set out in 1110.9(c), but 16 CFR 1110.13(a)(1) requires the certificate data elements to be filed into CBP's ACE at the time of entry, and the party who does that is the customs broker. A URL is not something he can transmit; the seven elements, set out one per row, are.

Two duties that are easy to confuse

What the broker actually works from

He files data elements. The workable form is therefore the seven elements of 16 CFR 1110.11(a) listed one per row, each labelled with the paragraph it comes from, rather than a document he has to read and transcribe under time pressure:

1. 16 CFR 1110.11(a)(1)Product identification
2. 16 CFR 1110.11(a)(2)Rules certified to
3. 16 CFR 1110.11(a)(3)Finished product certifier
4. 16 CFR 1110.11(a)(4)Individual maintaining records
5. 16 CFR 1110.11(a)(5)Date and place of manufacture
6. 16 CFR 1110.11(a)(6)Date and place of testing
7. 16 CFR 1110.11(a)(7)Certifier's attestation

A marketplace, a buyer or a broker sets its own document requirements, and those are theirs to state. CertSeven does not restate them, because they are not something this site can verify. What follows is what the federal rule requires of the certificate itself.

What CertSeven does not do

It does not file with CBP, with ACE or with any other agency, and it does no testing. It produces the certificate and the sheet of the same facts, one per row, printed with the certificate and downloadable as CSV. The sheet is not a filing format and carries no PGA or CATAIR field names — those cannot be verified here against a primary source, and inventing them would be worse than leaving them out.

Questions

Why does the broker need more than a link to the certificate?

Because the two duties are different. 16 CFR 1110.13(b) and (c) concern making the certificate available, on the conditions in 1110.9(c). 16 CFR 1110.13(a)(1) requires the certificate data elements to be filed into CBP's ACE at the time of entry. The broker is the party filing the entry, and he files data elements, not a hyperlink.

Does hosting the certificate satisfy the import requirement?

No. Hosting goes to 16 CFR 1110.13(b) and (c) through the conditions in 1110.9(c). It does not discharge 1110.13(a)(1), which is the eFiling duty at entry. Treating a hosted link as the whole obligation is the most expensive misreading of the restructured rule.

Does CertSeven file anything with CBP or ACE?

No. CertSeven does not file with CBP, ACE or any other agency, and it does no testing. It produces the certificate and a sheet setting out the same facts one per row, so the person filing the entry can read each element off in turn. The filing is the broker's act.

Is the broker sheet a filing format?

No. It is the seven elements of 16 CFR 1110.11(a) with the paragraph each one comes from, arranged to be read one at a time. It deliberately carries no PGA or CATAIR field names, because those cannot be verified here against a primary source and inventing them would be worse than omitting them.