CPSC eFiling for small-parcel importers: certificate ops that scale down

Published 2026-09-22 · CertFiling

The eFiling conversation is dominated by container importers, and that makes sense: they move the most volume. But the rule does not care about your volume. A DTC brand shipping single parcels from an overseas factory faces the same certificate requirement as the company filling forty-foot boxes, with a fraction of the staff to manage it.

The core problem for small-parcel importers is not willingness. It is fragmentation. Certificates live in email threads with three different labs, product data lives in Shopify, and nobody owns the link between a SKU and its test report. When CBP asks for certificate data on a parcel, the scramble begins. Multiply that scramble by every order and you have a process that only works until it does not.

The fix is boring and it works: one record per SKU tying the product to its certificate, its lab report, and its revision history. Not a shared drive of PDFs, a living record. When a lab issues a new report, the record updates. When a product changes suppliers, the record flags the certificate for review. The brands that survive eFiling at small-parcel scale are the ones where answering "show me the certificate for this SKU" takes thirty seconds, not three days.

There is also a sequencing question worth getting right early. Map your SKUs to their certificates before you need them, starting with your best sellers and anything in a high-scrutiny category like children's products. The brands that wait for their first held parcel end up building this system under time pressure, which is how data entry errors become the next hold.

Small-parcel eFiling is not a smaller version of container eFiling. It is the same requirement with tighter margins and fewer people, which means the system has to be simpler, not just scaled down. One record per SKU, kept current, accessible in seconds. Everything else is detail.