Collect the installation and embedded-emissions data your EU importer's declaration rests on, chase the returns, check each method against the last cycle, and hold the pack for your sustainability lead.
A group-level return rate can look complete while a few installations account for most of the amendments. Nestack reports the amendment rate by slice, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
First-cycle steel suppliers
9.1%
3.7×
Review
Scrap-bearing aluminium routes
7.3%
3.0×
Review
Tier 2 below the value-chain cap
4.1%
1.7×
Watch
Established installations
2.2%
0.9×
Normal
Bar: amendment-rate lift vs. established-installation baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
The loop closes on the boundary case
A cycle closes when the inconsistent boundary is a case the next release has to catch. That suite is what the next pack returned is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Amendment rate rises in a supplier slice.
02Diagnose
The mill that sent a number with no boundary attached is read back until one cause remains.
03Improve
The correction ships numbered, with the supplier returns that prompted it attached.
04Verify
Nothing ships while a touched boundary case is failing; it runs until it clears.
05Learn
It is kept as a standing case, and the method rules are revised alongside.
Learn → DetectThe return edge. The next pack is assembled against a suite one case longer.
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, collection workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Reporting discovery and boundary set and boundary definition.
02Installation and supplier assessment.
03Boundary, method and template mapping and rule mapping.
04Return ingestion and normalisation.
05Collection logic and evidence binding.
06Confidence scoring and gap routing.
07Sustainability lead approval.
08Reporting-system integration.
09Boundary and method cases.
10Guardrails and return controls.
11Pack-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 installation, one goodProductionProduction reporting systemsAdvancedMultiple sites / schemes
Introduced at Pilot
Collection to your boundary and rules✓✓✓
Lead approval✓✓✓
Supplier-return baseline✓✓✓
Introduced at Production
Reporting by installation—✓✓
Approval workflow in your systems—✓✓
Approved write-back—✓✓
Energy-and-process data integration—✓✓
Introduced at Advanced
Multiple schemes and boundaries——✓
Multi-stage reporting approvals——✓
High supplier volume——✓
Multi-scheme reporting 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 installation list and product routes→Return ingestion and boundary mappingWeek 1
02Representative supplier returns→Collection baseline and evidence bindingWeek 2
03Your monitoring plan and method rules→Boundary, method and template mappingWeek 1
04Access to relevant APIs, feeds or exports→Installation and supplier assessment, then integration setupWeek 2
05Figures you would not want verified→Verification cases and the evaluation suiteWeek 4
06What no emissions figure may hide→Confidence scoring, gap routing, guardrails and return controlsWeek 3
07A named sustainability lead to approve→Lead 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
The bands follow the data-collection season, which is why the fifth week carries both.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Reporting discovery, method mapping and the automation boundaryW2Installation integration and the collection baselineW3Collection workflow, confidence logic and approval controlsW4Evaluation suite, boundary and method checks and failure-mode testingW5Supplier integration, pilot returns and targeted correctionsW6One reporting year assembled under the sustainability lead, then handover
Reading the bandEach band covers only the weeks its work is named in. The week 5 overlap is real, not padding.
At the end of W6Validation closes on live packs and Agent Care picks up monitoring.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Manufacturing AI agent
Build an emissions-data agent around the pack your importer declares from.
Show us your installations, your EU customers and who signs the pack. The declarant who files is your importer, established in the Union; what you owe is contractual, owed to them.
