CPSC eFiling Requirements for Foreign Trade Zones
Beginning January 8, 2027, importers must provide CPSC certificate data when covered finished products are withdrawn from a Foreign Trade Zone and entered into U.S. customs territory for consumption or warehousing. The requirement applies at entry—not merely because merchandise was admitted to the zone—and each entry must reference the actual certificate for the product being withdrawn.
This guide explains the separate FTZ applicability date, type 06 and weekly-entry workflows, Full and Reference PGA filing, certificate-to-inventory matching, FIFO and Unique Identifier challenges, mixed certificate versions, Product Registry reuse, file-size planning, broker handoff, and the operational work needed before the January 2027 deadline.
Admission to an FTZ and entry into U.S. customs territory are different events
The final rule gives FTZ operations additional implementation time because the certificate must be matched to merchandise at withdrawal and entry. It does not require the finished-product certificate merely at FTZ admission, and it does not prevent merchandise from entering a zone for storage, testing, assembly, or work needed to bring products into compliance.
Merchandise can be admitted to the zone before entry
An FTZ may be used to hold products, assemble components, manufacture, test, certify, or bring goods into compliance before they enter U.S. customs territory. The CPSC certificate filing obligation attaches when covered finished products are entered for consumption or warehousing.
Certificate data must accompany the entry from the zone
As of January 8, 2027, the importer making entry for covered merchandise withdrawn from an FTZ must provide the required CPSC certificate data with the entry-level admissibility information in ACE.
Each finished-product certificate describes only one product
A weekly entry or inventory withdrawal can contain many products, lots, factories, and certificate versions. The data process must preserve the product-level relationship rather than assigning one broad certificate to a mixed entry.
Prepare goods that may be entered on or after January 8, 2027
Because CPSC places the requirement at entry from the FTZ, operators and users should identify inventory expected to remain in the zone and later enter U.S. customs territory after the compliance date—even if the original FTZ admission occurred earlier.
The separate date does not expand the underlying product scope
CPSC eFiling applies to finished products and regulated substances that require a certificate of compliance. FTZ status changes the timing and inventory-matching challenge; it does not make every zone withdrawal a CPSC-certified product.
The product is subject to a CPSC rule and requires a CPC or GCC
Examples can include covered children’s products, durable infant products, toys, apparel, mattresses, bicycles, helmets, lighters, carpets, storage units, and other regulated finished products. Applicability must be confirmed for the exact product and rule.
A product requires eFiling only when a certificate requirement applies
A tariff flag or general CPSC jurisdiction does not prove that a CPC or GCC is required. Resolve the finished product, applicable rule, certificate type, and any valid enforcement discretion or exclusion before assigning PGA data.
A true component part is not eFiled as a voluntary component certificate
Component parts used for further assembly and not packaged, sold, or held for consumer use are not finished products for this certificate requirement. Voluntary component-part certificates must not be eFiled in ACE, although their testing may support the later finished-product certificate.
Assembly or manufacturing can create a different finished product record
When components become a finished product in the FTZ, determine the final product identity, applicable rules, certifier, manufacturing place and date, testing basis, and certificate before entry. Do not reuse a component or pre-assembly identifier as the finished-product certificate automatically.
The operator, zone user, importer, broker, and certifier need one data contract
A successful FTZ workflow identifies who owns each fact, who matches inventory to certificates, who prepares the message set, and who remains legally responsible. These roles may be performed by different companies.
Owns certificate validity, accuracy, completeness, and availability
The responsible importer can allow brokers, laboratories, suppliers, or other trade partners to maintain records or enter data, but remains legally responsible for the finished-product certificate under the final rule.
Supports inventory control and release without automatically becoming the certifier
The operator’s systems may hold admission, UIN, lot, quantity, location, and withdrawal data. The operator needs a dependable way to receive or reference product and certificate identifiers from the party responsible for the goods.
Connects commercial product records to the actual inventory layer
The zone user or importer should maintain product identity, supplier, factory, manufacturing date, test records, certificate version, and status changes. This business context is usually not contained in the UIN alone.
Transforms validated certificate data into the CPSC PGA Message Set
The transmission party needs product-level Full PGA data or the correct Reference PGA identifiers before entry filing. It cannot infer a citation, laboratory, certificate version, or manufacturer from the tariff line alone.
Provide source data without changing legal responsibility
Manufacturers and laboratories can supply testing, factory, and product information; consultants can review data; and technical providers can generate files. The certifier still must verify the final certificate and filing inputs.
How CPSC certificate data reaches ACE for FTZ withdrawals
CPSC’s July 2025 FTZ guidance confirms that ACE can accept the CPSC message set on a type 06 consumption entry and as part of a weekly entry submission. Operational design must account for entry timing, product volume, message size, and the exact certificate attached to every product.
Transmit the CPSC message set with covered merchandise withdrawn for consumption
CPSC identifies type 06 as the existing entry type used for covered merchandise withdrawn from an FTZ for consumption. Map each line to the required certificate data before the entry is filed.
The CPSC message set can be included in weekly entry submission
Weekly filing does not permit one generic certificate for all quantities. The underlying product and certificate relationships must remain specific enough for the broker to transmit the actual data for the merchandise entered.
Large weekly submissions may need to be divided
CPSC’s guidance warns that CBP transaction file-size limitations may require multiple weekly entries so CPSC and CBP receive all required certificate data. Test high-volume scenarios before production and agree on a deterministic split method.
File at entry, or with entry and entry summary when filed together
The final rule states that certificate data is eFiled at the time of filing the CBP entry, or when filing the entry and entry summary together. Do not design a process that waits until a later entry-summary step after the product relationship is no longer available.
Type 21 may be considered as a different operational route
CPSC’s FTZ guidance lists use of a bonded warehouse and type 21 entry as an option FTZ operators may wish to consider. This is not an automatic exemption; evaluate customs, inventory, cost, timing, and certificate requirements with the responsible trade professionals.
Choose the filing route that preserves product-level certificate matching
Both routes satisfy the eFiling mechanism when implemented correctly. The best operational choice depends on product repetition, certificate stability, inventory traceability, broker systems, and the ability to keep Product Registry versions current.
Transmit the seven required certificate data elements in the entry
Provide Product ID, citation codes, manufacture date, manufacture place, product test date, testing laboratory, and point of contact. This route requires the complete data to be available and mapped for each covered entry line.
Transmit three identifiers for a certified Product Registry record
The broker sends Certifier ID, Product ID, and Version ID. The Product Registry must already contain a complete, certified certificate matching the exact product and version withdrawn from the FTZ.
Reuse the record only while certificate details remain identical
A Product Registry record can be referenced for repeated entries of the same product when certificate details are unchanged. New testing, a factory change, new materials, revised rules, or a different certificate basis may require an update or new version.
The Product Registry does not transmit the entry by itself
CPSC states that the Product Registry is a stand-alone repository and does not automatically communicate with CBP ACE. The identifiers still must be mapped to the withdrawal and transmitted through the broker’s PGA workflow.
Why ordinary FTZ inventory accounting may not identify the actual certificate
The final rule discusses industry concerns that FIFO and UIN-based virtual inventory may identify an article and supplier without preserving the specific certificate data for the physical inventory layer. CPSC nevertheless requires the actual certificate for the merchandise entered.
The article identifier remains stable while manufacture place changes
Separate inventory layers by manufacturer and production location. A certificate tied to Factory A cannot be assigned automatically to identical-looking units produced by Factory B without a supported certificate relationship.
The product code remains stable while the certificate version changes
Preserve the test date, laboratory, citations, certificate creation or version date, and effective inventory range. Do not attach the latest Registry version to older stock unless the actual certificate supports that stock.
Commercial inventory grouping hides compliance-relevant differences
Color, coating, material, model, size, age grading, or component changes can affect testing and citations. Add a certificate-matching key below the UIN level when the inventory method otherwise combines distinct finished products.
Actual removals exceed the planned quantity or product mix
The final rule notes that if the estimated quantity in the weekly entry is exceeded, entry must be made for the excess before removal into customs territory. The certificate dataset and quantity controls should identify the additional product rows before release.
Enhance FIFO traceability or adopt another inventory method
CPSC’s guidance suggests developing the technical capability needed to continue FIFO, or adopting an alternative inventory accounting method if FIFO cannot supply the required certificate data. The chosen method must produce a deterministic certificate match at entry.
What to complete before January 8, 2027
Treat the deadline as an inventory, certificate, and systems project—not merely a broker software update. The organization needs enough time to remediate old stock already in the zone, test high-volume weekly entries, and resolve missing supplier evidence.
Identify every product likely to remain in the zone after the deadline
Export active UINs, SKUs, lots, manufacturers, admission dates, quantities, and expected withdrawal dates. Separate non-CPSC goods, products within CPSC jurisdiction but not requiring certificates, components, and finished products requiring CPCs or GCCs.
Assign a stable CPSC Product ID and certificate-matching key
Connect the FTZ article or UIN to GTIN, UPC, SKU, Model Number, Serial Number, Registered Number, or a controlled Alternate Identifier. Add factory, production period, testing basis, and certificate version where needed to distinguish inventory layers.
Find inventory without a complete supported certificate
Check certificate type, citations, manufacturer, manufacture date, laboratory, test date, testing exclusions, component evidence, records contact, and attestation readiness. Return unsupported gaps to the responsible importer, supplier, or laboratory.
Define one source for every Full and Reference PGA field
Document source system, owner, format, validation, update frequency, and fallback for each certificate element and identifier. Do not require the broker to combine unrelated spreadsheets manually at the entry deadline.
Create, import, review, and certify Reference records in advance
Choose Product Collections and trade-party privacy, establish reusable manufacturers and laboratories, upload validated records, correct errors, and confirm certification status. An imported row that remains Awaiting Certification is not ready for Reference PGA use.
Agree on payload, cutoffs, rejection handling, and correction ownership
Define how the FTZ system sends product and certificate data, how the broker reports ACE warnings or errors, who corrects each source, and how late inventory changes are prevented from bypassing the certificate check.
Test realistic weekly entries and file-size boundaries
Include mixed products, multiple laboratories, repeated citations, different certificate versions, excess quantities, correction scenarios, and the largest expected week. Verify that any split entries remain complete and reconcilable.
Stop release when the certificate match is missing or stale
Before removal, verify product identity, covered status, certificate version, Product Registry certification state where applicable, entry data completeness, and regulatory freshness. Route unknowns for review instead of selecting the latest available certificate automatically.
Errors to remove before live entry filing
FTZ failures often come from certificate matching and timing rather than the message format itself. Test the business rules that decide which certificate belongs to the inventory being released.
The newest version is assigned to older inventory without verification
Match factory, production period, testing, citations, product design, and certificate version. The actual certificate for the withdrawn product is required; “latest” is not a valid matching rule by itself.
Virtual inventory combines multiple compliance states
Add lower-level product, lot, factory, or version attributes where a UIN includes multiple certificates. A successful quantity reconciliation does not prove a correct certificate match.
Old inventory lacks testing or factory records when the first entry is due
Review inventory expected to remain in the zone now. Supplier contacts, laboratories, corporate records, and product teams need time to reconstruct missing evidence or decide how the goods will be handled.
A Disclaim is used instead of the required certificate data
The final-rule discussion rejects using a Disclaim on a type 06 entry merely because a certificate exists elsewhere; that would not let CPSC match the certificate to the entry for automated risk assessment.
The January 2027 date is incorrectly used for direct non-FTZ entries
Most other covered imported products became subject to the rule on July 8, 2026. The additional six months applies to covered products entered for consumption or warehousing from an FTZ.
A CSV row exists but remains Awaiting Certification
Reference PGA requires the correct certified Registry record. Track upload validity and certificate status separately, then provide the broker with the identifiers for the certified version.
Connect FTZ inventory readiness to certificate preparation
Use the related guide for importer obligations, product scope, Product Registry setup, data fields, CSV preparation, upload troubleshooting, or marketplace workflows.
CPSC eFiling Resource Center for U.S. Importers
Open the central hub for compliance dates, official sources, filing routes, preparation guides, and the CSV application.
CPSC eFiling Requirements for U.S. Importers
Review certificate duties, filing routes, entry timing, broker coordination, effective dates, and current importer obligations.
Which Products Require CPSC eFiling?
Apply the finished-product, certificate, component, used-product, Section 321, and HTS screening rules.
How to Use the CPSC Product Registry
Understand Business Accounts, Product Collections, trade parties, certificate versions, bulk import, certification, and broker handoff.
CPSC eFiling Data Elements and CSV Field Requirements
Map product, manufacturer, laboratory, citations, testing, version, and contact data into the required fields.
CPSC eFiling CSV Template: How to Prepare a Bulk Upload File
Use the current template, preserve its structure, map source data, and export a controlled CSV.
CPSC eFiling CSV Upload Errors and How to Fix Them
Diagnose file failures, missing fields, invalid values, product updates, trade-party dependencies, and citation problems.
CPSC eFiling for Amazon and Private-Label Sellers
Organize importer roles, supplier data, testing records, product variants, and repeat imports.
Verify FTZ rules and technical requirements before implementation
CPSC, CBP, ACE, CATAIR, entry software, and Product Registry guidance can change. Use the current official materials and confirm customs procedures with the responsible trade professionals.
eFiling Guidance for Foreign Trade Zones
Official July 2025 one-page guidance covering the January 8, 2027 deadline, type 06 and weekly entry, file-size concerns, FIFO alternatives, and bonded-warehouse option.
Certificates of Compliance Final Rule
Official final-rule publication discussing FTZ timing, entry requirements, actual certificate matching, FIFO concerns, components, Product Registry, and finished-product responsibility.
eFiling Frequently Asked Questions
Official answers confirming entry timing, type 06 functionality, weekly submission, FTZ date, filing routes, Product Registry behavior, and current implementation details.
eFiling Document Library
Official location for FTZ guidance, CATAIR link, Product Registry guides, CSV files, HTS guidance, citation codes, and implementation updates.
Common questions about the January 2027 FTZ requirement
These answers summarize the current CPSC framework. The actual product, certificate, inventory method, entry, broker instructions, and current official technical requirements remain controlling.
When does CPSC eFiling apply to Foreign Trade Zone entries?
January 8, 2027, for covered regulated products and substances entered from an FTZ for consumption or warehousing. Most other covered imports became subject to the rule on July 8, 2026.
Is certificate data required when goods are first admitted to the FTZ?
The final rule places the finished-product certificate requirement at entry for consumption or warehousing from the FTZ. Admission can occur earlier for storage, assembly, testing, certification, or compliance work.
Can the CPSC message set be filed with a type 06 entry?
Yes. CPSC’s FTZ guidance states that ACE has functionality to accept the required certificate data through the CPSC message set on a type 06 consumption entry.
Can the CPSC message set be included in a weekly entry?
Yes. CPSC states that it can be transmitted as part of weekly entry submission. Large transaction files may require multiple weekly entries so every certificate dataset is received.
Can an FTZ continue using FIFO inventory accounting?
CPSC’s guidance suggests developing the technical requirements needed to continue FIFO. If FIFO cannot provide the actual certificate data for the merchandise entered, the zone user may need an alternative inventory accounting method.
Does a Product Registry record eliminate the broker filing?
No. The Registry stores the certified record but does not communicate automatically with ACE. The broker must transmit its Certifier ID, Product ID, and Version ID in the Reference PGA Message Set.
Can Registry Intelligence choose the certificate for an FTZ inventory layer?
No. The application can map, validate, and format user-supplied information after the product and certificate relationship is confirmed. It does not make legal or customs determinations, invent missing data, certify products, file entries, or guarantee acceptance.
Check certificate records before mapping them to withdrawals
Upload one or several supported source files, confirm the field mapping, identify missing and inconsistent information, and prepare a CPSC Product Registry-formatted CSV from rows supported by the data you provide.
Confirm product, certificate, inventory, and entry requirements separately
Registry Intelligence is not affiliated with, endorsed by, or operated by the U.S. Consumer Product Safety Commission, U.S. Customs and Border Protection, or the Foreign-Trade Zones Board. This page provides educational and data-preparation information, not legal advice, customs classification, FTZ administration, customs brokerage, product testing, certification, Product Registry access, or a government filing service. Official rules, current CPSC and CBP instructions, zone procedures, product evidence, and the importer’s determinations remain controlling.