CPSC eFiling for Toys: The Import Data Workflow Factories Must Get Right

A repeat toy order can look unchanged in the sales system while the facts behind its certificate have moved on. The assembly site is different. A colourant supplier has changed. The broker still has last season’s certificate reference.

That is the gap a useful CPSC eFiling workflow should close. Not another spreadsheet for its own sake, and not a PDF forwarded five minutes before a filing deadline. The importer needs a defensible connection between the toy being shipped, the evidence supporting its Children’s Product Certificate (CPC), and the certificate data used for the entry.

CPSC states that mandatory eFiling began on July 8, 2026 for most regulated consumer-product imports, with a January 8, 2027 effective date for covered foreign-trade-zone entries. Check the CPSC CPC guidance and eFiling document library against your actual entry circumstances. This guide focuses on the ordinary commercial toy-import handoff from China; mail, FTZ and other special entry situations need their own current guidance.

For toy brands and distributors, the practical question is simple: can the factory, importer and broker all identify the same product version before the entry is filed? Here is how to build that handoff without confusing legal certificate requirements with useful internal controls.

Scope note: This is operational guidance, not legal or customs advice. The importer and its qualified compliance advisers must determine product scope, applicable rules, testing and certification obligations. A customs broker should confirm the filing treatment. No workflow described here guarantees clearance.

CPC timing: what eFiling changes, and what it does not

A CPC was never a document to postpone until after importation. The underlying duty to certify a regulated children’s product is separate from the mechanics of transmitting its certificate data. eFiling does not replace required testing, make an incomplete certificate valid, or turn a factory’s test report into the importer’s certificate.

Under 16 CFR 1110.13, a required finished-product certificate must accompany the product or shipment. For the commercial imports covered by its ACE filing provision, the required certificate data must be eFiled at the time the entry is filed, or when entry and entry summary are filed together. That is the regulatory filing point—not a universal “48 hours before shipment” rule.

Booking, loading, sailing and entry filing are different events. A booking may be made while production is still underway; it does not prove that the certification basis is complete. Equally, an internal shipping deadline cannot move a legal filing obligation. Work backwards from the broker’s actual submission timetable and leave enough time to resolve testing or identity gaps before committing goods to a route that depends on them.

For the certificate fundamentals, use our step-by-step CPC guide for toys. The focus here is the operating chain around that certificate: factory facts, compliance review, controlled data and broker instructions.

Start with the product version, not last season’s entry

Consider this illustrative scenario, not a reported enforcement case. A brand reorders a rechargeable toy under the same sales name and SKU family. The factory moves final assembly to a sister site, substitutes the polymer in a battery-compartment insert and changes the screw arrangement. The commercial invoice still looks familiar, so somebody proposes reusing the previous Product Registry reference.

There are now two different questions. Does the certificate still contain accurate manufacturing information? And does the testing basis still support the product as changed? Correcting the factory address answers only the first. A broker’s successful syntax check answers neither.

The importer should stop automatic reuse, obtain the factory’s change record and ask the compliance owner and laboratory to assess the affected requirements. 16 CFR 1107.23 addresses material changes that could affect compliance and the testing and new CPC required for such changes. Not every administrative correction means a complete retest. Nor can a commercial team decide that a changed component is harmless simply because the toy still performs its intended function.

If the discrepancy is discovered before filing, the team can resolve the evidence and issue controlled instructions. If discovered after filing, it should promptly involve the importer’s compliance advisers and broker to determine the appropriate correction and shipment response. This example does not predict an automatic rejection, detention or release. It shows why an apparently routine reorder deserves a change check.

Awen’s recommendation is to keep a version record that connects the sellable model to its materials, accessories, production site and approved evidence. The record should make changes visible without forcing the broker to interpret a factory’s engineering history.

Name the accountable importer before assigning the work

For imported finished products, 16 CFR 1110.7 within Part 1110 generally makes the importer, as defined in that part, the finished-product certifier. Do not assume that a trading company, overseas factory, brand owner and importer of record are interchangeable legal entities.

The definition matters particularly where an authorised customs broker is the importer of record. Part 1110 allows that broker to identify the owner, purchaser or consignee that authorised entry as the party responsible for the certificate requirements through the filed data. Confirm the actual arrangement rather than relying on the shorthand “our broker handles compliance.”

For day-to-day work, assign responsibilities in plain language:

The certifier approves the certificate and its basis. It owns the decision that the data and evidence describe the goods. Under 16 CFR 1110.15, using another party to enter data or certify on its behalf does not remove its legal responsibility for validity, accuracy, completeness and availability.

The factory supplies the production facts. Ask for the actual manufacturing location, manufacture dates, controlled specifications and changes since the previous order. A sales office address is not a substitute for the required manufacturing information.

The laboratory supports the testing review. Its reports and relevant CPSC acceptance scope help the compliance owner establish what was tested. The lab does not automatically own the commercial model master or know about a later factory substitution.

The broker controls the filing handoff. Agree who maps the approved product data to entry lines, who returns validation messages and who raises discrepancies. That is a transmission role, not permission to guess missing product facts.

