How retailers can sell through AI shopping agents

Retailers can prepare for purchases through AI shopping assistants and, where eligible, enable specific buying routes today. The practical starting point is not to purchase an entirely new commerce stack. It is to establish which journey their existing store, payment provider and order systems can support, then check the requirements of the intended AI channel. A product feed is not a checkout, and a payment integration is not an order system.

Rezolve Ai's 9 October demonstration of Meta's Muse ordering coffee for in-store collection provides another illustration of this infrastructure taking shape. The company describes a consumer agent interacting with a merchant-side RezolvePay agent, with compatibility depending on the agent, merchant integration, payment method and jurisdiction. It is a demonstration, not evidence that every assistant can buy from every retailer or that the system increases sales. [1]

Choose the buying journey before the integration

Three experiences need to remain distinct. In a referral journey, the assistant helps a customer find a product and sends them to the retailer's website to buy. In embedded checkout, the customer completes an authorised purchase inside an AI channel connected to the merchant's systems. In delegated buying, an assistant carries out a task within the customer's instructions and the supported payment controls. Enabling one does not establish the others.

The earlier AI shopper analysis examined who grants agents access. This guide concerns what a retailer must connect after access is available. The first questions are where checkout happens, who authorises payment, which system creates the order and who handles fulfilment or a failed transaction. The routes below can overlap: a retailer might use Shopify for its store, Google for discovery and Braintree for payment processing, rather than buy five independent systems.

Shopify: inspect the channels already available

Shopify says Agentic Storefronts is active by default for eligible stores. Merchants manage product access and supported checkout behaviour in Sales channels > Agentic. Its management documentation describes both Shopify-managed settings and manual channel controls. That makes inspecting the existing account a useful first step, but a default setting is not proof that every channel is available. Setup differs for the Agentic plan, where direct checkout is deactivated by default. [2] [3]

Channel differences matter. Shopify currently describes ChatGPT as a discovery-focused referrer: customers finish in the merchant's online-store checkout, opened within ChatGPT's in-app browser or a separate browser tab. Google AI Mode and Gemini, Microsoft Copilot and Meta surfaces such as Muse can offer Shopify-powered direct checkout where the channel is supported and direct checkout is activated. [2]

For Google's direct-checkout route, Shopify requires a US-based store selling to US customers, a valid Merchant Center account, eligible products, completed policies and the relevant terms. Products and shipping information can be synchronised through the Google & YouTube channel, or supplied through another permitted feed route. Shopify warns that rollout might not yet have reached an otherwise eligible store. Customers outside the US are redirected to the retailer's online store. These Google conditions should not be assumed to describe every other Shopify AI channel. [11]

Stripe: a documented seller route, including Canada

Stripe's Agentic Commerce Suite documentation lists availability in the US, Canada and specified European countries. Retailers begin in the Agentic commerce dashboard, onboard as sellers and supply their business profile and policies. The implementation connects catalogue, inventory and pricing feeds with tax configuration and order handling. Country availability describes the documented service scope, not guaranteed access to every AI assistant. [4]

A retailer requests a connection to a supported agent, which must accept the request before the connection becomes enabled. A Stripe account alone does not activate every channel. The documentation also describes a checkout.session.completed webhook for fulfilment handling and transaction records tagged with the originating agent. These are mechanisms for connecting channel activity to actual orders, not evidence of incremental sales or universal attribution accuracy. [4]

PayPal and Braintree: connect payment to the chosen flow

PayPal Developer documents a Google Universal Commerce Protocol, or UCP, payment-handler integration using Braintree. It requires an active Braintree merchant account, Google Pay enabled and UCP merchant registration and enablement with Google. The merchant's server processes the single-use payment credential supplied in the checkout-completion payload. This is a payment-processing path, not a complete catalogue or order-management implementation. [5]

Its ChatGPT guide describes a custom app using the Apps SDK and Braintree as the payment provider. The delegated payment token is a one-use nonce bound to the merchant, with checks for maximum amount, currency and expiry. PayPal Wallet and Venmo Wallet are described as coming soon in that guide. This documented route involves app and server development, rather than simply adding a PayPal button to an existing website. Neither payment guide establishes universal geographic or live-channel access. [6]

For an existing Braintree merchant, examining these documented paths before replacing payment infrastructure is a reasonable operational step. The retailer still needs reliable product data, supported channel access and order handling around the payment integration. The relevant question is which responsibilities the provider covers and which remain with the retailer.

Google and OpenAI: published specifications are not live access

Google's UCP integration supports two distinct capabilities. Transfer to merchant cart moves a cart assembled on Google to the retailer's site for checkout. Native checkout on Google keeps the purchase in Google's experience. Merchants can choose either or both, but each has its own implementation and validation checklist. Cart transfer uses a Cart API; native checkout requires checkout-session services and order-status updates, followed by the applicable validation and review. [8]

