AI Agent for Vendor Performance Management (2026)

Vendor email threads are where qty and ETA change while the OMS still shows last month’s promise. OTIF, fill rate, defects, returns, price drift, lead-time slip — buyers already have the data, split across five exports. The job is a scorecard with a next action, not a chat that “sounds senior.”

On 17 June 2026, AgentCore Harness reached general availability (What’s New). After 30 July 2026, skip Classic for net-new vendor ops (lifecycle). This post is a sample health contract. It is not a client OTIF engagement. Scores in the artifact are fixtures.

First-party signals we reuse (not eCommerce outcomes) — Gateway server-side tools cut median tool round-trip ~180 ms → ~95 ms on a B2B CRM assistant (12 tools, ~8k turns/day) — Gateway post. Platform TCO silhouette: support-style AgentCore at 50K sessions/mo ~$791/mo platform + model (decision guide). Model your mix on the AgentCore pricing calculator.

Reproduce this — Open vendor-health-scorecard.md. Every problem needs evidence_tool. Ship gates: monday-checklist.md. Folder: ecommerce-ai-agents-series/.

This is series part 26 — vendor ops in 15 automations and back-office vendor communication. PO send stays on the purchase order agent. B2B sales agents (outbound quotes) are a different series post — do not reuse this prompt for them.

Inbound supply health is not outbound quoting. A vendor scorecard that can also “negotiate” is a write surface you did not review.

Opinionated take: output is Vendor Health → Problems → Root Causes → Recommended Actions. PO change is HITL. Trade-off: a delayed ASN sits in a queue instead of an auto-cancel. You also do not fire a supplier on a one-week shock.

Why this matters / who breaks without it: replenishment breaks when you dual-source on a port delay. Quality breaks when size returns hit the supplier score. Legal breaks when the model drafts a penalty that is not in the contract. Buyers already know the painful vendors. They need evidence-backed next steps that OMS will actually see.

Automate first

If ERP already emails OTIF < 90% to a buyer who updates the QBR, keep that. Add an agent when receipts, quality codes, price history, and PO promises disagree. Rules can flag a threshold. The agent joins systems and drafts. It does not rewrite the PO.

A weekly CSV in email is a workflow. An agent is for the week a fill-rate dip and a price change land in different systems and someone has to write a next step.

Scorecard contract

From the artifact:

Root causes without a tool stay unconfirmed.

flowchart TD
  VendorMetrics[Vendor Metrics]
  Health[Vendor Health]
  Problems[Problems]
  RootCauses[Root Causes]
  Actions[Recommended Actions]
  HITL[PO Change HITL]
  VendorMetrics --> Health
  Health --> Problems
  Problems --> RootCauses
  RootCauses --> Actions
  Actions --> HITL

Demo fixture VENDOR-KNIT-01 on watch after an 81% on-time window is a sample, not a client.

Health labels (ok / watch / at_risk) are your thresholds in the scorecard, not model confidence. at_risk still does not send mail or cancel a PO. It queues a buyer review with the tool rows attached (session id + Gateway spans), same HITL pattern as back-office vendor email.

Fill rate and on-time are different problems. A vendor can be on time and short-ship. A vendor can fill 100% two weeks late. Do not collapse them into one “score” the model invented.

Production shape

Bedrock = model. Harness or Runtime = host. Gateway + Cedar. Browser off (no scraping the supplier’s track-and-trace page). Next.js can hold the HITL queue. Strands is the framework if you need specialists — not the landing zone.

No native Shopify connector.

Context: Harness GA 17 June 2026 or Runtime; Policy LOG_ONLY then ENFORCE.

{
  "vendor_id": "VENDOR-KNIT-01",
  "health": "watch",
  "do_not": ["sendVendorEmail", "cancelPurchaseOrder", "switchPreferredVendor"]
}

Vendor concentration (one supplier = most of a category’s receipts) is a risk row, not a drop. Recommend a backup-vendor review. Switching preferred vendor is HITL and should cite getVendorPoHistory. Draft emails must not invent chargebacks or new unit costs — same rule as back-office vendor communication.

What broke

What broke — Sample scorecard treated a one-week OTIF dip as drop vendor and drafted a PO cancel. The calendar tool had a named port delay; fill rate was still in policy. Policy was LOG_ONLY; a send tool was already on the OpenAPI. Detection: eval required a second window before dual-source; Gateway showed cancelPurchaseOrder after a single getVendorOtif. Fix: one window = watch; PO change HITL; remove send until Cedar ENFORCE; do not invent penalty clauses. Lesson: vendor performance is a time series. A single shock is not a sourcing strategy.

What This Post Doesn’t Cover

• Legal contracts, chargebacks, or penalty language the model must not invent.
• Measured OTIF from a FactualMinds supplier program.
• B2B storefront sales agents (outbound).
• EDI 856/810 field maps.
• AgentCore Browser on supplier portals.
• Classic Agents.
• Using shopper-facing support prompts for vendor ops.

What to Do This Week

1. List vendor metrics you already trust in ERP. If a QBR already closes the loop, do not add an agent this week.
2. Clone vendor-health-scorecard.md. Name who may change a PO.
3. Read tools: OTIF, fill, defects, quality returns, price, lead time, PO history.
4. Harness or Runtime; Gateway; Policy LOG_ONLY. Browser off.
5. Prove DENY: sendVendorEmail, cancelPurchaseOrder on a non-buyer token.
6. Eval: one-week port delay must not recommend drop-vendor.
7. Model cost on the AgentCore pricing calculator. Contact us, Bedrock, retail / eCommerce.

Full ship list: monday-checklist.md.

If you only do one thing

Treat a single window as watch. Dual-source, PO cancel, and vendor email stay HITL with tool evidence — never a one-week OTIF dip.

FAQ

When should we NOT use an AI agent for vendor performance?

Skip it when ERP already scores OTIF and fill rate and a buyer already acts on a monthly QBR. The agent is for joining receipts, quality returns, price history, and PO promises when those live in different systems. Also skip it if you cannot name who may change a PO or switch preferred vendor.

What could go wrong if we drop a vendor from one bad week?

A port delay looks like supplier failure. You dual-source, lose volume pricing, and still miss the inbound that was never the vendor’s fault. One window is watch. Dual-source needs a second window or a named capacity constraint in a tool — then HITL.

What could go wrong if the agent auto-changes POs or emails vendors?

Qty and ETA change in a thread the OMS never sees, or a penalty clause the model invented. Draft email; send HITL. PO change is the same gate as create. Cedar DENY sendVendorEmail and cancelPurchaseOrder for tokens that are not associate/admin/buyer.

Are quality returns the same as vendor defects?

No. Fit and size returns are merchandising. WMS damage can be warehouse. Only receipt defects and quality codes your QA team owns should hit the vendor score. The scorecard fails eval if it blames the supplier from a generic refund rate.

Should this run on Harness or Runtime?

Harness fits a scheduled scorecard with read tools and draft actions. Use Runtime plus Strands if purchasing and vendor ops are separate specialists and must not share PO writes. Net-new builds should not use Agents Classic after 30 July 2026.

Is there a native Shopify AgentCore vendor connector?

No. Vendor, ASN, and receipt APIs are your Gateway OpenAPI or MCP targets. Shopify, Magento, and custom ERP look the same at that boundary.