Genuine SGS flammability report covering base style 5634 (pages 1–3); both shipment styles map to that base. 16 CFR 1610 and 1500.44 results are reported as Pass. Lab, test date, and citations match the shipment. Safe to rely on for the linked styles.
AI test-report review
An expert compliance reviewer
on every lab report.
When a factory attaches a test report to a shipment, Factory Sync reads the actual PDF and checks it against what was claimed — the laboratory, the test date, the citations, and the styles. You get five clear answers and a plain-English summary before you ever certify.
Valid small-parts report, but style 88120 (or its base) does not appear anywhere on the document — the report lists base 8021 only. Confirm the correct report is linked before certifying.
Five checks on every report
It reads the report so your reviewers don't have to.
Each uploaded PDF is analyzed against the data entered on the shipment. Every report gets the same five yes/no checks — consistent, every time.
Valid test report
Is the PDF a genuine product test report — lab letterhead, sample description, real results — and not a blank, unrelated, or fabricated-looking document?
Issued by the claimed lab
Was the report actually issued by the laboratory the factory selected — allowing for minor branding or entity-suffix differences?
Testing passed
Did the tested sample actually pass? If any required test failed, the check returns a clear "no."
Citations match
Does the report cover the citation codes claimed on the shipment — understanding that 1610 maps to 16 CFR 1610?
Styles found on report
Do the linked styles — or their base styles — appear on the report? It understands that 55634 and 75634 both test under base 5634.
Summary & recommendation
A concise reviewer-facing summary that cites the exact page or field on any discrepancy, plus an overall "approvable" or "needs attention" call.
The engine
Powered by Claude — with nothing left behind.
Analysis runs on Claude Sonnet 4.6 through a secure AI gateway with zero data retention enabled, so the gateway keeps no copy of your prompts or report PDFs. Your proprietary documents are used to produce a verdict — then they're gone.
- Zero data retention on every model call — no prompt or PDF logging.
- Documents are evidence, never instructions. The reviewer is explicitly hardened so text hidden inside a PDF can't hijack the analysis.
- Structured, auditable output — a fixed JSON verdict, recorded on the shipment with the model and timestamp.
Built for scale & cost
The static review prompt is cached, so repeat analyses bill at a fraction of the first. Identical report-and-style combinations are de-duplicated and reuse the prior verdict with no new model call.
Durable & reliable
Reviews run on a durable queue with automatic retries and a dead-letter fallback. Large PDFs stream through the Files API; transient hiccups never lose a report.
Hands-off by default
It just runs — and you can tune it.
On submission
When a shipment is submitted for review, every linked report is queued for analysis automatically.
Live results
The reviewer panel streams verdicts in as they finish — approvable reports and flags, side by side.
Run & re-run
Re-run any report on demand after a change to re-check it against the current styles.
Tunable guidance
Admins refine the domain guidance the reviewer follows — while the five core checks always stay in place.
See it on your own data
Turn weeks of compliance work into minutes.
Book a walkthrough and we’ll map Factory Sync to your import file, factories, and CPSC account.
No rip-and-replace · Works with your current production file · Live in days