Retail AI agent · Conformity documents
Product-Conformity Documentation AI Agent
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.
- Typical delivery
- 4–6 weeks
- Deployment
- Your stack
- Named signer
- Per market
- After launch
- Agent Care
What this agent does
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
- 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.
Goes to the product compliance specialist.
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 required
8 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 boundary
Agent 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 product
Illustrative example- Product
- Mains-powered lamp
- What the file shows
- Declaration on file, and a test report still inside its currency window
- Markets
- EU and Great Britain
- Document on file
- Declaration of conformity
- Confidence
- 93%
- Signature
- Named person, stated function
As received
Taken from the declaration and the test report as filed — nothing on this side is asserted by the agent.
Documents on file
- EU declaration signed
- Accredited lab report
- UK declaration on file
Why the signature is here
The US rule is silent on a signature; the EU declaration is not, and names one.
What the score decides
Below the configured threshold the file adds a counsel read before it reaches the specialist.
Action
ApproveAmendSend to counselValue
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value lands
Value 01 – 04
Every product line
From the documents on file
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.
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.
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.
Build 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 PIM
- Akeneo
- Salsify
- inRiver
- Product records
Supplier documents
- Supplier document portals
- Certificate stores
Testing and certification
- SGS
- Intertek
- TUV
- Bureau Veritas
Agent
Product-conformity documentation
- Reads the file
- Checks the currency
- Holds for the signer
Customs and entry
- ACE filing feeds
- Entry line data
Observability & evaluation
- OpenTelemetry
- Langfuse
- Supported monitoring/evaluation sources
Integration availability depends on the client's existing systems and API access.
Agent controls
Six layers between the model and the signature
The six read outward to inward. What none of them stops is set out in the map below.
L6 · Outermost — last line of defence
Inward → L1 · closest to the model
- L1 – L2
- Test whether a file may stand
- L3
- Puts the release in a specialist's hands
- L4 – L5
- Keep the product and the document behind it
- L6
- Reverts to conformity-file assembly when signals degrade
How Nestack evaluates it
Evaluate the whole assembly — not only the finished file.
Coverage runs the whole depth of the workflow, and every layer is cut by slice.
Surface — the file the specialist reads
- E1Final-output evaluationDid each document on file match the requirement it is filed against?
- E2Step-level evaluationDid the agent use the right market list, rules and product record?
- E3Tool evaluationDid it read and write the correct product and the correct market?
- E4Confidence calibrationDo low-confidence files actually attract more specialist amendments?
- E5Slice evaluationHow does performance change across specific markets and product types?
- E6Business outcomeHow many files needed an amendment or a correction after signature?
Floor — the outcome the signer answers for
Failure modes
Where each failure originates in the agent
Seven failure modes, each placed where in the lifecycle it starts.
Agent lifecycle
Direction of processing →
01 · Retrieval
1 mode
- GS-03
Hand-written model number
A model designation is read off a scanned report by hand.
Stage gathers
Product records, supplier documents and market lists
02 · Reasoning
2 modes
- GS-04
Mark taken as evidence
A CE mark on a spec sheet stands in for the declaration.
- GS-06
Interval without predicate
A longer testing interval is claimed without its predicate.
Stage proposes
Requirements, documents on file and confidence
03 · Tool / write
2 modes
- GS-02
Identifier mismatch at entry
Certificate and entry line carry different identifiers.
- GS-05
Stale signature carried
A template reissues a signatory who has left.
Stage writes
Only where write access and approval policy allow it
04 · Output
1 mode
- GS-01
Populated but withdrawn
A cited standard is present though its version has lapsed.
Stage returns
The file the specialist reads and signs against
05 · Change / Version
1 mode
- GS-07
Silent requirement regression
A model or rule change narrows what is asked for.
Stage tracks
Model, prompt, requirement rules and market config
- Sev-1 · agent acts outside the boundary
- Sev-2 · a wrong file reaches the signer
- Sev-3 · source degrades, file routes to review
Affected slices
One market can carry nearly all the gaps
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 aggregate
Illustrative 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 threshold
2 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 stages
Switchback — the path turns at Improve and returns at Learn
- 01
Detect
The document-gap rate rises in one market.
- 02
Diagnose
The item that went live with a certificate field nobody could fill is read back until the cause narrows to one.
- 03
Improve
Any change goes out numbered, with the products that caused it attached.
- 04
Verify
One conformity case still failing is enough to hold the release back.
- 05
Learn
One case joins the suite, one line joins the product record.
Learn → Detect
The 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.
Workstream
Week 1Week 2Week 3Week 4Week 5Week 6
- 01Conformity file discovery and boundary definition.Week 1
- 02Supplier and test-house source assessment.Week 1, Week 2
- 03Per-market requirement mapping and rule configuration.Week 1, Week 2
- 04Product-record and document ingestion.Week 2
- 05File assembly and currency checking.Week 2, Week 3
- 06Confidence scoring and gap-flag routing.Week 3
- 07Specialist approval workflow.Week 3, Week 4
- 08PIM and certificate-store integration.Week 5
- 09Document and currency cases.Week 4, Week 5
- 10Guardrails and declaration controls.Week 4
- 11Document-trail instrumentation.Week 5, Week 6
- 12Deployment, documentation and Agent Care handover.Week 6
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallel
Final 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 tier | PilotOne line, one market | ProductionProduction conformity systems | AdvancedMultiple 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 price | From $5,000 | From $8,000 | Custom quote |
- Final build price
- Confirmed after discovery based on integrations, workflow complexity, transaction volume, approval controls and deployment requirements.
- Separate from build
- Build 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 bring
We build with it
01Your product records and market list
→Product-record ingestion and document filing
Week 102Representative certificates and test reports
→Coverage baseline, requirement binding and currency checks
Week 203Your per-market requirement rules
→Per-market requirement mapping and rule configuration
Week 104Access to relevant APIs, feeds or exports
→Supplier and test-house assessment, then integration setup
Week 205Listings you would not want pulled
→Currency cases and the evaluation suite
Week 406What no declaration may assume
→Confidence scoring, gap routing, guardrails and approval controls
Week 307A named compliance specialist to review files
→Specialist approval workflow, then pilot and production validation
Weeks 5–6
Nothing else is required
Deployment, 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.
Phase
W1
W2
W3
W4
W5
W6
- DiscoveryW1
- BuildW2 – W3
- EvaluateW4 – W5
- Pilot & LaunchW5 – W6
Week focus
W1Conformity workflow discovery, requirement mapping and the automation boundary
W2Supplier-document integration and the coverage baseline
W3File assembly, currency logic and approval controls
W4Evaluation suite, currency checks and failure-mode testing
W5PIM and entry-data integration, pilot products and targeted corrections
W6One product launch run under the compliance specialist, then Agent Care handover
- Reading the band
- A bar covers only the weeks its work is named in. The week 5 overlap is real, not padding.
- At the end of W6
- Once the conformity file validates, Agent Care assumes the agent.
- Duration
- Six-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.
- Typical delivery
- 4–6 weeks
- Deployment
- Your product and document store
- Named signer
- Per market
- After launch
- Agent Care available
Nestack Agents · Product-conformity documentation
AGT-RT-17 · Agent Care available after launch