# What Is a Shopping Agent and What Can It Do in Your Store?

> What a shopping agent is, what permissions it can have when buying in your store, where the person confirms and how it reads your product pages.

URL: https://clione.ai/glossary/shopping-agent/
Lang: en

A shopping agent is the one that makes the purchase on a customer's behalf: "find me waterproof trail running shoes in size 10 under $130 and let me know if the price drops." It is not the assistant on your website, which works for your store, or a professional buyer who manages supplier orders at a company. It is an [AI agent](/glossary/ai-agent/) that **works for the person buying and visits your store the way that person would**, but reads it differently. It matters to you because some of the people looking at your [product pages](/glossary/product-page/) may already be a program with an assignment, and what it manages to do depends on what your store lets it read and on the permissions its user has given it.

## How it works

What sets one shopping agent apart from another is not the model it uses, but **how far it can go without asking**. There are three steps, and each calls for a different permission:

- **Research.** It searches, opens product pages, compares prices, sizes and delivery times. It changes nothing anywhere.
- **Prepare.** It creates a cart, picks a variant, fills in a shipping form. It changes things, but they can still be undone.
- **Pay.** It moves money. This is the step where every published system puts a person in front, or a signature from one.

ChatGPT agent is an example of the first and second steps. You describe the task, it starts it and **stops to ask for clarification or confirmation when needed**. If a site asks it to log in, it pauses and asks you to take control of its virtual browser, and while you have control it takes no screenshots. Among its safeguards, OpenAI cites user confirmations for the highest-impact actions and a "watch mode" that requires supervision on certain sites.[^openai-agent]

At the third step, each company has published its own confirmation point. With [Instant Checkout](/glossary/instant-checkout/), which OpenAI introduced on September 29, 2025, the person taps "Buy" and **confirms the order, the shipping and the payment before the purchase is completed**. OpenAI describes ChatGPT as the user's AI agent, passing information between buyer and merchant like a personal shopper, and promises that users explicitly confirm each step before any action.[^openai-buy] On March 24, 2026, OpenAI let merchants use their own checkout and concentrated its effort on product discovery.[^openai-discovery] Google introduced its [agentic checkout](/glossary/agentic-checkout/) on November 13, 2025: you track a product's price against the size, color and budget you set, and when it drops you can let Google buy it on the merchant's site with Google Pay. **Google asks permission first and only buys when you confirm the purchase and the shipping**; it began rolling out in the United States with eligible merchants.[^google-agentic-checkout]

[AP2 (Agent Payments Protocol)](/glossary/ap2/), which Google announced on September 16, 2025, turns that confirmation into a signed document, the [AP2 mandate](/glossary/ap2-mandate/). It distinguishes two cases. With the person present, the assignment is captured in an intent mandate and, when the agent shows the cart, the approval signs a cart mandate, a record that cannot be changed with the exact items and price. With the person absent, as in "buy the tickets as soon as they go on sale", a detailed intent mandate is signed beforehand, with price and time limits, and **the agent can generate the cart mandate on its own when those conditions are met**.[^ap2] That second case is the only one in which the agent pays with nobody watching at that moment, and even then within signed limits.

In all of these systems, the store is still the one selling. In OpenAI's protocol, the merchant accepts or rejects the order, charges through its payment provider and handles shipping and customer service as before.[^openai-buy]

## How it reads your store

A shopping agent that browses does not look at your site on a screen. Google's guide for web developers explains it: **agents see a site in three ways, through screenshots, through the HTML and through the accessibility tree**, and modern ones combine all three. With screenshots they recognize where everything is; with the HTML, which button belongs to which product; with the accessibility tree, the role, name and state of each element they can interact with.[^webdev-agents] Google's guide to AI features in Search describes browsing agents the same way: they can visit your site and analyze screenshots, inspect the DOM structure and interpret the accessibility tree.[^google-ai-guide]

Very specific failures follow. A `div` that works as a button thanks to CSS and JavaScript may not be recognized as one; a transparent layer over an element can make the agent discard it; and an add-to-cart button that moves around depending on the category confuses an agent working from screenshots.[^webdev-agents] Before it ever reaches your site, the agent may also have found you through the data you send out: in ChatGPT, product discovery is fed by the [product feeds](/glossary/product-feed/) that merchants share.[^openai-discovery]

## In a store

The shoe assignment, step by step, at a mountain gear store. It is a **fictitious example**: the store, the product and the route are made up to show where each permission is used and who confirms.

| Step (fictitious example)              | Permission used | Who confirms                                  | What it reads from your store                                                 |
| -------------------------------------- | --------------- | --------------------------------------------- | ----------------------------------------------------------------------------- |
| Searches waterproof shoes in size 10   | Research        | Nobody                                        | Your feed and your product pages: waterproofing, sizes, price                 |
| Compares three product pages           | Research        | Nobody                                        | Price, stock by size, delivery time and shipping cost                         |
| Watches the price of the one it picked | Research        | The person set the budget at the start        | The [product page](/glossary/product-page/)'s price, every time it comes back |
| Adds size 10 to the cart               | Prepare         | Depending on the system, nobody or the person | The size selector and the add button, as recognizable elements                |
| Pays                                   | Pay             | The person, or a mandate signed beforehand    | The total, the shipping and the terms your checkout shows                     |


The column that says the most is the third: **at three of the five steps nobody confirms**, and at those steps the agent decides alone with whatever your store lets it read. If the waterproofing is only in a photo, or the sold-out size 10 still shows as available, the error happens before any person looks.


**Believing that a shopping agent pays without anyone seeing it.** In the published systems, the person confirms the order, the shipping and the payment before anything is charged: that is how OpenAI describes it for Instant Checkout and Google for its agentic checkout.[^openai-buy][^google-agentic-checkout] The case with no person in front exists in AP2, but with a mandate signed beforehand that sets price and time limits.[^ap2] What does happen with nobody watching is everything before that: searching, comparing and ruling out your product.


## How to check it

1. **Open a product page in Chrome DevTools and look at its accessibility tree.** There you see what an agent recognizes as a button, link or field, and under what name.[^webdev-agents]
2. **Review the purchase elements**: the variant selector, the add-to-cart button and the shipping form fields have to be `button` or `a` elements, or fields with their `label`, not a styled `div`.[^webdev-agents]
3. **Check that the add-to-cart button is in the same place** on product pages in different categories.[^webdev-agents]
4. **Run the assignment yourself with ChatGPT agent** in your own store, up to the step before paying, and note where it stops to ask for confirmation or for control of the browser.[^openai-agent]
5. **Compare what the agent says about your product with your published product page**: price, available size and the attribute that decided the choice. If they do not match, the fault is in what reaches it from your store.

## Related concept: AI agent

An AI agent is any system that decides its own steps and uses tools to complete a task; the shopping agent is one with a specific role, **that of the customer**. The difference matters because it changes which side it is on. An agent your store installs to serve or recommend works for you and knows your catalog from the inside; a shopping agent arrives from outside, compares your product page with those of other stores and answers to whoever gave it the assignment. Both use the same technology, but only the second can rule you out. And the setting it moves in is [agentic commerce](/glossary/agentic-commerce/), with [agentic checkout](/glossary/agentic-checkout/) as its last step.

To go further, the [agentic commerce reading path](/learn/agentic-commerce/) orders the protocols a shopping agent uses to talk to a store.