Poppy and the Merchant’s Next Question: What Did the Shopper Actually Approve?

Poppy helps AI agents discover a retailer and access a shopper’s account. Merchants still need to know what the shopper approved, and when to ask again.

A shopper asks an AI agent to find a jacket, check the delivery date and place an order. Later, the agent returns to the retailer with a proposed change: replace the jacket with a more expensive version and ship it to a different address.

The retailer may recognize the agent. It may even know which customer account is connected. But that still leaves a consequential question: did the shopper authorize this change?

That distinction matters as retailers prepare to serve customers who increasingly arrive through software acting on their behalf. The opportunity is a new way to reach and serve shoppers. The challenge is making sure the merchant can still recognize the customer, understand the agent’s permission and keep the customer involved when a decision calls for it.

Personal Agent Protocol, known as Poppy, is an emerging part of that picture.

What Poppy Does

Poppy defines how a personal agent acting for a user can work with a company. It covers discovery, identity, account access and interactions through a company’s website, APIs or its own agent.

In practical terms, a retailer can publish information that helps an agent find the available routes into its business and understand the access it can request. A shopper can sign in with the retailer and approve access for the agent. The protocol uses OAuth, an established authorization framework, to support that account access.

Sierra announced version 1.0 of Poppy in November. Its commerce extension connects Poppy with the Universal Commerce Protocol, or UCP. Sierra describes the distinction this way: UCP handles shopping activities such as finding products, filling a cart and checking out; Poppy helps an agent discover the business and establish access.

Neither a protocol nor an account connection settles every decision a retailer will face. The details of what an agent may do, and when a customer should be asked to approve something new, still matter.

Three Questions, Not One

Who is the shopper? A retailer needs to distinguish an agent arriving without a known account from one acting with access to a specific customer’s account. Poppy supports signed-out sessions as well as sign-in. A signed-out identifier can help distinguish a user’s activity without telling the merchant who that person is.

What access did the shopper authorize? When a customer signs in and approves an agent’s requested access, that approval has a scope. For example, a retailer might offer permission to view orders separately from permission to change them. The retailer decides which actions require which scopes and enforces them across its APIs and company-agent actions.

Does this particular action need fresh approval? Knowing an account and having some permission to act do not automatically answer whether the customer agreed to a specific change. A shopper may have authorized an agent to check an order, but not to change its delivery address or accept a higher price.

In that case, the agent should not proceed on the strength of account recognition alone. Depending on the access needed, Poppy specifies a new sign-in when a task requires more scope than the existing grant allows. A retailer may also choose to require a specific customer approval as part of its own transaction and risk policies. The protocol does not make every merchant’s approval decisions for it.

The Relationship After Checkout

The order change is only one moment in a longer customer relationship. Shoppers may want to check delivery, use loyalty benefits, arrange an exchange or speak with someone about a problem. If those interactions begin in an agent, the retailer still needs a reliable way to serve the person behind it.

That is a business question as much as a technical one. A new channel can bring a customer to the store, but the merchant still needs to decide how that customer is recognized and supported after the sale.

LoginID’s focus is helping merchants recognize the customer behind an AI shopping agent, understand what the agent has permission to do, and ask the customer to approve a specific action when needed. The aim is to help retailers serve customers through agents while keeping the direct customer relationship with the merchant.

A Practical Takeaway

Pick one common post-purchase action, such as changing a delivery address. Walk through it as an agent-assisted request: can your team identify the customer, see what access was granted, and stop the change for a fresh approval when your policy requires one?

That exercise gives product, fraud and customer-service teams a concrete place to start. It also reveals where a working agent connection is not yet the same thing as a complete customer experience.

Open one capability to agents

AIGW verifies the agent, authenticates the user, and issues scoped tokens your application checks on every request.