United States · CPSC certificate eFiling software and workflows · Reviewed August 25, 2026.
The short version
CPSC eFiling software should solve the part of the workflow that is actually breaking: certificate-data preparation, Product Registry submission, broker handoff, evidence control, or all four. The free CPSC Product Registry already supports individual entry, CSV upload and an API. Commercial software earns its cost only when it reduces repeat work, connects suppliers and laboratories, catches missing data, or produces a cleaner handoff to the customs broker.
Comply PRO+ is the clearest documented direct-filing option for brands that want supplier data collection, certificate generation and Product Registry submission in one system. Texbase is the strongest documented fit for larger programs with multiple laboratories, factories and repeated SKUs. ComplyMyImport is an evidence-led pilot option that separates Product Registry submission from the broker’s ACE filing. eFiling Solutions offers a narrower test-report-to-filing workflow. CertEvidence is not a filing replacement; it is an evidence and change-control layer for teams whose broker already handles the entry.
Pricing is mostly quote-only. CertEvidence is the exception: its reviewed public page lists plans from $750 per month. Do not choose from a feature table alone. Run one real product through the proposed workflow and require the provider to demonstrate the Registry receipt and broker package.
JurisdictionUnited StatesFederal scope
Quick verdict
LOW VOLUME · FREE BASELINE
CPSC Product Registry
Start here when volume is small, certificate data is already organized, and staff can handle individual entry or CSV upload. It is free, but it does not automatically transmit the customs entry to ACE.
DIRECT REGISTRY AUTOMATION
Comply PRO+
Best documented fit for brands that want supplier collection, compliance checks, CPC/GCC generation, direct Product Registry submission and a broker reference package in one workflow.
MULTI-LAB · ENTERPRISE WORKFLOW
Texbase
Best documented fit for larger product programs that already need connected testing, laboratory collaboration, reusable product records and bulk filing through the CPSC API.
EVIDENCE-LED PILOT
ComplyMyImport
Promising fit for importers that need source-linked evidence review, gap resolution, human approval, Registry submission and a clearly separated broker handoff.
NARROW PDF-TO-FILING FLOW
eFiling Solutions
Potential fit when the starting point is a laboratory report and the goal is a reviewed CPC plus a Registry filing and broker delivery. Public product detail and pricing remain limited.
EVIDENCE CONTROL · NOT DIRECT FILING
CertEvidence
Best fit when the broker workflow already works but certificate values, versions and supporting records are scattered. It prepares a Registry workpaper and broker packet rather than replacing the filer.
First choose the filing path
A software comparison is useful only after the filing path is clear. CPSC describes two different connections: third-party software can integrate with the Product Registry API, while software that transmits through CBP’s Automated Commercial Environment follows the CPSC PGA Message Set in CATAIR. Those are not interchangeable claims.
- Product Registry reference path: certificate data is created in the Registry by individual entry, CSV upload or API. The broker later transmits the Certifier ID, Product ID and Version ID in the ACE PGA Reference message.
- Full PGA path: the certificate data is transmitted in the customs entry. CPSC states that an importer filing Full PGA Message Sets does not have to use the Product Registry.
- Evidence-only path: a records system prepares controlled certificate data and supporting evidence, while the importer or broker completes the Registry and ACE steps.
A Product Registry filing is not an ACE filing. CPSC says the Registry is a stand-alone application and does not automatically communicate with ACE. A provider needs to describe the broker handoff or customs integration separately.
Read the CPSC eFiling requirements guide before buying a tool. Then use the Product Registry versus ACE workflow guide to identify the handoff your broker expects.
CPSC eFiling software comparison
| Option | Best documented fit | Registry role | Broker or ACE handoff | Public price | Evidence note |
|---|---|---|---|---|---|
| CPSC Product Registry | Low volume or an internal team that can manage certificate data | Official free system; individual entry, CSV and API | Reference IDs still go to the broker; no automatic ACE transmission | Free | CPSC primary source |
| Comply PRO+ | Brands needing supplier collection, checks, certificates and direct Registry filing | API connection; provider says it files to the Registry with one click | Emails reference data and bulk-filing reports to brokers or direct importers | Configurator or quote; no stable amount on reviewed public page | Detailed official product page; provider claims require demo verification |
| Texbase | Multi-lab, multi-factory and larger SKU portfolios | Direct submission through the CPSC Product Registry API | Not detailed on the reviewed eFiling page; confirm in proposal | Quote only | Detailed official workflow; no public eFiling price |
| ComplyMyImport | Evidence review, laboratory-gap resolution and guided implementation | Submits human-approved certificate data to the Registry | Creates a Reference PGA package; broker remains the ACE filer | Pilot quote after workflow assessment | Clear boundary documentation; new pilot-stage offering |
| eFiling Solutions | A narrow test-report-to-CPC-to-Registry service | Uses the customer’s API credentials and account after review | Can transmit filed-certificate references to a designated broker | Separate agreement or order form | Terms define boundaries; public product documentation is brief |
| CertEvidence | Versioned evidence, provenance and broker-ready records | Produces a workpaper aligned to the CPSC CSV template; it does not claim direct filing | Broker packet with Certifier, Product and Version IDs | $750, $1,750 or $3,000 per month by portfolio size; larger portfolios quoted | Transparent price and boundary documentation; not a filing replacement |
How to read the table: “Official product page” means the provider documents the capability on its own current site. It is not independent proof that the feature works in your configuration. Ask for a live demonstration using a non-sensitive sample product and obtain the promised workflow in the contract.
Provider profiles
FREE GOVERNMENT BASELINE
CPSC Product Registry
The official Product Registry is the control option against which paid software should be measured. CPSC allows individual entry, bulk CSV upload and API integration. That makes it workable for small portfolios and for teams with their own data engineering. Its limits are operational: the team organizes source data, manages versions, resolves validation errors and sends the resulting identifiers to the broker.
Best fit: importers with low filing volume, clean certificate data and staff who can own the process.
DIRECT API · SUPPLIER WORKFLOW
Comply PRO+
Comply PRO FILE+ says it connects to the Product Registry by API, collects supplier and production information, generates digital CPCs or GCCs, checks for missing data and files to the Registry. Its documented broker handoff is an emailed reference-data set or bulk-filing report. The public pricing page sends buyers to a configurator and does not expose a stable plan amount that can be verified without completing that flow.
The breadth is useful, but it also increases implementation scope. Ask the demo team to show how your laboratories, suppliers, certificate versions and broker fit into the system—not a generic sample account.
Best fit: small and midsize brands that need one operational workspace from supplier collection through Registry filing.
MULTI-LAB · SYSTEM OF RECORD
Texbase
Texbase documents a connected workflow for test requests, laboratory results, product records, certificate generation and direct CPSC API submission. It emphasizes multiple laboratories, repeated products and bulk filing. That positions it closer to a compliance operations platform than a single-purpose uploader.
The reviewed page does not publish the eFiling product price or describe the final broker handoff in enough detail to score it. Buyers should request both before treating it as a complete entry workflow.
Best fit: larger brands and retailers with many SKUs, multiple factories or laboratories, and an existing need for structured product-testing data.
EVIDENCE REVIEW · GUIDED PILOT
ComplyMyImport
ComplyMyImport documents source-linked extraction, deterministic rule mapping, human approval, laboratory-scope matching, Product Registry submission and a broker-ready Reference PGA package. It expressly says the broker remains responsible for the CPSC PGA Message Set and ACE transmission. That boundary is more useful than a vague “end-to-end” claim.
The product is offered as a founding-customer pilot, with pricing provided after a workflow assessment. Treat it as a candidate to test, not as a mature default. Ask for security documentation, export rights, support terms and a demonstration of the receipt and broker package.
Best fit: importers that need evidence cleanup and guided implementation before automation can help.
TEST REPORT IN · REGISTRY FILING OUT
eFiling Solutions
eFiling Solutions describes a focused service: upload a test report, review extracted certificate data, file through the customer’s CPSC account and deliver reference data to the designated broker. Its terms clarify that the customer remains responsible for review, accuracy and legal decisions, and that the service is not a system of record or backup.
The narrow workflow may be attractive to a small importer, but the public site provides little detail about integrations, version management and pricing. Require a written order form, data-retention terms and a sample broker output before committing.
Best fit: importers seeking a focused managed workflow rather than a broad compliance platform.
PROVENANCE · CHANGE CONTROL
CertEvidence
CertEvidence takes a different position: the importer and broker keep the certification and filing roles, while the software connects every certificate value to a source, records human approvals, seals versions and produces a Registry workpaper and broker packet. That distinction makes it unsuitable for a buyer who needs one-click Registry submission, but relevant for teams whose expensive problem is unreliable evidence.
Its reviewed public pricing is $750 per month for up to 100 certificate families, $1,750 for 101–400, and $3,000 for 401–1,000. Larger portfolios are quoted. Every tier offers a 14-day trial, and annual prepayment is listed as two months free.
Best fit: importers with a working broker process but weak provenance, version control or records readiness.
How to evaluate a demo
Use the same product and the same expected outputs for every demonstration. A polished dashboard is not evidence that the provider can survive your real certificate data.
- Bring one difficult product: include the current certificate, laboratory report, supplier information and one known inconsistency.
- Show applicability boundaries: require the provider to distinguish extraction from a legal or technical decision.
- Trace every field: ask where each certificate value came from and how corrections create a new version.
- Submit to a safe environment: watch the Registry submission, validation response and acknowledgement flow.
- Inspect the broker package: confirm what your broker receives and whether it matches the broker’s preferred process.
- Test export and exit: request a complete export, retention schedule and answer for what happens after cancellation.
- Price the whole workflow: include onboarding, supplier seats, implementation, API work, support, filing volume and managed services.
When a provider publishes no stable price, XrdaGrid reports “quote only” instead of an unsupported range. The price-verification methodology explains this rule.
Options reviewed but not ranked
eFileIQ says it extracts certificate elements from laboratory reports, generates a CPC or GCC and files to the Product Registry. The reviewed public page is too brief to verify pricing, broker handoff, company terms, records controls or implementation scope. It remains a candidate for a future refresh rather than a ranked recommendation.
Generic customs-entry software, laboratory portals and customs brokers were also excluded unless their current official material documents the exact CPSC workflow being compared. A broker can be essential without being CPSC certificate-management software; a laboratory can supply test evidence without owning the importer’s certificate process.
How we compared the options
Criteria were fixed before provider scoring: official evidence of the Product Registry role, separation from ACE filing, certificate-data preparation, source traceability, version control, supplier and laboratory workflow, broker handoff, implementation support, public pricing and evidence depth.
The CPSC Product Registry was included as the free baseline. Commercial providers were retained only when an official current page documented a real product or service. Features are attributed to the provider; government workflow claims are grounded in current CPSC sources. CPSC does not endorse the providers on this page.
The discovery gate passed because the reviewed market contains a free government workflow, two documented direct-API platforms, two narrower submission services and a materially different evidence-control product. New or thinly documented services receive narrower conclusions than established platforms.
Frequently asked questions
Do I have to buy CPSC eFiling software?
No. The CPSC Product Registry is free and supports individual entry, CSV upload and API integration. Paid software is an operational choice, not a condition for compliance.
Does Product Registry software file the customs entry in ACE?
Not automatically. CPSC describes the Product Registry and ACE as separate systems. Confirm whether the provider only submits certificate data, prepares broker references, or actually supports the ACE PGA message through a documented customs workflow.
Can my customs broker handle CPSC eFiling?
A broker can transmit the CPSC PGA message in ACE, but the importer or certifier remains responsible for accurate certificate data and supporting evidence. Confirm who creates and controls the Registry record before the shipment moves.
Which CPSC eFiling software has public pricing?
Among the commercial products ranked here, CertEvidence publishes numeric subscription pricing. It is an evidence and change-control product, not a direct Registry filing replacement. The reviewed filing platforms and services require a configurator, pilot assessment or quote.
What should I ask a provider to demonstrate?
Use one real product. Require source tracing, validation handling, version control, the Registry acknowledgement, the exact broker output, a full data export and the total contract price.
Does CPSC approve eFiling software providers?
No provider on this page is presented as CPSC-approved or endorsed. CPSC publishes API resources for software developers, while the buyer remains responsible for validating a provider’s current capabilities and contract.
Sources and review date
Last fact-checked: August 25, 2026.
CPSC sources
- CPSC — eFiling program hub
- CPSC — Product Registry
- CPSC — eFiling resources for software developers
- CPSC — eFiling Document Library
- CPSC — eFiling frequently asked questions
Provider sources
XrdaGrid provides general informational content about United States consumer-product certificate workflows. This page is not legal, regulatory, customs or purchasing advice, does not determine which requirements apply to a product, and does not guarantee a filing, entry-release or provider outcome.