EntryProof Changelog

A free CPSC Penalty Calculator tool shipped as part of a portfolio-wide three-tool trio, followed by six more pages under the Day 23 SEO ship. A content pass expanded the HTS lookup and CPSC penalty calculator pages to clear the 2,000-word YMYL floor and fixed an EEAT unclaimed-review false positive.

This release also ships the page you're reading: a public status page at /cpsc-efile/status backed by hourly uptime snapshots, and this changelog at /cpsc-efile/changelog.

The CPSC Penalty Calculator answers a specific, high-anxiety question, "what could this actually cost me if I get it wrong," with real statutory penalty ranges rather than vague warnings, which is why it needed its own word-count and citation pass to clear the YMYL content floor rather than shipping as a thin calculator widget.

The August Gold SEO ship added comparison pages against three named incumbents (Enhesa, Assent, Descartes CustomsInfo) plus a glossary and calendar content, part of ten pages shipped across the portfolio under Google Perfection Standard v2.

Comparison pages against Enhesa, Assent, and Descartes CustomsInfo were chosen because those three are the incumbents importers researching CPSC eFiling compliance actually search for by name. The pages exist to give an honest, specific answer to "how is EntryProof different from [incumbent]" rather than a generic feature-comparison table, which is why each one cites the incumbent's own public pricing and feature pages rather than assuming.

A solo-founder due-diligence pass shipped a Terms of Service page for EntryProof and wired up `/api/cpsc/health` so uptime monitoring has something to actually check. JSON-LD structured data also shipped this release, closing a P0 finding that EntryProof was shipping zero schema markup.

Both fixes closed real gaps an external due-diligence review would have flagged immediately: a product with no Terms of Service page and no working health endpoint looks unfinished to anyone evaluating it seriously, regardless of how good the underlying readiness checker is. Neither fix changed user-facing product behavior; they closed the gap between "the product works" and "the product looks like it was built by a team that ships professionally."

A lever-sweep pass added three more platform PSEO pages, broker LOI CSV export prep, and Delta lifecycle emails with exit-intent capture. Eight fixes from an EntryProof-specific review closed out a warm-ping issue, a missing score tooltip, the case-study accordion, dynamic day counting, a cohort-counter fallback, source validation on inbound leads, and a PixelProof cross-sell placement.

This day's portfolio-wide hardening pass also touched EntryProof directly: sanitized error responses, type-guarded POST bodies, closed CSRF/enum gaps, custom 404/500 pages, iOS input-zoom and ToS/methodology copy fixes, and full-funnel PostHog conversion tracking.

The broker LOI CSV export prep exists because EntryProof's early growth motion leans on customs brokers referring their import clients, not paid ads. A broker needs a clean list of prospects to reach out to, and that list has to come from somewhere real rather than being assembled by hand. The cross-pick PostHog funnel wiring that shipped the same day means EntryProof's conversion funnel (checker run to email capture to founding-cohort signup) is now measured the same way PixelProof's and TariffWatch's are, on one shared events schema.

Later the same launch day, EntryProof added an HTS auto-estimate with primary-source citations and a video hero, a founding-cohort waitlist CTA with a real-time spot counter, and an embeddable readiness badge visitors can put on their own site. A CPSC rule-change calendar and five platform-specific PSEO pages shipped alongside a self-serve account-deletion flow and an FAQ expansion from 4 to 8 questions.

The embeddable readiness badge was a distribution play as much as a feature: any store that passes the checker can drop a snippet on their own site, which is a free, self-propagating signal of the tool's existence to every visitor of that store. The HTS auto-estimate's primary-source citations link back to the actual CBP and CPSC guidance rather than summarizing it, a deliberate EEAT choice given how much of EntryProof's traffic arrives already skeptical of compliance-tool accuracy.

EntryProof's M0 build shipped at /cpsc-efile: a landing page, a free readiness checker, email capture, and the `pick2` Supabase schema (later renamed to `cpsc_efile` the same day to match the product's own build plan). Same-day security fixes closed an HMAC unsubscribe-token gap, a reflected-XSS issue, a missing scanId validation, and added per-email rate limiting on the checker.

The product also went through a naming reconciliation this day: it shipped internally as "SafeShip" before being renamed to EntryProof to match the plan, and its route moved from an earlier draft path to the current /cpsc-efile.

The M0 scope was deliberately narrow: a free readiness checker rather than a paid product, because EntryProof launched into a rule (16 CFR Part 1110) that had already been in effect since July 8, 2026, and the fastest way to find real demand was to let importers check their exposure for free before asking for a card. The `cpsc_efile.readiness_scans` and `cpsc_efile.email_captures` tables created this day are still the core data model the product runs on.