E-commerce
August 19, 2026
Amazon Buy for Me is a product card, not an audit. The directory labels it automatic purchase, all merchants, United States, with search, price, and payment filters. It has no gross merchandise volume, no successful order rate on merchant sites, and no failed 3-D Secure rate. Neither does this article. It reads the mechanism that Amazon documents: a customer searches in the Amazon app, sees an item that the Amazon store does not sell, confirms an Amazon checkout page, and then an agent completes the purchase on the brand's website. This is not Rufus. This is not UCP. This is not ACP.
Amazon described Buy for Me on April 3, 2025 as a beta in the Shopping app, iOS and Android, for a subset of US customers, on a limited number of shops and products. The customer confirms the address, taxes, shipping costs, and payment method on an Amazon page. The agent, Amazon writes, then pushes the encrypted name, address, and payment onto the brand's checkout funnel. Amazon announced Shop Direct streams on March 11, 2026: Shop Direct is the discovery program (items outside the Amazon store). Buy for Me is only one of two possible actions, and only for eligible products. The totals of "100 million products" or "400,000 merchants" are publisher figures. We quote them as such, not as an independent census.
If the idea of a software buyer is new: what agentic commerce is. The 2026 timeline: what has been delivered. Other directory listings: AI shopping agents. Official totals remain human shopping journeys: 2026 e-commerce statistics.
Summary
Buy for Me is not Rufus
Two Amazon products, two contracts. Rufus (then, in other Amazon posts, Alexa for Shopping) remains in the Amazon catalog: questions, comparisons, reviews, Amazon checkout funnel. Buy for Me leaves the store. It only exists if the item is not currently sold on Amazon, and only if Amazon has decided that this Shop Direct listing is eligible for delegated payment.
Product | Where it happens | What you control |
|---|---|---|
Rufus / in-app assistant | Amazon catalog and checkout funnel | Your marketplace listing, not your product detail page |
Shop Direct (button) | Redirection to your site, after a warning | Your site, your session, your tracking |
Buy for Me | Amazon checkout page, then agent on your checkout funnel | Your theme, your web application firewall, your 3-D Secure, your order system |
Pasting them into an "Amazon agent" slide erases the only useful question: does the order originate in Seller Central, or in your own store? Buy for Me, as Amazon describes it, originates with you. The human, however, has barely left the Amazon app. This is the attribution trap, not a screen detail.
The directory is right to separate the two listings. It is wrong if we read "all merchants" as "the Amazon agent crawls the entire open web". Amazon describes a selection, an eligibility, and a choice of participation on the brand side. A universal journey is not that.
Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion
Empowering 200+ e-commerce merchants
The journey that Amazon documents
Amazon, in April 2025, describes a five-step journey. This is not an open specification. It is the publisher's narrative of the product.
In-app search: the customer searches for a brand or product. They see the Amazon store, and sometimes a section "Shop brand sites directly" (later: Shop Direct).
Amazon product page: tapping Buy for Me opens a page within the Amazon app, not on your theme. Amazon says it displays information "similar" to its own product pages.
Amazon checkout page: the customer confirms address, taxes, shipping, payment. They authorize Amazon to buy from the brand on their behalf.
Agent on your site: Amazon says it runs this on Bedrock, using Amazon Nova and Anthropic's Claude models. The agent completes the merchant checkout funnel with encrypted data. Amazon says it does not see the customer's other orders with the brand.
Split after-sales: confirmation email from the brand. Tracking in a Buy for Me Orders tab of the Amazon app. Delivery, returns, exchanges, customer service: the brand, writes Amazon.
Three artifacts, three owners. The page the customer reads is Amazon. The card they confirm is Amazon. The cart your payment provider sees is yours. A 3-D Secure failure or an application firewall blocking the agent is not read in Seller Central. It is read in your logs and at your acquirer.
Oliver Messenger, director of shopping at Amazon, sells "increased exposure" and "seamless conversion" for brands. This is a launch quote. This is not a rate. We do not make it an indicator.
Shop Direct is not Buy for Me
Shop Direct and Buy for Me share a discovery. They do not share the checkout funnel.
Shop Direct, in the March 2026 post, is the experience that shows products from other stores when Amazon does not sell them. The customer can tap Shop Direct: Amazon warns them that they are leaving Amazon, then redirects them to your site. There, it is a human on your product page. Pixel, session, possible promo code: yours.
Buy for Me, for eligible products, keeps the human in the app. Amazon takes the consent, then an agent goes through your payment funnel. You receive an order. You do not necessarily receive a visit. Treating both buttons as a single "Amazon traffic" channel is mixing a browser session and a mandated headless browser.
Amazon claims to clearly display the store name, whether the customer goes via redirection or via Buy for Me. Useful for the buyer. Insufficient for your measurement: the referrer of the Buy for Me order is not a human click on a results page. It is an agent with a mandate.
Eligibility, United States, walled garden
The entry condition, repeated by Amazon, is narrow: the item is not currently sold in the Amazon store. If you already sell the same SKU there, Buy for Me is not the described path. It is Rufus, the Amazon product detail page, the Amazon checkout funnel. Two catalog strategies, not one.
Geography: the directory says United States. The Buy for Me post says beta, subset of US customers, iOS and Android. The Shop Direct post says Shop Direct is available to all US customers, on Amazon.com, the app, the mobile web, and in Rufus. Do not merge "Shop Direct everywhere in the US" and "Buy for Me for everyone." One is the storefront. The other is an additional eligibility.
Amazon also writes that brands have the choice to participate, and the feeds post mentions the opt-out option via the Shop Direct merchant page. "All merchants" in the directory is a family label, not proof that your Magento is already in the mix. Without a feed, without an agreement, without Buy for Me eligibility, you are not in this funnel. You are, at best, a site that the agent is not allowed to pay.
The listing filters (product search, price, checkout) are human uses of the directory, not protocols: agents for product search, agents for checkout. Buy for Me can carry all three labels and still remains a single Amazon product.
Who delivers, who refunds, who has the customer
Amazon, on Buy for Me, splits the post-purchase process in one sentence: the brand handles delivery, returns, exchanges, and customer service. The merchant receives the name and address. The customer receives an email from the brand and can track the order in the Amazon tab. Two interfaces. One package.
Question | The answer Amazon writes | What this does not solve |
|---|---|---|
Who delivers? | The brand | Your delivery times, your logistics provider, your actual stock at the moment the agent clicked |
Who refunds? | The brand (returns and exchanges) | The card reason code if the customer disputes through Amazon or through you |
Who has the customer? | You have the name and address. Amazon has the account and the tracking tab | Marketing email, consent, single customer profile |
Who is the merchant of record? | The checkout tunnel is yours, so the order is yours | This is not a UCP (Universal Commerce Protocol) specification. Ask your payment provider, not a blog |
Amazon claims not to see the customer's previous or separate orders on the brand's website. This is a promise of compartmentalization, not a PCI audit published here. You see a new order, often without history, sometimes without the same email as the Amazon account. Your fraud prevention tool will see a "new" buyer with a tokenized card pushed by an agent. Calibrate your rules.
The words mandate, merchant of record, delegated payment: the glossary of agentic commerce. Here, the mandate is not AP2. It is consent within the Amazon app, then an agent running your form. Do not copy Google or Stripe vocabulary on this sheet.
When it breaks after the purchase (wrong size, ghost stock, customer opening a dispute from the Amazon app), the cost falls on the systems you have not changed for an agent: orders, customer service, chargebacks. The catalog of limitations: where agentic commerce still breaks.
Your checkout, your firewall, your 3-D Secure
Buy for Me is a browser agent with an Amazon logo, not an HTTP notification from the UCP. It must successfully navigate your theme, your shopping cart scripts, your modals, your 3-D Secure. A checkout tunnel that relies solely on heavy JavaScript, a banking challenge designed for a present human, an application firewall that kills any headless browser: three ways to "participate in Shop Direct" and fail Buy for Me without any message in the Amazon interface.
It is the same work at the entry point as for Operator or Claude Chrome, with a commercial difference: the agent arrives with an Amazon customer already identified on their end, and a cart that you did not promote. The three platform changes (readable catalog, robot policy, delegated payment) apply, but the readable catalog here is primarily your product page and your Shop Direct feed, not Merchant Center: what the platforms must change.
In the logs, it looks like a polite scraping bot: bursts on product pages and the checkout tunnel, no mouse, a User-Agent that your "block bots" rule didn't anticipate. Deciding who gets through is a policy, not an Amazon button. How to read this traffic: server log monitoring.
Test a real order (small amount) as if you were the agent: same path, same fields, same 3-D Secure. If a patient human already fails, the agent will fail. If only the headless browser fails, it's the application firewall or the JavaScript, not "Amazon not liking your brand."
The Shop Direct feed, not an open protocol
The March 2026 post is the merchant text. Amazon says that merchants can plug in the same feeds they already send to Feedonomics, Salsify, or CEDCommerce to sync catalog, price, and stock in real-time with Shop Direct. The products can then appear in search results and in Rufus. Other syndicators and an Amazon portal with a direct feed are announced as upcoming. This is not a documented public API here like the UCP.
Amazon boasts "more than 100 million products," "more than 400,000 merchants," "tens of millions" eligible for Buy for Me, and "millions" of redirects to merchant sites. These are publisher totals in a program post. Not an audit report. Not your volume. An up-to-date feed remains the useful work, regardless of the press release figure: what a machine needs to compare.
Amanda Doerr (Core Shopping) promises traffic and sales while keeping the customer relationship. Keep the second half: you keep shipping and after-sales service. The first half (traffic, sales) has no incremental definition here. A SKU you refuse to put on Amazon that Shop Direct shows, yes, that could be volume that the marketplace was not cannibalizing. A SKU close to an Amazon listing that is already yours is another, internal conversation.
To get started, Amazon directs to the Feedonomics, Salsify, or CEDCommerce representative, or to shopdirect@amazon.com if the syndicator is not in the program. We are not adding a third URL. If you do not have a clean feed, this email fixes nothing.
It is neither UCP nor ACP
UCP (Google, AI Mode / Gemini) and ACP (Stripe, OpenAI, Meta) are public rails: the agent and the merchant talk to each other according to a specification. Buy for Me is not that. Amazon does not publish, in the two texts cited here, a merchant checkout tunnel OpenAPI. It publishes an agent that plays your site. Comparing open protocols: how protocols differ.
ChatGPT has, on the Stripe side, an ACP integration. Gemini has UCP. Buy for Me has Amazon eligibility and a headless browser. Three ways of "being in AI". A single word in a sales pitch. Ask for the deliverable: Shop Direct feed, Shopify Agentic channel, ACP access point, or a theme that survives an agent. Buy for Me is the first plus the fourth, not the third.
You do not implement Buy for Me the way you implement an HTTP notification. You accept (or refuse) to be in Shop Direct, you maintain a feed, you let an agent pay at your place. If your policy is "no robots in the checkout tunnel", Buy for Me is incompatible by design. This is not a program bug. This is the contract.
What the two Amazon posts do not measure
Neither of the two Amazon posts provides a successful agent payment rate, a 3-D Secure rate, a Buy for Me returns rate, a dispute rate, or the share of incremental versus cannibalized orders. We are not making these numbers up.
Order Accuracy: the agent can validate a size, a variant, or a stock level that your product page displays incorrectly. The order is real. The error is yours to fulfill or cancel.
Attribution: the customer converted in the Amazon app. Your pixel may not have seen anything. Your acquisition and e-commerce teams will fight over the credit.
Two-door customer service: the customer opens the Amazon tab or your email. Two scripts. One package. Amazon says customer service is yours. The customer hasn't necessarily read that.
Coverage: 100 million and 400,000 are Amazon totals. Your category, your country outside the United States, your tech stack: irrelevant until you are in the flow and eligible.
A Verified listing on this site does not buy a spot in Shop Direct. Editorial and the Amazon program remain separate. Treat the listing as a starting point for an internal question (can our checkout tunnel handle an agent?), not as proof that "everyone is already buying this way."
Three gestures, not twenty slides
This week, three actions, not twenty slides.
Catalog: list the SKUs you don't sell on Amazon and would agree to show in Shop Direct. Price, stock, identifier, variants. The same feed work as everywhere else.
Checkout funnel: place a test order without an interface (or a real small order if you are already eligible). Note 3-D Secure, windows, application firewall. Assign one fraud owner plus one theme owner.
Program: if you want to join: a syndicator already on the Amazon list, or shopdirect@amazon.com. If you want to leave: the Shop Direct merchant page Amazon mentions. It's not a button in the directory.
The single test: would this work still be useful if Amazon removed Buy for Me tomorrow and only kept Shop Direct as a redirect? A clean feed and a sustainable checkout funnel, yes. An exclusive "Buy for Me inside" connector, no. Amazon does not document one here.
If you already sell your entire catalog on Amazon, Buy for Me is not your priority. Rufus is. If you are a direct-to-consumer brand that refuses the marketplace, Buy for Me is the case where Amazon agrees not to be the shop, while keeping the attention. Decide if this attention is right for you before talking about "agentic stack".
Frequently Asked Questions
Is Buy for Me the same as Rufus?
No. Rufus helps choose from the Amazon catalog and handles checkout on Amazon. Buy for Me handles checkout on a brand's website, for items that the Amazon store does not sell, if the product is eligible. Two different profiles. Two internal owners.
Is it agentic commerce in the sense of UCP or ACP?
In the broad sense (software buying for someone), yes. In the sense of an open rail documented by Google or Stripe, no. It is an Amazon agent on your checkout funnel. Do not apply UCP or ACP by analogy.
Who is the seller of record for the transaction?
Amazon describes a checkout funnel on the brand's site, a confirmation email from the brand, and brand customer service. This points to you as the merchant of the order. This is not a legal opinion. Ask your payment provider and check your Shop Direct contract.
Should we open the firewall to all bots?
No. A policy is needed: who is allowed to run the checkout funnel, at what rate, and with what proof. Blocking all headless browsers breaks Buy for Me. Letting everything through opens you up to price scraping. The decision is not in the directory.
Are the 100 million products an addressable market?
That is an Amazon total in a Shop Direct post. It is not your market. It is not a conversion rate. It is not proof that your SKU is in there.
What to do this week?
Separate Rufus and Buy for Me in your mind. Clean up the feed of non-Amazon SKUs. Test the checkout funnel as an agent. Decide whether to participate or opt out. Postpone exclusive integrations.
Sources
Enzo
August 19, 2026
