CPSC eFiling Requirements for Importers

CPSC eFiling has applied to most imported, certificate-required CPSC-regulated finished products since July 8, 2026, including Section 321 de minimis shipments of any value. If you sell regulated consumer products into the United States, the customs entry needs CPSC certificate data, either transmitted in full through ACE or referenced from a certificate in CPSC’s Product Registry.

Rules as of October 25, 2026.

The practical change is significant. A test report stored by your supplier is no longer enough by itself. Before a regulated product clears customs, the importer needs a valid finished-product certificate, product-to-certificate matching, and a way for the broker, carrier, or filing system to send the required data at entry.

What are the CPSC eFiling requirements?#

CPSC eFiling requirements are import-entry requirements for certificate data covering finished consumer products subject to a CPSC-enforced rule, ban, standard, or regulation. They apply when certificate-required products are imported for consumption or warehousing, and they connect product compliance records to customs clearance.

The legal basis is CPSC’s revised certificates rule in 16 CFR part 1110. The final rule became effective for most imported certificate-required finished products on July 8, 2026. It does not create a new safety standard. It changes the certificate content, availability, and electronic filing requirements for standards that already apply.

The trigger is the product, not the sales channel. A children’s product sold through Shopify, Amazon, a social-commerce listing, wholesale replenishment order, or direct-to-consumer parcel can be in scope when the product requires certification. The same is true when a U.S. customer orders from a foreign seller.

A finished product is the item in the condition in which it is sold to, or used by, a consumer. Components are different. A zipper supplier can provide testing evidence for a zipper, but the seller or importer of the finished jacket is responsible for the certificate covering the jacket. CPSC permits voluntary component-part certificates, but says they must not be eFiled in ACE. A finished-product certifier can rely on compliant component testing or certificates when issuing its own certificate. CPSC’s final rule

The finished-product certificate will generally be one of two documents:

• A Children’s Product Certificate, or CPC, for a children’s product subject to applicable children’s product safety rules.

• A General Certificate of Conformity, or GCC, for an applicable non-children’s product.

A CPC must be based on testing by a CPSC-accepted third-party laboratory for applicable children’s product safety rules. A GCC for a general-use product must be based on testing of each product or a reasonable testing program, according to CPSC guidance for general-use products.

CPSC eFiling does not decide whether a product is safe or compliant. It transmits certificate data identifying the product, the requirements being certified, the party making the certification, and the evidence supporting it.

Certification and eFiling are different jobs#

Certification is the legal statement that a product complies with applicable CPSC requirements. eFiling is the electronic delivery of specified certificate information at import. A merchant can have a properly tested product and still have an entry problem if its certificate is incomplete, cannot be matched to the goods, or is not transmitted when required.

This distinction matters because product, sourcing, compliance, fulfillment, and customs teams often own different records. Product teams may hold test reports. Sourcing knows the factory and production run. A broker files entry data. The importer must make sure those pieces form a valid certificate and reach ACE through the correct path.

Domestic products are not eFiled. However, the revised certificate-content requirements also took effect for domestic certifiers on July 8, 2026. A domestic certifier must issue the certificate no later than distribution in commerce and make it available to CPSC within 24 hours when requested. CPSC’s certificates guidance explains the distinction between domestic and imported treatment.

Which imports need CPSC certificate data?#

Imported finished products need CPSC certificate data when they are subject to a CPSC-enforced rule, ban, standard, or regulation requiring certification and are imported for consumption or warehousing. The test is not parcel value, seller size, shipping method, or whether a marketplace handled the sale.

This is a product-scope decision before it is an entry-data decision. The merchant must determine whether the exact item needs a CPC or GCC. That requires facts about intended user, age grading, materials, construction, electrical features, product category, packaging, labels, and use.

A toy intended for children can have different certification requirements from a decorative object that looks similar. Sleepwear can raise different issues from ordinary clothing. Lamps, battery-powered devices, bicycle helmets, furniture, and corded products may have product-specific requirements that do not appear in a generic listing title.

An HS or HTS code helps connect goods to customs processes, but it does not decide CPSC applicability by itself. Classification describes goods for tariff purposes. CPSC applicability depends on the finished product and the safety rules that apply to it. A tariff heading can cover items with different intended uses and regulatory treatment.

Each sellable SKU needs enough structured data to answer two separate questions:

1. What is the imported product for customs classification and entry?

