01 · ATTEST
Reviewer approves
A reviewer confirms the CPSC attestation and approves a complete shipment. It moves to Submitted to CPSC.
CPSC eFiling engine
Approve once.
We file with the CPSC.
Behind a single attestation, Factory Sync builds your CPSC V4 filing, transmits it, and tracks it to completion — then writes the result back onto the shipment. No re-keying into a government portal. No guesswork about whether it went through.
SHP-2026-0423
22 styles · 8 lab reports · Harbor Goods Co.
Draft
In Review
3
Submitted to CPSC
4
Approved
I certify this data is accurate and complete and that I am authorized to certify it to the CPSC on behalf of the importer.
Transmitting to CPSC eFiling… polling /getImportStatus
Collection resolved · 22 coreProduct rows built
Directives + certifier attached
Awaiting import log…
The clock is running
The CPSC eFiling requirement takes effect July 8.
Importers of regulated consumer products will need to file electronically with the CPSC. Standing up that capability from scratch is a project. Turning it on with Factory Sync is a setting.
Time remaining
--
Days
--
Hrs
--
Min
--
Sec
Under the hood
From attestation to acknowledged — automatically.
Approval publishes the shipment to a queue that a dedicated, isolated worker drains. It speaks the CPSC V4 API so your team never has to.
02 · BUILD
V4 payload assembled
The worker resolves your collection and builds the /import body — a product list of core products and directives, with your certifier and POC attached.
03 · TRANSMIT
Sent & polled
The filing is transmitted, then the worker polls /getImportStatus until the upload completes — no manual checking.
04 · CONFIRM
Result written back
It reads /getImportLog for per-row validations, then flips the shipment to Approved — or to a failed state with the exact CPSC reason.
Always know where you stand
An eight-state lifecycle, locked at every step.
Inputs are editable only while a shipment is a draft or has been sent back. Every other state locks the form on both the client and the server, so a filing can't change underneath you.
Draft
Editable. The factory prepares the shipment and uploads reports.
In Review
Submitted internally; factory fields lock while reviewers inspect it.
Rejected
Sent back with a reason; the factory can edit and resubmit.
Submitted to CPSC
Approved and transmitting; the worker is filing and polling status.
Approved
Filed with the CPSC. Fields are locked for the record.
CPSC Sync Failed
Filing didn't land; reviewers resolve the cause and retry in one click.
Amendment in Progress
A newer amendment exists; this version is read-only.
Superseded
Replaced by a corrected filing and kept for history.
Resilient by design
Nothing falls through the cracks.
Filing is queue-driven and durable. If the CPSC API is briefly unavailable or a row is rejected, the shipment lands in a clear failed state with the reason — never a silent failure.
- One-click Retry API Sync re-files after you resolve the cause.
- Amend approved filings — a new draft is created and the original is preserved.
- Readiness gates stop incomplete shipments (missing manufacturer, POC, citations) before they ever reach the CPSC.
Connect your CPSC account
Live the moment your credentials are in.
Bring your Product Registry certifier ID and API token. Factory Sync auto-detects your collection, and the filing pipeline activates as soon as your credentials are configured — no redeploy.
- Collections auto-detected — or pick one by name when your account has several.
- Token-and-secret auth handled for you, with optional auto-certify on import.
- Your certifier ID flows through to the broker EDI export too.
The deadline is real — the setup isn’t
Be CPSC eFiling-ready before July 8.
Onboarding takes days, not months. Bring your existing production file and start filing.
No rip-and-replace · Works with your current production file · Live in days