Keep compliance evidence tied to every product.

Every test report and certificate linked to the product and revision it covers, and ready when a broker or retailer asks.

Start with a development review How it works

Evidence index · CAT-042

Document	Covers	Added	Status
Fabric test report	12 oz canvas, mill spec revision 2	Week 4	Linked
Supplier declaration	Canvas mill	Week 4	Linked
Wash and shrink test	Sample S03, revision E	Week 8	Linked
Import certificate	Revision E, lots 1 to 3	—	Draft for broker

One index: every document, what it covers and whether it still applies.

Sound familiar?

The broker asks for the certificate and someone hunts for the test report.
A test passed on an earlier revision, and nobody knows if it still counts.
Each retailer wants its evidence in a different format.

Missing evidence can hold up a shipment or an order, and it’s easier to keep it linked than to hunt for it later.

What changes.

TodayWith the engine

Where evidence lives: Inboxes, drives and a supplier’s portalOne index, by product and revision
Whether it still counts: AssumedFlagged when the revision, material or factory changes
Gaps: Found when a broker asksListed per product and market before shipping
Who decides: Whoever has the fileA named person for each decision, on record

How it works. 5 steps, 4 stages.

AI1
Rules and automation3
Your team1
Approval

1Collect
1. Rules and automation
  Collect reports and certificates
  Test reports, supplier declarations and certificates arrive in one place.
  - Outlook
  - Specright
2Match
1. AI
  Match each document to a product
  Reads the report and ties it to the product, revision, material and factory it covers.
3Check
1. Rules and automation
  Check coverage and age
  Flags evidence that predates a change, and products with nothing linked for their market.
4Decide
1. Your teamApproval
  Decide what the evidence proves
  Your compliance owner, or a qualified lab, decides. The index never says a product is compliant.
2. Rules and automation
  Hand the index to the importer
  The broker or retailer gets the linked evidence for each product.

A change to a revision reopens its evidence

What you get. Real work, every week.

Needs a decision

Wash and shrink testRun on sample S03, before the thread was changedReviewQuality lead
Import certificateDraft assembled for the brokerDraftBroker files
Supplier declarationLinked to the canvas mill and mill spec revision 2CurrentNo action

What needs a person. Evidence that may no longer cover the product is flagged, never dropped.

How you’ll know it’s working.

Products with complete evidence for each market
The number a broker or retailer will ask for first.
Time to assemble a certificate or evidence request
Shows how much of the hunt is left once evidence is linked.
Evidence gaps found before shipping
A gap found at the dock costs more than one found at the desk.

Baselines agreed before we build.

Works with what you have.

PLM & specs

FlexPLM
Centric PLM
Specright

Commerce

NetSuite

ERP, CRM & inbox

Outlook

We configure first: Your PLM or spec platform may already store test reports. We link them to the revision and check what’s missing, rather than start a new repository.
We build when: Reports and certificates sit in inboxes and drives, and nobody can say which products are covered.

What a first build includes.

Built in your accounts, around your team. Scope, fee and baseline agreed before we start.

1Design
2Build
3Run it, or hand it over

Start with a review Scope this build

We build

An evidence index keyed by product and revision
Matching of reports and certificates to products
Alerts when a change makes evidence stale
A package for your importer, broker or retailer

We start from

Test reports, declarations and certificates
Product and revision records
Your markets and the evidence each needs

From your team

Owner: Quality or compliance lead
Involves: Quality
Development
Sourcing
Logistics

Questions teams ask.

What does CPSC certificate eFiling change?

Certificate eFiling for covered imports took effect on July 8, 2026. We keep each product’s evidence linked, so the importer or broker can find it. Whether a product is covered, and what its certificate says, is for your compliance owner and broker to decide.

Does this cover cosmetics?

MoCRA requires safety substantiation for cosmetics. We keep that file linked to each product and revision. A qualified person decides whether it’s adequate, and we never describe a product as approved.

Is this a compliance AI?

No. It finds, matches and flags. It never decides that a product is compliant, and it doesn’t file anything on its own.

Who owns it once it’s running?

You do. It’s built in your accounts, documented, with training for the people who run it. Ownership usually sits with your quality or compliance lead. We can keep running it with you, or step back.

How do we start?

Usually with a development review: two to four weeks, a fixed fee credited to the build, and a plan that’s yours. If the job is already clear, we can scope the build directly.