Line up the certificates, declarations and test reports each destination market requires against what is actually on file, and hold the gaps for the compliance specialist who signs.
Proves the document exists, never that it complies
In
01
A product is onboarded, and the agent lists the certificates, declarations and reports each market requires.
02
A supplier document arrives, and it is filed against the requirement it is meant to answer.
Reason
03
A test report ages, and its currency and the laboratory accreditation are checked.
04
A harmonised standard is withdrawn, and the reference on file is marked stale.
05
A change notice reaches the product, and a person is asked whether it is a material change.
Decide
06
A declaration is drafted, and the signature block is left for the signer.
07
A market is added to the listing, and the file is re-checked.
Out
08
An entry is filed, and since 8 July 2026 the certificate data set goes with it and must match the line.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
The agent assembles the file; a named natural person signs the EU declaration under sole responsibility, and no assembly of evidence stands in for that.
Example workflow
One product, file to signature
AgentHuman
1Product record receivedPIM entry, supplier pack, factory test report or certificate
2Requirements resolvedCertificates, declarations, reports and notified-body documents each market asks for
3File assembledCoverage, currency, accreditation status and confidence
4Controls appliedRequirement-coverage checks, test-report currency, laboratory accreditation and confidence threshold
No human action required
Stages 1 to 4 run unaided, and nothing is declared at any of them — the agent is assembling, and the specialist's lane opens at the confidence gate.
5DecisionBranches at the confidence threshold
High confidence
Goes to the product compliance specialist.
Low confidence
Adds a regulatory counsel read first.
Specialist approval
The file is held with its gaps, its expiry dates and the confidence.
Approve · Amend · Send to counsel
Approved — released to sign▼
6Product record updatedOnly where write access and approval policy allow it
7Outcome evaluatedRequirement coverage, document currency, filing reconciliation and post-signature corrections
Amendments
Specialist amendments are counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Signing or issuing the EU declaration of conformity.
Certifying that a product complies with a rule.
Determining that a change is a material change.
Affixing a CE or UKCA mark to a product or its label.
Automation boundaryAgent acts unaided
✓Line up the documents each destination market requires per product.
✓Check each test report for currency and accreditation.
✓Track the signatory, the function and the date on file.
✓Report the gaps that must close before a listing or a shipment goes.
Assembly is a fact about the file. The signature is a named person's, under sole responsibility.
Deciding which entity is the finished product certifier.
Judging whether a test report supports the certificate.
Filing certificate data with the customs entry.
Changes to market, requirement or approval rules.
Example output
One product file, annotated
What the agent records is attached to the document it came from.
Conformity output · single productIllustrative example
Product
What the file shows
Markets
Document on file
Confidence
Signature
Mains-powered lamp
Declaration on file, and a test report still inside its currency window
EU and Great Britain
Declaration of conformity
93%
Named person, stated function
As receivedTaken from the declaration and the test report as filed — nothing on this side is asserted by the agent.
Documents on fileEU declaration signedAccredited lab reportUK declaration on file
Why the signature is hereThe US rule is silent on a signature; the EU declaration is not, and names one.
ActionApproveAmendSend to counsel
What the score decidesBelow the configured threshold the file adds a counsel read before it reaches the specialist.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
Every product lineFrom the documents on file
03Assembly
Build the file from the documents
Draw on the certificates and declarations on file. A declaration that cannot be supported takes the presumption of conformity with it for the whole model, and the copy is retained ten years.
01Approved path
A document, not a belief
Coverage is read off the documents on file, not off a mark on the carton. GAO reported in January 2026 that no detailed plan yet covered overseeing that filing.
02Human review
The specialist the catalogue defers to
The catalogue agent copies certification fields from the documents on file; this one proves those documents exist, are current, and cover the market published into.
04Build an evidence trail
The product, the document it rests on and the person who signed stay on the file.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Product and PIMAkeneo · Salsify inRiver · Product records
A catalogue-wide document-coverage figure can look sound while one market absorbs most of the missing and expired documents. Nestack reports coverage by market, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Children's products, EU
8.5%
3.6×
Review
Private-label toys, GB
6.1%
2.6×
Review
Electrical goods, EU
3.8%
1.6×
Watch
US general-use goods
1.4%
0.6×
Normal
Bar: document-gap lift vs. US general-use baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
The loop closes on a new test
The loop shuts when the missing certificate is a regression case. That suite is what the next listing cleared is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
The document-gap rate rises in one market.
02Diagnose
The item that went live with a certificate field nobody could fill is read back until the cause narrows to one.
03Improve
Any change goes out numbered, with the products that caused it attached.
04Verify
One conformity case still failing is enough to hold the release back.
05Learn
One case joins the suite, one line joins the product record.
Learn → DetectThe return edge. The next detection is measured against a suite that just grew.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, file assembly, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Conformity file discovery and boundary definition.
02Supplier and test-house source assessment.
03Per-market requirement mapping and rule configuration.
04Product-record and document ingestion.
05File assembly and currency checking.
06Confidence scoring and gap-flag routing.
07Specialist approval workflow.
08PIM and certificate-store integration.
09Document and currency cases.
10Guardrails and declaration controls.
11Document-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne line, one marketProductionProduction conformity systemsAdvancedMultiple markets / brands
Introduced at Pilot
Assembly to your markets and rules✓✓✓
Specialist approval✓✓✓
Document-coverage baseline✓✓✓
Introduced at Production
Reporting by market—✓✓
Approval workflow in your systems—✓✓
Approved write-back—✓✓
Supplier-document integration—✓✓
Introduced at Advanced
Multi-regime requirement rules——✓
Multi-stage conformity approvals——✓
High product volume——✓
Multi-market conformity controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, transaction volume, approval controls and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01Your product records and market list→Product-record ingestion and document filingWeek 1
02Representative certificates and test reports→Coverage baseline, requirement binding and currency checksWeek 2
03Your per-market requirement rules→Per-market requirement mapping and rule configurationWeek 1
04Access to relevant APIs, feeds or exports→Supplier and test-house assessment, then integration setupWeek 2
05Listings you would not want pulled→Currency cases and the evaluation suiteWeek 4
06What no declaration may assume→Confidence scoring, gap routing, guardrails and approval controlsWeek 3
07A named compliance specialist to review files→Specialist approval workflow, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Each of these bands spans the weeks its phase honestly needs, which is why week five holds two.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Conformity workflow discovery, requirement mapping and the automation boundaryW2Supplier-document integration and the coverage baselineW3File assembly, currency logic and approval controlsW4Evaluation suite, currency checks and failure-mode testingW5PIM and entry-data integration, pilot products and targeted correctionsW6One product launch run under the compliance specialist, then Agent Care handover
Reading the bandA bar covers only the weeks its work is named in. The week 5 overlap is real, not padding.
At the end of W6Once the conformity file validates, Agent Care assumes the agent.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Retail AI agent
Build a conformity-file agent around the markets you sell into.
Show us your product records, your market list and your document store. The EU declaration is signed by a named natural person with a stated function, under the sole responsibility of the manufacturer, and the agent never signs it.