The records contact keeps the evidence retrievable. Name a person or qualifying staffed position, not an unattended inbox. Give that contact access to the approved certificate and underlying records before the next shipment creates an urgent request.

This role split is a recommended operating arrangement. It is not a contract allocating every party’s legal liability.

CPSC eFiling for toys: separate required certificate data from working controls

One combined spreadsheet can be useful, but only if its headings distinguish three things: certificate content required by the rule, technical filing fields required for the selected route, and supplementary controls chosen by the business.

The certificate content required by the rule

Use 16 CFR 1110.11 as the governing checklist, rather than treating an older sample CPC as a complete specification. The current rule requires the following content, summarised here for workflow planning.

Product identity. Include at least one permitted unique identifier, such as a model number, SKU, GTIN or UPC, plus a description sufficient to match the finished product to the certificate. Lot, style and colour identifiers may assist identification; the rule does not make every possible identifier mandatory.

Applicable rules. Identify each applicable CPSC-enforced rule, ban, standard or regulation separately. Do not use “complies with all U.S. standards” as a substitute for the required citations.

The certifier. Provide the certifier’s name, street address, city, state or province, country or administrative region, email address and telephone number.

The records contact. Provide the required individual or qualifying position identification and contact details, including address, email and telephone. The rule permits a position title if it is always staffed and responsive to CPSC requests.

Manufacture date and place. Provide at least the month and year, together with the manufacturer name, physical address and required contact details. For a manufacturing run over a series of days, the rule specifies the initial manufacture date, at least by month and year. This is not an invitation to copy an old production date into a new order.

Testing date and place. Provide the most recent date and the required details of each testing party on whose testing the certificate depends. Where a permitted statutory or regulatory testing exclusion is claimed, identify that exclusion as required by the rule instead of inventing test details. A testing exclusion is not automatically an exemption from certification or from listing the applicable rule.

The certifier’s attestation. Follow the attestation requirements for the certificate format and filing route. An informal “approved” comment in a project chat is not a substitute.

The CPSC business-education page is useful background, but it expressly warns that its guidance may not include the new eFiling requirement. Where a simplified example and the current rule differ, have the compliance owner work from the rule and current filing guidance.

The supplementary controls that make those facts reliable

A BOM revision, colourway matrix, test-report filename, purchase-order number, inspection reference and internal signoff are useful controls. Do not label them all as mandatory CPC fields. Some underlying evidence and records are separately required by testing and recordkeeping rules; “supplementary to certificate content” does not mean “safe to discard.”

For each sellable version, keep a readable connection between the commercial identifier, product marking, package identity, material and accessory configuration, production site, report set and approved certificate. Add the filing reference where used. Someone reviewing an invoice line should be able to find the approved product scope without searching a chain of emails.

For example, “blue toy” is a weak scope description if two blue versions use different coatings. The useful control is the link to the actual approved material specification—not simply another colour column. Our CPSIA paperwork alignment guide explains the broader matching problem.

Choose the filing route, then control the reference

The Full PGA Message Set transmits certificate data with the filing. The Reference route uses identifying information to refer to certificate data held in CPSC’s Product Registry. Both depend on accurate underlying facts. A registry record reduces repeated data entry; it does not remove the need to check the goods against that record.

For a stable repeat product, a controlled reference can make the handoff easier. For a changing range, the priority is reliable revision control, whichever route the team uses. Ask the broker to confirm the complete identifier set and current technical mapping. Do not assume that forwarding one informal “certificate ID” is sufficient for every software implementation.

A Disclaimer Message Set is not a workaround for missing test evidence or an unfinished CPC. Its use must follow the current product-specific and filing guidance. HTS flags help identify filing requirements, but the team still needs to assess the product and applicable certification duties.

Use the CPSC eFiling document library, CBP CPSC eFiling Implementation Guide and ACE CATAIR resources. On October 24, 2026, CBP’s guide landing page listed version 2.5 dated June 22, 2026. The CPSC library also listed newer citation, testing-exclusion and disclaim guidance. Recheck the relevant documents before implementation; a guide version is not proof that every associated code list is unchanged.

Make the China-to-broker handoff a release decision

Start before the shipment becomes urgent. Agree the product scope and evidence responsibilities during order planning. Freeze the final production facts once they are known, and require any later changes to reopen the review. Do not ask the factory to certify an unknown future production date just to fill a spreadsheet.

The importer’s compliance owner should reconcile that factory pack against the approved reports and CPC. For every rule citation, the reviewer should be able to identify the supporting testing or permitted exclusion and the product scope it covers. A report title is not enough. Check the relevant model, component, material and test location, and confirm the laboratory’s acceptance for the required scope where third-party testing is required.

Then give the broker an approved instruction set tied to the current shipment. Request acknowledgement of the route, product-to-entry mapping and any missing information. Keep technical validation separate from substantive compliance review: accepting a data format does not prove that the right toy was tested.

