Measure each part order against the window Reg. (EU) 2023/1670 owed on the day it arrived, five working days and later ten, and leave the price and the impossibility call to a named person.
A part is ordered, and the window runs from receipt, inside a seven-year period counted from end of placement.
02
A part is ordered in year six, and ten working days is owed; the first five years of that period owed five.
Reason
03
A part is ordered by an end-user, and Reg. (EU) 2023/1670 sends only some part classes that far.
04
A passport is demanded in a tender, and no Digital Product Passport obligation binds an electronics product today.
05
Placement of the last unit ends, and operating-system and security updates are owed free for at least five years.
Decide
06
A source-code release lands, and a security update is owed in four months, a functionality update in six.
07
An order lands on a chain with no EU manufacturer, and Art. 5(3) walks the duty down to the seller.
Out
08
A repair information form is voluntary under Art. 4(1); once given, its price holds thirty calendar days.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
The agent holds the availability file and measures delivery against the owed window; a named person decides a repair is impossible, approves the price and signs the declaration.
Example workflow
One order, receipt to close
AgentHuman
1Part order receivedEnd-user request, professional repairer order or a service-network draw
2Availability file matchedModel, end-of-placement date, part class, audience and the window owed on the day of receipt
3Window recordedFive or ten working days, with the registration and access windows a professional repairer is owed
4Controls appliedClock checks, part-class checks, cascade checks and completeness confidence
No human action required
Stages 1 to 4 run unaided, and nothing is promised or priced at any of them — the agent is measuring, and the compliance lane opens at the completeness gate.
5DecisionBranches at the completeness gate
Window met
Goes to the product compliance lead to close.
Anything late or thin
Adds a regulatory counsel read first.
Product compliance review
The file is held with its clocks, its part classes and its gaps.
Close the order · Append evidence · Send to counsel
Closed — by a named person▼
6Parts and service records updatedOnly where write access and disclosure policy allow it
7Outcome evaluatedWindow margin, evidence completeness, counsel corrections and what a later review found
Corrections
Each counsel correction is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Deciding that a repair is impossible.
Approving a repair price, or any part of one.
Issuing or standing behind a repair information form.
Declaring a model conformant in EPREL.
Automation boundaryAgent acts unaided
✓Hold one availability file for each model and for each part class.
✓Run the owed window from receipt of the order.
✓Measure each actual delivery against the working-day window owed.
✓Flag the day the five-day window turns into ten.
Nothing is promised or priced except by a named person, inside the agreed boundaries.
Judging which party the Art. 5(3) cascade lands on.
Telling a customer a part class is out of scope.
Setting an operating-system support end date.
Changes to window rules, part classes or file fields.
Example output
One order, annotated
Directive (EU) 2024/1799 applied on 31 July 2026, and this file is what a person closes the order from.
Availability file · single orderIllustrative example
Order
Owed as
Clock
Window of record
Confidence
Held for
Display assembly, slate tablet
Display assembly to an end-user, year six of seven
Day 7 of ten working days
Reg. (EU) 2023/1670, Annex II B.1.1
Held unclosed
The product compliance lead, in person
As receivedTaken from the availability file and the order receipt — Art. 5 reaches only the Annex II product groups.
What the file holdsThe order receiptEnd-of-placement datePart class and audience
Why no price call hereA reasonable price is the Art. 5(2) test, and the Annex I form carries no signature block.
ActionClose the orderAppend evidenceSend to counsel
What the score decidesBelow the configured threshold the file picks up a counsel read before.
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 orderFrom the parts system
03Evidence
Statutory window, not service level
Warranty triage and field service own commercial repair; this is the window the rule owed, and take-back sits with our EEE producer agent.
01Approved path
The clock changes gear
Five working days for the first five years of the availability period, ten for the remaining two — Reg. (EU) 2023/1670, applying from 20 June 2025.
02Human review
Where the score and the seal live
The repairability class sits in energy-labelling Reg. (EU) 2023/1669, and an EPREL verification taken without a trade-register code expires 22 April 2027.
04Build an evidence trail
The part, the window it was owed in and the person who approved the repair 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.
Parts and service systemsERP parts master · spares Service-network order feeds
Product and lifecycle recordsPLM · model masters End-of-placement records
Registration and labellingEPREL model registrations Repairer registration portal
Agent
Repair obligation & parts
Reads the order Measures the window Holds for the lead
Repair and case systemsService tickets · RMA Repairer access requests
A model-level window-adherence figure can read clean while a single model line absorbs most of the corrections. Nestack reports the counsel-correction rate by model, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Models in the final two years
6.8%
3.7×
Review
Foldable and hinged models
5.0%
2.7×
Review
Current-generation handsets
3.1%
1.7×
Watch
Slate tablets in early years
1.8%
1.0×
Normal
Bar: counsel-correction-rate lift vs. early-year slate-tablet baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
What an unreconstructable file costs
A cycle closes when the missed delivery window is a regression case. That suite is what the next order measured is judged against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Counsel-correction rate rises in one model line.
02Diagnose
The part promised in five days by a clock that had already moved to ten is read back until one cause remains.
03Improve
Changes go out numbered, and the models that drove them ride along.
04Verify
One model case still failing keeps the release where it is.
05Learn
It joins the suite for good, and the window rules move in the same commit.
Learn → DetectThe return edge. The next order is measured 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, file assembly, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Repair-obligation discovery and boundary definition.
02Parts, PLM and service sources.
03Availability-window and part-class rule mapping.
04Order ingestion and file normalisation.
05Model, part-class and audience binding.
06Completeness scoring and counsel routing.
07Named-person close workflow.
08Parts and service-system integration.
09Window and availability cases.
10Guardrails and approval controls.
11Order-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 model line, one marketProductionProduction parts workflowAdvancedMultiple lines / markets
Introduced at Pilot
File assembly to your rules✓✓✓
Named-person close✓✓✓
Availability-period baseline✓✓✓
Introduced at Production
Reporting by model—✓✓
Close workflow in your systems—✓✓
Approved write-back—✓✓
Parts-system integration—✓✓
Introduced at Advanced
Multi-market repair duties——✓
Cross-model window packs——✓
High order volume——✓
Multi-market obligation 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 model masters and parts data→Order ingestion and part-class mappingWeek 1
02Representative orders and model files→File baseline, window binding and evidence captureWeek 2
03Your window rules and part classes→Window-rule, part-class and audience mapping and the automation boundaryWeek 1
04Access to relevant APIs, feeds or exports→Parts, PLM and service-record assessment, then integration setupWeek 2
05Orders you would not want promised→Window cases and failure testingWeek 4
06What no availability record may promise→Completeness scoring, counsel routing, guardrails and close controlsWeek 3
07A named product compliance lead to close→Named-person close 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 band is the honest length of its phase in working weeks, which is why one week carries two.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Repair-obligation discovery, window mapping and the automation boundaryW2Source integration and the availability baselineW3File assembly, window logic and close controlsW4Evaluation suite, window cases and failure-mode testingW5Parts-system integration, pilot orders and targeted correctionsW6One availability year run under the product compliance lead, then Agent Care handover
Reading the bandA bar covers only the weeks its own work is named in. The doubled fifth week is real work, not padding.
At the end of W6Once the availability file validates, Agent Care picks up the agent.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Electronics AI agent
Build a repair-obligation agent around a clock that changes gear mid-life.
Germany adopted its Reparaturgesetz on 26 June 2026, and the EUR-Lex implementing-measures list could not be read, so we publish no count of Member States that finished. Next step: send us one model file, and we will measure last month's orders against the window each was owed.
