Catch certificate, lab-report and SKU mismatches before CPSC eFiling
Saxum builds one product-family evidence map, flags contradictions and creates a broker-ready data sheet without claiming that a document proves substantive product compliance.
No portal credentials. No guaranteed external result. Scope confirmed before sensitive material is transferred.
Current implementation snapshot
CPSC’s revised certificate and eFiling requirements took effect for covered imported products on 8 July 2026. The foreign-trade-zone effective date is 8 January 2027. Saxum checks evidence alignment and data readiness but does not certify substantive product compliance.
Why the standard portal or checklist is not enough
Certificate data can be individually plausible yet inconsistent across the CPC/GCC, laboratory report, SKU catalog, manufacturer facts and customs handoff. Those mismatches create expensive last-minute questions.
Best-fit customer
Product-compliance advisers, testing labs, importers and private-label sellers
Problems this product helps control
CPSC eFiling certificate data, Product Registry records, SKU mappings and CPC/GCC evidence that disagree before import filing or certification.
A bounded intake, not an open-ended data dump
The case starts with enough context to reproduce the problem and define responsibility. Credentials, unrelated personal data and unsupported assumptions are excluded.
- CPC or GCC
- Supporting test reports
- SKU, UPC, ASIN or model list
- Manufacturer, importer and production-lot facts
What arrives at the end of the engagement
The output is designed to be reviewed, handed off and defended—not merely marked “passed.”
- Certificate-to-test-report cross-check
- SKU and model mapping
- Missing-field and contradiction register
- Broker-ready certificate data sheet
- Supplier/lab question list
- Evidence-pack index
From messy source material to a reviewable release packet
Each stage has a clear stop condition. When evidence is insufficient, the case pauses rather than manufacturing certainty.
Map
Bind every listed product identifier to the certificate and supporting report.
Check
Compare dates, parties, laboratories, rules and product descriptions.
Resolve
Create a focused question list for unsupported or contradictory facts.
Handoff
Produce the reviewed eFiling data sheet and evidence index.
Preflight certificate evidence across importer and product portfolios
Keep importer/product families segregated while reusing approved evidence mappings, certificate checks and broker-handoff controls.
Segregated accounts
Each customer, entity or operating unit keeps separate source evidence, mappings, exceptions and outputs.
Reusable controls
Approved mappings and review policy reduce repeat setup without allowing one client's assumptions to leak into another.
Portfolio oversight
Firm teams can see recurring due work, unresolved exceptions and evidence-backed outcomes without flattening client boundaries.
Show the buyer exactly what Saxum proved
The first controlled cycle produces customer-visible proof before the workflow is expanded. Saxum keeps internal completion separate from external/provider acceptance and never turns estimates into verified outcomes.
Source coverage
See which files, mappings and authority sources were used, what was missing and which assumptions remained unresolved.
Exception register
Every blocker has a reason, owner and current state. Unsupported facts remain open instead of disappearing into a generic pass.
Evidence-graded scorecard
Separate Saxum-completed work from provider-final evidence, verified value, source-backed exposure, observed time savings and estimates.
Use this when the cost of an unresolved exception exceeds the cost of review
Saxum is strongest when the workflow repeats, the evidence is fragmented and one preventable mistake can delay revenue, create rework or weaken the customer’s audit trail.
The engine can monitor Product Registry exports and recurring product files, but it never certifies a certificate automatically; an authorized certifier retains that action.
Start a product-family readiness review →CPSC eFiling Control FAQ
Direct answers on access, responsibility, deliverables and limits.
No. Saxum checks document and data consistency. Product testing and legal compliance remain with qualified parties.
Sometimes, depending on the underlying product and evidence. Saxum maps the relationship but does not invent equivalence.
No. The importer and customs broker retain submission control.
Yes. The partner workflow is designed for repeat product-family reviews.
The conflict is surfaced and routed back to the responsible supplier, lab or adviser.
Verify the underlying requirement
Saxum product pages link to primary agency or platform material so buyers can confirm the official requirement themselves.
Primary-source review date: 18 August 2026. Re-check before each engagement.
Continue the control layer
Bring the real case, not a hypothetical
Describe the workflow, deadline and evidence you already have. Do not send passwords, API keys or regulated data through the public form.
See the workflow before you bring customer data
Every executable Saxum product now has a synthetic first-cycle walkthrough. Where a free checker or guide exists, it is linked here too.