Manufacturing AI agent · Procurement
Procurement & Supplier-Management AI Agent
Turn demand into requisitions and draft orders against live agreements, chase acknowledgements and dates, expedite shortages and reconcile receipts to invoices — a buyer with delegated authority commits the spend.
- Typical delivery
- 4–6 weeks
- Deployment
- Your stack
- Spend commit
- Buyer only
- After launch
- Agent Care
What this agent does
Prepares the order, does not place it
In
- 01
Take demand from MRP results, planned and firm orders, open requisitions and the stock on hand and on order.
- 02
Load the agreements, price conditions, lead times, approved sources per part and the vendor records they point at.
Reason
- 03
Match each demand line to a live agreement, its current price condition and a source approved for that part and process.
- 04
Check the vendor against the screening, qualification and change-notification status your supplier quality holds.
- 05
Read acknowledgements, ship notices and receipts against the order, and mark where a date or quantity disagrees.
Decide
- 06
Hold a line with no live agreement, an unapproved source or a screening hit for a buyer instead of drafting it.
- 07
Route a match exception or a disputed performance figure to the buyer or supplier-quality lead who owns it.
Out
- 08
Present a draft order, an expedite or a match exception with the agreement, the source and the dates behind it.
- 09
Retain the demand read, the agreement version, the screening result and every edit the buyer made.
Product statement
The agent prepares, chases and reconciles inside limits a buyer set. Committing spend, changing an agreement and approving a source stay with the people who hold that authority.
Example workflow
One demand line, end to end
- 1Demand line raisedAn MRP result, a planned order, a shortage called from the line or a requisition someone entered
- 2Position gatheredOn-hand and on-order stock, open orders, lead times, the vendor record and what the last receipts actually did
- 3Agreement and source checkedThe live agreement and price condition, the source approved for that part and process, and the vendor's screening date
- 4Order or expedite draftedQuantity, price, dates and terms taken from the agreement, with what the expedite costs elsewhere named
No human action required
Stages 1 to 4 run without a person in the loop — gathering, checking and drafting all finish before a buyer is asked to read anything. A line with no live agreement or an unapproved source ends that stretch on the spot.
Goes to the buyer as a draft order.
Held with what is missing for a person to decide.
Buyer or supplier-quality lead
Reads the draft, the agreement it rests on and the source it names, edits it, and commits the spend under their own authority.
Commit · Edit line · Send back
Committed — handed back
- 6Order made ready to sendSent to the supplier only after a buyer with delegated authority commits it; the agent sends nothing
- 7Outcome evaluatedOrder-to-agreement accuracy, approved-source correctness, date reliability, match exceptions and buyer edits
Edits
What the buyer changes on the draft is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required
8 items
- Committing spend or sending an order.
- Changing price, quantity or terms on an agreement.
- Approving, re-qualifying or de-listing a supplier.
- Naming a new source for a part.
Automation boundary
Agent acts unaided
- ✓Draft requisitions and orders against the live agreement and price.
- ✓Chase acknowledgements, dates and shortages, and record what came back.
- ✓Reconcile receipts and invoices to the order and raise the exception.
- ✓Assemble the sourcing or qualification pack with its evidence and its gaps.
The agent writes a draft, a chase and an exception. Sending the order and approving a source are not its to write.
- Clearing a restricted-party or export-control hit.
- Accepting a supplier process or sub-tier change.
- Closing a three-way match exception.
- Releasing an invoice for payment.
Example output
One drafted order line, annotated
Everything the agent proposes is attached to the demand, the agreement and the vendor record it was built from.
Procurement output · one demand line
Illustrative example- Demand line
- Bearing housing, 240 pcs
- Need date
- Week 34, line 2
- Agreement
- Rev 4, live
- Drafted
- Approved source, rev-4 price
- Confidence
- 91%
- Commit
- Not made by the agent
As received
The demand, the need date and the agreement it points at — read from the ERP, not inferred.
Evidence used
- Agreement rev 4, still live
- Approved for this process
- Vendor screened 11 days ago
Why this source
Two sources are approved for the part; only one for the heat treatment.
What the score decides
Confidence says how cleanly the line matched the agreement, not whether the price is right.
Action
CommitEdit lineSend backValue
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value lands
Value 01 – 04
Every demand line
MRP results, requisitions and shortages
Buy against your own agreements
Use the live agreement and price condition, the source approved for that part and that process, and the vendor's screening and qualification status.
Give the buyer a line already checked
Each draft arrives with the agreement version, the approved source and the dates behind it, so the buyer decides rather than assembles.
Put the held lines in front of a person
A part with no live agreement, a source approved for something else or a screening hit reaches a buyer as a held line, not as an order already sent.
Build an evidence trail
Retain the demand read, the agreement version, the screening result, the acknowledgement and the buyer's edit — on both paths.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
ERP & purchasing
- SAP MM
- Oracle
- Dynamics 365
- Infor
- Requisition and order records
Agreements & pricing
- Outline agreements
- price conditions
- Catalogues
- lead-time records
Supplier quality
- Qualification records
- approved sources
- Change notices
- scorecards
Agent
Procurement & supplier management
- Drafts the order
- Chases the dates
- Reconciles receipts
Screening & trade
- Restricted-party lists
- sanctions
- Export classification
- audit trail
Observability & evaluation
- OpenTelemetry
- Langfuse
- Supported monitoring/evaluation sources
Integration availability depends on the client's existing systems and API access.
Agent controls
Six layers between the model and the order
Each control wraps the one inside it. A draft clears every layer before a buyer sees it, and the commit sits outside all six.
L6 · Outermost — last line of defence
Inward → L1 · closest to the model
- L1 – L2
- Decide whether a line may be drafted at all
- L3
- Stops a vendor the screening flagged
- L4 – L5
- Keep the commit with a buyer, trail intact
- L6
- Pulls automation back when signals degrade
How Nestack evaluates it
Evaluate the whole buy — not only the order it drafts.
Coverage runs the whole depth of the workflow, and every layer is cut by slice.
Surface — the draft the buyer opens
- E1Final-output evaluationDid the drafted line match the live agreement and its price?
- E2Step-level evaluationDid it read the right agreement version and approved source?
- E3Tool evaluationDid it read the right vendor, part, order and receipt records?
- E4Screening coverageWere new and changed vendors screened before a draft was made?
- E5Slice evaluationHow does accuracy hold across supplier tier and spend band?
- E6Business outcomeHow many orders needed a buyer's correction or a credit note?
Floor — the parts that arrive on the dock
Failure modes
Where each failure originates in the agent
Seven failure modes plotted against the five stages of the agent lifecycle. None of them sends an order, changes an agreement or approves a supplier — the buyer's delegated authority, supplier quality's approved-source list and your own purchasing controls are what stop them. If one gets through and the parts are already on the dock, the demand, the agreement version, the screening result and the acknowledgement held in the record are what the containment, the quarantine and the supplier notification are built from.
Agent lifecycle
Direction of processing →
01 · Retrieval
1 mode
- SU-01
Order on a superseded agreement
Price and terms taken from a version no longer live.
Stage gathers
Demand, stock, agreements and vendor records
02 · Source check
2 modes
- SU-02
Source approved for something else
The vendor is approved, but not for that part or process.
- SU-03
Screening hit missed on a new vendor
A restricted-party or ownership match nobody ran.
Stage checks
Approved sources, qualification and screening
03 · Drafting
1 mode
- SU-04
Expedite that creates the next shortage
One line pulled in, the material behind it pushed out.
Stage drafts
The order line, its price, dates and terms
04 · Follow-up
2 modes
- SU-05
Match closed on a short receipt
Three lines agreed against a delivery that was wrong.
- SU-06
A score the supplier can disprove
Late dates counted against the supplier's own evidence.
Stage chases
Acknowledgements, receipts and invoice matches
05 · Change / Version
1 mode
- SU-07
Supplier change never notified
A process or sub-tier moved and no duty was enforced.
Stage tracks
Agreement, price, vendor and configuration changes
- Sev-1 · a purchasing control is bypassed
- Sev-2 · the plant commits on a wrong figure
- Sev-3 · buyers stop trusting the drafts
Affected slices
A first order is not a repeat buy
A part on a two-year-old agreement has a price, a source and a lead time everyone already agrees on. A first order from a supplier approved last month has none of that. Nestack reports performance by slice, not only in total.
Slice performance — reported separately, not only in aggregate
Illustrative example| Slice | Failure rate | Lift | Lift vs. threshold | Status |
|---|---|---|---|---|
| New suppliers, first orders | 7.0% | 3.9× | Review | |
| Single-source parts | 5.4% | 3.0× | Review | |
| Off-agreement spot buys | 3.4% | 1.9× | Watch | |
| Settled agreement, repeat part | 1.4% | 0.8× | Normal |
Bar: buyer-correction-rate lift vs. settled-agreement baseline · scale 0–4.0× · tick marks 2.0×
2 of 4 slices over threshold
Evidence-linked improvement
Every buyer edit says which record was stale
What the buyer edited, and what goods-in actually booked, come back as agreement corrections and match rules the next order has to respect.
Improvement cycle · five stages
Switchback — the path turns at Improve and returns at Learn
- 01
Detect
Buyer edits climb, or match exceptions concentrate on one supplier, part or spend band.
- 02
Diagnose
Traced to a stale agreement version, an approved-source record, a screening gap or a lead time nobody updated.
- 03
Improve
The agreement record, source rule or screening trigger changes under your purchasing controls, with a named owner.
- 04
Verify
Replayed against the orders that went wrong, including every line a buyer sent back.
- 05
Learn
The corrected rule becomes a standing check, and the stale agreement goes back to whoever owns that contract.
Learn → Detect
The return edge. A supplier's process or sub-tier change is not the agent's to accept — it goes to supplier quality, and the parts already bought against the old process are identified from the record.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, agreements and access, drafting and the source and screening gates, evaluation, then parallel running and handover.
Workstream
Week 1Week 2Week 3Week 4Week 5Week 6
- 01Purchasing-workflow discovery and boundaries.Week 1
- 02Agreement, price-condition and catalogue review.Week 1, Week 2
- 03ERP, requisition and receipt access assessment.Week 1, Week 2
- 04Approved-source and qualification-record mapping.Week 2, Week 3
- 05Demand, stock and open-order ingestion.Week 2
- 06Draft requisition and purchase-order preparation.Week 3, Week 4
- 07Restricted-party screening triggers and holds.Week 3
- 08Acknowledgement and date-chasing workflow.Week 4
- 09Receipt, invoice and match-exception rules.Week 4, Week 5
- 10Scorecard and change-notification tracking.Week 5
- 11Evaluation suite and replayed bad orders.Week 4, Week 5
- 12Buyer review, deployment and Agent Care handover.Week 6
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallel
Final 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 tier | PilotOne category, one plant | ProductionProduction ERP integration | AdvancedMulti-site / multi-category |
|---|---|---|---|
| Introduced at Pilot | |||
| Draft orders against live agreements | ✓ | ✓ | ✓ |
| Approved-source check on every line | ✓ | ✓ | ✓ |
| The agreement and source shown with each draft | ✓ | ✓ | ✓ |
| Spend committed by a buyer | ✓ | ✓ | ✓ |
| Baseline evaluation | ✓ | ✓ | ✓ |
| Introduced at Production | |||
| Restricted-party screening on new vendors | — | ✓ | ✓ |
| Acknowledgement and delivery-date chasing | — | ✓ | ✓ |
| Receipt, invoice and match-exception handling | — | ✓ | ✓ |
| Observability and evaluation | — | ✓ | ✓ |
| Introduced at Advanced | |||
| Scorecards and change-notification tracking | — | — | ✓ |
| Multi-site and enterprise controls | — | — | ✓ |
| Build price | From $5,000 | From $8,000 | Custom quote |
- Final build price
- Confirmed after discovery based on categories and plants in scope, the state of your agreement and approved-source records, ERP and supplier-quality integrations, screening requirements and deployment requirements.
- Separate from build
- Build 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 bring
We build with it
01Your agreements and price conditions, with the versions that are actually live
→Agreement, price-condition and catalogue review
Week 102Access to ERP requisitions, orders, receipts and vendor records
→ERP, requisition and receipt access assessment
Week 203The approved-source list per part, as supplier quality holds it today
→Approved-source and qualification-record mapping
Week 304Your delegated-authority matrix — who may commit what, and up to what
→Draft preparation and the buyer commit workflow
Week 305How you screen a vendor today, and who clears a hit when one lands
→Restricted-party screening triggers and holds
Week 306The orders that went badly — wrong price, wrong source, short receipts
→Evaluation suite, replayed bad orders and failure-mode testing
Week 407Named buyers who commit spend today
→Buyer review workflow, then parallel running
Weeks 5–6
Nothing else is required
Deployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Phases are drawn over the weeks they actually occupy. Week 5 carries both the replayed bad orders and the first drafts your buyers commit from.
Phase
W1
W2
W3
W4
W5
W6
- DiscoveryW1
- BuildW2 – W3
- EvaluateW4 – W5
- Pilot & LaunchW5 – W6
Week focus
W1Purchasing-workflow discovery, agreements and price conditions
W2ERP and receipt access, then demand, stock and open orders
W3Approved-source mapping, screening holds and draft preparation
W4Evaluation suite, date chasing and match-exception rules
W5Replayed bad orders, first parallel drafts and scorecard checks
W6Your buyers commit from the agent's drafts, then Agent Care starts
- Reading the band
- The approved-source and screening gates are built in week 3, before a draft reaches a buyer in week 5. A line that clears neither is not a draft — it is a hold with a name on it.
- At the end of W6
- The agent has prepared and chased alongside your existing purchasing method, and every order it drafted has been committed by a buyer holding the authority to commit it, then Agent Care takes over monitoring.
- Duration
- Six-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Manufacturing AI agent
Build a procurement agent around your own agreements.
Show us one category, the agreements and approved sources behind it, and a quarter of orders that went wrong — the off-agreement buys, the short receipts and the expedites. We'll re-draft those lines against your own agreement versions, report where the price and the source record no longer matched, and show you the order a buyer would commit.
- Typical delivery
- 4–6 weeks
- Deployment
- Your purchasing stack
- Spend commit
- A buyer, always
- After launch
- Agent Care available
Nestack Agents · Procurement & supplier management
AGT-MFG-04 · Agent Care available after launch