Recommend from the attributes in your catalogue, hold to the review and disclosure rules you configured, and put a purchase to the shopper as its own authorisation the merchant can produce later.
In aggregate the disowned-order rate looks settled; by slice, a few session types carry most of it. Nestack reports the disowned-order rate by cohort, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Third-party agent surfaces
3.7%
3.4×
Review
Bundles and accessories
3.1%
2.8×
Review
New-launch product lines
2.2%
2.0×
Watch
Repeat reorders on file
1.0%
0.9×
Normal
Bar: disowned-order-rate lift vs. repeat-reorder baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
A cycle ends with a standing test
Explaining a bad recommendation does not close the cycle. A standing regression case does, and that suite is what the next session is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Disowned orders rise in one session slice.
02Diagnose
The named commerce owner opens the sessions and the cards behind them until one cause holds.
03Improve
The fix is versioned against the sessions that produced it.
04Verify
The release stops until every affected case is passing.
05Learn
The case stays in the suite, and the recommendation policy is amended.
Learn → DetectThe return edge. What comes next is measured against a longer suite.
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, recommendation workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Commerce workflow discovery and boundary definition.
02Catalogue, PIM and feed source assessment.
03Review, disclosure and price-rule configuration mapping.
04Catalogue ingestion and normalisation.
05Ranking logic and attribute binding.
06Confidence scoring and check routing.
07Shopper authorisation workflow.
08Commerce-platform and payment integration.
09Authorisation-path cases.
10Guardrails and purchase controls.
11Session-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 storefrontProductionProduction storefrontsAdvancedMultiple markets / stores
Introduced at Pilot
Ranking from your catalogue✓✓✓
Shopper authorisation✓✓✓
Recommendation-quality baseline✓✓✓
Introduced at Production
Reporting by category—✓✓
Authorisation flow in your systems—✓✓
Approved write-back—✓✓
Commerce-platform integration—✓✓
Introduced at Advanced
Multi-market disclosure sets——✓
Multi-storefront authorisation——✓
High session volume——✓
Multi-market storefront controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, session volume, authorisation 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 catalogue attributes and price-card structure→Catalogue ingestion and attribute mappingWeek 1
02Representative shopper sessions→Ranking baseline, attribute binding and comparison logicWeek 2
03Your review-handling and disclosure rules→Review, disclosure and price-rule mapping, and the boundaryWeek 1
04Access to relevant APIs, feeds or exports→Catalogue, PIM and commerce-platform assessment, then setupWeek 2
05Recommendations that should not have gone out→Authorisation cases and the evaluation suiteWeek 4
06Where a session must stop and ask the shopper→Confidence scoring, check routing, guardrails and purchase controlsWeek 3
07A named commerce owner to sign the rules→Shopper authorisation 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
Phases occupy the weeks the work really needs, so week 5 runs evaluation and launch side by side.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Commerce workflow discovery, rule mapping and the automation boundaryW2Catalogue integration and the ranking baselineW3Ranking workflow, confidence logic and purchase controlsW4Evaluation suite, review and disclosure checks, and failure-mode testingW5Payment integration, pilot sessions and targeted correctionsW6One trading period run under the commerce team, then handover
Reading the bandEach bar spans only the weeks its work is named in. The week 5 overlap is real work, not padding.
At the end of W6The period closes validation and Agent Care picks up the monitoring.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Electronics AI agent
Build a commerce agent around an authorisation you can produce.
Show us your catalogue, your disclosure rules and who owns them. If you cannot yet show what a shopper authorised, we start there — that question is unsettled.
