Lay the supplier acknowledgement against the order it answers, show which terms differ and what UCC § 2-207 does with the difference, then hold the pair unmatched for the purchasing lead.
An order is raised, sent, and later met by the receipt and the invoice that answer it.
02
An acknowledgement arrives, and each term that differs is put beside the order term it displaces.
Reason
03
An order for goods meets UCC § 2-207, which forms a contract but not one on your terms.
04
An acknowledgement conflicts, and the majority knock-out rule kills both clauses, leaving Code defaults.
05
An addition is non-material, and between merchants § 2-207(2) lets it in on silence rather than assent.
Decide
06
An acknowledgement is also a confirmation, and § 2-201(2) gives ten days to object in writing.
07
An order buys services, so Article 2 is out and the last-shot rule hands the supplier the lot.
Out
08
An order crosses a border, and CISG Article 19 may govern the answer unless the contract excluded it.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
Raising, sending and comparing belong to the agent. Matching belongs to a named purchasing lead, who accepts the terms that survived and owns them there.
Example workflow
One order, raised to reconciled
AgentHuman
1Requisition receivedApproved requisition, contract terms, catalogue entry or price record
2Order raised and sentThe line items, the quantity, the delivery terms and the buying terms the order carries on its face
3Acknowledgement read against itEach term that differs, what it displaces and what the difference does
4Controls appliedConflict checks, materiality checks, governing-law checks and matching confidence
No human action required
Stages 1 to 4 run unaided, and nothing is matched at any of them — the agent is comparing, and the buyer lane opens at the conflict gate.
5DecisionSplits at the conflict gate
Acknowledgement agrees
Goes to the purchasing lead to match.
Anything conflicting
Adds a legal read first.
Purchasing review
The pair is held with the order as sent, the answer as received and the terms that differ.
Match · Object · Send to terms review
Matched — by the purchasing lead▼
6Purchasing and payables records updatedOnly where write access and records policy allow it
7Outcome evaluatedConflict coverage, objection timing, lead corrections and what the read found
Corrections
Each correction made in review is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Accepting an acknowledgement that differs.
Waiving a term the purchase order carried.
Committing the company to a supplier form.
Ruling a term conflict immaterial.
Automation boundaryAgent acts unaided
✓Raise the order and send it on your own terms.
✓Read the acknowledgement against the order it answers.
✓Set out each differing term beside the order term it displaces.
✓Hold the pair unmatched and name the clock that has started running.
Nothing is matched except by a named purchasing lead, inside the boundaries agreed.
Deciding whose terms govern a disputed order.
Telling a supplier the order stands as sent.
Choosing the law an order is bought under.
Changes to order templates or matching rules.
Example output
One order and its answer, annotated
Our manufacturing supplier agent commits orders against live prices and approved sources; this record is what happens after the supplier answers, and whose terms survived.
Order and acknowledgement · single pairIllustrative example
Order
Recorded as
Supplier
Evidence of record
Confidence
Held for
Direct materials, one delivery
Answered with differing terms
Terms compared, not matched
Supplier acknowledgement, 3 August 2026
Held unmatched
The purchasing lead, by name
As receivedRead off the order as sent and the acknowledgement as received, and it claims nothing past those two.
What the record holdsThe order as sentThe acknowledgementThe conflict list
Why no match hereMarking this pair matched is a legal act a purchasing lead owns.
ActionMatchObjectSend to terms review
What the score decidesAbove the configured threshold the pair collects a legal read before the lead sees it.
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 supplier that answered
03Evidence
Where the evidence is used
Where a pair was matched wrongly and the goods have already shipped, the lead objects in writing, the pair reopens with its comparison attached, and the case joins the suite.
01Approved path
Your form probably lost
Send the order first and it still may not govern: for goods the conflicting clauses fall away on both sides, and outside Article 2 the last form sent before performance takes the lot.
02Human review
What was checked, and not found
No statute or regulation examined obliges an ordinary private company to run a three-way match: FAR 44.3 and DFARS 252.244-7001 reach federal contractors and their subcontractors, and Sarbanes-Oxley asks for a management assessment of internal control over financial reporting rather than for any named procurement control. Article 2 asks a buyer for no signature, no certification, no filing and no retention period, and the 2022 amendments leave § 2-207 untouched. So the match is a control this page treats as a control, and the exposure it is run against is silence.
04Build an evidence trail
The order, the acknowledgement against it and the terms that survived stay together.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
A form-level conflict figure can read clean while conditional acknowledgements carry most of the terms that never survived. Nestack reports the conflict rate by supplier form, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Conditional acknowledgements
11.0%
3.7×
Review
Cross-border goods orders
7.9%
2.7×
Review
Services and hybrid orders
4.9%
1.6×
Watch
Catalogue and repeat orders
2.0%
0.7×
Normal
Bar: conflict-rate lift vs. catalogue-order baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
What a matched pair costs
The loop shuts when the acknowledgement matched unread is a regression case. That suite is what the next order raised is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Conflict rate rises on conditional acknowledgements.
02Diagnose
The supplier confirmation that arrived with its own terms on the back and was marked matched is worked backwards until one cause is left standing.
03Improve
Every change goes out numbered, with the orders that caused it attached.
04Verify
Nothing releases while one touched order case is still red.
05Learn
The case stays on, and the matching rules are rewritten alongside it.
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, order and comparison logic, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Order-terms discovery and automation-boundary design.
02Purchasing, portal and invoice sources.
03Order-to-acknowledgement and terms-conflict mapping.
04Order raising and order dispatch.
05Acknowledgement capture and term binding.
06Conflict scoring and review routing.
07Purchasing review workflow.
08ERP and receiving integration.
09Term-conflict and matching cases.
10Guardrails and acknowledgement 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 supplier, one order typeProductionProduction purchasing workflowAdvancedMultiple entities / jurisdictions
Introduced at Pilot
Term comparison to your order form✓✓✓
Named purchasing-lead matching✓✓✓
Order-and-terms baseline✓✓✓
Introduced at Production
Reporting by supplier form—✓✓
Terms review workflow in your systems—✓✓
Approved write-back—✓✓
Purchasing-system integration—✓✓
Introduced at Advanced
Multi-form reconciliation——✓
Cross-supplier term packs——✓
Large order volumes——✓
Multi-jurisdiction terms controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, order 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 live order forms and the terms each one carries→Order-term capture and conflict mappingWeek 1
02Representative acknowledgements and confirmations→Acknowledgement capture, comparison logic and the term baselineWeek 2
03Your buying calendar and the leads it names→Order-term mapping, form binding and the automation boundaryWeek 1
04Access to relevant APIs, feeds or exports→Purchasing, portal and invoice source assessment, then integration setupWeek 2
05Orders you would not want litigated→Conflict cases and the evaluation roundWeek 4
06What no purchase order may impose→Conflict scoring, review routing, guardrails and release controlsWeek 3
07A named purchasing lead who matches the pair→Release to the purchasing lead, 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
Widths here follow the work rather than the grid, which is why one band runs under another one.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Order-term discovery, form binding and the automation boundaryW2Purchasing and portal integration and the order baselineW3Acknowledgement comparison, conflict logic and release controlsW4Evaluation suite, conflict cases and failure-mode testingW5Receipt and invoice integration, pilot orders and correctionsW6One order cycle run under the purchasing lead, then Agent Care handover
Reading the bandEach bar covers only the weeks its own work is named for, and one band runs beneath another by design.
At the end of W6Once the terms record validates, Agent Care assumes the agent.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Procurement AI agent
Build a purchase-order agent around the acknowledgement your last order never answered.
Show us one supplier you buy from every month and the acknowledgement it sent back. Whose terms govern that order is decided by what both forms said and what neither of you answered, not by which of you sent first. An order nobody objected to comes back as a finding.