2. What CPSC rules, if any, require certification for that exact finished product?

A description such as “kids item” or “home accessory” cannot answer either question reliably. It is not precise enough for classification, compliance review, certificate matching, or customs entry.

border.bot’s CPSC eFiling checker can help teams check a product against CPSC eFiling categories and identify whether a CPC, GCC, testing exclusion, or disclaimer path may apply. Use that check before entry filing, alongside the underlying product and compliance review.

Products manufactured outside the United States#

For a finished product manufactured outside the United States, the importer must eFile certificate data when the product is subject to a CPSC-enforced requirement requiring certification and is imported for consumption or warehousing. The CPSC FAQ confirms that the July 8, 2026 obligation covers commercial imported finished products requiring a certificate.

The importer is normally the finished-product certifier. Do not treat “importer” as a label that can be casually assigned to a supplier, platform, or broker. The party acting as importer needs to know whether it holds the certifier role and whether it has the evidence and authority to make the certification.

A foreign manufacturer can provide factory details, test reports, production dates, and product identifiers. A broker can file the entry. A compliance provider can prepare Product Registry data. Those arrangements do not automatically remove the importer’s responsibility.

Products withdrawn from a Foreign Trade Zone#

Foreign Trade Zone merchandise has its own date. CPSC-regulated merchandise requiring certification that is withdrawn from an FTZ for consumption or warehousing becomes subject to the revised eFiling requirements on January 8, 2027. CPSC’s certificates update states that date.

Brands using FTZs for staging, postponement, or distribution should track the withdrawal event. Product changes during storage, relabeling, repackaging, factory changes, or later production can affect whether the certificate details remain current.

Commercial sales, gifts, and personal effects#

A commercial transaction does not become noncommercial because it is low value, shipped as a parcel, or addressed to an individual consumer. CPSC says a sale through an online marketplace or other sales platform is commercial and does not qualify for the noncommercial exemption. CPSC’s FAQ is explicit on this point.

The exemption is narrow. A noncommercial shipment from one consumer outside the United States to another consumer in the United States, such as a gift or transfer of personal effects already possessed by the sender, is not subject to eFiling. That is not a workaround for merchant fulfillment. If the parcel is connected to an ecommerce sale, treat it as commercial.

Used products#

A used product manufactured before the effective date of the applicable CPSC rule, ban, or standard does not require a certificate and therefore is not subject to eFiling. A used product manufactured after that applicable effective date remains subject to eFiling when commercially imported. CPSC’s FAQ explains the distinction.

This matters for resale platforms, vintage sellers, liquidation businesses, and returns programs. “Used” does not establish the exemption. The importer needs evidence of when the item was manufactured and when the applicable CPSC requirement became effective.

Does de minimis exempt a shipment from CPSC eFiling?#

De minimis is the value below which an import may qualify for a customs duty exemption under a country’s rules. In the United States, Section 321 is the low-value entry provision commonly used for eligible shipments with an aggregate fair retail value of $800 or less.

CPSC eFiling is not waived because a shipment is eligible for the Section 321 duty exemption. CPSC states that certificate-required products eligible for Section 321 must be eFiled regardless of shipment value. The final rule and eFiling Quick Start Guide both say so.

That is the operational trap for direct-to-consumer merchants. Low-value clearance can reduce or remove customs duty for an eligible shipment. It does not remove product-safety obligations. A small parcel can still contain a regulated children’s product, a product requiring a GCC, or another finished product requiring certification.

For Entry Type 86, commonly used for de minimis cargo entries, CPSC’s final-rule preamble says the importer of a regulated finished product requiring a certificate must file CPSC’s Partner Government Agency, or PGA, Message Set at entry. Low-value customs treatment does not change that certificate obligation.

A worked Section 321 example#

Consider a $321 direct-to-consumer order containing one imported children’s product manufactured outside the United States and shipped from China to a buyer in California. Assume the product qualifies for the Section 321 de minimis duty exemption and requires a Children’s Product Certificate under an applicable CPSC rule.

The $321 order value is below the $800 Section 321 threshold. In this example, the shipment pays $0 customs duty because it qualifies for the stated duty exemption. The certificate obligation remains. The importer needs a CPC for the finished product and must eFile CPSC certificate data with the Entry Type 86 entry through either a Full PGA Message Set or a Reference PGA Message Set.

