CPSC eFiling Requirements: What International Ecommerce Sellers Shipping to the US Need to Know

Selling a consumer product to a customer in the United States is no longer only a question of choosing a carrier and completing a customs declaration. If the imported product is subject to a rule, ban, standard, or regulation enforced by the US Consumer Product Safety Commission that requires certification, its certificate data must now be submitted electronically as part of the US import process.

The requirement is already in force for most covered imports. It applies to commercial direct-to-consumer orders as well as conventional bulk shipments, and the value of a parcel does not create an exemption. That makes the issue relevant to international brands, marketplace sellers, subscription businesses, and other merchants that may never have considered themselves traditional importers.

The practical challenge is data coordination. Product identifiers, applicable safety rules, manufacturing details, test information, certificate ownership, and customs-entry data may sit with different organizations. The seller, factory, laboratory, customs broker, carrier, and US consignee need to agree on who supplies each field and when it is ready.

This guide explains the rule in operational terms: how to determine whether a product is covered, what must be filed, which party remains responsible, how the two filing methods work, and what a cross-border ecommerce team should check before releasing an order. It is a general business overview, not legal advice; product-specific questions should be reviewed with qualified product-safety and customs professionals.

Before mandatory electronic filing, CPSC generally collected a certificate after a shipment had been selected for examination. The new process gives the agency certificate information earlier so it can assess risk while a product is being imported. CPSC announced that mandatory electronic filing is now in effect for regulated imported consumer products.

For a merchant, this moves compliance data upstream. A certificate cannot remain as a PDF that someone tries to locate after a carrier has collected the parcel. The required fields must be available when the customs entry is filed, or earlier in the special case of international mail. Product and shipment records therefore need to connect before dispatch.

That connection should sit alongside the normal international rating and checkout process. A store using international shipping software still needs accurate origin, destination, package, carrier, service, and customs information. The workflow should also prevent a covered SKU from advancing when the compliance record is missing, expired, linked to the wrong product version, or unavailable to the party transmitting the entry.

The rule does not apply to every item within CPSC's broad jurisdiction. CPSC regulated products are covered only when the imported finished product is subject to a CPSC-administered rule, ban, standard, or regulation that requires a certificate. The Federal Register final rule describes two finished-product certificate types:

This distinction matters because a product can be within CPSC's jurisdiction without having a certificate requirement. CPSC does not currently require a Disclaimer PGA Message Set for a product that is outside its jurisdiction, is not regulated, or is regulated but does not require certification.

The first task is therefore product classification. For every US-bound SKU, determine its intended use, age grading, materials, applicable mandatory rules, testing basis, and certificate type. CPSC provides a regulated product database and a Regulatory Robot through its eFiling resource page, but those resources do not replace product-specific analysis.

Do not use an HTS code as the only compliance test. CPSC provides HTS code flagging guidance, but its current FAQ states that the published list is not all-encompassing. Tariff classification and product-safety coverage answer different questions. The Calcurates guide to HTS codes for international ecommerce explains why tariff classification must still be accurate, while the certificate decision must be tied to the actual product and applicable safety rule.

In a consumer product compliance ecommerce workflow, each SKU should have one of four statuses: certificate required, certificate not required, outside CPSC jurisdiction, or unresolved. An unresolved SKU should not automatically proceed merely because a low parcel value or a familiar tariff code makes the order look routine.

Three related records are often confused.

The first is the finished-product certificate. A CPSC certificate of compliance identifies one product, states each applicable rule, identifies the certifier and recordkeeper, records manufacturing and testing information, and includes the required attestation. A business may hold this information in a structured system or in a human-readable certificate, but the underlying data must be accurate and supported.

The second is the CPSC Product Registry. It is a secure repository where an importer can store and manage certificate data in advance. It does not independently send an entry to US Customs and Border Protection's Automated Commercial Environment, or ACE.

The third is the Partner Government Agency Message Set filed in ACE. It connects the applicable certificate information to a specific customs entry line. Depending on the selected method, the filer sends either the complete certificate fields or identifiers that reference a certificate already stored in the registry.

Uploading a certificate to the registry does not complete the customs filing. The broker or other eligible filer still needs the correct message set at entry, and a technically accepted message does not prove that the underlying certificate or testing is valid.

The general effective date was July 8, 2026. CPSC's current certificate and eFiling guidance confirms that date for imported products in general and for the updated certificate content rules. At the time of publication, the obligation is operational rather than a future planning exercise.

There is one later implementation date in the final rule. Products imported into a US Foreign Trade Zone and later entered for consumption or warehousing become subject to the electronic filing requirement on January 8, 2027. The later date applies to that FTZ scenario; it is not a general extension for ordinary entries or direct-to-consumer parcels.

Domestic manufacturers must follow the updated certificate content and availability rules, but the electronic import filing obligation does not apply to a domestically manufactured product. The relevant question is where the finished product was manufactured and how it enters US commerce.

The final rule organizes the required content around seven groups. In practical data terms, a covered product needs:

The exact technical field structure is controlled by CPSC's current CATAIR, registry guidance, code lists, and upload specifications. Those materials can change independently of a blog article, so implementation teams should use the latest files in the official eFiling Document Library.

Certificate records and their supporting documents also have a retention requirement. The final rule requires finished-product certifiers to maintain certificates and supporting records for at least five years from the certificate creation date. The certificate must be made available to CPSC or CBP within 24 hours of a request.

