Skip to main content
Products:PixelProofEntryProofTariffWatch|Free tools:Meta Pixel DebuggerHTS Code LookupCPSC Penalty CalculatorSchema Markup GeneratorRobots.txt CheckerPrivacy Policy GeneratorCookie Consent Checker|Help|Pricing|About|API docs|SDKs|RoadmapChangelog

Help center · EntryProof

Downloading GCC/CPC certificates

By Andy Gaber · Published August 23, 2026 · Last updated August 23, 2026

Once you've uploaded a valid third-party test report (see uploading test reports) and confirmed the accepted lab, EntryProof generates a signed PDF certificate. This guide walks the download flow, the versioning model, and the two share paths (email attachment, signed URL).

Where the certificate lives

Open the SKU on your dashboard and click the Certificates tab. Every certificate that has been generated for this SKU appears in a version-list: version number, generated-at timestamp, the underlying test-report ID it was built from, and a Download button. The most recent version is the one to send to a marketplace or a customs broker; older versions remain accessible in case you need to prove what a certificate said on a particular date.

Two certificate types, chosen automatically

The certificate type is determined by whether the product is a children's product (defined by CPSIA as any consumer product designed or intended primarily for children 12 or younger, per 15 U.S.C. 2052(a)(2) on congress.gov):

  • Children's Product Certificate (CPC): children's products under CPSIA. Requires third-party testing at a CPSC-accepted lab and disclosure of tested-standards passes.
  • General Certificate of Conformity (GCC): non-children consumer products subject to a CPSC-enforced rule (a cigarette lighter under 16 CFR Part 1210, a rug under 16 CFR Part 1630, etc.). Testing can be first-party (manufacturer's own) for GCCs; third-party is only mandatory for children's products under 16 CFR Part 1107 on ecfr.gov.

EntryProof picks the type from the product category field on the SKU. If you disagree with the auto-pick, override it from the SKU settings.

Required fields on every certificate

Every CPSC certificate must, by 16 CFR Part 1110 on ecfr.gov, include: product identification, each rule the product complies with, the importer or manufacturer's name and full address, contact for records including phone and email, date and place of manufacture, date and place of testing, and the identity of the third-party lab (for CPCs). EntryProof pre-fills all of these from your account settings and the SKU test-report parse. The CPSC certificates of compliance guide on cpsc.gov walks the same field list from the regulator's perspective.

Downloading

Click the Download button next to the certificate version. The file is a PDF, signed with an embedded X.509 signature from EntryProof so the recipient can verify the certificate was not modified after generation. File names follow the pattern EntryProof-{ASIN}-CPC-v{version}-{yyyymmdd}.pdf.

Sharing with a marketplace

Two paths:

  • Email attachment: download the PDF and attach it to the marketplace ticket. Amazon Seller Support and Walmart Marketplace both accept PDF attachments on Product Compliance tickets.
  • Signed URL: click the "Share link" button to generate a time-bounded URL (default 7 days, extendable to 30). The link is public but unguessable and expires. This path is preferred when the marketplace has a URL-input field rather than an attachment slot.

Versioning: what triggers a new certificate

EntryProof re-generates the certificate (bumping the version) any time one of the underlying fields changes: a new test report is uploaded and matches the same standard, the responsible-party contact info changes, the product's manufacturing address changes, or the recognized rule changes. Every previous version stays available.

Related articles

FAQ

How long is a certificate valid? Until any input field changes (test date, rule reference, responsible party). Reissue is automatic when a triggering field changes.

Can I use one certificate for a family of similar SKUs? Only if the SKUs share the same manufacturer, same materials, same tested lot, and each is separately identified on the certificate. In practice, generate one per ASIN unless your legal team confirms otherwise.

What if the marketplace rejects my certificate? Most rejections trace to a missing responsible-party contact or a lab that is not on the CPSC accepted-lab list. Check the SKU's Reports tab for the accepted-lab confirmation before re-submitting.

Still stuck? Email support@digitalempireholdings.com or support@digitalempireholdings.com.

Was this helpful?

Still stuck?

Email support@digitalempireholdings.com.

Digital Empire builds compliance tools for regulated verticals — pharma, consumer products, metals.

Also from Digital Empire

Bundle deal: all 3 for $299/yr (5 founding spots). Founding Trio → | All pricing
PixelProofMeta Pixel monitoring for ShopifyEntryProofCPSC eFiling readiness checkerTariffWatchSection 232 exposure checker

Popular free tools & roundups

Free Meta Pixel DebuggerFree HTS Code Lookup (§232)Free CPSC Penalty CalculatorBest Shopify pixel monitors 2026Best CPSC eFiling tools 2026Best Section 232 tools 2026Help centerAll free toolsAll productsReferral programRoadmapChangelogStatusTrust & SecurityAPI docs