The certificate is not a tariff charge. CPSC’s cited materials do not state an eFiling fee for this example, so do not add an assumed CPSC filing fee to checkout. The cost is operational: testing, certificate preparation, recordkeeping, data integration, broker instructions, and exception handling.

For duty, tax, and carrier charges beyond the certificate question, calculate the real order rather than infer its landed cost from the safety filing. border.bot’s United States landed cost calculator calculates duties, taxes, and fees from the product, origin, value, and destination.

Why $800 is not a compliance threshold#

The $800 figure is a customs-value threshold for a particular duty treatment. It is not a safety-compliance safe harbor. A $20 toy and a $321 children’s product can raise the same certificate issue if both are within a rule requiring certification.

Checkout and order-routing systems therefore need two decisions. One determines customs treatment and expected landed cost. The other determines whether the product needs a CPSC certificate and eFiling. Do not let a “de minimis eligible” field suppress the CPSC workflow.

What information must a finished-product certificate contain?#

A finished-product certificate must identify one product, state every requirement being certified, identify the certifier and recordkeeper, connect the product to manufacturing and testing information, and include the required attestation. An eFiled certificate must be in English. 16 CFR part 1110 contains the detailed requirements.

The one-product rule matters for ecommerce catalogs. A finished-product certificate cannot broadly state that every item in a seasonal collection complies. Variants may require separate certificates when differences in materials, construction, factory, applicable rule, testing, or product identity mean they are not the same finished product for certification purposes.

Each certificate needs at least one unique product identifier. CPSC recognizes a GTIN, model number, registered number, serial number, SKU, UPC, or alternate identifier. The certificate also needs a description sufficient to match the product to the certificate.

A SKU may identify an item inside your own catalog, but the description gives customs, CPSC, retailers, and internal teams a way to verify what was certified. Choose an identifier that remains consistent across the product information system, compliance records, customs data, and fulfillment platform.

Applicable rules and citations#

Each certificate must separately identify every applicable CPSC-enforced rule, ban, standard, or regulation to which the product is certified. A statement that a product “complies with all U.S. safety laws” is not enough. The certificate must identify the requirements that actually apply.

Maintain an item-level regulatory matrix. For every finished product, record the applicable requirement, certificate type, certification basis, test result or testing exclusion, and current certificate version. Maintain that record as products change, rather than rebuilding it during a customs emergency.

Product changes can affect the evidence required. A change in intended age, material, battery, coating, cord, closure, factory, or construction may require a review of the existing certificate.

Certifier and recordkeeper details#

The certificate must identify the certifier and the person maintaining supporting records. For each party, the required information includes name, address, email address, and telephone number. CPSC’s final rule requires these fields.

The certifier and recordkeeper may be the same organization. In a more complex supply chain, the importer may certify while a third-party compliance provider holds test files. The certificate must identify both roles accurately.

Do not use an unmonitored inbox. Finished-product certifiers must furnish required certificates to each distributor or retailer and make certificates available to CPSC or CBP within 24 hours upon request. The contact information should reach people who can actually retrieve the records.

Manufacturing, testing, and exclusions#

The certificate must provide manufacturing date and place. The date must include at least month and year. For a production run manufactured across several days, the certificate uses the initial manufacture date of that run. CPSC’s certificates rule sets that standard.

The manufacturing place should identify the source of the finished product. For merchants using several factories, a factory change is not just a procurement note. CPSC says a different manufacturing facility requires a new Version ID for a Product Registry certificate.

The certificate must also provide the most recent test date, identify the place of testing, and identify every laboratory or other testing party whose results support it. For children’s products, applicable tests must come from a CPSC-accepted third-party laboratory. For general-use products, a GCC must be supported by tests of each product or a reasonable testing program.

From July 8, 2026, a certifier relying on a statutory or regulatory testing exclusion must identify that exclusion on the certificate instead of providing test date and place information for that requirement. CPSC’s FAQ explains that alternative. A testing exclusion is not a generic option for untested goods. It must be a specific exclusion that applies to the exact finished product.

Attestation#

The revised rule requires the certifier to attest that the product complies with the listed requirements and that the certificate information is true and accurate. The prescribed attestation warns that a knowing and willful materially false, fictitious, or fraudulent statement, representation, or omission is a U.S. federal crime. The final rule includes the required attestation.

