EntryProof FAQ library
The full 50-question objection library covering cpsc efiling packet generation for importers. Grouped by pricing, trust, technical, comparison, objections, and legal. The top 20 (all P0 plus highest-value P1) also surface on the EntryProof landing for fast-scan buyers; this page keeps the complete set for research-mode readers.
Pricing
P0How much does EntryProof cost?
$79/mo flat. No per-user fees, no per-SKU fees, no tiers to decode. Whether you have 5 SKUs or 500, three users or one exhausted compliance person wearing four hats — same price. We priced it flat specifically because our main competitor charges $30 per user plus $20 per 25 SKUs, and importers hate doing that math.
P0Is there a free trial?
Yes — full access, no feature limits, cancel before it ends and pay nothing. You can load your SKUs, generate certificates, and see the Federal Register alert digest working before a dollar moves. Card required at signup, but we email you before the trial converts.
P0What's the refund policy?
Annual plans: 30-day money-back, no interrogation. Monthly: the free trial is your risk-free window, but if you hit a real problem after paying, email support@digitalempireholdings.com — we grant reasonable refund requests case-by-case because arguing over $79 is beneath both of us.
P0Can I cancel anytime?
Yes, self-serve from the billing page, effective end of period. Before you go, export everything — your certificate records and filing history download in one click, because your compliance records need to outlive any vendor. Ours included.
P1Does the price really not scale with SKUs?
Really. 10 SKUs or 1,000, still $79/mo. If you're an importer with genuinely enormous catalogs (10,000+ SKUs) we may eventually need to talk about infrastructure costs, but no one has hit that ceiling yet, and we'll grandfather early customers regardless.
P1Is there an annual discount?
Yes — two months free on annual, so $790/yr instead of $948. Annual also happens to match how compliance budgeting works: one line item, approved once.
P1Can multiple team members share one account?
Yes, at no extra cost — flat means flat. Your ops person, your broker liaison, and your QA lead can all be in the same workspace. We'd rather your whole team sees the compliance state than charge you $30/head to hide it.
P2Do you offer invoicing/PO-based billing?
Card via Stripe is standard, and every charge produces a proper PDF invoice with your company details for the bookkeeper. Annual plans can arrange bank transfer if your AP process demands it — email support@digitalempireholdings.com.
P2What happens to my certificates if I stop paying?
You get a 90-day grace window with read/export access to everything before archival. Compliance records aren't hostages here. Under CPSIA you need to be able to furnish certificates on demand — we will never be the reason you can't.
P2What's the Founding Trio bundle?
$99/mo for EntryProof plus PixelProof and TariffWatch — our whole portfolio, five slots only. If you're an importer touching steel or aluminum derivative products, EntryProof + TariffWatch together is a genuinely useful pairing. Details on the /pricing page.
Trust & security
P0Is my product and supplier data safe with you?
Yes. Data encrypted in transit (TLS 1.2+) and at rest (AES-256) on US infrastructure (Vercel + Supabase/Postgres). Payments live entirely inside Stripe (PCI DSS Level 1) — we never see card numbers. Your supplier relationships and test reports are commercially sensitive and we treat them that way: no selling, no sharing, no "insights" products built on your data.
P0Are you SOC 2 certified?
Not yet — honest answer, small company, audit is on the roadmap. What we can show your security reviewer today: architecture docs, our encryption posture, Stripe handling all payment data, and a data-flow diagram that fits on one page. Ask and we'll walk through it live.
P0Who can see my filing data?
You and the teammates you invite. Nobody at EntryProof browses customer filings; production access is limited and logged. We're not a marketplace, we're not a data broker, and your certificate data will never appear in anyone else's benchmark.
P1Are you GDPR/CCPA compliant?
Yes for the personal data we actually hold (your account details): full export and deletion on request at support@digitalempireholdings.com, no data sales, standard contractual clauses with processors. Most of what you store with us is product data, not personal data — which keeps this simple.
P1Does CPSC or CBP see anything through you that they wouldn't otherwise?
No. eFiling means you're providing certificate data to CPSC via the Product Registry / ACE PGA Message Set — that's the regulation, not our choice. We help you structure and manage what the government already requires. We add zero extra government visibility.
P1What happens if EntryProof goes down during an entry filing?
Your certificates live in CPSC's Product Registry once filed — an outage on our side doesn't invalidate anything already registered. For in-flight work, everything is exportable, and our status page shows uptime honestly. We also alert you well before deadlines so you're never filing at the last possible minute.
P2Who's behind EntryProof?
Digital Empire Holdings LLC, a Wyoming company. Founder-run and small — which for you means support answers come from someone who actually knows the eFiling rule, within 12 business hours.
P2Can I delete my data completely?
Yes. Email support@digitalempireholdings.com and we hard-delete within 30 days with written confirmation. Export first — you're required to retain certificate records under CPSC rules, so make sure a copy lands in your own archive before we wipe ours.
Technical
P0What does EntryProof actually do?
It manages your CPSC certificate compliance across every import channel: builds and stores your GCCs (General Certificates of Conformity) and CPCs (Children's Product Certificates), structures the data for eFiling through CPSC's Product Registry, tracks which SKUs are covered by which test reports, and watches the Federal Register so rule changes hit your inbox as a digest instead of a surprise at the port.
P0Setup time?
Most importers are functional in under an hour: import your SKU list (CSV upload works), attach existing certificates and test reports, map products to their applicable rules. From there the system tells you what's missing. The Federal Register monitoring starts working the minute you list your product categories.
P0What is CPSC eFiling and do I actually have to do it?
If you import consumer products requiring a certificate — almost certainly yes. CPSC's final rule (amending 16 CFR part 1110, published January 2025) made electronic filing of certificate data mandatory as of July 8, 2026 for regulated imported products. Certificate data now goes to CPSC electronically via the Product Registry or ACE at entry, instead of paper-on-request. If you've been coasting on PDFs in a folder, that era is over.
P0Does EntryProof file directly with CPSC/CBP for me?
We prepare and structure the data; the filing itself flows through CPSC's Product Registry (which we help you populate correctly) and your broker's entry filing in ACE references it. Think of us as the system that makes sure the right certificate data exists, is current, and is where your broker and the Registry need it — before the entry, not after the hold.
P1What's the difference between a GCC and a CPC?
GCC: General Certificate of Conformity — non-children's products subject to CPSC rules, based on testing or a reasonable testing program. CPC: Children's Product Certificate — children's products, which require third-party testing at a CPSC-accepted lab. EntryProof handles both and tells you which one each SKU needs, which is half the battle.
P1Which product categories do you cover?
Any consumer product subject to a CPSC rule requiring certification — toys, children's apparel, electronics, furniture, household goods, and the long tail. You map SKUs to applicable rules in the app; if you're unsure which rules apply to a product, the rule-mapping helper narrows it down and we'll answer specific questions at support@digitalempireholdings.com.
P1What does "multi-channel" mean here?
Your certificate obligations don't care whether the product arrived via ocean freight to your 3PL, direct import, or a marketplace-fulfilled channel. EntryProof tracks compliance per SKU across all the ways it enters, so one product with three import paths has one source of truth instead of three spreadsheets.
P1How does the Federal Register monitoring work?
We poll the Federal Register API continuously for CPSC rules, notices, and effective dates matching your product categories, then send a digest with plain-English impact — "this affects your SKU group X, effective date Y" — instead of forwarding you 40 pages of regulatory prose. It's the part customers say they'd miss most.
P2Can I bulk-import my existing certificates and test reports?
Yes — CSV for the SKU catalog, drag-and-drop for certificate and test report files, and we link them. The tedious part is one afternoon, once, and then it stays organized permanently.
P2Do you integrate with my broker's software?
Not via direct API yet — broker systems are a fragmented mess. What works today: share a live, read-only compliance view or export exactly the certificate data set your broker needs for the entry. Broker-side integrations are on the roadmap; tell us which broker and we'll prioritize by demand.
Comparison
P0My customs broker handles all this — why do I need you?
Ask your broker one question: "Are you creating and maintaining my CPSC certificates?" The answer is no — brokers file entries with data *you* supply. Under CPSIA §14, the certificate obligation sits with the importer: you. When the eFiling data is wrong or missing, the exam, the hold, and the penalty land on your entry, not your broker's license. We manage the part that was always legally yours.
P0How do you compare to Comply PRO+?
They're a capable, established platform priced at $30/user plus $20 per 25 SKUs — which for a 5-person team with 200 SKUs is $310/mo before you've done anything. We're $79 flat, unlimited users and SKUs, focused tightly on the importer eFiling workflow rather than a sprawling suite. If you need their enterprise breadth, buy them. If you need the eFiling job done without a pricing spreadsheet, that's us.
P1Can't I just use CPSC's Product Registry directly? It's free.
You can, and you should — we work *with* the Registry, not around it. What the free Registry doesn't do: track which SKUs lack current test reports, warn you before certificates go stale, monitor rule changes for your categories, or give your team one workspace. The Registry is the government's filing cabinet; we're your system for keeping it correctly fed.
P1We manage this in spreadsheets today.
So did almost everyone before July 8, 2026. Spreadsheets don't alert you when a test report ages out, don't map new Federal Register rules to your SKUs, and break silently when the one person who maintains them goes on vacation. $79/mo against one avoided port hold or penalty letter is not a hard business case.
P1Our testing lab manages our certificates.
Labs issue test reports; some help draft certificates. But labs don't track your entry-by-entry eFiling readiness, don't monitor rule changes across your catalog, and stop caring the moment the report is delivered. The lab is an input to your compliance program. We're the program.
P1Versus hiring a compliance consultant?
Consultants are great for judgment calls — is this product a "children's product," which standard applies to this weird SKU. That's $150-400/hr well spent occasionally. The ongoing bookkeeping of certificates, deadlines, and rule monitoring shouldn't cost consultant rates. Many of our customers use both: us for the system, a consultant for the edge cases.
P2What about big GTM/trade platforms (Descartes, etc.)?
Enterprise trade platforms are excellent and priced like it — implementations run five to six figures with months of onboarding. If you're a $500M importer, go that way. We're built for the $2-50M importer who needs the CPSC eFiling job done this month for $79.
P2Amazon already asks me for compliance docs — doesn't that cover it?
Amazon's document requests protect Amazon, not your customs entries. Marketplace compliance and import eFiling compliance are separate obligations with separate enforcement. Handily, keeping your certificates organized in EntryProof makes the Amazon doc requests trivial too.
Objections
P0We've imported for years without eFiling problems.
Because until July 8, 2026, mandatory eFiling didn't exist — certificates were furnish-on-request paper. That regime is gone. Certificate data now rides with the entry electronically, which means gaps that were invisible for years are now machine-checkable at the border. Past quiet is not future quiet; the rule change is the whole point.
P0$79/mo for compliance paperwork feels like pure overhead.
It is overhead — so is insurance. Context: CPSC civil penalties run six figures per violation (inflation-adjusted caps well past $100K each, with aggregate caps in the eight figures), and a single held container costs you demurrage, missed delivery windows, and a very unpleasant week. $948/yr against that risk profile is the cheapest line item in your import budget.
P0You're new and this is a compliance product. That worries me.
Reasonable. Three things: your filings live in CPSC's own Registry, not trapped in our database — if we vanished tomorrow, your compliance record stands; everything exports one-click at any time; and the free trial lets you verify our rule-mapping against your own knowledge before paying. We earn trust by being auditable, not by claiming it.
P1My broker says they've "got it handled."
Get that in writing with specifics — which certificates, maintained by whom, updated on what trigger. Nine times out of ten "handled" means "we transmit what you give us." The importer of record holds the CPSIA §14 obligation regardless of what anyone handles. If your broker truly does full certificate management, they're rare — keep them, and use us as the verification layer.
P1We only import a few SKUs. Overkill?
Small catalogs get held at ports too, and a 5-SKU importer usually has zero compliance staff — you're the compliance department between other jobs. The fewer SKUs you have, the faster setup is (30 minutes, maybe), and the more a single entry problem hurts as a fraction of your business.
P1I'll wait and see how enforcement shakes out.
CBP and CPSC built the eFiling pipeline precisely to make enforcement cheap and automatic — targeting runs on the data now. "Wait and see" with a border agency means your test case is your own container. Also worth knowing: setup takes an afternoon now, versus a panicked weekend after your first hold.
P2Our products barely qualify as "consumer products."
Maybe — the definitions have real edges. Send us your product list at support@digitalempireholdings.com and we'll give you an honest read, including "you probably don't need us" if that's true. We'd rather tell ten people no than have one wrong-fit customer churn angry.
P2Another subscription, another login, another thing to manage.
Fair, except this one replaces things: the certificate spreadsheet, the Federal Register email you never read, and the "wait, which test report covers this SKU?" Slack thread. Net tools count: probably negative one.
Legal & compliance
P0Which regulations does EntryProof actually cover?
Core: CPSIA Section 14 certificate requirements (15 U.S.C. §2063), the CPSC eFiling rule amending 16 CFR part 1110 (mandatory since July 8, 2026), and the product-specific CPSC rules your SKUs map to — plus continuous Federal Register monitoring for changes to all of the above. We cite the specific rule on every requirement we flag, so you can verify us.
P0Is EntryProof legal advice?
No. We're compliance software plus honest documentation — we organize, structure, alert, and cite the rules. For genuine judgment calls (is this a children's product, does this exemption apply), we'll say plainly "this one needs counsel" rather than let software impersonate a lawyer. Our terms state this and we mean it.
P1If I file wrong data using EntryProof, who's liable?
You remain the importer of record and the certifier — no software transfers that. What we do: validate structure, flag gaps and stale test reports before filing, and timestamp your records so you can demonstrate a good-faith compliance program, which matters enormously in how CPSC treats violations. We reduce the odds of the mistake; we can't absorb its legal ownership.
P1Who owns the compliance records I build in EntryProof?
You, completely. Certificates, test report mappings, filing history — exportable at will, retained 90 days after cancellation, hard-deleted on request (after you've exported, please — CPSC retention obligations survive your subscription).
P2Do you keep an audit trail?
Yes — certificate versions, edits, and filing-relevant actions are timestamped and attributable. When CPSC or CBP asks "what did you know and when," a clean audit trail is the difference between a conversation and a penalty negotiation.
P2Can you provide documentation for our customers' compliance requests?
Yes — retailer and marketplace compliance questionnaires get much easier when every SKU's certificate and test report are one click away. Export as PDF per SKU or as a batch. Several customers bought us for import compliance and stayed for how painless retailer audits became.