Trace the packaging you place on each market to a weight and a source, put the producer question against the definition each jurisdiction writes, and hand the person who registers a dated file.
A pack spec changes, and the component weights and materials come across from the catalogue with their records.
02
A material is mapped to the category list the receiving programme actually publishes.
Reason
03
A carton reaches a market, and shipment volumes carry it through to a weight.
04
A brand licence moves, and the producer question is put again for that state.
05
A returned pack, a sample and a transport pallet each carry a stated treatment, not an assumption.
Decide
06
A registration falls due, and the route you intend to use is tracked.
07
An exemption is claimed by a person, and it is a registration.
Out
08
A German material threshold comes into view mid-year, not in April against an unextendable 15 May.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
The agent assembles the producer file; a named person registers and submits it, and in Germany a registered auditor signs the producer declaration with a qualified electronic signature by an unextendable 15 May.
Example workflow
One material, catalogue to filing
AgentHuman
1Packaging record receivedBill of materials, pack specification, shipment volumes or supplier data
2Producer question testedLegal entity, brand licence, market of supply and the definition that jurisdiction writes
3Tonnage builtWeight by material category, its provenance and confidence
4Controls appliedPer-programme category lists, exclusion treatments, deadline status and confidence threshold
No human action required
Stages 1 to 4 run unaided, and nothing is registered or reported at any of them — the agent is assembling, and the filer's lane opens at the confidence gate.
5DecisionBranches at the confidence threshold
High confidence
Goes to the named filer to read.
Low confidence
Adds an EPR counsel read first.
Filer review
The line is held with the definition it was tested against, its evidence and the confidence.
Approve · Amend · Send to counsel
Approved — released to file▼
6Packaging records updatedOnly where write access and approval policy allow it
7Outcome evaluatedTonnage provenance, definition outcomes, deadline status and post-submission restatements
Amendments
Filer amendments are counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Deciding producer status for a jurisdiction.
Registering with a programme, a PRO or a register.
Submitting a supply or source-reduction report.
Signing a German declaration of completeness.
Automation boundaryAgent acts unaided
✓Test each material against the definition that jurisdiction writes.
✓Trace weight by material category to the record behind it.
✓Hold the methodology note the receiving body will test.
✓Track each deadline with its status and the day it was last checked.
Assembly is a computation against a rule. Registration and reporting are a named person's acts.
Taking an exemption or small-producer position.
Appointing an EU authorised representative.
Choosing which compliance route to use.
Changes to definition, category or approval rules.
Example output
One material line, annotated
What the agent assembles is attached to the record it was drawn from.
Producer-file output · single materialIllustrative example
Material
What the record shows
Jurisdiction
Definition applied
Confidence
Filing route
Corrugated shipper
Ships the online order and is discarded by the household that receives it
California
Cal. Pub. Res. Code §42041(w)
93%
PRO membership on file
As receivedTaken from the bill of materials and the shipment record — nothing on this side is decided by the agent.
Evidence behind the tonnageComponent weight on fileShipment volume recordBrand licence in force
Why this definitionCalifornia runs a three-step test, and this entity owns the brand in the state.
ActionApproveAmendSend to counsel
What the score decidesBelow the configured threshold the material adds a counsel read before it reaches the filer.
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
The packaging in scopeFrom the bill of materials
03Provenance
Build the tonnage from records
Draw on the component weights and shipment volumes on file, mapped to each programme's own category list. California revised its own cost estimate inside one rulemaking by changing a single waste-tonnage input — two measurements of one quantity, not two points on a trend.
01Approved path
Producer means eight things
California runs a three-step hierarchy at PRC §42041(w) and Washington a flat brand-owner test at RCW 70A.208. Oregon has been enjoined since 6 February 2026 only as against companies that were NAW members that day.
02Human review
Where the catalogue stops
The catalogue agent holds per-SKU attributes; the inventory-forecast agent holds quantities sold. This one holds what was placed on a market under a legal definition — and a tonnage filed too low returns as a restated submission and a recalculated invoice.
04Build an evidence trail
The material, the definition it was tested against and the person who filed stay on the record.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Product and packaging dataAkeneo · Salsify · PIM SAP · Stibo · Spec systems
A jurisdiction-level tonnage-provenance figure can look sound while one programme absorbs most of the lines no record supports. Nestack reports provenance by programme, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Programmes under injunction
8.9%
3.6×
Review
Newly effective programmes
6.5%
2.7×
Review
Flexible and composite materials
4.1%
1.7×
Watch
Rigid single-material packs
1.8%
0.7×
Normal
Bar: provenance-gap lift vs. rigid single-material baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
A cycle is not closed until a test exists
The loop shuts when the missed registration is a regression case. That suite is what the next report filed is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
The provenance-gap rate rises in one programme.
02Diagnose
The same carton, and two states disagreeing about who owns it, is read back through the licence and the entity until the cause narrows to one.
03Improve
Any change ships with a number, and the programmes attach to it.
04Verify
One programme case still failing is enough to hold the release.
05Learn
One case joins the suite, one line joins the material record.
Learn → DetectThe return edge. The next detection runs against a suite that has grown by one case.
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, tonnage workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Producer-file discovery and boundary definition.
02Catalogue and shipment source assessment.
03Per-jurisdiction definition and category mapping.
04Packaging-record ingestion and matching.
05Tonnage build and provenance binding.
06Confidence scoring and exception routing.
07Filer review workflow.
08Catalogue and shipment integration.
09Definition and tonnage cases.
10Guardrails and filing controls.
11Material-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 programme, one entityProductionProduction packaging systemsAdvancedMultiple markets / entities
Introduced at Pilot
Tonnage to your programmes and rules✓✓✓
Filer review✓✓✓
Tonnage-provenance baseline✓✓✓
Introduced at Production
Reporting by programme—✓✓
Approval workflow in your systems—✓✓
Approved write-back—✓✓
Packaging-spec integration—✓✓
Introduced at Advanced
Multi-entity rule configuration——✓
Multi-stage compliance approvals——✓
High material volume——✓
Multi-jurisdiction producer 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 packaging specs and the entities in scope→Packaging-record ingestion and material mappingWeek 1
02Representative pack specifications→Provenance baseline, tonnage build and evidence bindingWeek 2
03Your per-jurisdiction definition and category rules→Per-jurisdiction definition and category mappingWeek 1
04Access to relevant APIs, feeds or exports→Catalogue and shipment assessment, then integration setupWeek 2
05Filings you would not want audited→Definition cases and failure-mode testingWeek 4
06What no submitted tonnage may estimate→Confidence scoring, exception routing, guardrails and approval controlsWeek 3
07A named person to register and report→Filer review 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
A band is exactly the weeks its own phase eats, which is the reason week five is not one but two.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Producer-file discovery, definition mapping and the automation boundaryW2Catalogue and shipment integration and the provenance baselineW3Tonnage workflow, confidence logic and approval controlsW4Evaluation suite, deadline-status checks and failure-mode testingW5Portal and register integration, pilot programmes and targeted correctionsW6One programme year run under the packaging lead, then Agent Care handover
Reading the bandEach bar spans the weeks its work is named in, and nothing else. The week 5 overlap is real, not padding.
At the end of W6Once the programme year validates, Agent Care assumes the running agent.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Retail AI agent
Build a packaging EPR agent around the person who registers and reports.
Show us your pack specs, your markets and the person who registers. Which of your published dates are real today — Maine ran a stewardship-organisation RFP that closed with no proposals on 18 August 2026, so its dates wait on a contract nobody has signed.