Google describes the integration hub as gradually rolling out in the US, with checkout available to select merchants. Retailers can review eligibility and submit interest, but an ordinary Merchant Center feed does not itself enable the Buy now experience. The documentation describes Australia and Canada as future expansion markets, not part of the current US rollout. Retailers should obtain channel-specific confirmation rather than assume that a published specification gives them production access. [7] [8]

OpenAI's Agentic Checkout Spec describes merchant-hosted checkout-session services, payment processing and order lifecycle updates on the retailer's existing commerce stack. Its Products specification separately states that a discovery feed or checkout-eligibility flag does not complete checkout onboarding. The standard OpenAI-format product upload targets the US, with additional markets requiring confirmation for the integration. These documents explain technical requirements; they do not establish that every retailer has live checkout access or define the approval policy of every OpenAI commerce programme. [9] [10]

Where Rezolve fits

Rezolve Ai is a Nasdaq-listed commerce technology company founded in 2016. Its latest announcement illustrates a merchant-side agent accepting a Muse coffee order for collection, and says the receipt identifies the ordering agent. Broader interoperability is a company architecture claim subject to the stated compatibility conditions, not a verified list of production connections to every consumer assistant. [1] [12]

Retailers considering specialist infrastructure should request a proposal tied to named agents, markets, supported payment methods and a defined order journey. Implementation costs, transaction economics, support responsibilities and demonstrable production integrations matter more than a broad claim to support agentic commerce. This is an editorial evaluation approach, not a ranking or endorsement of the providers described here.

Six things retailers should do first

1. Pick one buying journey

Choose one market, channel and manageable product category. Decide whether the objective is referral, embedded checkout or authorised delegated buying. If in-channel checkout is not available, keep a reliable retailer-site route rather than promise a capability that has not been enabled.

2. Audit the systems already in place

Inspect Shopify's Agentic settings, Stripe's seller-onboarding route, Braintree's documented prerequisites or the relevant platform programme. Confirm actual merchant eligibility and channel access with the provider. Assign ownership for catalogue, checkout, payment and order operations before deciding whether an additional supplier is necessary.

3. Make the catalogue dependable

Maintain accurate product identifiers, variants, descriptions, prices and stock. Keep delivery, collection and returns policies consistent with the offer. Connected feeds must reflect changes promptly: stale availability can turn a plausible product recommendation into a checkout failure. A discoverable product is not necessarily a purchasable one. [4] [10]

4. Connect the whole order

Confirm that tax, shipping, customer authorisation, payment, order creation and fulfilment work together in the chosen journey. Document which system confirms an order and how status changes reach the customer and channel. The earlier AI-built-interface analysis explains why hosting a decision and retaining commercial responsibility are different questions.

5. Test the exceptions before launch

Test stock changes, declined payments, cancellations, refunds and repeated requests. Validate the applicable token limits and expiry. Check idempotency and retry behaviour so a repeated completion request does not create a duplicate order. These are recommended operating tests informed by the specifications, not claims that every provider supports every exception in the same way. [6] [9]

6. Measure completed business separately

Reconcile channel-labelled orders with payment, cancellations, refunds and successful fulfilment. Track revenue and margin after relevant costs where the data permits. Shopify documents AI-channel reporting, with a current limitation for headless stores; Stripe documents originating-agent transaction tags. Keep referral sales separate from orders completed inside an AI channel, and keep both separate from machine visibility. Neither reporting feature proves incremental revenue without an appropriate comparison or research design. [3] [4]

AEO Updates Takeaway

The first useful move is to establish one reliable buying route through the systems a retailer already uses. AI visibility can put a product into consideration, but accurate catalogue data, authorised checkout and dependable fulfilment are separate operational requirements. A retailer should verify channel access, connect those requirements and test the order journey before treating an AI-commerce announcement as a working sales channel.

References

[1] Rezolve Ai, Rezolve Ai Opens Retail to Any AI Shopping Agent with RezolvePay, 9 October 2026.

[2] Shopify Help Center, Shopify agentic storefronts, accessed 9 October 2026.

[3] Shopify Help Center, Managing agentic storefronts, accessed 9 October 2026.

[4] Stripe Documentation, Sell through agents, accessed 9 October 2026.

[5] PayPal Developer, Universal Commerce Protocol integration, last updated 10 June 2026; accessed 9 October 2026.

[6] PayPal Developer, Agentic Commerce Protocol integration, last updated 10 June 2026; accessed 9 October 2026.

[7] Google Developers, About Universal Commerce Protocol integration hub in Merchant Center, last updated 2 October 2026; accessed 9 October 2026.

[8] Google Developers, How to start UCP integration in Merchant Center, last updated 5 October 2026; accessed 9 October 2026.

[9] OpenAI Developers, Agentic Checkout Spec, accessed 9 October 2026.

[10] OpenAI Developers, Products: Agentic Commerce, accessed 9 October 2026.

[11] Shopify Help Center, Selling on Google AI Mode and Gemini, accessed 9 October 2026.

[12] Rezolve Ai Investor Relations, FAQs, accessed 9 October 2026.