Map each product to its raw inputs before the order is placed, register each document with where it came from, and hold the pack for the named person who signs the importer statement.
A programme-level tier-coverage figure can read well while a few raw inputs carry nearly all of the unevidenced tiers. Nestack reports coverage by input, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Cotton and yarn tiers
9.4%
3.7×
Review
Polysilicon and cell tiers
6.8%
2.7×
Review
Aluminium and casting tiers
4.6%
1.8×
Watch
Single-tier finished goods
2.2%
0.9×
Normal
Bar: unevidenced-tier lift vs. single-tier baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
No cycle closes without a new case
A cycle is done when the unevidenced tier has become a case the next release must pass. That suite is what the next pack built is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
The unevidenced-tier rate rises for one raw input.
02Diagnose
The mill two steps past the supplier who answered is read back until the cause narrows to one.
03Improve
Number the change; the shipments that drove it are filed under it.
04Verify
Each touched tier case is run once more, and one red holds it back.
05Learn
It stays as a standing test, and the provenance rules move with it.
Learn → DetectThe return edge. Every later detection meets a suite that grew 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, pack assembly, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Import workflow discovery and boundary definition.
02Sourcing, PO and traceability assessment.
03Sector document checklist and provenance mapping.
04Order and supplier-response ingestion.
05Chain mapping and document registration.
06Confidence scoring and gap routing.
07Reviewer approval workflow.
08Purchase-order and broker integration.
09Tier and provenance cases.
10Guardrails and submission 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 product lineProductionProduction import systemsAdvancedMultiple categories / entities
Introduced at Pilot
Mapping to your orders and tiers✓✓✓
Reviewer approval✓✓✓
Tier-coverage baseline✓✓✓
Introduced at Production
Reporting by input—✓✓
Approval workflow in your systems—✓✓
Approved write-back—✓✓
Purchase-order integration—✓✓
Introduced at Advanced
Multi-sector checklist rules——✓
Multi-stage trade approvals——✓
High import volume——✓
Multi-tier evidence 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 purchase-order and vendor record structure→Order ingestion and supplier mappingWeek 1
02Representative supplier responses and documents→Chain-mapping baseline, document registration and provenance markingWeek 2
03Your sector document checklist and approved sources→Sector document checklist and provenance-rule mappingWeek 1
04Access to relevant APIs, feeds or exports→Sourcing, PO and traceability assessment, then integration setupWeek 2
05Packs you would not want detained→Document-provenance cases and failure testingWeek 4
06What no pack may pass off as proof→Confidence scoring, gap routing, guardrails and approval controlsWeek 3
07A named trade compliance lead to review packs→Reviewer 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 chart is laid out in worked weeks, not in slide inches, and that is why the fifth one doubles.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Import workflow discovery, checklist mapping and the automation boundaryW2Source integration and the chain-mapping baselineW3Pack assembly, confidence logic and approval controlsW4Evaluation suite, provenance checks and failure-mode testingW5Broker integration, pilot packs and targeted correctionsW6One import season run under the trade compliance lead, then Agent Care handover
Reading the bandEach bar sits only on the weeks its work is named in. The week 5 overlap is real, not padding.
At the end of W6When the pack validates, Agent Care takes the agent on.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Retail AI agent
Build an import-evidence agent around your sourcing calendar.
Show us your purchase orders, your tier map and who signs the consignee statement. The pack has to survive an officer reading it cold, which is why it is built before the order ships — this is pre-import prevention, not detention rescue.
