B2B agentic commerce: when the procurement agent becomes the customer.

A short definition

B2B agentic commerce is the automation of business purchasing by AI agents. A procurement agent discovers, compares and triggers orders for a company, within defined limits, most often connected to its systems (ERP, e-procurement). It is agentic commerce applied to B2B constraints. Established

What sets B2B apart

• Negotiated and contract pricing: the offer depends on the customer, not a single public price.
• Quotas and commitments: volumes, cadences, contractual lead times.
• Multi-stakeholder approval: approval chains and signing thresholds.
• Integration with the buyer's systems: ERP, e-procurement, accounting traceability.

These constraints make authorization central: proving who committed the company and within which limits. AP2's mandates (intent, cart, payment) align naturally with B2B approval chains. Emerging

Assisted or delegated: the distinction that governs everything

This is the point the specification settles explicitly, and it decides what a procurement agent may actually do on its own. UCP's Checkout capability requires the order to be finalized manually by the user through a trusted UI, unless the AP2 Mandates extension is supported. Established

Without AP2 mandates, a procurement agent assembles the cart and a human signs off. With them, it can execute while the buyer is absent, inside limits signed in advance. For a procurement function this is not a technical footnote: it is the line between a decision-support tool and a delegation of authority to commit company funds.

Source: UCP specification, Checkout capability, version 2026-04-08.

The checkout lifecycle, and why it speaks B2B

A checkout session exposes a status that tells the agent which action is expected. The states defined by the specification are incomplete, requires_escalation, ready_for_complete, complete_in_progress, completed and canceled. Established

requires_escalation is the one a B2B supplier should look at. It is the standardized hand-off to a human. A signature threshold exceeded, a manager's approval, a pricing exception: these stop being broken journeys to work around and become a state the protocol anticipates. Approval chains, long the main obstacle to procurement automation, finally have a defined place to live.

The specification also grades errors by severity: recoverable, requires buyer input, requires review, or unrecoverable. That granularity is what lets an agent tell a stock-out apart from a compliance refusal, and respond to each differently.

Contract pricing: eligibility verification

B2B rarely sells at list price. UCP provides for eligibility verification: claims must be resolved before a transaction can complete. Established This is the mechanism by which an agent authenticated as acting for a given company receives that company's negotiated terms rather than a catalogue price.

One structural point for suppliers: the Merchant of Record does not change, and the specification notes that the Checkout capability introduces no PCI DSS compliance obligation for card payments. The agent does not become a commercial intermediary. It remains a channel.

A B2B supplier's readiness

To stay selectable by a procurement agent, a distributor or manufacturer must expose:

• Typed per-customer offers: contract price, quota, lead time, terms.
• Traceability of the agent's decisions, integrable into the buyer's ERP.
• Pre-authorization of recurring orders with threshold and signature.
• Clear governance (eligibility, pricing, dispute).

It is the same foundation as agentic commerce in general, applied to B2B. The implementation guide and the audit methodology help build it. See also the use cases (including the B2B distributor scenario).

Frequently asked questions