AI Commerce WatchTracking the agents that shop

Sep 15, 2026 - AI Commerce Watch

When AI Agents Start Buying: What Agentic Checkout Means for Your Store

The next bot that checks out on your store may have a human's credit card and permission behind it. Agentic commerce - AI assistants executing purchases for users - is early, funded, and incompatible with how most storefronts distinguish friend from bot.

The collision course

Storefront defenses are built to stop automation. Agentic shoppers ARE automation - legitimate, revenue-carrying automation that looks, to a naive bot filter, exactly like the enemy. Merchants face a fork: block agent traffic and lose a growing sales channel, or allow automation and reopen the door to hostile bots wearing an agent's clothes.

What breaks first

Bot policy. 'Block automation' stops working as a default; the question becomes which automation, verified how. Attribution. When an agent researches and buys in one machine-speed session, the marketing journey compresses to a point - last-click will credit 'direct' or the agent's referer, neither of which describes how the sale was won. Fraud screening. Velocity and behavior rules tuned for humans will false-positive on agents, and rules relaxed for agents will be exploited by bots imitating them.

What to do now

Merchants do not need an agent strategy deck; they need three practical capabilities. Visibility: detect and separately report agent-class traffic rather than lumping it with human or hostile traffic. Identity: support emerging agent-authentication standards as they stabilize, so good agents can prove themselves. Terms: decide what agents may do on your storefront - browse, cart, checkout - and enforce at the edge, where policy can keep pace with machine speed.

The takeaway

The stores that win agentic commerce will be the ones that can tell three kinds of automation apart in real time: hostile bots, beneficial crawlers, and paying agents. That is a detection problem first and a strategy problem second.

AI Size Finders That Recommend the Wrong Size

A size finder that recommends from the wrong data sends the customer the wrong size with confidence. The return costs the store more than the sale was worth.

A customer enters her height, weight, and usual size into an AI size finder. It recommends a medium. She orders the medium, it arrives too tight across the shoulders, and she returns it. The finder was not wrong about her measurements. It was wrong about the garment, because it had never seen this brand's actual fit data, and it recommended from generic sizing tables instead.

Size finders fail quietly. The customer blames her body, or the brand, and the store eats a return that cost more than the margin on the item. The fix is data the store already has, if it is willing to use it.

Where the recommendation comes from

Most AI size finders work from one of two sources: the brand's own return and fit data, or generic size tables. The generic tables are the problem. A medium in one brand is a large in another, and a finder that has never seen this brand's garments cannot know that. It recommends the average, and the average is wrong for the customer who needed the tool in the first place.

The second problem is the input. Height, weight, and a usual size are weak predictors of fit across the shoulders or the waist. A finder that does not ask about fit preference, loose or fitted, or about the specific garment's cut, is guessing from the weakest signals available, and presenting the guess as a recommendation.

What good fit data looks like

The stores that get size finders right feed them their own data: the measurements of the actual garment, not the size chart, and the return reasons for that style. A style with a high return rate for tight shoulders needs a recommendation that sizes up for broad-shouldered customers, and only the return data says that.

The honest finder also shows its working. A recommendation that says medium, with a note that customers with your measurements usually keep the large in this style, is more useful than a bare medium. The customer can decide, and the store has shared the uncertainty instead of hiding it behind a confident label.

Measuring whether it works

The metric is the return rate for size reasons on orders that used the finder, compared with orders that did not. If the finder is working, the rate should be lower. If it is the same or higher, the finder is not helping, and it is probably hurting, because customers who trusted it and got the wrong size are less likely to reorder than customers who guessed.

Run the comparison by style, not in aggregate. A finder can be right on t-shirts and wrong on jackets, and the aggregate hides it. The styles where it fails are the ones where the fit data is thinnest, and those are the styles to fix first, or to exclude from the finder until the data exists.

Related reading: Glossary, About, AI Review Summaries That Contradict the Reviews Underneath Them.

Frequently asked questions

Why do AI size finders recommend the wrong size?

Most work from generic size tables, not the brand's own garment measurements and return data. A medium varies between brands, so a finder that has never seen this brand's fit data recommends the average, which is wrong for the customer who needed help.

What data makes a size finder work?

The measurements of the actual garment, not the size chart, and the return reasons for that style. A style with high returns for tight shoulders needs a recommendation that sizes up for broad-shouldered customers, and only return data reveals that.

How do I know if my size finder is helping?

Compare the return rate for size reasons on orders that used the finder against orders that did not, style by style. If the finder rate is not lower, the finder is not helping, and customers who trusted it are less likely to reorder.

Should a size finder show its reasoning?

Yes. A recommendation with a note, such as customers with your measurements usually keep the large in this style, lets the customer decide. A bare size label hides the uncertainty behind a confident guess.

Frequently asked questions

What is agentic checkout?

A purchase completed by an AI agent acting for a shopper: the agent finds the product, applies the shoppers preferences and payment details, and checks out, with the human setting the task rather than clicking through each step.

What should a store check first about agent purchases?

How its products appear to agents: whether catalogue data, prices, stock, and terms are machine readable and current. Agents buy from the data they can read, and stale or hidden data means being skipped or misrepresented.

Who is responsible when an agent buys the wrong thing?

That depends on the stores terms and the agents mandate, which is why both need writing down before disputes. Stores that define how agent orders are treated avoid absorbing every ambiguity personally.

Will agent checkout replace normal checkout?

Not wholesale. It suits repeat, well specified purchases first. Stores should expect a growing share of orders arriving through agents alongside ordinary shoppers, and design product data for both.