Certificate preparation is not mechanical data entry. If a supplier provides vague product names, missing factory details, or unsupported test claims, resolve those gaps before certification. Do not make incomplete evidence appear complete.

How do Full and Reference PGA Message Sets work?#

CPSC allows certificate data to be filed through either a Full PGA Message Set or a Reference PGA Message Set in ACE. The Full method transmits certificate data with the customs entry, while the Reference method points ACE to certificate data already stored in CPSC’s Product Registry.

ACE is the Automated Commercial Environment used for U.S. trade processing. A PGA Message Set is data submitted for a participating government agency, here CPSC, alongside entry information. The two paths create different operating models, but neither one changes who is legally responsible for the certificate.

Full PGA Message Set#

A Full PGA Message Set transmits all required certificate data elements to ACE. The importer or filing party does not need to store the certificate in CPSC’s Product Registry before filing if it uses the Full method.

This route can suit merchants with lower shipment volume, irregular imports, short product runs, rapidly changing catalogs, or broker integrations able to transmit full certificate data per entry. It also keeps the certificate transmission inside the customs-entry workflow.

The tradeoff is repeated data handling. If the same product ships hundreds of times, every relevant entry must contain complete and accurate data. Small differences in a SKU description, facility field, citation, laboratory, or testing date can create mismatches.

Reference PGA Message Set#

A Reference PGA Message Set points to certificate data stored first in CPSC’s Product Registry. The entry filer uses three Certificate Identifiers:

1. Certifier ID.

2. Product ID.

3. Version ID.

CPSC’s eFiling Quick Start Guide describes the identifier structure. CPSC’s FAQ says the registry supports manual data entry, CSV bulk uploads, and API integration.

The reference path can work well for recurring direct-to-consumer shipments, repeat replenishment, or stable catalogs. Instead of re-keying a certificate on every entry, the filer references the matching certificate version.

A Product Registry reference does not make an outdated certificate valid. CPSC says a new Version ID is needed when certificate information changes, including a material change, a different manufacturing facility, or a different testing laboratory.

Choose a path based on data control#

The filing decision is not only manual versus automated. It is a decision about where your business can keep authoritative and current certificate data.

Use a Full PGA Message Set when the broker or customs platform can reliably receive complete fields for each shipment, imports are irregular, or products change frequently. Use a Reference PGA Message Set when you have repeat products, disciplined version control, and a reliable Product Registry maintenance process.

Some merchants will use both. A stable core catalog can use references. New launches, unusual orders, and short runs can use full data while the registry process is completed. In either case, the finished-product certificate must be valid before entry.

Who is responsible when a broker, supplier, or platform files?#

The importer is normally the finished-product certifier for imported finished products, and that certifier remains legally responsible for the certificate’s validity, accuracy, completeness, and availability. Delegating data entry, registry maintenance, or entry filing changes workflow responsibilities, not legal accountability.

Many parties can touch the data. A manufacturer may create technical records. A laboratory issues reports. A compliance provider prepares certificate fields. A broker submits the PGA Message Set. A marketplace collects documents. Those parties can support the process, but the certifier remains responsible for the certificate.

This matters when a merchant uses an importer-of-record service. The commercial agreement should clearly state who is importer, certifier, records custodian, Product Registry administrator, and authorized approver of a new certificate version. If those answers are unclear, the shipment is not ready for a regulated-product workflow.

A customs broker has its own exposure. Under 16 CFR 1110.15, a broker that fails to submit a CPSC PGA Message Set identifying the owner, purchaser, or consignee responsible for certification can be held legally responsible for certificate data. The final rule addresses that responsibility.

Brokers therefore have good reason to request complete instructions. But a broker should not determine product compliance from a commercial invoice alone. The importer should provide the item-level determination and the approved full-data fields or certificate reference.

Build a release-control process#

A workable program assigns responsibility for every regulated SKU. One person or team approves the product for sale. Another determines applicable requirements and the certificate basis. A data owner maintains product, factory, testing, and version records. An entry owner, usually a broker, carrier, customs platform, or internal trade team, files the required data.

The same person can hold more than one role. The problem is an undefined gap, usually between compliance approval and fulfillment. A product team approves a sample, the warehouse creates a SKU, and the broker receives only a generic shipment description. No one sends the approved certificate reference.

Create a U.S. launch gate. A new SKU should not be available for U.S. fulfillment until it has a compliance status, certificate decision, product identifier, and filing path.