Both filing methods can satisfy the electronic requirement. The better method depends on catalog size, import frequency, product change rate, and system maturity.

With the full method, all required certificate data is transmitted through ACE for the entry. It can be practical for occasional covered imports, but the filer needs a complete, validated field set for every relevant line. Re-keying long contact and testing records creates avoidable error risk.

With the reference method, the full certificate is stored in the Product Registry in advance. At entry, the filer submits the certificate identifiers - Certifier ID, Product ID, and Version ID - that point to the stored record.

This method can be more efficient for stable products imported repeatedly and supports maintenance through a user interface, CSV upload, or API. The reference works only when the product and version identifiers are correct and the stored record remains current.

A cross-border shipping platform may pass order and customs data to another system, while customs document automation may reduce re-entry of repeated fields. Neither approach should silently choose a certificate version. The business needs an explicit rule for matching the order SKU, manufacturing or test version, and certificate identifiers.

For a covered product manufactured outside the United States, the importer defined by the rule is normally the finished-product certifier. The final rule generally starts with the Importer of Record. If an authorized customs broker is the Importer of Record, the broker may identify the owner, purchaser, or consignee that authorized entry as the party responsible for certification.

The certifier may rely on other parties to conduct permitted testing, maintain records, enter data in the registry, or transmit the message set. Delegation does not transfer the certifier's legal responsibility for the certificate's validity, accuracy, completeness, and availability. Where children's product rules require third-party testing, that testing must be performed by a CPSC-accepted laboratory.

One named business still needs authority to approve the finished-product certificate and control changes, even when a factory, laboratory, consultant, and broker each handle part of the data.

Direct-to-consumer shipments need an explicit responsibility decision. For products imported by mail or entered under a Section 321 duty exemption, the rule identifies the importer for certificate purposes as an eligible owner, purchaser, consignee, or authorized customs broker. CPSC also states that it will not typically treat an end consumer buying or receiving a product for personal use as the responsible importer. Sellers should therefore confirm the responsible certifier and eligible filer with their customs partner instead of assuming that responsibility passes to the customer.

The responsibility matrix should be agreed before the first shipment:

If the importer, seller, and broker use different product numbers, create a controlled mapping. The store SKU, UPC or GTIN, broker item number, certificate Product ID, and certificate Version ID should resolve to the same physical product. This mapping is a core part of international shipping data management.

A workable process begins before checkout and ends with entry feedback. The following sequence connects product data to shipment execution.

This is where shipping compliance software can be useful: not by making the legal determination, but by enforcing status checks, required-field validation, version control, and exception routing. Likewise, customs clearance automation should stop an incomplete covered order rather than simply move it faster toward entry.

For a broader view of how duties, landed cost, documentation, and delivery expectations fit together, see Calcurates' guide to cross-border ecommerce shipping. The safety certificate is one data stream within the larger import workflow, but it has its own regulator, timing, and accountability.

Parcel value does not answer the certificate question. CPSC's current eFiling FAQ states that a product requiring certification must have electronically filed certificate data regardless of shipment value, with no Section 321 exemption for this requirement.

This is especially important for foreign direct-to-consumer sellers. A commercial order sold through a store or marketplace does not become a noncommercial gift because it is sent as a small parcel.

International mail has a specific timing rule. When a covered finished product manufactured outside the United States is imported by mail, the certifier must enter the required certificate fields into the Product Registry before the product arrives in the country. Teams using postal injection or consolidators should verify who performs that step and how the shipment is linked to the stored record.

Import programs and eligibility rules can change. Merchants should confirm the current CBP entry method with their broker or carrier instead of assuming that last year's low-value process is still available. The stable CPSC principle is that shipment value does not remove a certificate obligation that exists for the product.

Most implementation problems are not caused by one missing PDF. They result from mismatched or stale data across systems.

A dependable exception queue should show the order, product, reason for the block, responsible owner, and next action. The team must distinguish a missing certificate decision, incomplete data, invalid reference identifier, broker warning, and product compliance concern.

Before shipping a covered product to the United States, confirm that:

Run a test entry or broker validation before scaling. Include a children's product, a GCC product, a non-certificated item, a direct-to-consumer order, and any mail or FTZ scenario the business actually uses.

CPSC eFiling is now an import-readiness requirement, not a document task that can wait until a shipment is questioned. Before a covered SKU leaves fulfillment, the business should be able to answer four questions: Does this product require a CPC or GCC? Which certificate version covers the item being shipped? Who is the finished-product certifier? And will the broker file the full data set or the three Product Registry identifiers?

The decisive handoff happens before the customs entry is transmitted. Product compliance must give the broker or eligible filer a certificate record that matches the exact SKU and production version. If that match is unresolved, the order should remain on hold - whether it is a bulk import, a direct-to-consumer parcel, or a low-value shipment. Treating that match as a release condition turns CPSC import requirements into a concrete operational control instead of a last-minute document search.

Calcurates' International Shipping feature can calculate and present cross-border shipping options for the order, but it does not create or validate CPSC certificates. The practical setup is to keep shipping calculation and compliance status connected without confusing their roles: Calcurates handles the delivery calculation, while the merchant's compliance process determines whether the US-bound order is ready to be released.