Agentic Commerce Readiness Checklist: What Merchants Need Before AI Agents Can Buy

Agentic commerce readiness means a merchant can be found, understood, and bought from by AI agents without breaking price accuracy, checkout control, payment authorization, or dispute evidence. The practical readiness bar is not “install an AI tool.” It is clean product data, an agent-reachable transaction path, scoped payment authorization, logs, and a named owner.

Short answer

If most of the checklist below is unchecked, start with product data and governance. If product data is clean but checkout and payment are not ready, focus on API checkout, authorization, and evidence. If all sections are mostly checked, you are ready to run a limited pilot and measure agent-driven discovery, checkout attempts, completed orders, exceptions, and disputes.

Readiness scorecard

Area	Ready looks like	Risk if missing
Product data	Complete, structured, current, and matched to the live store	Agents misread, ignore, or misquote products
Discoverability	Products and tools are visible to the agent surfaces customers use	You are absent from the agent’s consideration set
Checkout	The cart and checkout path can be called through structured APIs	Agent sessions fail or fall back to brittle page scraping
Payments	Tokens, mandates, or network credentials are scoped and understood	Authorization and fraud questions become hard to defend
Evidence	Authorization, cart, price, agent, and order records are logged	Disputes become reconstructions instead of records
Governance	One owner can decide standards, risk, and vendor choices	Teams make incompatible platform and payment decisions

1. Product data

Start here. For agentic commerce, your product data is the storefront an agent reads. It needs to be complete enough to compare, structured enough to parse, accurate enough to transact against, and current enough that price and availability do not drift.

• Every product has a stable identifier, title, description, price, currency, availability, image, brand, category, variant data, and relevant product identifiers.
• Prices and inventory match the live store exactly, to the cent and the unit.
• Price, availability, promotions, and variants update quickly enough that agents do not act on stale terms.
• Product pages and feeds agree with one another.
• Someone monitors feed-to-store drift and treats mismatches as operational incidents.

For the deeper version, use how to prepare your product catalog for agentic commerce.

2. Discoverability

Once the catalog is reliable, ask where agents will find it. This might be through a commerce platform, a shopping feed, an agent marketplace, a protocol integration, or an MCP server exposing merchant tools. The readiness question is not only “are we listed?” but “do we know how agents represent and rank us?”

• You know which agent surfaces matter for your customers.
• You can verify how your products are described, compared, and filtered.
• If a platform syndicates your feed, you have checked that syndication is enabled and current.
• You have a way to monitor impressions, recommendations, referrals, or agent calls when those reports become available.

3. Checkout and transactability

An agent-ready merchant needs a transaction path that software can call without guessing at rendered page behavior. For ACP, that means an Agentic Checkout API. For UCP or other surfaces, the exact interface may differ, but the principle is the same: the agent needs structured cart, fulfillment, tax, policy, and order responses.

• Checkout can be reached through structured APIs, not only browser clicks.
• The checkout path can return current pricing, shipping, tax, availability, restrictions, and policy links.
• Your team understands which standard matters for the surfaces you care about: ACP, UCP, or both.
• You have completed a test agent-initiated order in a sandbox or pilot.

4. Payments and authorization

Payment readiness is about proving the user authorized the agent’s action and limiting the payment artifact’s scope. ACP uses the Shared Payment Token model in its reference implementation. AP2 uses signed mandates to prove authorization. Card-network programs use tokenization and registered-agent controls.

• You understand which payment artifact will be used: Shared Payment Token, network token, mandate-backed credential, stablecoin rail, or another mechanism.
• Tokens or credentials are scoped to the merchant, amount, cart, and permitted action.
• You have read the terms for liability, disputes, consumer protection, and fees.
• Fraud and customer-service teams know what a valid agent transaction looks like.

For the mechanics, see how AI agents pay and AI shopping agent authorization.

5. Evidence and monitoring

Agent transactions need a defensible record. The evidence does not only help with disputes. It also helps support teams explain what happened, helps fraud teams detect abuse, and gives leadership the measurement layer needed to decide whether the channel is working.

Keep records of:

• the customer authorization or mandate;
• the agent or platform that acted;
• constraints such as amount, merchant, product, date, and recurrence;
• the cart, price, shipping, tax, and policy state shown at checkout;
• the payment artifact presented;
• the final order, refund, cancellation, or exception.

6. Governance and risk

Readiness is also an ownership problem. Agentic commerce spans ecommerce, product data, payments, legal, privacy, customer service, analytics, and marketing. If nobody owns the whole decision, a merchant can accidentally accept a payment program, expose product data, or sign a platform contract without understanding the tradeoffs.

• Assign an executive or operating owner.
• Decide which standards and surfaces are in scope for the next 90 days.
• Define the risk review for privacy, disputes, fraud, and customer data.
• Use an RFP or vendor scorecard before committing to a platform.
• Track what is live, what is announced, and what is only a roadmap claim.

The downloadable version of this checklist is available on the resources page, alongside the vendor evaluation scorecard and RFP question bank.

The bottom line

The safest path into agentic commerce is staged. Clean the catalog first, make checkout callable second, understand payment authorization third, then pilot with logs and governance in place. The standards are still moving, but those foundations are low-regret. They improve conventional ecommerce and make the business easier for agents to represent accurately.

FAQ

What is the minimum readiness bar for agentic commerce? Complete structured product data, exact live-store parity, an API path to checkout, a payment and authorization model you understand, transaction logs, and a named owner.

Should a merchant start with payments or product data? Product data. Agents cannot choose or buy what they cannot understand, and stale product data can break checkout even when payment works.

Does readiness mean choosing ACP or UCP now? Not always. It means knowing which customer surfaces matter and what each requires. Some merchants can wait while they clean data and governance; others need ACP, UCP, or both because their platform already depends on them.

What evidence should a merchant keep? The authorization, agent identity, constraints, cart, price, payment artifact, order, and any exception or refund record.