What changes for mail shipments and postal ecommerce?#

Mail shipments have a separate CPSC transition because international mail historically could not transmit the CPSC PGA Message Set through ACE. CPSC now says certificates for mail shipments must be eFiled through a Full or Reference PGA Message Set beginning January 20, 2027, tied to CBP’s Entry Type 13 requirement.

That deadline is separate from the January 8, 2027 date for CPSC-regulated merchandise withdrawn from an FTZ. The dates affect different import channels. Do not collapse them into a single January compliance deadline.

For imported goods sent by mail, the original final rule required the finished-product certifier to enter certificate data into CPSC’s Product Registry before the shipment arrived in the United States. That interim approach existed because the mail channel could not transmit the PGA Message Set through ACE.

CPSC’s October 2026 guidance for mail shipments sets out the next phase. CPSC says CBP will require Entry Type 13 for mail shipments upon or before arrival, and CPSC will require certificates to be eFiled through a Full or Reference PGA Message Set beginning January 20, 2027.

Ask your postal consolidator, shipping platform, and customs provider how they will collect and transmit certificate data for Entry Type 13. A postal label, electronic customs form, or plain-language product description does not automatically provide the PGA certificate data.

For the wider entry distinction, read border.bot’s guide to Type 11 versus Type 13 entry. The CPSC analysis remains product-specific: if the mailed finished product requires a certificate, plan for a CPSC filing path.

How should merchants prepare product and entry data?#

Merchants should treat CPSC eFiling as a product-data program, not a last-minute customs-document task. The reliable process joins a structured catalog, compliance evidence, manufacturing records, certificate versioning, and a controlled handoff to the broker, carrier, or customs filing system.

Start with the sellable catalog, including variations and bundles. Every imported finished product needs a stable internal identifier that maps to SKU, description, GTIN or UPC where used, product category, intended user, country of manufacture, factory, production run, and customs classification.

Classification still matters because the HTS code affects entry and may help identify agency review needs. Use descriptions that say what the item is, how it functions, relevant materials, and intended user. border.bot’s HS code classifier can turn a description, URL, or photo into a tariff-classification starting point, but classification should be reviewed separately from CPSC product analysis.

For each product, record whether it requires a CPC, GCC, no certificate because no certification requirement applies, or a specific testing exclusion. Link the applicable CPSC citations, test reports, laboratories, test dates, testing place, production details, and records custodian.

Then create a certificate versioning rule. A certificate is not static simply because the SKU is unchanged. CPSC specifically identifies a material change, different manufacturing facility, and different testing laboratory as changes requiring a new Version ID for Product Registry use.

Finally, give the filing party a controlled feed. The broker, carrier, or entry system needs either the full certificate fields or the three Reference PGA identifiers. It should not receive a folder of unapproved supplier files and be asked to guess which document matches the goods.

A shipment-release checklist#

The following checklist is for a merchant shipping certificate-required consumer products into the United States through courier, freight, marketplace, or postal channels.

Listing, checkout, and returns changes#

Most storefronts do not need to display a CPSC certificate number to shoppers. But the back-office record attached to the listing needs to support compliance. Product information systems should store the SKU-to-certificate relationship, and fulfillment systems should preserve it when goods are bundled, split into parcels, or routed through different warehouses.

Do not add an invented CPSC tax or government fee at checkout. CPSC eFiling is a certificate-data requirement, not a stated duty or tax charge in the cited guidance. Testing and compliance overhead can affect product pricing, but that is a commercial decision.

DDP does not remove the compliance work. It changes who arranges import clearance and pays import charges. The seller still needs to determine whether the product requires a certificate and who is acting as certifier.

Returns and replacement shipments need review too. A merchant’s replacement shipment does not automatically become noncommercial because the customer paid nothing for it. The CPSC noncommercial exception concerns consumer-to-consumer gifts or personal effects already possessed by the sender, not merchant fulfillment.

What happens if certificate data is missing or wrong?#

CPSC says it does not initially intend for ACE to reject an entry solely because the filer omitted a Full or Reference PGA Message Set, and instead initially intends to issue warning messages. That is not a permanent safe harbor, and merchants should not treat a warning as permission to keep shipping without required certificate data.

The agency’s FAQ says CPSC may seek seizure of non-compliant products and will use certificate data to adjust an entry line’s risk score. Certificate data can therefore affect scrutiny even where system behavior does not automatically reject every missing message.

