CPSC eFiling Compliance: The July 2026 Readiness Playbook

On July 8, 2026, the Consumer Product Safety Commission's mandatory eFiling requirement takes effect for all importers of regulated consumer products. Starting that date, every entry filed through CBP's Automated Commercial Environment (ACE) for CPSC-regulated goods must include a new set of product safety data fields. Importers who are not ready will face cargo holds, increased examination rates, and civil penalties reaching $150,000 per violation.

This is not a paperwork update. It is a fundamental change in how consumer product safety data flows between importers, customs brokers, and federal regulators. CPSC gains real-time visibility into every regulated shipment the moment it is filed. The era of submitting general conformity certificates only when CBP asks for them is over.

For high-volume importers, the operational implications are significant. You need to collect new data fields from manufacturers, reorganize your certificate management systems, update your ACE filing workflows (or your broker's templates), and build a process that scales across hundreds of SKUs and dozens of suppliers.

This guide walks through exactly what is required, who is affected, and how to build a compliant process before July 8. With roughly 15 weeks remaining as of late March 2026, the window is tight but workable, provided you start now.

The importers who will struggle on July 8 are those who assume their broker will handle everything. Some brokers will, but only with data they do not currently collect from you. The data collection problem is yours to solve, and it starts with your factories.

The importers who thrive are those who treat this deadline as an opportunity to build a systematic CPSC compliance infrastructure, one that reduces their examination rates, supports faster customs clearance, and creates an audit-ready document trail that protects them in any CPSC investigation.

CPSC eFiling applies to any importer bringing regulated consumer products into the United States. The scope is broader than most importers realize, and many discover mid-project that product categories they considered routine are fully in scope.

Products Requiring a Children's Product Certificate (CPC)

A CPC is required for any product primarily intended for children under 12. These products must be tested by a CPSC-accepted third-party laboratory before being imported. Categories include:

• Toys and games: Any item marketed for children under 12, including games, puzzles, ride-on toys, and play structures
• Children's apparel and footwear: Garments and footwear for children under 12, tested for drawstring hazards, lead content, and flammability
• Cribs, bassinets, and playpens: All infant and toddler sleep environments
• Car seats and strollers: Child restraint systems and wheeled transport products
• Children's furniture: High chairs, changing tables, bed rails, and bunk beds
• Children's jewelry: Items marketed for children, tested for lead and cadmium content
• Pacifiers and feeding items: Products that contact infants directly

Products Requiring a General Conformity Certificate (GCC)

A GCC is required for general-use consumer products subject to a specific CPSC rule, ban, or standard. GCCs do not always require third-party laboratory testing, but the issuer must have a reasonable basis for the conformity claim. Categories include:

• Household appliances: Products subject to CPSC safety standards including UL listings or specific CPSC rules
• Furniture: Upholstered furniture, mattresses, and structural furniture subject to flammability standards
• Electrical and electronic accessories: Extension cords, power strips, and similar items
• Seasonal and holiday products: Artificial trees, holiday lighting, and decorative products
• Lighters and matches: Subject to child-resistant packaging requirements
• Bedding and textiles: Items subject to flammability standards under the Flammable Fabrics Act

What Is Explicitly Outside Scope

Industrial products, medical devices (regulated by FDA), food and beverages (FDA), and automotive parts (NHTSA) fall outside CPSC eFiling scope. If your product line is purely industrial B2B with no consumer end use, you are likely not affected. Products that are solely regulated by another federal agency are also excluded. When in doubt, consult a licensed customs broker with CPSC experience or customs counsel, as misclassifying an in-scope product as out-of-scope is itself a compliance risk.

How to Calculate Your Exposure Before July 8

Pull your complete list of 10-digit HTS codes imported in the last 12 months. Map each code against CPSC's regulated product category list, available on CPSC's website. Any HTS code that touches a regulated category needs a compliance workflow. Most importers with 50 or more active SKUs will find that 30 to 70 percent of their product lines require eFiling data, depending on their product mix.

Do this mapping now, not in May. The mapping is the foundation of your entire compliance effort. Without it, you cannot scope your supplier outreach, size your certificate library gap, or prioritize your broker conversations.

CPSC eFiling adds seven new required data elements to every ACE entry filing for regulated goods. These go beyond the commercial invoice and entry summary data that CBP already collects. Understanding exactly what is required, and where each field must come from, is the foundation of your compliance plan.

Field 1: CPSC Product Category Code

The specific CPSC product category code that identifies which safety regime governs the product. CPSC publishes the official category list with numeric codes. Your broker needs this mapped to each HTS code in your active product catalog. For products that could fall into more than one category, consult the CPSC category definitions carefully. Incorrect category codes are flagged during ACE processing and can generate an automatic request for correction.

Field 2: Applicable Safety Rule Citation

The specific CPSC regulation, standard, or ban under which conformity is claimed. For example, a children's toy entry might cite 16 CFR Part 1250 (Safety Standard for Toys) and 16 CFR Part 1303 (Lead Paint). Multiple citations are allowed and often required for products subject to several overlapping standards. This is the most commonly incorrect field in early eFiling implementations because importers rely on their broker to know the applicable rules rather than providing them explicitly.

Field 3: Certificate Type

Whether the product requires a CPC (Children's Product Certificate) or GCC (General Conformity Certificate). This field is straightforward once your product mapping is complete, but it must be accurate. Filing a GCC for a product that requires a CPC is a substantive compliance error, not just a data quality issue.

Field 4: Manufacturing Facility Name and Address

The exact legal name and address of the facility where the finished product was manufactured. This must match the manufacturing facility identified on the conformity certificate. If you use multiple factories for the same product, each shipment must identify the specific facility that produced those goods. Factory nicknames or abbreviated names are not acceptable. The field must reflect the legal business name as registered.

Field 5: Manufacturing Date or Date Range

The date or date range when the goods were manufactured. For importers buying from factories running continuous production, this is typically the start and end dates of the production run from which your shipment was drawn. This field links your shipment to a specific production batch, which is critical if CPSC later identifies a product safety issue and needs to trace affected units.

Field 6: Test Date

The date the most recent product safety test was conducted. For CPC products, this must be the date a CPSC-accepted third-party laboratory completed its testing. For GCC products without mandatory third-party testing, this is the date of the most recent conformity evaluation, whether conducted internally or by a lab. The test date must precede the manufacturing date in most cases. A test date that is after the shipment date suggests the goods were shipped before testing was complete, which triggers immediate scrutiny.

Field 7: Test Record Custodian Contact Information

The name, address, phone number, and email address of the party that holds the test records supporting the certificate. This is typically the importer of record for U.S.-based importers. If your supplier maintains the records in China or another country, you may list them as custodian, but you must be able to produce the records within the timeframe CBP or CPSC specifies upon request, typically 24 to 72 hours. Designating an overseas custodian who cannot respond quickly to a U.S. government request is a practical compliance risk even if it is technically permitted.

Data You Have vs. Data You Must Collect

Most importers already have manufacturer name and country of origin from their commercial invoices. What they almost never have in a structured, retrievable format are the specific regulatory citations for each product, the manufacturing date per shipment, and the test date from the actual certificate documents. These fields typically live in PDFs scattered across email inboxes and shared drives. Before July 8, you need a system that stores all seven fields at the SKU level and is updated whenever a new production run or new test certificate is issued.

The most common compliance failure point for CPSC eFiling is not the ACE technical integration. It is the upstream data collection from factories and testing labs. Suppliers in China, Vietnam, India, and other manufacturing countries are not always organized to provide structured, field-level data in the format U.S. customs regulations require.

Building Your Supplier Data Request

Send every affected supplier a formal written request specifying the exact fields required under CPSC eFiling. Do not ask for "the certificate." Ask for the specific data fields you need. A well-structured request asks the supplier to confirm, in writing:

• Exact manufacturing facility name and address: As it appears on the factory's official business registration documents, not an abbreviation or trade name
• Manufacturing date range for each purchase order: The start and end dates of the production run for your specific order
• Testing laboratory name and CPSC accreditation number: Third-party labs must be CPSC-accepted; confirm accreditation status at CPSC's Consumer Product Testing Laboratory (CPTL) database before each new test cycle
• Test date for the most recent report: The date on the test report cover page, not the date the certificate was issued by the importer
• Certificate type (CPC or GCC): Confirm which type applies per product category
• Applicable CPSC safety rule citations: Your supplier's quality manager or the testing lab should provide this; cross-reference against CPSC's product standards database to verify completeness

Supplier Compliance Tier System

Not all suppliers respond at the same speed or quality level. Build a three-tier tracking system:

• Tier 1, Fully Compliant: Supplier provides all required data fields in a structured format within five business days. Test date is current (within the required cycle for their product category). No action required beyond quarterly refresh before each production run.
• Tier 2, Partial Data: Supplier provides some data but is missing fields such as test date or precise facility address. Assign a follow-up owner with a hard deadline. Consider requiring Tier 2 suppliers to copy your compliance team on all future lab report emails so you receive test records directly rather than waiting for them to be forwarded.
• Tier 3, Non-Responsive or Deficient: Supplier does not respond, provides data that fails validation, or cannot confirm current third-party testing for CPC products. Escalate immediately to your sourcing team. A supplier that cannot provide compliant eFiling data by June 1 creates a cargo hold risk on every shipment from that factory starting July 8. You may need to pause new purchase orders until compliance is confirmed.

Integrating Data Collection Into Your PO Workflow

Beyond the initial compliance sprint, build CPSC data collection into your ongoing procurement process. Add these checkpoints to your purchase order workflow:

• At PO issuance: Confirm the current test report validity. For most CPC products, test reports from a CPSC-accepted lab must be current. If the last test was more than 12 months ago or if there have been material changes to the product or its components, a new test is required before shipment.
• At production confirmation: Request the manufacturing date range from the factory. This should be standard in your production confirmation form, not a separate conversation.
• At pre-shipment inspection: Verify the manufacturing date on the packing list matches the data collected. Discrepancies between packing list dates and declared manufacturing dates are a common filing accuracy problem.
• At booking confirmation: Provide all seven CPSC data fields to your customs broker together with the commercial invoice. Do not assume your broker has the data from a prior shipment. For ongoing orders, confirm whether the prior test is still valid or whether a new test cycle has occurred.

Language and Communication Barriers

Many factory contacts in Asia do not speak English as a first language and may not be familiar with U.S. CPSC requirements specifically. Prepare a concise fact sheet, translated into Mandarin, Vietnamese, or the relevant language, that explains what CPSC is, what eFiling requires, and exactly what format you need the data in. Factories that work with multiple U.S. importers will be receiving similar requests from all of them as the deadline approaches. Getting your request in front of them in a clear, easy-to-respond-to format before the June rush gives you faster, more accurate responses.

Certificates of conformity are the documentary foundation of CPSC eFiling compliance. The data fields you transmit to CBP through ACE must match the underlying certificates. A discrepancy between your eFiling data and your certificates is not just a data quality problem. It is evidence of a compliance process gap that CPSC can use to question the substantive validity of your conformity claims.

What a Compliant CPC Must Contain

A Children's Product Certificate must be issued by the importer of record or the domestic manufacturer. It must be based on passing test results from a CPSC-accepted third-party laboratory. Required certificate content includes:

• Product identification (name, model number, or other identifier)
• Citation of each CPSC children's product safety rule applicable to the product
• Identification of the importer of record or domestic manufacturer issuing the certificate
• Contact information for the person maintaining test records (the test record custodian)
• Date and place of manufacture
• Date and place of testing (the lab name, location, and date of testing)
• Identification of the CPSC-accepted third-party laboratory that conducted testing

The test date and manufacturing location on your CPC are the same fields that flow directly into eFiling. If your existing CPCs do not contain these fields in a clear, explicit format, they are not compliant certificates, regardless of whether the underlying product actually passes the safety tests. Audit your current CPC library for format compliance before you attempt to populate eFiling data from them.

What a Compliant GCC Must Contain

A General Conformity Certificate must be issued by the importer of record or domestic manufacturer for any general-use consumer product subject to a CPSC rule, ban, or standard. Unlike CPCs, GCCs do not always require third-party laboratory testing, but the issuer must have a reasonable basis for the conformity claim, whether from their own product testing, supplier testing data, or documented product knowledge. Required GCC content mirrors the CPC requirements except that third-party lab identification is only required when third-party testing was performed.

Building a Structured Certificate Library

High-volume importers typically maintain hundreds of certificates across dozens of suppliers. A shared drive of PDF files will not support the field-level data retrieval that eFiling compliance requires at scale. You need a structured certificate library, whether implemented in a compliance software platform, a purpose-built database, or a well-organized spreadsheet, organized by:

• SKU or product code: Each certificate linked directly to one or more SKUs in your product catalog so that your team can retrieve the relevant certificate at booking time without searching through folders
• Certificate type (CPC or GCC): Separated by type, since the compliance workflows and data fields differ
• Renewal or review date: An alert that fires 60 days before a test cycle renewal is due, or when a material change to the product should trigger a new test. Certificate validity is not formally time-limited under CPSC rules, but best practice and many buyer compliance programs treat certificates older than 12 months for CPC products as requiring review.
• Applicable safety rule citations: Indexed at the SKU level so your broker can pull the correct rule citations for any HTS code at filing time, without needing to read through the PDF certificate itself

Retesting Triggers to Know Before July 8

CPSC requires a new third-party test for CPC products when there is a material change in the product's design, materials, components, or production process. This includes changes to component suppliers, even if the finished product looks identical. If you have changed any component supplier, moved production to a new factory, or modified a product design in the past 12 to 24 months, audit whether the change was material enough to trigger a new test requirement. Certificates that no longer reflect your current production configuration create both eFiling accuracy problems and substantive compliance exposure if CPSC examines the goods and finds the certificate does not match what was manufactured.

CPSC eFiling data is transmitted to CBP through ACE, the same system used for all U.S. import entry filings. Most importers do not file directly with CPSC. The data flows from your customs broker (or your internal entry filing system) to CBP via ACE, and CBP shares the relevant fields with CPSC in real time through the Partner Government Agency (PGA) message set.

How the Data Flow Works

For most importers, the end-to-end workflow is:

1. You provide CPSC-required data fields to your customs broker together with the standard commercial invoice and packing list, typically at the time of cargo booking or vessel load
2. Your broker inputs the data into their ACE-certified filing software (platforms such as Descartes, 3CE Technologies, or comparable ABI-certified systems)
3. The broker transmits the entry via ACE before arrival, typically at vessel load for ocean freight or upon air waybill issuance for air freight
4. CBP processes the entry and shares the CPSC PGA data with CPSC's automated targeting system in real time
5. CPSC's system screens the data against its targeting criteria and flags entries for examination, document review, or hold as appropriate

Questions to Ask Your Customs Broker Now

Your broker should already be aware of the July 8 mandate. If they are not, that is a concern worth addressing directly. Key questions to ask in the next 30 days:

• Has your ACE filing software been updated to support the CPSC eFiling PGA message set, and when was it tested in CBP's ACE Certification Environment?
• What format do you need me to provide the CPSC data in, such as a structured spreadsheet, a data field in your portal, or an attachment to the commercial invoice package?
• How will you flag entries where CPSC data is missing or incomplete before filing? What is your process for a hold-back if required fields are absent?
• What is your process for responding to a CBP or CPSC hold after July 8, and what data do you need from me to resolve a hold quickly?
• Do you have dedicated staff with CPSC product category knowledge, or do you treat CPSC eFiling purely as a data entry function?

What Good Broker Support Looks Like

A broker who is genuinely prepared for CPSC eFiling can show you their updated entry template with the new CPSC fields, confirm their software certification, and explain their escalation process for entries that arrive at port without complete CPSC data. A broker who says "we'll figure it out in June" is telling you that your preparation timeline is at risk. For importers with high shipment volumes of regulated goods, broker readiness is worth verifying in writing, not just in a phone call.

Self-Filing Importers

If you file your own entries through ACE using an in-house customs team, your ACE entry preparation system must be updated to include the CPSC PGA fields. Contact your ACE software vendor for the updated field schema. CBP's ACE Business Office publishes technical specifications for PGA message sets through the CBP.gov portal, and CPSC publishes a separate eFiling implementation guide with field-level specifications and example filings. Build in time to test your system in CBP's ACE Certification Environment before going live on July 8. Untested changes to ACE filing workflows are a common source of first-day errors.

Air Freight Timing Considerations

For air freight shipments, CPSC eFiling data must be included in the entry filing, but the timing window is different from ocean. Air entries are typically filed within hours of arrival rather than days in advance. Ensure your air freight broker has the same CPSC data pipeline in place as your ocean broker. High-velocity air replenishment of consumer goods is a common CPSC examination target, so accuracy on air entries matters as much as on ocean.

With approximately 105 days between late March 2026 and July 8, you have enough time to build a solid compliance process, but not enough to move slowly. The following plan is organized by two-week blocks and assumes you are starting from a baseline where no formal CPSC eFiling workflow exists today.

Weeks 1 to 2: Assessment and Scoping (March 25 to April 7)

• HTS code audit: Pull your last 12 months of entry summaries and extract every unique 10-digit HTS code imported. Map each against CPSC's regulated product category list. Flag every HTS code that falls within a regulated product category. This is your compliance scope.
• Supplier identification: For each flagged HTS code, identify the supplying factory or factories. Build a master list of every factory whose shipments will require eFiling data after July 8.
• Broker conversation: Contact your customs broker and confirm their ACE software update timeline for CPSC eFiling support. Ask for a written confirmation of their go-live date and their preferred data format for CPSC fields.
• Certificate inventory: Pull all existing CPCs and GCCs from your records. Log each one in a spreadsheet with the product it covers, the issuing date, the test date, and whether it contains all required fields. Flag certificates that are missing fields or that may no longer reflect current production configurations.

Weeks 3 to 5: Supplier Outreach (April 7 to April 28)

• Issue formal supplier data requests: Send written data requests to every factory on your flagged list. Specify all seven required fields and set a response deadline of April 21. Include a translated fact sheet for factories where English is not the primary working language.
• Follow up on non-responses: By April 14, follow up with any factory that has not responded. Copy your sourcing team on escalations. A factory that cannot respond to a structured data request in three weeks has a process gap that will affect every shipment after July 8.
• Tier supplier responses: By April 28, classify each supplier as Tier 1 (complete data), Tier 2 (partial data requiring follow-up), or Tier 3 (non-responsive or deficient). The Tier 3 list is your highest compliance risk and requires immediate escalation.

Weeks 6 to 8: Data System Build (April 28 to May 19)

• Build your CPSC data registry: Create a master product-level database linking each regulated SKU to its seven required eFiling fields. This can be a structured spreadsheet, a compliance software platform such as Compliance and Risks or ItemMaster, or an internal database. The key requirement is that data is retrievable by SKU in under two minutes by any member of your logistics team.
• Certificate remediation: For Tier 2 suppliers, collect missing data fields. For products whose certificates do not reflect current production configurations, initiate the process for new testing at a CPSC-accepted laboratory. Allow at least six to eight weeks for a full third-party test cycle for CPC products, which means triggering any new tests no later than the first week of May.
• Broker data template: Agree with your broker on a standard CPSC data delivery format. This should be a structured spreadsheet column set or a data portal field that maps directly from your CPSC registry to the broker's ACE entry software inputs, with no manual transcription required.

Weeks 9 to 11: Testing and Training (May 19 to June 9)

• Test filing with your broker: Run three to five test entries with your broker using the new CPSC data fields for a representative sample of your regulated SKUs. Confirm that the data transmits correctly through ACE and that no fields are rejected or flagged for error.
• Train your operations team: Ensure everyone on your procurement and logistics team understands the new pre-shipment data collection requirement. Add CPSC data collection as a required step in your booking checklist alongside the commercial invoice and packing list submission.
• Escalate remaining Tier 3 suppliers: Any supplier that is still non-compliant by June 9 represents an active cargo hold risk starting July 8. Work with your sourcing team to either pause new purchase orders, find a compliant alternative supplier, or negotiate a short-term risk mitigation plan.

Weeks 12 to 14: Pre-Go-Live Verification (June 9 to June 30)

• Full dry run: For the first week of July, operate as if eFiling is already live. Have your broker file using the new CPSC data fields on all regulated entries and confirm zero errors before July 8.
• Internal audit: Pull a sample of 10 to 15 recent entries and verify that you have complete, accurate CPSC data for all line items. Fix any gaps before the deadline.
• Document your process: Write down the end-to-end CPSC compliance workflow so it can be executed by anyone on your team, not only the person who built it. Process documentation is also your first line of defense in any CBP or CPSC inquiry.

Understanding how CPSC eFiling enforcement works after July 8 helps you prioritize your compliance investments correctly. Not all risks are equal, and some product categories and importer profiles receive higher scrutiny than others.

CBP Holds for Missing or Incomplete Data

CBP has the authority to place a hold on any shipment that arrives with incomplete or non-compliant CPSC eFiling data. A hold means your cargo sits at the port or CFS warehouse while you resolve the deficiency. For ocean freight, this typically means daily port storage charges of $150 to $300 per container, plus the risk of missing retailer delivery windows that trigger chargebacks.

CBP typically phases in enforcement of new eFiling requirements, beginning with informational messages and requests for correction before escalating to formal holds. However, importers already on CPSC's watch list due to prior violations, recent recall history, or elevated examination rates should expect stricter treatment from the first day of enforcement. If your company has had a CPSC Section 15(b) report, a Fast Track recall, or a CPSC civil penalty in the last five years, treat July 8 as a hard enforcement date with no grace period.

CPSC Pattern Analysis and Targeting

CPSC uses eFiling data not just to screen individual shipments but to conduct aggregate pattern analysis across importers, product categories, manufacturers, and testing laboratories. Patterns that trigger CPSC interest include: certificates from laboratories with a history of issuing non-conforming results, manufacturing facilities flagged in CPSC's surveillance database, product categories with elevated injury report rates, and importers with a history of certificate deficiencies.

This means a technically accurate eFiling does not guarantee you will avoid examination. If CPSC's targeting model identifies your factory or product category as elevated risk, your entries will receive higher examination rates regardless of how cleanly your data is filed. The benefit of accurate filing is that you avoid the additional enforcement escalation that comes from data errors on top of examination selection.

Civil Penalty Exposure

CPSC civil penalties for knowing violations of consumer product safety rules reach $150,000 per violation and $1.875 million for a series of related violations. Filing knowingly false eFiling data, including wrong test dates, fabricated facility addresses, or certificates issued by laboratories that are not CPSC-accepted, constitutes a knowing violation. The risk is not just a financial penalty but potential detention of all your regulated goods and, in serious cases, referral to the Department of Justice for criminal prosecution.

The civil penalty risk attached to eFiling is not primarily about data typos. It is about structural misrepresentation: claiming a product has been tested when it has not, or listing a test date that precedes a manufacturing change that required new testing. These are the scenarios CPSC's enforcement division investigates when eFiling data surfaces inconsistencies.

Prioritizing Your Compliance Investment

If you are working against a tight timeline, prioritize your compliance efforts in this order:

1. Children's products requiring CPCs: Highest regulatory priority, mandatory third-party testing, highest penalty exposure, and most frequent target of CPSC examination
2. Electrical and fire-risk products: Extension cords, appliances, and lighting products are high-frequency examination categories
3. High-volume SKUs first: A filing error on a product you import 50 containers per year creates more cumulative exposure than one on a product imported once annually
4. New suppliers: Factories onboarded in the last 12 to 18 months carry higher compliance uncertainty than suppliers with a long track record of providing accurate data

The July 8, 2026 CPSC eFiling deadline is a structural shift in how consumer product import compliance operates in the United States. For the first time, federal regulators have real-time, entry-level visibility into product safety certificate data for every regulated shipment. The importers who treat this purely as an administrative burden to be delegated to their broker will struggle. Those who build a systematic, supplier-integrated compliance process will find that it strengthens their sourcing relationships, reduces examination rates, and creates an audit-ready document trail that protects them in any CPSC inquiry.

The work required before July 8 is substantial but finite. You need a complete HTS-to-CPSC-category mapping, a structured supplier data collection workflow, a certificate library linked to your SKU catalog, and coordinated data pipelines with your customs broker. Done correctly, these systems serve you well beyond the deadline, creating a compliance infrastructure that scales as your product lines grow.

Start the supplier outreach now, in April, not in June. Factories and testing laboratories that are compliant today will be overwhelmed with remediation requests from less-prepared importers in May and June. Getting into the compliance process early gives you access to faster responses, more accurate data, and fewer last-minute problems.

Three questions to ask your team this week:

• Which of our HTS codes fall within CPSC-regulated categories, and do we have compliant certificates for all of them?
• Has our customs broker confirmed that their ACE filing software supports CPSC eFiling, and have we agreed on a data delivery format?
• Do we have a structured product registry that stores test dates, manufacturing facility data, and rule citations at the SKU level, or are we relying on PDF certificates in email folders?

If the answer to any of these is no or uncertain, the 90-day action plan in this guide gives you a clear path to July 8 readiness. Cubic's customs brokerage team works with consumer product importers to build CPSC eFiling workflows, manage certificate libraries, and ensure accurate ACE filings from the first day of enforcement. If you would like to review your current compliance posture, contact our regulatory team for a CPSC eFiling readiness assessment.