EntryProof Docs

EntryProof checks whether your CPSC-regulated shipment's data is ready for the Product Registry electronic-filing rule (16 CFR Part 1110), mandatory since Jul 8 2026. A missing or malformed field in that filing can hold a container at the port. This page covers getting your first readiness check running, common questions, how EntryProof fits alongside customs software you may already use, and what to do when something looks wrong.

1. Run the free readiness checker. Go to /cpsc-efile and enter your store URL and the HTS code(s) for the product you're shipping. The checker scores your readiness and flags specific missing or likely-incorrect data elements against the Product Registry rule.
2. Read your score and band. The result includes a numeric score and a readiness band (see the glossary for exact terminology), plus which specific filing fields are the likely gap — a Manufacturer ID (MID) formatting issue and a missing product-category classification are two of the most common findings.
3. Understand what EntryProof is, and isn't. This is a readiness assessment tool, not a customs broker service — EntryProof does not file on your behalf or transact customs business under 19 CFR 111. It tells you what's likely to trip up a real filing so you or your broker can fix it before it does.
4. Join the founding cohort waitlist if you want early access to deeper features beyond the free checker — see the signup form on the landing page for current cohort status.
5. Check the compliance calendar. /cpsc-efile/calendar (also available as an iCal feed) tracks CPSC rule-change dates relevant to filing requirements, so a deadline doesn't catch you by surprise.

Is this legal advice? No. EntryProof provides a readiness assessment based on publicly documented CPSC and CBP requirements, cited to the regulation or statute itself where one exists. It is not a substitute for advice from a licensed customs broker or trade attorney, and it does not cover every product category's specific requirements — see the glossary FAQ for more on this boundary.

Does EntryProof file with CPSC or CBP for me? No — this is the single most important boundary. EntryProof assesses readiness; it does not submit filings, and doing so on your behalf would require different regulatory standing under 19 CFR 111. Pair a good EntryProof score with your actual customs broker's filing process, not instead of it.

How is this different from Descartes CustomsInfo, Enhesa, or Assent? Those are broader compliance-data platforms covering many regulatory regimes across many countries. EntryProof is narrowly focused on one specific, high-stakes requirement — CPSC Product Registry electronic filing — with a free, no-signup first check. See the platform-specific comparison pages linked from /cpsc-efile/best-cpsc-efiling-tools-2026 for detail on each.

What data does the free check collect? Store URL and the HTS code(s) you enter, plus a hashed IP for basic abuse prevention — no payment information is required for the free checker. See /cpsc-efile/privacy for full detail, including the 30-day retention window on this data (enforced automatically, not just stated).

• CBP Partner Government Agency (PGA) messaging — the readiness check is built around the specific data elements CPSC requires through CBP's PGA system at time of entry.
• HTS classification — the free HTS Code Lookup tool is a standalone companion for classifying products before running a readiness check.
• CPSC Penalty Calculator — a companion free tool at /tools/cpsc-penalty-calculator estimating potential civil penalty exposure under CPSA §15(b) for reporting violations, separate from Product Registry filing violations.
• PostHog — product analytics and, with consent, session replay; see the cookie policy.
• Stripe — billing once a paid tier is available beyond the current founding-cohort/waitlist phase.

My readiness score seems low but I think my filing data is correct. The checker flags patterns statistically associated with rejected or delayed filings — it is a risk signal, not a guarantee your filing will fail. A low score with data you're confident is correct is still worth a second look from a customs broker before you rely on your own confidence alone; the checker's whole reason for existing is that filing-data errors are easy to miss without a second set of eyes.

I entered an HTS code and got no result. Confirm the code is a full, valid HTS classification (use the HTS Code Lookup tool if you're not certain) — a partial or malformed code will not return a meaningful readiness score. If a clearly valid code still returns nothing, that's worth reporting via the account request flow on /cpsc-efile/account.

I'm on the waitlist and haven't heard back. The founding cohort is currently limited; waitlist status and expected timing are shown on the signup confirmation. Behavioral and milestone emails (see the changelog for when these shipped) will notify you of status changes automatically — check spam if it's been more than a few days since signup.

A comparison page seems out of date. Comparison pages against Descartes CustomsInfo, Enhesa, and Assent are reviewed periodically, not continuously — if you know of a pricing or feature change we've missed, the fastest fix path is flagging it through the corrections process described on /corrections.

For anything not covered here, the fastest path is running a fresh free readiness check — it takes under a minute and requires no signup.