A missing message and an inaccurate message are different failures. A missing message indicates that the filing workflow was not completed. An inaccurate message may mean the certificate cannot be matched to the product, omits applicable rules, contains stale factory or laboratory details, or makes an unsupported certification claim.

The certifier’s attestation raises the stakes. The required language warns that a knowing and willful materially false, fictitious, or fraudulent statement, representation, or omission is a U.S. federal crime. The answer is evidence-first controls, not copying unknown supplier claims into a certificate.

Retention and correction#

Certificates and supporting records must be retained for at least five years from the certificate creation date. The final rule sets the retention period. A finished-product certifier must furnish required certificates to distributors or retailers and make them available to CPSC or CBP within 24 hours upon request.

Store the final certificate, product identifier and description, applicable citations, test reports, manufacturing records, testing-exclusion analysis where used, Product Registry identifiers, version history, and shipment references together or through durable links. Do not rely on an employee inbox or an expiring supplier file-share link.

If a certificate-required product shipped without expected filing data, do not treat it as a broker-only issue. Identify affected products, shipment dates, importers, entry channels, and certificate status. Confirm whether a CPC or GCC was required and whether supporting evidence exists. Correct the product record, establish the right filing path, notify the filer, and seek qualified customs or product-compliance advice where the failure or product scope is uncertain.

How should platforms, developers, and 3PLs build for CPSC eFiling?#

Platforms, developers, and fulfillment providers should treat CPSC eFiling as structured compliance data attached to a sellable product and carried through the order lifecycle. A document-upload feature alone is not enough when entry filing requires product identifiers, certificate fields, and current version control.

A marketplace should collect data during onboarding and listing creation, not only when a parcel is manifested. It should distinguish between a test report, a finished-product certificate, and a seller declaration. It should capture whether the product has a CPC or GCC, what product it covers, which citations are listed, and whether the record matches the SKU shipping to the United States.

A 3PL should hold an SKU-level status that is more precise than “CPSC compliant.” Useful fields include certificate-required status, certificate type, certificate path, effective certificate version, product identifier, and exception status. That makes it possible to block a U.S.-bound order if it lacks an approved filing instruction.

A shipping or customs integration needs a clear decision tree: Is the product entering the United States? Is it a finished product? Is it commercially imported for consumption or warehousing? Does it require a CPSC certificate? If yes, should the system send full data or a Product Registry reference? For mail after January 20, 2027, can the system pass the data through the Entry Type 13 flow?

Record the answer used at shipment. Product data changes over time. A certificate reference valid at shipment may later be superseded by a new version.

For API users, separate tariff classification from the agency-compliance decision. border.bot’s Comply product and Comply API documentation identify agency requirements per item, including CPSC certificate requirements, citations, testing exclusions, and filing-related flags. That result should become part of the product record that feeds customs and fulfillment systems.

Sources#

The sources below are CPSC’s final rule, agency guidance, and supporting materials used for the effective dates, scope rules, certificate fields, filing methods, mail transition, testing standards, and recordkeeping requirements described in this guide. Check CPSC’s current documents before changing an entry or compliance workflow.

• Certificates of Compliance, Final Rule, 16 CFR Part 1110, U.S. Consumer Product Safety Commission, January 8, 2025

• Update: Certificates of Compliance and eFiling, U.S. Consumer Product Safety Commission, accessed October 2026

• eFiling Quick Start Guide, Version 1.1, U.S. Consumer Product Safety Commission, January 2025

• eFiling Frequently Asked Questions, U.S. Consumer Product Safety Commission, accessed October 2026

• CPSC Guidance for Mail Shipments on Electronic Filing of Certificates of Compliance, U.S. Consumer Product Safety Commission, October 2026

• Children’s Product Certificate, U.S. Consumer Product Safety Commission, accessed October 2026

• General Use Products: Certification and Testing, U.S. Consumer Product Safety Commission, accessed October 2026

• eFiling Document Library, U.S. Consumer Product Safety Commission, accessed October 2026

Frequently asked questions about CPSC eFiling#

CPSC eFiling questions usually come down to product scope, low-value shipments, certificate content, and responsibility between sellers and brokers. The answers below address the operational questions merchants, marketplaces, and import teams should resolve before releasing a product for U.S. delivery.

Last updated: October 2026