After filing, retain the approved inputs and returned messages with a traceable shipment reference. 16 CFR 1110.17 requires finished-product certificates and specified supporting records to be maintained for at least five years from certificate creation. Have the compliance owner apply the relevant recordkeeping duties; an internal shipment folder alone is not proof of compliance.

Also check the physical identity on the goods. Country-of-origin marking before cartons leave China belongs in the wider release process, even though origin marking and CPSC certification are not the same requirement.

Awen’s recommended 48-hour internal handoff gate

This is a recommended Awen operating buffer, not a CPSC or CBP deadline. Aim to complete the review at least 48 hours before the earlier of your planned shipment-release decision and the broker’s agreed filing-data cutoff. Use a longer buffer where weekends, time zones, laboratory work or the transport plan demand it. The legal filing requirement still applies independently.

The buffer is for final reconciliation, not for discovering that certification testing has never been arranged. If a gap needs new testing, 48 hours may be nowhere near enough. Agree the commercial response early: hold the affected goods, separate an unaffected shipment where appropriate, or revise the plan with the accountable parties. Do not treat a booking cost as a reason to approve unverified data.

Use these five checks as the release conversation, with a named owner and recorded outcome for each:

1. Identity: Can the physical toy, packaging, invoice and broker line be traced to the same approved model and variant? Confirm the manufacturing location and current manufacture date information.

2. Evidence: Does each applicable citation have a documented basis, with the correct testing party, date and scope or permitted testing exclusion? Resolve changed materials, components and designs before reuse.

3. Certificate: Are the certifier, records contact, required content and attestation complete and current? Is the approved certificate available to the people who need it?

4. Filing: Has the broker acknowledged the approved route and mapping? For Reference filings, has the team checked the actual registry data and complete reference information rather than relying on last season’s email?

5. Exceptions and records: Have all differences from the previous shipment been reviewed, unresolved issues assigned and the release decision recorded? Can the team retrieve the approved input and subsequent filing messages?

A factory move, coating substitution, battery-compartment redesign or accessory addition should trigger a scope review. A changed contact or identifier may require a data correction without the same testing consequence. Keep those decisions separate. “Everything changed” creates unnecessary work; “nothing changed” without evidence creates avoidable risk.

Need help getting the factory facts ready before your broker files?

Awen Hollek helps overseas toy brands, inventors and distributors organise the China-side evidence behind a dependable CPSC eFiling workflow: product and variant records, factory identity, material-change information, production facts and a controlled document handoff.

We do not replace the importer’s certification responsibility, its legal advisers, customs broker or CPSC-accepted laboratory. Our role is to make the product and supplier facts clearer and available early enough for those parties to act.

Contact Awen Hollek to discuss your toy programme’s handoff. Start with the product range, target shipment timing and where responsibility currently becomes unclear. The useful outcome is not a thicker folder. It is an importer and broker working from the same approved facts.

Frequently asked questions

When did mandatory CPSC eFiling begin for imported products?

CPSC states that mandatory eFiling began on July 8, 2026 for most regulated consumer-product imports, with a January 8, 2027 effective date for covered foreign-trade-zone entries. Confirm the treatment of the actual product and entry with the current CPSC guidance, your customs broker and qualified compliance advisers.

Does eFiling replace the Children’s Product Certificate or change when it is needed?

No. eFiling does not remove the underlying testing and certification duties. A required certificate must accompany the product or shipment. For imports covered by the ACE filing provision in 16 CFR 1110.13(a)(1), certificate data must be eFiled when entry is filed, or when entry and entry summary are filed together. Special entry situations need their own current guidance.

Is the 48-hour handoff gate a legal requirement?

No. It is Awen Hollek’s recommended internal buffer before the earlier of the planned shipment-release decision and the broker’s agreed filing-data cutoff. It does not replace regulatory deadlines, and more time may be needed for testing, corrections, weekends or transport arrangements.

What is the difference between the Full and Reference PGA Message Sets?

The Full Message Set transmits certificate data with the filing. The Reference route uses identifying information to refer to certificate data held in CPSC’s Product Registry. The importer and broker should confirm the complete identifier set and current technical mapping for their chosen route.

Can the factory or customs broker prepare the eFiling data?

Other parties may help collect or enter data, but the finished-product certifier remains legally responsible for the certificate’s validity, accuracy, completeness and availability. For imported finished products, identify the responsible importer under 16 CFR Part 1110 rather than assuming the factory, brand and importer of record are interchangeable.

Can the same certificate reference be used for a repeat toy shipment?

Do not reuse a reference automatically. Check that the product scope, evidence and certificate data remain appropriate for the goods. Manufacturing changes may require a data update; material changes that could affect compliance require assessment under the applicable testing rules, including 16 CFR 1107.23. The same sales name or SKU is not sufficient proof.

Is an HTS code enough to decide whether a toy needs CPSC certification?

No. HTS flags and disclaimer guidance assist filing, but they do not replace product-specific assessment of applicable rules and certification duties. A disclaimer is not a remedy for missing required testing or an incomplete certificate.