The New First Buyer

One of my earliest jobs was at a YC-backed e-commerce startup, and I later spent a few years at Amazon. That made me pay attention to how online shopping actually works. Small changes in search, ranking, inventory, and fulfillment can reshape how millions of people experience a purchase.

Agentic commerce feels different from a normal change in checkout or distribution. It changes who, or what, the merchant has to persuade.

For most of the consumer internet, the merchant built for the human at the screen. Now the first thing to satisfy may be the shopper's agent, which wants structured data, reliable inventory, deterministic pricing, provable identity, and low transaction risk.

SEO is an imperfect analogy because the decision-maker changes. Search engines helped humans find options. Agents increasingly decide which options are worth showing. A search result can tolerate uncertainty because the human interprets, compares, and takes the risk. An agent has a different incentive. If it recommends stale inventory, ambiguous pricing, or a broken checkout path, the user blames the agent for a bad recommendation.

The website does not disappear, but its role changes. It carries the brand and handles direct traffic, but its most important job may become less like a storefront and more like a transaction layer. The page is what the human sees when they arrive. The feed, manifest, checkout endpoint, identity layer, and payment permissions help determine whether the human's agent arrives at all.

Online merchants have spent years improving persuasion through landing pages, photography, recommendations, reviews, and checkout UX. Those matter when a human is in the loop. Agents first need to know whether the transaction can be evaluated and completed safely.

What agents need

Most commerce websites are built to be interpreted by people. Agents need data that is explicit enough to act on, including product attributes, inventory, delivery windows, return policies, discounts, substitutions, bundles, and payment constraints. In human search, imperfect information can lead to a click. In agentic commerce, it may prevent the option from being considered.

There is no single interface that every merchant can implement once and forget. Each agent platform asks the merchant to expose products, checkout, identity, payments, and policy in a slightly different shape. Merchants have to decide which platforms matter before demand is obvious.

Trust is harder because agentic commerce lets software browse a catalog and, more importantly, commit money, identity, and intent. Payment protocols are trying to solve this with scoped credentials and authorization records. Stripe's shared payment tokens, for example, let an agent pass limited payment credentials to a seller without exposing the underlying card. Google's Agent Payments Protocol frames the payment layer around mandates that can be used to verify what was authorized and what was purchased.

Those details sound technical, but the merchant is still on the hook when the agent gets it wrong. The failure modes include fraud, chargebacks, bad discounts, incorrectly indexed products, confused substitutions, policy violations, and disputes over whether the user or the agent authorized a transaction. A merchant can tolerate a new acquisition channel being inefficient. It is harder to tolerate one that can apply the wrong discount to a catalog or approve the wrong substitution at machine speed.

The merchant does not want a protocol war

From the merchant's perspective, the problem is not that protocols exist. It is that each protocol points merchants toward a different platform bet. One is centered on ChatGPT. Another is centered on Google and Shopify. Another is centered on payment networks. Another is centered on merchant-hosted agents that negotiate directly with buyer agents.

The Agentic Commerce Protocol, built around programmatic checkout between buyers, agents, and sellers, is one path. Universal Commerce Protocol, co-developed by Shopify and Google, is another. Stripe's agentic commerce docs now point sellers toward either UCP or ACP, depending on the integration.

The cost resembles earlier standards wars. The platform with the most distribution can ask the ecosystem to conform. The smaller merchant has to decide whether the integration is worth the work. If there is one winner, the problem eventually simplifies. If the market stays split, merchants either maintain multiple integrations or rely on an abstraction layer that makes the split less painful.

The translation problem

The useful product here may be narrower than "make my website AI-ready." It looks more like a translation layer. Take the merchant's existing product, inventory, fulfillment, pricing, and payment data, then expose it in whatever shape the relevant agent requires. The value is not only implementation speed. It is reducing the number of platform bets a merchant has to make before knowing where demand will come from.

The first product merchants pay for will show which problem matters most to them. Protocol mapping points to engineering cost. An agent-readiness audit points to visibility. Delegated payment controls point to liability. I would watch the last category most closely. The downside is not a missed click. It is a transaction the merchant did not mean to accept.

The fixed price starts to look less fixed

Agents may negotiate with each other. UCP describes commerce capabilities as something merchants and agents can declare and negotiate. That matters because commerce is full of conditional behavior, including discounts, fulfillment constraints, loyalty status, substitutions, bundles, pickup windows, payment methods, and return policies. Once those conditions are machine-readable, price and terms stop being only what is printed on the page. They become something software can reason about.

At first, this looks mundane. An agent asks whether a merchant can apply a loyalty discount, find a substitute, bundle items, or meet a delivery window. But the direction is more interesting than the first use case. If buyer agents can represent willingness to pay, timing, preferences, brand constraints, and substitution tolerance, and seller agents can represent margin, inventory pressure, promotions, and fulfillment capacity, then the listed price starts looking more like a starting point.

That creates problems for brands. What does fairness mean when some consumers have better agents than others? What happens to comparison shopping when the comparable object is no longer just product plus price, but product plus negotiated terms?

Online retail has already had dynamic pricing for a long time, but agentic commerce makes the negotiation more explicit. Agents can keep checking and negotiating in ways people usually will not. A person may not want to open twelve tabs, read return policies, compare loyalty programs, and haggle over bundles. An agent might. That could expand online commerce in categories where the friction was previously too high, especially services, B2B purchasing, configured goods, and high-consideration purchases.

Where consideration starts

Not every purchase will move into an agent interface. People still browse, brands still need websites and product pages, and many purchases are emotional or aesthetic in ways that resist full delegation.

The shift matters most when agents become the first filter for high-intent purchases. In those cases, a merchant has to be eligible before it can be visible. The data has to be readable, the transaction has to work, and the risk has to be acceptable.

The shopper is still the customer. But in more transactions, the first thing a merchant may need to satisfy is the buyer's agent.