By the Digital Empire Regulatory Research Team (EntryProof Analysis Team) · Published August 24, 2026 · Last updated August 24, 2026
Editorial policy at /editorial-policy.
Short version: the CBP ACE Portal is the free government system of record for every U.S. import entry. It is authoritative, universal, and legally load-bearing. It is also famous for the exact things a working operations manager needs and does not get: readable interpretation, proactive alerting, and a UX built for anyone who is not a full-time trade analyst. EntryProof is not trying to replace ACE — it reads the same entry data ACE holds and interprets it back to the importer in the form of "these 3 shipments are missing a linked CPSC certificate."
The Automated Commercial Environment is CBP's primary electronic system for processing imports and exports, developed under mandatory-use milestones through the 2010s and modernized via a phased portal migration completed 2023-2025. ACE holds every entry filed under the importer's importer number, the responses CBP issued, and the associated PGA transmission data (including CPSC certificate references transmitted under 16 CFR Part 1110). It is free to register and use, and CBP publishes training materials and reports guides.
It is not a monitoring product, and it was never designed as one. There is no alert-when-this-HTS-code- gets-added-to-a-PGA-list feature, no plain-language weekly digest of an importer's certificate coverage, and no interpretation layer that turns raw ACE report exports into "these 3 entries failed to link a valid CPC." ACE's report builder is documented in broker blogs and Dimerco as brutal — a 2005-era BI shape that assumes an experienced compliance analyst as the user.
In 2026, CBS News covered a difficult launch of CBP's tariff-refund portal (built on ACE infrastructure): small business owners on hold with CBP support for 4+ hours, "Duplicate tax ID" errors binding importer accounts to unrelated parties, and outage windows during peak periods. That is the same operational surface that CPSC eFiling data flows through. The lesson is not that CBP is incompetent — the system runs at massive scale — but that a working importer cannot treat ACE as if it were a monitored SaaS product with a support SLA.
| Capability | CBP ACE Portal | EntryProof |
|---|---|---|
| Price | Free | Free readiness check + paid tiers |
| Role | Government system of record for U.S. imports/exports | Independent readiness and interpretation layer |
| Data authority | Ground truth — the actual entries CBP holds | Reads ACE-side data and CPSC-side certificate data together |
| Interpretation | None — raw report builder | Plain-language weekly digest |
| Alerts | None (CF-28 / CF-29 arrive after the fact) | Proactive alerts before filing |
| UX target | Trained compliance analyst / broker | Ops manager who does not know what a CF-28 is |
| Support | CBP support line; 4+ hour hold times reported at peak | Email support with response SLA |
For any question of legal record — "what did CBP actually accept for this entry number," "what is the definitive transmitted certificate reference," "what is the response history on this line" — ACE is authoritative by definition and no third-party tool can substitute for it. Every importer needs an ACE account, and every operations team should periodically pull ACE reports directly. A broker uses ACE constantly; an importer with in-house compliance staff uses it weekly.
For the working-week question — "are the shipments I have coming in over the next 30 days covered by valid CPSC certificates, and is anything missing before it becomes a CF-28" —EntryProof is the right layer and ACE is not built to answer that. ACE will tell you what you filed; EntryProof tells you what you are about to file and what is likely to bite you. That is a different question, and it is the one the ops manager without a compliance background actually has.
This is a hypothetical scenario, not a real customer case. An importer's broker files 15 entries in a month across three product families. One family (a children's toy line) is subject to 16 CFR Part 1501 small-parts testing; the broker's templated CPC reference on file was for the prior season's product and does not cover the reformulated 2026 version. All 15 entries release. Two months later a CBP CF-28 lands requesting substantiation for one of the toy entries; the importer discovers the CPC gap only then. Pulling the ACE report retroactively confirms the reference was stale; EntryProof run against the pre-shipment packing list would have flagged the mismatch before any of the entries filed.
EntryProof is a data preparation and readiness-assessment tool for the CPSC Product Registry. EntryProof is NOT a customs broker, NOT a testing laboratory, and NOT a legal-advice service. Compliance decisions remain the responsibility of the importer. EntryProof does not guarantee that any classification, packet, or filing will be accepted by CPSC or CBP.
EntryProof is not affiliated with the U.S. Consumer Product Safety Commission (CPSC), U.S. Customs and Border Protection (CBP), Amazon, Shein, Temu, or TikTok Shop. References to the CBP ACE Portal are nominative-fair-use for the sole purpose of comparing capabilities of a government system to those of the EntryProof product.
The Automated Commercial Environment (ACE) is U.S. Customs and Border Protection's primary electronic system for processing imports and exports. It has been developed since 2001 at billions of dollars in federal investment; mandatory-use milestones for most entry filings ran through the 2010s, and a modernized portal migration completed in 2023-2025. Every formal customs entry into the United States passes through ACE; brokers, importers, and carriers all interact with it.
Yes. ACE Portal access is free to any importer who registers. That is the case for the fee.
No. ACE is a record-keeping and transactional system: it records the entries that were filed and the responses CBP issued. It does not surface an alert when an importer's CPSC eFiling data was structurally incomplete, when an HTS code the importer regularly ships moves onto a PGA-required list, or when a certificate reference is stale. Errors surface as CBP CF-28 requests for information or CF-29 notices of action — after the fact, in the mail or in the ACE inbox the importer may or may not check.
CBS News reported in 2026 that CBP's tariff-refund portal (built on ACE infrastructure) had a difficult launch: small-business owners on hold with CBP support for 4+ hours, "Duplicate tax ID" errors binding importer accounts to other parties, and outages during peak periods. Beyond that specific launch, the general ACE reality documented by broker blogs and Dimerco is a report builder that resembles 2005-era BI tooling, no alerting, no interpretation, and phased migrations that periodically break existing workflows.
No, and it cannot — ACE is the government system of record for U.S. imports, and every formal entry passes through it as a matter of law. EntryProof reads ACE-adjacent data and CPSC-side certificate data to produce readiness alerts before the ACE filing goes in. EntryProof is a layer above; ACE is the settlement layer below.
Two things: (1) an importer-friendly interpretation of the raw entry data — "these 3 entries in the last 30 days are missing a linked CPC certificate; here is which SKU"; (2) proactive alerting tied to CPSC rule changes affecting the importer's actual product lines, not the entire tariff schedule. ACE holds the truth; EntryProof reads it back in the form an operations manager can act on.