AI-generated from the captured TikTok policy text. Verify against the TikTok source before acting.
CPSC eFiling is an electronic product-certificate filing process used before import for certain products. Creators and seller educators should explain that sellers need the right certificate type, current test reports, and accurate filing data; eFiling changes the submission process, not the underlying compliance obligation.
Key points
Applies to all seller types named in the source: FS, POP, and Local sellers.
CPSC eFiling is a pre-entry electronic declaration for product certificate information during customs clearance.
Children’s products generally use CPC; many non-children’s products subject to CPSC rules generally use GCC.
CPCs and GCCs must be supported by valid, complete, up-to-date test reports.
Children’s product testing must use CPSC-accredited laboratories; GCC testing does not require CPSC accreditation.
Test reports should cover required components and may include lead, phthalates, small parts, button cell batteries, magnets, and lithium ion batteries.
Reference message set is generally for repeat imports; full message set is generally for one-time or lower-repeat imports.
Disclaimer may be used when certificate data is not required for the specific product.
Missing, outdated, or inaccurate filing data can lead to shipment delays, border scrutiny, seizure risk, notices of violation, and operational disruption.
Say / show
Check whether the product is in scope before discussing filing expectations.
Match the product to the right certificate type: CPC or GCC.
Keep certificates and test reports current and ready before shipment.
Use reference filing for repeat products when pre-registered data exists.
Use full filing when submitting complete certificate data at entry.
Confirm seller type before promising filing support.
Verify edge cases before giving final guidance.
Tell users to verify against the TikTok source before acting.
Do not say / show
CPC and GCC are interchangeable.
All shipments are exempt because they are small or low-value.
EFile always means a new certificate is required.
The platform files for every seller type.
Filing support is the same for all seller types.
A certificate name alone is enough; supporting data does not matter.
Use guesses for unclear product scope or certificate type.
Violation risks
Shipment delays
Additional scrutiny at the border
Seizure risk
Notices of violation
Downstream listing and operational disruption
Who it affects
All seller types covered in the source
Full Service (FS) sellers
Partner-owned-Partner-operated (POP) sellers
Local sellers
Cross-border from China to US (CCCU) sellers
Affiliate Cross-border from China to US (ACCU) sellers
Local-to-Local (L2L) sellers
Importers handling products subject to CPSC eFiling
Source notes
The source says scope is broad and includes de minimis shipments.
The source says FS sellers receive filing support, while POP, CCCU, ACCU, and L2L sellers are supported through education because importer-of-record responsibilities differ.
The source says disclaimer filing is for cases where certificate data is not required for the specific product.
Verify details against the TikTok source before taking action, since operational setup can vary.
Confidence: high · Model: gpt-5.4-mini · Prompt: creator-policy-summary-v1
Readable Policy Copy
Captured policy content rendered without TikTok navigation, scripts, tracking markup, or page chrome. Source: article-html.
In this guide, you will learn about:
What CPSC eFiling is?
What CPSC eFiling changes, and what stays the same
Which deadlines matter and which products are broadly in scope
The types of certificates and test reports needed for products that require eFiling
What filing information is generally required and the main filing methods
Risks to sellers and the platform if products are not eFiled
Support available to Full Service, as well as POP and Local sellers
This guide applies to all seller types, including Full Service (FS), Partner-owned-Partner-operated (POP), and Local sellers. The Consumer Product Safety Commission (CPSC) eFiling introduces a pre-entry electronic declaration platform for product certificate information during customs clearance. This means that key compliance data must be filed electronically with the CPSC prior to the import of certain products. The following documents are required when eFiling with the CPSC
Valid, up-to-date Children's Product Certificate (CPC) for products intended for children 12 and younger
Valid, up-to-date General Certificate of Conformity (GCC) for certain general use products (see list below)
Valid, complete and up-to-date test reports, conducted by a CPSC accredited laboratory within the last 365 days and which covers all required components
CPC vs. GCC at a glance
A simple way to explain the difference:
CPC is generally used for children’s products, such as toys and other products made for children, and is tied to children’s product safety requirements
GCC is generally used for non-children’s consumer products that are subject to applicable CPSC rules or standards
For learner-facing education, it is usually enough to say: the product type determines which certificate is needed, and teams should not treat CPC and GCC as interchangeable. Test reports: CPCs and GCCs must be supported by test reports. Children's Products must be tested by third-party laboratories that are accredited by the CPSC, and generally observe testing requirements from ASTM International (a standards organization), such as the ASTM F963 standard. In general, test reports should follow the entire ASTM program, but in particular they should include testing for:
lead
phthalates
small parts
button cell batteries
magnets
lithium ion batteries
among other tests.
Additional information may be found here: Third Party Testing Guidance. GCCs must be based on a "reasonable testing program", the details of which can be found in this website: General Certificate of Conformity (GCC) FAQ. GCC testing may be done in house, or by a third-party, but does not require CPSC accreditation.
What information is generally filed
At a high level, eFiling uses certificate-related product data such as:
finished product identification
the party certifying compliance
the consumer product safety rule or rules the product was certified against
date and place of manufacture
the location and time of the most recent compliance test
contact information for the person maintaining testing records
Some filing paths may also rely on reference identifiers instead of re-entering the full certificate details each time. The exact operational setup can vary, so education content should stay focused on readiness: accurate certificate data, current records, and clear ownership of documentation.
Options for eFiling
Sellers may either file through a reference message set or a full message set. For sellers that are repeatedly importing into the United States, the reference message set is probably the best option. Please refer to the CPSC's Quick Start Guide on eFiling for more details.
1. Reference message set
This is generally used when certificate data has already been registered in advance and the filer can submit reference details instead of the full certificate information each time. It is often the more practical option for repeat imports of the same product. Importers choosing to eFile through the reference message set must register a business account and eFile their products through the CPSC Product Registry.
2. Full message set
This is generally used when the filer submits the full certificate data at the time of entry. It may be more common for 1-time or lower-repeat import situations. For education purposes, the simplest rule is: repeat products often benefit from a reference-based approach, while one-off situations may rely more on full filing.
Disclaimers (Exemptions)
This is generally used when a product is imported under a code associated with CPSC review, but the specific product does not require certificate filing data. In that case, the filer may submit a disclaimer rather than certificate details, but is not required to. (However, this is considered a good practice and can improve sellers' risk scores with CPSC.) For more information, visit the Citations, Testing Exclusions, and Disclaims guide.
Best Practices
To ensure eFiling readiness, sellers should adopt the following repeatable habits:
Check if your product requires eFiling with the CPSC: confirm whether the product is subject to a mandatory CPSC safety requirement before advising on filing expectations.
Match the product to the right certificate: children’s products generally require CPC, while many non-children’s consumer products subject to CPSC rules require GCC.
File early: do not wait until shipment is about to move. Teams should encourage stakeholders to have certificates and filing information ready in advance.
Repeat imports should use reference message set, 1-time imports should use full message set
Check seller type before promising support: education support may apply broadly, but filing support does not.
Use careful language on edge cases: if product scope or certificate type is unclear, confirm before giving final guidance.
The biggest risks are usually not about understanding the rule in theory. They come from incomplete or inaccurate readiness in practice. Common risks include:
missing CPC or GCC documentation
outdated or unsupported certificate records
inaccurate filing data
confusion about whether a product needs CPC or GCC
assuming low-value or de minimis shipments are excluded
assuming education support means filing support
Incomplete test reports
Test reports not performed by CPSC accredited laboratories
If filing data or certificate readiness is missing or inaccurate, likely consequences may include:
shipment delays
additional scrutiny at the border
seizure risk
notices of violation
downstream listing and operational disruption
Common mistakes to prevent
A few mistakes are especially worth calling out in training:
Waiting until the deadline is close: readiness usually takes longer than expected because documentation has to be checked, not just collected.
Treating all seller types the same: support expectations differ.
Focusing only on the certificate name: the supporting data elements matter too.
Overpromising certainty on edge cases: where product scope is unclear, teams should guide stakeholders to confirm applicability instead of guessing.
Frequently Asked Questions (FAQs)
Do I need to get a new certificate because of eFiling?
Not necessarily. eFiling changes the submission process, not the underlying obligation to have the right certificate. If the product already requires a CPC or GCC, the key question is whether the certificate and related data are accurate, current, and ready for filing.
Does eFiling apply only to large commercial imports?
No. The source material says the scope is broad and includes de minimis shipments (Shipments with a full retail value of less than $800), so teams should not assume smaller shipments are exempt.
How do I know whether a product needs a CPC or a GCC?
At a high level, children’s products generally use a CPC, while many non-children’s consumer products subject to applicable CPSC rules use a GCC. If the product category is unclear, confirm before giving guidance.
Will the platform file for every seller type?
No. FS sellers receive filing support, while POP, Cross-border from China to US (CCCU), Affiliate Cross-border from China to US (ACCU), and Local-to-Local (L2L) sellers are supported through education because importer-of-record responsibilities differ.
Which filing method should I expect to use?
It depends on the situation. Disclaimer filing is used when certificate data is not required for the specific product, reference filing is commonly used for repeat products with pre-registered data, and full filing is used when the complete certificate data is submitted at entry.